agentleFS
Sign inStart free
markmhendricksonmarkmhendrickson/neotoma/.claude/skills/create-prototype/SKILL.md

create-prototype

Skill38 starsChanged 2 months agoMITView on GitHub

Create Prototype

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 19
  2. Very specific:

    Follow foundation/development/feature_unit_workflow.md Step 1 (Prototype Creation).

    line 21
  3. Distinctive:

    No UI changes required (skip prototype)

    line 30
  4. Very specific:

    Read foundation-config.yaml to get feature unit settings

    line 35
  5. Distinctive:

    Verify UX Requirements section exists in spec (from Checkpoint 0)

    line 44
  6. Distinctive:

    If no UI changes → skip to implementation

    line 45
  7. Distinctive:

    If UI changes present → proceed

    line 46
  8. Very specific:

    Use configured prototype directory structure (or default: frontend/src/prototype/)

    line 49
  9. Very specific:

    Create prototype component(s): {prototype_dir}/components/{{input:feature_id}}_*.tsx

    line 50
  10. Very specific:

    Create mock API fixtures: {prototype_dir}/fixtures/{{input:feature_id}}_*.ts

    line 51
  11. Distinctive:

    All API calls mocked (no real backend)

    line 56
  12. Distinctive:

    All UI states testable (empty, error, loading, success)

    line 57
  13. Very specific:

    Ensure prototype can be run (e.g., npm run dev:prototype)

    line 63
  14. Distinctive:

    Document how to run prototype

    line 64
  15. Distinctive:

    STOP and proceed to Checkpoint 1 (Prototype Review)

    line 70
  16. Distinctive:

    Update prototype based on feedback

    line 86
  17. Very specific:

    Document approval in spec: Prototype Approved: YYYY-MM-DD

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Source: foundation/.cursor/skills/create-prototype/SKILL.md -->

name: create-prototype description: Create prototype per foundation command. triggers:

  • create prototype
  • /create_prototype
  • create-prototype

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
  7. Output:
    • Prototype location and run command
    • Summary of what prototype demonstrates
    • List of mocked APIs
    • STOP and proceed to Checkpoint 1 (Prototype Review)

User Review Prompt

Present:

  • Prototype location
  • How to run: [command]
  • Summary of prototype features

Ask:

  • "Please review the prototype at [location]. Run with [command]."
  • "Does the prototype meet your requirements? (yes/no)"
  • "Any changes needed? (list changes or 'none')"

If User Requests Changes

  • Update prototype based on feedback
  • Re-run prototype creation
  • Repeat until approved

If Approved

  • Document approval in spec: **Prototype Approved:** YYYY-MM-DD
  • Proceed to implementation (use Run Feature Workflow)

Inputs

  • feature_id (string): The feature identifier

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free