prototype
Build and iterate on disposable prototypes for design or behavior questions, preserving the chosen reference for a clean implementation handoff.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- prototype
- metadata
- { "author": "Brenden Bishop", "attribution": "../../ATTRIBUTION.md" }
- description
- Build and iterate on disposable prototypes for design or behavior questions, preserving the chosen reference for a clean implementation handoff.
- disable-model-invocation
- true
02 资源文件 5
- 参考文档agents/openai.yaml43 B
- 参考文档references/logic.md976 B
- 参考文档references/ui.md1.2 KB
- 参考文档REVIEW.md5.4 KB
- 参考文档WORKFLOW.md4.7 KB
03 SKILL.md 正文
Prototype
Read and follow the approved prototype workflow. It owns framing, construction, verification, iteration, selection, and cleanup. Load only its applicable UI or logic guide.
Use decision authority for the caller's scope and who selects the result. Use workspace access for a persistent session directory at artifacts/prototypes/<session>/ beneath the owning private workspace. An isolated application worktree may hold runnable code; keep its path and launch instructions with that session.
When a planning question called this workflow, return its accepted answer and usable artifact references to Wayfinder. Do not silently resolve the question or create an ADR because a variant was preferred.
Before authorized production implementation, prepare a handoff and transfer to a fresh context running implement. Preserve the selected target until the receiver has the needed reference and reusable pieces. If the host cannot launch that context, leave a usable handoff and report the needed launch step. Never substitute an in-place continuation for an explicitly required unattended fresh-session transfer.
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.