to-design

to-design is a skill for Claude Code from smallnest/pigo. It costs 96 tokens per session (3,535 once invoked), scanned A, original, MIT.

A design document made from a PRD, or product requirements document, explaining how a software change could be built and why that approach was chosen. It follows the structure of official Go design proposals.

In plain words
What is it for?
Use it when a team needs to agree on the approach for a risky, breaking, or difficult-to-reverse change. It is for deciding how to build something, not for defining an exact implementation contract.
Why use it?
It makes tradeoffs, alternatives, compatibility concerns, and implementation decisions clear before coding begins.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/smallnest/pigo/to-design
Any agent
npx skills add smallnest/pigo --skill to-design
Clone the repo
git clone --depth 1 https://github.com/smallnest/pigo

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for to-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/smallnest/pigo/to-design.svg)](https://agentmods.dev/skills/smallnest/pigo/to-design)
Your own site
<a href="https://agentmods.dev/skills/smallnest/pigo/to-design"><img src="https://agentmods.dev/badge/skills/smallnest/pigo/to-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,535 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00096 $0.03535
Opus 5 $0.00048 $0.01767
Sonnet 5 $0.00019 $0.00707
Haiku 4.5 $0.00010 $0.00353

Measured 6d ago against content hash e6819c049a64, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

to-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • to-design — 100% identical, 0 lines differ
internal/builtinskills/skills/to-design/SKILL.md · 282 lines

How it starts

The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.

to-design — PRD to Design Document

Turn a PRD (or a rough idea) into a design document written in the style of Go's official design proposals: plain language, concrete examples, and—above all—an honest account of why this approach and not the alternatives.

This is not the same as prd-to-spec. A SPEC is an implementation contract (tables, endpoints, schemas) for an engineer to build against. A design document is a decision artifact: it argues for an approach, surfaces the tradeoffs, and lets a team agree on the same facts before anyone writes code. When the question is "how should we build this and why", produce a design doc; when the question is "give me the exact contract to implement", produce a SPEC.

设计哲学源自对 5 篇 Go 官方 proposal(泛型 / 错误包装 / loopvar / slog / try)的分析。核心信念:文档的价值不取决于方案是否通过,而取决于它是否让讨论建立在同一套事实和取舍之上。


When to Use

  • A PRD exists and you need to decide how to build it before committing to implementation
  • The approach has real tradeoffs and you want them documented and debated
  • The change is risky, breaking, or hard to reverse (a design doc forces the compatibility conversation early)
  • Multiple people need to agree on a direction before work fans out
  • You want a durable record of "why we chose X and rejected Y" — even if the proposal is later rejected

If the team just needs the concrete contract to code against, use /prd-to-spec instead (or run to-design first, then prd-to-spec).


The Job

  1. Locate input — find or receive the PRD (or idea)
  2. Analyze context (optional) — scan the codebase for existing patterns, constraints, and prior art
  3. Surface the decisions — identify the real design forks and ask clarifying questions (max 3-5)
  4. Generate the design doc — following the structure and writing style below
  5. Review — present for feedback, especially on the Rationale and Compatibility sections
  6. Save — write to the agreed location

Step 1: Locate Input

Provide the PRD (or idea) to design from:

A. File path (e.g., tasks/prd-priority-system.md)
B. GitHub Issue URL
C. Paste content directly
D. Just describe the idea — I'll design from the conversation

Read the full file on GitHub · 282 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 282 lines · 96 tokens per session scan A e6819c049a64

Subscribe to this mod's changes

to-design is a skill published in the GitHub repository smallnest/pigo (424 stars, last pushed 6d ago), licensed MIT. It adds 96 tokens to every session and 3,535 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

write-swift

How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know…

wangmiaozero/pi-harness · 107 tokens

emil-design-eng

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

wangmiaozero/pi-harness · 35 tokens

apple-design

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading)…

wangmiaozero/pi-harness · 80 tokens

animate-expo

Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…

wangmiaozero/pi-harness · 112 tokens

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

wangmiaozero/pi-harness · 22 tokens

wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

wangmiaozero/pi-harness · 46 tokens