component-spec

component-spec is a skill for Claude Code from Infrasity-Labs/dev-gtm-claude-skills. It costs 22 tokens per session (265 once invoked), scanned A, original, MIT.

A written blueprint for a reusable interface component, covering its options, behavior, visual states, and accessibility needs.

In plain words
What is it for?
It helps document buttons, forms, navigation elements, and other design-system components before or during implementation.
Why use it?
It gives designers and developers a shared reference so components behave consistently and edge cases are not overlooked.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the marketing-skills plugin — 116 skills, 8 commands, 23 agents, 1 hook shipped together , and of writing-skills

Good fit It helps document buttons, forms, navigation elements, and other design-system components before or during implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/infrasity-labs/dev-gtm-claude-skills/component-spec
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.

Any agent
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill component-spec
Clone the repo
git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 116 skills, 8 commands, 23 agents, 1 hook.

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 component-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/component-spec/github.svg)](https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/component-spec)
Your own site
<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/component-spec"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/component-spec/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 component-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/component-spec"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/component-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 265 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.00022 $0.00265
Opus 5 $0.00011 $0.00133
Sonnet 5 $0.00004 $0.00053
Haiku 4.5 $0.00002 $0.00026

Measured 8d ago against content hash af81fec406a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

component-spec 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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/component-spec/SKILL.md · 24 lines

What it actually says

Component Spec

You are an expert in writing thorough, implementable component specifications for design systems.

What You Do

You create complete component specs covering anatomy, behavior, variants, states, accessibility, and usage.

Specification Structure

  1. Overview — Name, description, when to use / not use
  2. Anatomy — Visual breakdown, required vs optional elements
  3. Variants — Size (sm/md/lg), style (primary/secondary/ghost), layout
  4. Props/API — Name, type, default, description, required status
  5. States — Default, hover, focus, active, disabled, loading, error
  6. Behavior — Interactions, animations, responsive behavior, edge cases
  7. Accessibility — ARIA roles, keyboard nav, screen reader, focus management
  8. Usage Guidelines — Do/don't examples, content rules, related components

Best Practices

  • Write for both designers and developers
  • Include examples for every variant and state
  • Specify behavior, not just appearance
  • Consider all input methods
  • Document edge cases explicitly
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. 8d ago First seen · 24 lines · 22 tokens per session scan A af81fec406a7

Subscribe to this mod's changes

component-spec is a skill published in the GitHub repository Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 265 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

wcag-accessibility

Use when building UI components, reviewing color contrast, adding ARIA attributes, handling keyboard navigation, writing alt text, creating forms, or ensuring WCAG 2.2 AA compliance. Covers color contrast ratios, semantic HTML, focus management, screen reader support, motion preferences, and accessibility auditing.

LeahyCC/claude-skills · 64 tokens

accessibility

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

addyosmani/web-quality-skills · 51 tokens

information-architecture

Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system…

rampstackco/claude-skills · 131 tokens

frontend

Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.

code-yeongyu/oh-my-openagent · 49 tokens

shiny-bslib-theming

Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bstheme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection…

posit-dev/skills · 87 tokens

tastemaker

Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble…

codeswithroh/tastemaker · 202 tokens