build-prototype

build-prototype is a skill for Claude Code from samkawsarani/sams-product-plugins. It costs 72 tokens per session (1,460 once invoked), scanned A, original, MIT.

A workflow for building working React and TypeScript prototypes from product requirements, briefs, or user stories. It uses Shadcn/ui, a collection of ready-made interface components.

In plain words
What is it for?
Extracting requirements, setting up a prototype project, implementing key screens and interactions, and testing the result against the brief.
Why use it?
It turns an idea into a testable demo, helping teams check user flows and feasibility before building the finished product.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the build-prototype plugin — 1 skill shipped together

Good fit Extracting requirements, setting up a prototype project, implementing key screens and interactions, and testing the result against the brief.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/samkawsarani/sams-product-plugins/build-prototype
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 samkawsarani/sams-product-plugins --skill build-prototype
Clone the repo
git clone --depth 1 https://github.com/samkawsarani/sams-product-plugins

Made for: Claude Code.

Or install build-prototype, the plugin that ships this one along with the rest of its 1 skill.

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 build-prototype

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/build-prototype"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/build-prototype.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,460 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.00072 $0.01460
Opus 5 $0.00036 $0.00730
Sonnet 5 $0.00014 $0.00292
Haiku 4.5 $0.00007 $0.00146

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

Security

Grade A, and why

build-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 8d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/extract_requirements.py, scripts/init_prototype.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/build-prototype/skills/build-prototype/SKILL.md · 221 lines

How it starts

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

Dependency Check

Run command -v python3 node npm npx — if any are missing, tell the user which tools are required. python3: brew install python or brew install uv && uv python install. node/npm/npx: brew install node (all three included). Stop if any are missing.


Prototype Builder

Create functional code prototypes from product requirements to validate concepts and demonstrate feasibility.

Quick Start

From a PRD or Brief

  1. Read the PRD/brief to understand requirements
  2. Extract requirements: python scripts/extract_requirements.py path/to/prd.md
  3. Initialize project: python scripts/init_prototype.py <project-name>
  4. Build prototype based on identified components and flows
  5. Test and validate against requirements

From User Stories

  1. Parse user stories to identify key flows and components
  2. Extract requirements (manually identify UI needs)
  3. Initialize project and implement core flows

Workflow

1. Understand Requirements

Read the source document (PRD, brief, or user stories):

  • Identify core features and user flows
  • Note technical constraints
  • Understand success criteria

Extract UI components:

python scripts/extract_requirements.py path/to/prd.md

This analyzes the document and suggests:

  • Shadcn components to install
  • User interactions to implement
  • Data requirements
  • Key features

2. Initialize Project

Create new prototype:

python scripts/init_prototype.py <project-name>
cd <project-name>
npm install

This creates a complete React + TypeScript + Vite + Shadcn/ui project.

Install required components:

# Install components identified in step 1
npx shadcn@latest add button card input dialog table
# etc.

3. Build Core Features

Focus on essential flows - not production-ready implementation:

  • Implement key user journeys
  • Use Shadcn components for all UI
  • Keep business logic simple but functional
  • Add basic error handling

Reference patterns:

  • See references/ui-patterns.md for common layouts
  • See references/shadcn-components.md for component usage

Read the full file on GitHub · 221 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 221 lines · 72 tokens per session scan A 985f25589f89

Subscribe to this mod's changes

build-prototype is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,460 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

frontend-ui-dark-ts

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.

microsoft/skills · 48 tokens

cobejs

Use when adding a lightweight interactive globe with cobe (canvas setup, markers, interaction, performance, integration with React/Next.js).

MengTo/Skills · 31 tokens

stitch::react-components

Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.

google-labs-code/stitch-skills · 43 tokens

seed-design

An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.

daangn/seed-design · 33 tokens

ss-studio

Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…

bitjaru/styleseed · 75 tokens