prototype

prototype is a skill for Claude Code from bromso/metapowers. It costs 48 tokens per session (724 once invoked), scanned A, original, MIT.

A Figma building step that creates a component with the variations and interaction states defined in its specification, using the chosen design approach and shared design values. A prototype here is a visual version on the Figma canvas, not necessarily working software.

In plain words
What is it for?
Use it after defining and exploring a component to draw its variants and states in Figma.
Why use it?
It turns an agreed design direction and written requirements into a concrete Figma component that can be reviewed.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the design plugin — 8 skills, 1 MCP server shipped together

Good fit Use it after defining and exploring a component to draw its variants and states in Figma.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add bromso/metapowers
Claude Code
/plugin install design

Made for: Claude Code.

Or install design, the plugin that ships this one along with the rest of its 8 skills, 1 MCP server.

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 prototype

README.md
[![agentmods](https://agentmods.dev/badge/skills/bromso/metapowers/prototype/github.svg)](https://agentmods.dev/skills/bromso/metapowers/prototype)
Your own site
<a href="https://agentmods.dev/skills/bromso/metapowers/prototype"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/prototype/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 prototype

Your own site · 80×15
<a href="https://agentmods.dev/skills/bromso/metapowers/prototype"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/prototype.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 724 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.00048 $0.00724
Opus 5.5 $0.00019 $0.00290
Sonnet 5.5 $0.00010 $0.00145
Haiku 4.5 $0.00005 $0.00072

Measured 3d ago against content hash ce86146b7796, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

prototype 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 3d 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.

plugins/design/skills/prototype/SKILL.md · 58 lines

How it starts

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

Prototype

Build "$ARGUMENTS" in Figma as a component with all variants and states specified in the component contract.

Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/design/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.

Prerequisites

Read .metapowers/design/<project>/02-define.md (required — hard gate enforced by hook). Read .metapowers/design/<project>/03-ideate.md. If this file does not exist, tell the user:

Phase 3 (Ideate) has not been completed for "". Run /design:ideate <project> first, or use --skip-checks to bypass.

Process

  1. Read context files:

    • Read .metapowers/design/<project>/02-define.md for the component contract (props, variants, states, tokens)
    • Read .metapowers/design/<project>/03-ideate.md for the chosen design approach (if exists)
    • Read ${CLAUDE_PLUGIN_ROOT}/shared/component-contract-template.md for reference
  2. Read the design system via MCP tools:

    • Call figma_get_variables to get current token values for fills, spacing, typography
    • Call figma_get_design_system_summary to understand the system structure
  3. Build the base component:

    • Call figma_create_component with the component name and base dimensions
    • Call figma_set_auto_layout to establish layout structure
    • Call figma_create_text for text elements
    • Call figma_create_shape for visual elements
    • Call figma_apply_styles to apply token-based fills, strokes, and effects
  4. Build variant components for each variant dimension:

    • Create a component for each variant value
    • Call figma_arrange_component_set to combine as a variant set

Read the full file on GitHub · 58 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. 3d ago First seen · 58 lines · 48 tokens per session scan A ce86146b7796

Subscribe to this mod's changes

prototype is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 724 once invoked, about $0.0002 per session on Opus 5.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-10-21.

Related

Other skills, from other repositories