acss-kit-component-author

What problem does it solve?

It solves the maintenance bottleneck of adding a new accessible component by standardizing how the maintainer documents the component’s verified contract and placeholders before implementation.

Core Features & Use Cases

• Scaffolds the canonical documentation skeleton for a new acss-kit component reference, including verification and divergence notes.
• Validates maintainer inputs by enforcing lowercase kebab-case and refusing to overwrite an existing component directory.
• Captures upstream alignment details by asking for the fpkit version reference and whether behavior diverges from upstream before files are generated.

Quick Start

Run the command from the maintainer workflow: send /acss-kit-component-author <component-name> (for example, /acss-kit-component-author tabs) to create the component-<component-name> skill directory and reference.md skeleton.