write-react-component-design

Explicitly request a design record for a specific component, optionally providing a path. The Skill reads nearby records, React code, tests, and package metadata, then writes a few paragraphs covering the component boundary and rationale that code cannot explain.

It should state the component boundary and only the rationale or constraints that code and tests cannot explain. Topics like ownership, anatomy, props, context, rendering, CSS APIs, opt-outs, exports, or bundle cost are covered only when they explain the decision.

Request one only when you explicitly need documented rationale for a React component decision. The Skill requires an explicit request and will not generate records proactively or add companion records without a separate request.

No. The record links to source files instead of copying inventories or mechanics, and includes alternatives or consequences only when material. It stays limited to a few paragraphs of non-inferable rationale.

Records are intentionally compact and exclude HTML contracts or companion records unless separately requested. They document decisions, not full API references, so they are not a substitute for generated API documentation.