webkit: Skill for Claude Code

.claude/skills/spec-create/SKILL.md

spec-create is a skill for Claude Code from aziontech/webkit. It costs 0 tokens per session (1,678 once invoked), scanned A, original, MIT.

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

In plain words
What is it for?
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.
Why use it?
It turns design requirements and user decisions into a documented specification that can be checked before implementation, without writing component code.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is aziontech/webkit's own configuration. It tells Claude Code how to work on webkit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything webkit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aziontech/webkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/aziontech/webkit/main/.claude/skills/spec-create/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for spec-create

README.md
[![agentmods](https://agentmods.dev/badge/skills/aziontech/webkit/spec-create/github.svg)](https://agentmods.dev/skills/aziontech/webkit/spec-create)
Your own site
<a href="https://agentmods.dev/skills/aziontech/webkit/spec-create"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/spec-create/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for spec-create

Your own site · 80×15
<a href="https://agentmods.dev/skills/aziontech/webkit/spec-create"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/spec-create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01678
Opus 5.5 $0.00000 $0.00671
Sonnet 5.5 $0.00000 $0.00336
Haiku 4.5 $0.00000 $0.00168

Measured 2mo ago against content hash 9fc211e8b9c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo ago.

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

  1. 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.
  2. 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).
  3. Structure decision. Call structure-decide with the regions/answers. Default to monolithic when in doubt.
  4. Write the spec. Copy .specs/_template.md to .specs/<name>.md, fill every section, frontmatter status: draft, created/last_updated = today, no checksum.
  5. 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.

  1. 2mo ago 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 (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,678 tokens. 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.

Related

Other skills, from other repositories

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

data-dashboard

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data…

plugin87/ux-ui-agent-skills · 113 tokens

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 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