agentsclimarketplace
Sign in

Prototype build

Skill neumie/almanac/skills/other/prototype-build

Use when building throwaway logic or UI prototypes to answer design questions before production implementation; terminal state app or UI variants.From its SKILL.md

Install
npx -y skills add neumie/almanac --skill prototype-build

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 363 tokens by cl100k_base, as published. Nobody here has run it

Prototype Build

A prototype is throwaway code that answers a question. The question decides the shape.

Pick A Branch

Identify the question from the prompt, nearby code, or by asking if the user is around:

  • Logic / state model question: read ~/.claude/skills/almanac/prototype-build/references/logic.md. Build a tiny interactive terminal app that pushes state through hard cases.
  • UI shape question: read ~/.claude/skills/almanac/prototype-build/references/ui.md. Generate several radically different UI variants switchable from one route.

If ambiguous and user is unavailable, default to the branch matching surrounding code: backend module means logic; page/component means UI. State the assumption at the top of the prototype.

Rules

  1. Throwaway from day one. Place code near where it informs real work, but name it so readers know it is a prototype.
  2. One command to run. Use the project's existing task runner. Do not add a package manager or runtime just for the prototype.
  3. No persistence by default. State lives in memory unless persistence is the question.
  4. Skip polish. No tests, no broad error handling, no abstractions beyond what makes it runnable.
  5. Surface state. After every logic action or UI variant switch, show the relevant state.
  6. Delete or absorb when done. Keep the decision, not the prototype shell. Do not preserve a prototype-only branch.

When Done

Capture the answer somewhere durable: commit message, ADR, issue, or NOTES.md beside the prototype. Include the question it answered. Then delete the prototype or fold the validated part into real code.

What ships with it: 2 files

4.4 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,499. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.