foundation: Skill for Cursor

.cursor/skills/create-prototype/SKILL.md

create-prototype is a skill for Cursor from markmhendrickson/foundation. It costs 10 tokens per session (693 once invoked), scanned A, a copy of create-prototype, MIT.

A workflow for building a working browser-based prototype from a feature specification. It uses simulated APIs, so the interface can be tried before the real backend is connected.

In plain words
What is it for?
Use it to create client-side prototypes, read the project's feature settings, and implement the interface described in a feature specification. It uses the feature's manifest and prototype directory.
Why use it?
It gives a concrete, interactive version of a feature after its specification is complete. It skips prototype work when the feature does not include interface changes.

Skill for Cursor

Written for Cursor: installed under .cursor/.

This is markmhendrickson/foundation's own configuration. It tells Cursor how to work on foundation 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 foundation configures →

Reuse

Borrowing it

Nothing to install: this file belongs to markmhendrickson/foundation. 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/markmhendrickson/foundation/main/.cursor/skills/create-prototype/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/foundation

Made for: Cursor.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/markmhendrickson/foundation/create-prototype"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/create-prototype.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 693 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 95% copy Near-identical to another mod 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.00010 $0.00693
Opus 5.5 $0.00004 $0.00277
Sonnet 5.5 $0.00002 $0.00139
Haiku 4.5 $0.00001 $0.00069

Measured 1mo ago against content hash 8fb4e8262bbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-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 1mo 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

This is a copy

95% identical to create-prototype — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/skills/create-prototype/SKILL.md · 92 lines

How it starts

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

Create Prototype

Create fully functional client-side prototype for Feature Unit {{input:feature_id}}.

Follow foundation/development/feature_unit_workflow.md Step 1 (Prototype Creation). Configuration is read from foundation-config.yaml.

This happens after Checkpoint 0 (spec creation) and before Checkpoint 1 (prototype review).

Implements prototype creation after Checkpoint 0 (spec) is complete. Creates a fully interactive, client-side prototype with mocked APIs.

Trigger

  • Spec created with UI requirements (Checkpoint 0 complete, UI changes present) OR
  • No UI changes required (skip prototype)

Tasks

  1. Load configuration:

    • Read foundation-config.yaml to get feature unit settings
    • Determine directory structure and prototype paths
  2. Load spec and manifest:

    • {configured_directory}/in_progress/{{input:feature_id}}/{{input:feature_id}}_spec.md (or completed/ if completed)
    • {configured_directory}/in_progress/{{input:feature_id}}/manifest.yaml (or completed/ if completed)
  3. Check if UI changes present:

    • Review spec and manifest for UI components
    • Verify UX Requirements section exists in spec (from Checkpoint 0)
    • If no UI changes → skip to implementation
    • If UI changes present → proceed
  4. Create prototype:

    • Use configured prototype directory structure (or default: frontend/src/prototype/)
    • Create prototype component(s): {prototype_dir}/components/{{input:feature_id}}_*.tsx
    • Create mock API fixtures: {prototype_dir}/fixtures/{{input:feature_id}}_*.ts
    • Integrate into prototype main file
  5. Prototype requirements:

    • Fully interactive (click, type, navigate)
    • All API calls mocked (no real backend)
    • All UI states testable (empty, error, loading, success)
    • Accessible (keyboard nav, ARIA if applicable)
    • Uses existing design system components (if available)
    • Documented mock API responses
  6. Make prototype runnable:

    • Ensure prototype can be run (e.g., npm run dev:prototype)
    • Document how to run prototype

Read the full file on GitHub · 92 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. 1mo ago First seen · 92 lines · 10 tokens per session scan A 8fb4e8262bbe

Subscribe to this mod's changes

create-prototype is a skill published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 693 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to create-prototype, differing in 7 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens