narrative-nonfiction
Use when writing self-help books, memoirs, or prescriptive guides with story elements. Trigger on: 'self-help book', 'transformation arc', 'metaphor consistency', 'reader journey', 'exercise design', or narrative nonfiction projects.
What this skill does
# Narrative Nonfiction Workshop Workflow for self-help and prescriptive nonfiction using narrative elements and metaphors to guide reader transformation. **Core concept:** Prescriptive advice + storytelling. Reader is protagonist on a journey. Book provides map and tools. ## When to Use This skill is for: - ✅ Self-help and prescriptive nonfiction books - ✅ Memoirs with lessons or transformation arcs - ✅ Books using extended metaphors or narrative framing - ✅ Practical guides that include storytelling elements - ✅ Reader journey design (before state → after state) ## When NOT to Use This skill is NOT for: - ❌ Pure fiction (novels, short stories) - use `fiction-workshop` instead - ❌ Academic writing or research papers - different conventions - ❌ Straight journalism or reporting - no transformation arc - ❌ Technical documentation or how-to guides without story elements - ❌ Business books focused purely on data/case studies without reader journey --- ## Stage 1: Foundation Building **Goal:** Establish promise, metaphor system, and transformation arc. ### Initial Questions 1. Target reader? (Demographics + psychographics) 2. Transformation promise? 3. Central metaphor/framing? 4. Reader's "before" and "after" states? 5. Book's unique angle? 6. How much outlined vs. drafted? ### Core Components **Promise:** What reader gains. "This book will help you [transformation] by [method]" **Metaphor:** Central metaphor, how it maps to advice, where it helps/misleads **Reader's Journey:** Entry point (where they start), pain points, resistance, transformation stages, exit point (who they become) **Twist/Reveal** (if applicable): What's revealed, setup needed, how to earn payoff Use `assets/book-blueprint-template.md` if needed. **Exit condition:** Clear grasp of reader, promise, metaphor, arc. --- ## Stage 2: Chapter Development **Goal:** Draft or refine chapters balancing advice, story, and exercises. **Chapter structure:** Hook (story/question) → Setup (why this matters) → Content (teaching) → Evidence (stories/research) → Application (exercises) → Bridge (to next) ### Writing Modes Switch between these as needed: | Mode | Invocation | Focus | |------|------------|-------| | **Voice Editor** | "Check voice consistency..." | Tone, metaphor alignment, author persona | | **Content Editor** | "Evaluate the teaching in..." | Clarity, completeness, accuracy | | **Exercise Designer** | "Design exercises for..." | Practical application, appropriate difficulty | | **Metaphor Consultant** | "Check metaphor consistency..." | Extended metaphor alignment, avoiding confusion | | **Reveal Engineer** | "Set up the reveal..." | Foreshadowing, misdirection, payoff | See `references/` for detailed guidance on each mode. ### Creation Workflow 1. **Purpose Check:** Key takeaway? Where in arc? What must reader believe before next chapter? 2. **Outline Beats:** Hook options, teaching points (2-4), stories/examples, exercises, bridge 3. **Draft:** Write chapter. Use "write like you talk" voice. 4. **Layer Metaphor:** Present but not forced. 5. **Add Exercises:** Use `references/exercise-design.md` 6. **Polish:** Check voice, pacing, reader energy ### Editing Workflow 1. **Read as Target Reader:** Engaged? Understand? Believe I can do this? Overwhelmed or ready? 2. **Diagnose:** Confusion → clarify | Boredom → add story | Resistance → address objections | Overwhelm → simplify 3. **Invoke Mode:** Load relevant reference file 4. **Implement:** Use `str_replace` --- ## Stage 3: Arc Integrity Check **Goal:** Verify book works as complete transformation journey. **Read full outline/manuscript for:** 1. **Promise Delivery:** Book delivers promise? Transformation clear and achievable? 2. **Pacing:** Change speed appropriate? Integration plateaus? Energy builds? 3. **Metaphor:** Maintained throughout? Breaks or contradicts? Still serves at end? 4. **Reveal** (if applicable): Twist earned? Seeds planted? Reframe lands emotionally? 5. **Exercise Progression:** Build on each other? Difficulty matches stage? Variety? ### Common Issues | Symptom | Cause | Fix | |---------|-------|-----| | "Too preachy" | Not enough story/example | Add narrative | | "Too abstract" | Missing concrete advice | Add specific how-to | | "Overwhelming" | Too much per chapter | Narrow focus, add chapters | | "Why should I care?" | Missing pain point connection | Open with reader's struggle | | "I can't do this" | Missing scaffolding | Add smaller steps, examples | --- ## Self-Check: Is This Working? Use these checkpoints to verify you're following the workflow correctly. **After Foundation Building:** - [ ] Can you state the book's promise in one sentence? - [ ] Can you describe the reader's "before" and "after" states clearly? - [ ] Do you understand the central metaphor and how it maps to the advice? - [ ] Can you outline the transformation arc stages without looking at notes? **After drafting a chapter:** - [ ] Does the chapter have all six elements: hook, setup, content, evidence, application, bridge? - [ ] Is the metaphor present but not forced? - [ ] Is the voice consistent with previous chapters? - [ ] Would the target reader understand and believe they can apply this? **After designing an exercise:** - [ ] Does the exercise difficulty match where the reader is in their journey? - [ ] Can the reader complete it with the knowledge they have so far? - [ ] Is it specific enough to be actionable (not "improve your productivity" but "track your time for three days")? - [ ] Does it build on previous exercises? **After invoking a mode:** - [ ] Did you explicitly request "Voice Editor" or "Metaphor Consultant" or specific mode? - [ ] Is the feedback focused on that mode's domain? - [ ] Did you avoid mixing concerns (voice + content + exercises all at once)? **Before claiming "done":** - [ ] Does the full arc deliver on the promise made in chapter 1? - [ ] Is the metaphor consistent throughout (or intentionally evolved)? - [ ] Do exercises progress logically from simple to complex? - [ ] If there's a reveal/twist, are seeds planted in earlier chapters? If you answered "no" to any checkpoint, return to that stage before proceeding. --- ## Common Mistakes | Mistake | Why It Happens | Fix | |---------|---------------|-----| | **Skipping Foundation Building** | "I just want to start writing" | Without clarity on promise, metaphor, and arc, chapters drift. Spend 30 minutes on blueprint—saves hours of rewriting. | | **Forcing the metaphor** | Trying to make every sentence fit the frame | Metaphor should illuminate, not constrain. Use it where it helps understanding, skip where it doesn't. Natural beats forced. | | **Too much teaching, not enough story** | Wanting to share all your knowledge | Readers connect through story first. Aim for 40% story/example, 40% teaching, 20% application. Adjust per chapter needs. | | **Exercises that don't match reader readiness** | Copying exercise formats from other books | Exercise difficulty must match where reader is in arc. Early chapters = simple reflection. Later chapters = bigger challenges. | | **Losing voice consistency** | Switching between academic and conversational tone | Pick one voice (usually conversational for self-help) and maintain it. Use "Voice Editor" mode to check consistency. See example below. | | **Ignoring reader resistance** | Assuming reader agrees with premise | Address objections explicitly. "You might be thinking..." shows you understand their skepticism and builds trust. | | **Reveal without setup** | Planning twist ending but not planting seeds | If book has reframe/reveal, every chapter needs subtle foreshadowing. Use "Reveal Engineer" mode to plant and track seeds. | ### Example: Voice Consistency **Inconsistent voice (Chapter 1 conversational, Chapter 4 academic):** Chapter 1: "You know that feeling of finishing a 'productive' day without accomplishing anything important? That's your brain telling you
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.