본문으로 건너뛰기
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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neeeophytee/finding-unknowns-skills
설치 방법 보기

포함된 파일(1)

  • SKILL.md1.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

agent-interface-design

무료

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일 업데이트

assumption-test

무료

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일 업데이트

blindspot-pass

무료

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일 업데이트

change-quiz

무료

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일 업데이트

context-audit

무료

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일 업데이트

implementation-notes

무료

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의 스킬 모두 보기

이 스킬의 문제 신고