design

A product-definition process that combines product requirements, technical decisions, and acceptance tests into one reviewed document.

In plain words
What is it for?
It is for creating a reviewed definition.md with product rules, an architecture position diagram, black-box acceptance criteria, and a core user flow.
Why use it?
It makes important decisions explicit before building, including failure behavior, hard-to-reverse technical choices, and what must count as working.

Skill for Claude CodeCodex

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/wallkop/opc-develop/design
Any agent
npx skills add wallkop/opc-develop --skill design
Clone the repo
git clone --depth 1 https://github.com/wallkop/opc-develop

Made for: Claude Code, Codex.

Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 800 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 $0.00115 $0.00800
Opus 5 $0.00057 $0.00400
Sonnet 5 $0.00023 $0.00160
Haiku 4.5 $0.00012 $0.00080

Measured 2d ago against content hash 13a1be81e9ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

skills/design/SKILL.md · 49 lines

What it actually says

design

PRD / 技术设计 / E2E TestCase 三件套本是同一批决策的三种视角——本环节一次定案为产品定义。 格式与粒度以 docs/harness.zh-CN.md 第 7.5 节为权威,判据只有一条:只写决策,不写实现—— 模型可以自己安全决定或推翻的内容,不进产品定义。

前置

加载 ${CLAUDE_PLUGIN_ROOT}/shared/core-contract.md;已有 brief.md(及 Demo 决策清单,若做过 Demo)。

拷问

以 grilling / grill-me 的方式,按三个维度批量出题,每轮 5-10 个问题,每题附推荐答案与理由:

  • 产品维度 → PD:不可退让的底线是什么?失败 / 空态 / 极端场景下产品该怎么表现? Demo 确认的决策逐条落位,逐条编号。
  • 技术维度 → TD:哪些选择难以回头(供应商、协议、数据所有权、领域边界)? 理由与被排除的备选是什么?可逆的实现细节一律不收录,并写"不收录"反例示范粒度。
  • 测试维度 → AC:从真实用户入口、以黑盒定义"什么算对、什么算不合格" (must / must_not / 超时 / 必需证据),每条 AC 回指一条 PD; 必须恰好指定一条 Core-Case(F0 正向主链路)并声明其 test / production 冒烟投影。

架构位置图(TD 固定首条)

从项目全景架构图裁剪本需求视角的位置图:只许引用全景已有节点名,标色画出触及的层次、 模块与依赖方向。它是升级规则的检测器:

  • 只用到现有节点与现有边 ⇒ 架构未动,画完即决策背景;
  • 出现新节点 / 新依赖边 / 跨领域调用 ⇒ 本需求动了架构,必须同步产出或修订 ADR 与全景标色快照(宏观架构图),产品定义内只留决策一句话加链接。

项目尚无全景图时,先补立项决策(走 harness-init / harness-retrofit); 不允许架构语义只存在于某个 feature 的 definition.md 里。

收口

definition.md(+ 必要的 ADR / 全景快照)交人类 review:确认 → 状态置为已定案,进入 build; 否则按反馈修改再审。定案后每一条都不许模型自行推翻。

产出

已定案的 definition.md(含架构位置图、Core-Case 与冒烟投影声明)。下一步:build

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. 2d ago First seen · 49 lines · 115 tokens per session scan A 13a1be81e9ee

Subscribe to this mod's changes

design is a skill published in the GitHub repository wallkop/opc-develop (11 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 800 once invoked, about $0.0006 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens