Draft a .specs/<name>.md file for a new webkit component.
npx skills add https://github.com/aziontech/webkit --skill spec-create-aziontech
Please help me install this Agent Skill. Skill: spec-create Source: https://github.com/aziontech/webkit/tree/main/.claude/skills/spec-create Command: npx skills add https://github.com/aziontech/webkit --skill spec-create-aziontech
It removes the guesswork and back-and-forth needed to create a new component spec file, ensuring the initial draft is consistent with the repo’s templates and cross-references (like DESIGN and Figma) without writing any component code.
.specs/<name>.md with status: draft, ensuring mandatory sections exist for later approval by spec-validator.Run /spec-create my-new-component --figma <figma-url> to generate a draft spec at .specs/my-new-component.md for review.
High-intent search queries and answers about installing and using this skill.
To create a component spec draft from a Figma design, use the spec-create command with a Figma URL argument to interactively pre-populate token information and map design tokens against DESIGN.md.
Drafting component documentation for Storybook involves interactively collecting component requirements like props, events, and slots, then writing a structured markdown spec file with mandatory sections for later validation.
You cannot overwrite an approved, implemented, or locked component spec file. The spec drafting process enforces kebab-case naming and prevents overwriting existing finalized specs to maintain repository stability.
The best way to document undefined component properties during spec creation is to use TBD placeholders, ensuring all mandatory spec sections are present so the draft remains structurally valid for later approval.
Spec-create writes only component documentation, specifically a .specs/<name>.md file with a draft status. It does not write component code, but instead focuses on requirements, accessibility details, and token mapping.
Component onboarding fails without a spec file because cross-references and templates are missing. Generating an initial draft spec resolves this by aligning component requirements with the repository's taxonomy before code creation.
Owl-ListenerDefine and organize design tokens across color, spacing, typography, elevation, border, and motion.
dceoyGenerate a ready-to-plan specification from a natural-language feature description.
dylantarreSynchronize design tokens between codebases and Figma bidirectionally via API workflows involving Tokens Studio or Variables.
cosmixFix alignment and spacing issues in Markdown tables.