agentleFS
Sign inStart free
rikilamadridrikilamadrid/pathfinder/skills/prototype/SKILL.md

prototype

Skill1 starsChanged 43 days agoMITView on GitHub

Create and iterate the cheapest useful artifact for validating a product, interaction, architecture, or technical assumption.

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, soak-test and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 12 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 14 projects that use this

  • +5 more from lilangMax
  • +3 more from CoralGame

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill after debate recommends validation or when the human asks to see or test a direction before production planning.

    line 8
  2. Distinctive:

    Read the debate conclusion and relevant project context.

    line 12
  3. Distinctive:

    Create only the prototype.

    line 16
  4. Distinctive:

    Do not install a framework solely for a prototype without approval.

    line 32
  5. Distinctive:

    Do not silently promote prototype code into production.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “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

Prototype

Use this skill after debate recommends validation or when the human asks to see or test a direction before production planning.

Process

  1. Read the debate conclusion and relevant project context.
  2. Name the single primary assumption being validated.
  3. Recommend the cheapest useful prototype format.
  4. Define success/rejection criteria and an output location under prototypes/.
  5. Create only the prototype; avoid production architecture unless the task is explicitly a technical proof.
  6. Present focused review questions.
  7. On feedback, revise the same direction, replace it, approve it, or stop.
  8. Record approved direction, rejected assumptions, and explicit production exclusions under ## Durable Decisions in context/project-overview.md, creating the file from templates/project-overview.template.md if it does not exist yet.

Supported Forms

  • wireframe or user-flow diagram
  • static visual concept
  • interactive HTML/CSS/JS
  • prototype using an already-installed project stack
  • API/integration/AI/animation/offline proof of concept
  • architecture or data-flow diagram

Do not install a framework solely for a prototype without approval.

Human Review

Ask:

  • Is the purpose or tested assumption clear?
  • Is the main flow/behavior correct?
  • What should be removed, revised, or replaced?
  • Is the direction approved for specification?

Rules

  • Prototype only what needs validation.
  • Label shortcuts and mocked behavior.
  • Do not silently promote prototype code into production.
  • Iterate rather than generating unrelated alternatives unless replacement is requested.

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