demo

A realistic product preview that uses fake data so people can try an unfinished idea in the real application interface.

In plain words
What is it for?
It is for testing user flows, loading and error states, empty results, and extreme data, then recording which decisions were confirmed, changed, or rejected.
Why use it?
It helps settle unclear product decisions through hands-on feedback before committing to full implementation.

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

Made for: Claude Code, Codex.

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 654 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.00086 $0.00654
Opus 5 $0.00043 $0.00327
Sonnet 5 $0.00017 $0.00131
Haiku 4.5 $0.00009 $0.00065

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

Security

Grade A, and why

demo 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/demo/SKILL.md · 40 lines

What it actually says

demo

捏泥人:数据是假的,手感是真的。Demo 的价值 ∝ 未定产品决策的数量—— 产品行为能用文字无歧义写清就跳过本环节;不要把发现机制变成仪式。

前置

  • 加载 ${CLAUDE_PLUGIN_ROOT}/shared/core-contract.md;必须已有 brief.md
  • Mock 走 Harness 探索面:Port 上的 Fake Adapter、run --mock 一键纯前端闭环 (见 docs/harness.zh-CN.md 第 5 章)。项目还没有该能力时就地搭最薄的假后端, 缺口留给 harness-retrofit,不在本环节建框架。

做法

  1. 纯 vibe-coding:不写测试、不设门禁、不跑验证,速度优先。Demo 落在真实项目前端里 (真组件、真路由、真请求层,只有数据是假的),通过真实应用壳可达——不做孤立 HTML。
  2. 必须支持独立部署/预览:给人一个能打开的 URL 或一条能跑的命令。
  3. Mock 至少可注入延迟、错误、空态、极端数据四类条件——不注入延迟的 Demo, 等于替用户决定了"这个产品没有加载态设计"。体感验收至少过一遍非正常路径。
  4. 体感循环是主体:人随口反馈、随手改,不留记录。只警惕一条边界—— 改变"什么是真的"(人群错了、主流程错了)属于 revise,回 brief.md。

收口(唯一的硬要求)

  1. 待确认决策清单在看 Demo 之前列出(人裁判同样先锁 Oracle); 人逐条给出 确认 / 修改 / 否决——不许一句"感觉不错"。 留痕带上 Mock 配置摘要:0ms 延迟下确认的决策和 300ms 注入下确认的,是两个事实。
  2. 显式决定 Demo 代码哪些保留、哪些重写——不允许默认全部转正。
  3. 确认的产品决策带进 design,成为 PD 的直接来源。

产出

可体验、可独立部署的 Demo + 确认的产品决策清单。下一步:design

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 40 lines · 86 tokens per session scan A 2c926873bf96

Subscribe to this mod's changes

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