跳到正文
cccskills
免费在 GitHub 公开

brainstorm-prototypes

Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Brainstorm and prototypes

The user has unknown knowns: criteria they can't verbalize but will recognize on sight. Finding those during prototyping is cheap; finding them mid-implementation is expensive, because small spec changes can mean drastically different code. Give them things to react to.

Steps

  1. Establish scope first: what is being decided (layout? approach? data model? tone?) and what is explicitly out of scope. One decision per round.
  2. Produce 3-5 variations that are wildly different, not shades of the same idea. If two variations would get the same reaction, replace one.
  3. Make them cheap and disposable:
    • Visual/UX → a single self-contained HTML file with fake data, no backend, no state.
    • Approaches → a one-screen sketch of each: the idea, what it optimizes for, its sharpest tradeoff.
    • Ranked lists → order from cheapest to most ambitious so the user can draw their line.
  4. Label each variation with the belief it bets on ("this one assumes density beats whitespace"), so the user's reaction reveals the underlying criterion, not just a preference.
  5. Collect reactions, then verbalize what was learned: "you consistently rejected X, which suggests the real requirement is Y." That sentence is the deliverable — it becomes part of the spec.

Guardrails

  • Nothing produced here is production code. Say so, and don't wire prototypes into the real app.
  • Do not converge early to the variation you'd pick. The point is spanning the space.
  • If the user reacts to none of them, that's signal too: the decision space was framed wrong. Reframe and rerun rather than generating more of the same.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.

中文简介正在准备中。当前显示原文说明。

Neeeophytee/finding-unknowns-skills3532026年9月28日 更新

Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

中文简介正在准备中。当前显示原文说明。

Neeeophytee/finding-unknowns-skills3532026年9月28日 更新

Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."

中文简介正在准备中。当前显示原文说明。

Neeeophytee/finding-unknowns-skills3532026年9月28日 更新

After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.

中文简介正在准备中。当前显示原文说明。

Neeeophytee/finding-unknowns-skills3532026年9月28日 更新

Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.

中文简介正在准备中。当前显示原文说明。

Neeeophytee/finding-unknowns-skills3532026年9月28日 更新

Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.

中文简介正在准备中。当前显示原文说明。

Neeeophytee/finding-unknowns-skills3532026年9月28日 更新

查看 Neeeophytee 的全部技能

报告此技能的问题