agentleFS
Sign inStart free
virtualmasevirtualmase/lifecycle-skills/skills/prototype/SKILL.md

prototype

Skill1 starsChanged 3 months agoMITView on GitHub

Create small, reversible demonstrations that reduce uncertainty before a larger implementation. Use for experience concepts, workflow experiments, content tests, interface proofs, and technical spikes that need a defined hypothesis, safe data boundary, measurement, and handoff decision.

194 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

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 3

    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 to test an important uncertainty before committing to a full build.

    line 8
  2. Distinctive:

    Use synthetic, public, or explicitly authorized data only.

    line 17
  3. Distinctive:

    Do not present a prototype as a live product, gather private data by default, expose secrets, claim performance not observed, bypass …

    line 28

“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 to test an important uncertainty before committing to a full build. A prototype is an instrument of learning, not a production release, safety certification, or substitute for accessibility, security, or operational review.

Intake

Record the question, property, intended participant, decision owner, success measure, maximum scope, data classification, permitted data, rollback path, and review date. If any item is unknown, reduce scope or ask before exposing the prototype.

Workflow

  1. State the uncertainty and the smallest artifact capable of testing it.
  2. Use synthetic, public, or explicitly authorized data only. Make the prototype reversible and separate from production systems.
  3. Define observations before exposing the prototype: task success, confusion signals, accessibility risks, error paths, and exit conditions.
  4. Record what worked, failed, confused participants, or created risk. Distinguish observations from interpretation.
  5. Decide whether to retire, revise, run a follow-up test, or hand off a reviewed specification to Builder.

Deliverable

Provide the prototype, a concise experiment brief, an observation log, a decision recommendation, and a removal or archive plan. State the artifact location, validation limits, accountable owner, and next role.

Boundaries

Do not present a prototype as a live product, gather private data by default, expose secrets, claim performance not observed, bypass accessibility review, or release externally without named approval.

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