An interactive planning skill for writing a Markdown specification for a new web component before coding begins.

Use it to create a component spec from a Figma design or from a component name and category, including its intended behavior and initial draft status.

It turns design requirements and user decisions into a documented specification that can be checked before implementation, without writing component code.

spec-create — Skill by aziontech

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/aziontech/webkit/spec-create

Any agent

npx skills add aziontech/webkit --skill spec-create

Clone the repo

git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code, Codex.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,678 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00051	$0.01678
Opus 5	$0.00026	$0.00839
Sonnet 5	$0.00010	$0.00336
Haiku 4.5	$0.00005	$0.00168

Measured yesterday against content hash 9fc211e8b9c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-create scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/spec-create/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: spec-create

Purpose

Produce a .specs/<name>.md that is complete enough for spec-validator to flip to status: approved. The user runs /spec-create <name> (optionally with --figma <url>); this skill drives the interaction.

When to invoke

The slash command /spec-create was used.
The user said "I need a new component" / "criar componente" but there is no .specs/<name>.md yet, and /component-create was about to fail because of that.

Inputs & mode

<name> (kebab-case) — required in Mode B; optional in Mode A. In Mode A (Figma), when <name> is omitted the name is derived from the frame's component name (normalized to kebab) and confirmed with the user; a passed <name> overrides the frame. See Name resolution in the Mode A section.
The mode is chosen by input:
- Mode A — Figma-driven: --figma <url> is present. The frame is the source of truth.
- Mode B — Name + Category: no --figma. The user is building without a design; --category <name> is required (ask + confirm if missing). This mode is more blocking — see below.

Confirm the mode with the user before drafting. If it's ambiguous which one they want, ask.

Workflow — shared steps

Argument parsing & name resolution. Parse the flags. A passed <name> must be kebab-case (reject otherwise) and always wins (explicit override). If <name> is absent: in Mode B reject (no frame to derive from); in Mode A defer — the name is resolved from the frame in Name resolution below, before any file path is computed. Only once the name is known: reject if .specs/<name>.md already exists with status ∈ {approved, implemented, locked} (the user is editing the wrong file) and ask for a different name.
Category. Use the taxonomy in .specs/_template.md frontmatter. State the inferred/received category and ask the user to confirm (mandatory in Mode B — never assume).
Structure decision. Call structure-decide with the regions/answers. Default to monolithic when in doubt.
Write the spec. Copy .specs/_template.md to .specs/<name>.md, fill every section, frontmatter status: draft, created/last_updated = today, no checksum.
Echo. Print the path. Tell the user to review it, then run /component-create <name> (which calls spec-validator) or set status: approved and re-run.

Read the full file on GitHub · 80 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 80 lines · 0 tokens per session scan A 9fc211e8b9c3

Subscribe to this mod's changes

spec-create is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 1,678 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Frontend Planning Writing and docs component-library frontend-platform monorepo ui-architecture workspace

monorepo-management

Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.

soulcodex/agentic · 63 tokens

bazel-monorepo-expert

Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.

kinhluan/rules-quarkus-skills · 43 tokens

pnpm

Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.

pledgeandgrow/pledge-skills · 31 tokens

fast-typescript-check

Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…

internet-development/www-sacred · 84 tokens

port-sacred-terminal-ui-to-typescript-cli

Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.

internet-development/www-sacred · 0 tokens

port-sacred-terminal-ui-to-react-using-same-conventions

Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…