fable-field-guide-skills

Surface the user's unknown unknowns before they start work in an unfamiliar area (new codebase area, domain, or tool). Produces a read-only blindspot briefing plus advice on how to prompt better. Use when the user says "blindspot pass", "盲区扫描", "unknown unknowns", asks what they don't know or might miss before diving in, says "我刚接手这块代码", "开工前帮我看看有什么坑", or merely describes facing unfamiliar territory — the statement is the request. Not for finished or pre-merge work (use change-quiz), nor for interviewing the user (use interview-me); mixed requests start here — brief, then hand off.

Generate one droppable self-contained HTML report (never a Cursor canvas) explaining a change set, ending with a quiz the user must pass before merging. Use when the user says "quiz me", "考考我", "change quiz", "变更测验", or, after a large change or session, wants to verify they truly understand it — e.g. "merge 之前考考我这轮改动", or says "review" meaning their own understanding, not bug-finding. The audience is the user themselves — selling it to reviewers is pitch-explainer; finding bugs is a code review. Not for writing tests or quizzes unrelated to a change set (general knowledge, interview prep).

Generate several deliberately divergent single-file HTML prototypes with fake data so the user can react before real implementation — iterable HTML, not one generated image or a Cursor canvas. Use when the user wants design options or a UI mockup to react to ("mock up a page"), says "design directions", "出几个设计方向", "出几版 UI", "哪种页面风格好", "我说不好想要什么样", or can only judge a design by seeing it; also consider offering directions first when the user asks to build a UI whose look was never discussed. Not for technical feasibility spikes or functional MVPs ("做个原型验证跑不跑得通"), and not for copying one concrete reference as the end state (use reference-hunt); a reference named only as inspiration stays here.

Master index for the fable field-guide family (8 finding-unknowns skills): routes to the right skill and defines the artifact contract they share. Use when the user says "field guide", "which of these skills", "该用哪个 skill", "这套流程怎么用", "finding unknowns 工具怎么选", asks which of these skills applies or how the family fits together, or is stuck and can't say what they need — "不知道从哪下手", "where do I even start", "你都会什么", "装了哪些技能"; also read when unsure which finding-unknowns skill fits the current situation.

Keep a running implementation-notes.md logging decisions, plan deviations, and surprises during implementation. Use PROACTIVELY the moment you start implementing an agreed plan, spec, or decision — the trigger is you beginning the work, not the user's wording: terse approvals ("开搞", "go ahead", "LGTM"), incremental starts ("先做第一步"), resuming across sessions, or starting from a reference-hunt taking list. If you notice mid-implementation it is missing, create it and backfill. Also use when the user says "keep implementation notes", "记录实现笔记". Not for post-hoc summaries of already-finished work.

Write an implementation plan that leads with the decisions the user is most likely to change and buries mechanical work at the bottom. Use when the user says "implementation plan", "实现计划", "开发计划", "落地方案", "先出方案再动手", "先别写代码，想清楚给我看看", asks for an RFC/技术方案 or a pre-work buy-in proposal (立项提案), or wants a reviewable plan after brainstorming. Also read whenever a built-in plan mode is active (Cursor, Claude Code, Codex) — before writing any plan, whether you switched into it or the session started there. Not for trivial changes or resolving open questions (run interview-me first); if a reviewed plan already exists, start with implementation-notes instead.

Interview the user one question at a time to turn ambiguities into explicit decisions before implementation, prioritizing architecture-changing questions. Use when the user says "interview me", "访谈我", "开工前把需求问清楚", "帮我把这个需求里的模糊点理清楚", "ask me clarifying questions" before starting, complains the requirements are too vague to start ("需求太模糊没法干"), or wants pre-task Q&A. Not when the user merely permits questions while working ("有不确定的可以问我", "ask me if unclear") — permission for later is not an interview now. Not for interview practice (面试题) or researching pitfalls (use blindspot-pass; run it first when both apply).

Package the spec, prototype, and implementation notes of finished or nearly-finished work into one self-contained document that gets reviewers to buy in fast. Use when the user says "pitch doc", "提案文档", "打包给评审", "给这轮工作写个提案", "把成果打包成汇报材料", "跟团队讲清楚这次改动", asks for a one-pager or explainer aimed at reviewers or approvers, or needs sign-off from people out of the loop. Not for verifying the user's own understanding (use change-quiz), proposals to green-light work not yet started (use implementation-plan), routine status reports (日报/周报), or neutral knowledge docs — wikis, READMEs, onboarding guides.

Port the semantics of a reference implementation by reading its actual source, not screenshots or docs. Use when the user says "reference hunt", "照着这个实现", "像这个一样", "要做成像 X 那样", "抄作业" while pointing at a concrete product, library, or code, says "find me a reference implementation" or "steal X's logic", asks "how does <product> do that? I want that here" — the question is the trigger — or struggles to articulate a behavior they can recognize. If the user has no reference — or has one but wants several divergent directions to react to — use design-directions (a reference hunt can feed it one direction's semantics). Not for finding documentation or tutorials, and not for merely matching the project's existing code style.