Browse skills

Everything the book needs to reach the market — logline, back cover synopsis, editorial synopsis, query letter for publishers/agents, and cover brief for designers. Three specialists in one. Use in Phase 6 of book-genesis or when the manuscript is ready for submission.

Builds and maintains ENTITY_STATE.yaml — the persistent structured database of every character, location, object, organization, timeline entry, and world rule in the manuscript. Operates in BUILD mode (initial extraction from existing chapters) and UPDATE mode (incremental tracking as new chapters are written or revised). The single source of truth that other skills consume instead of rebuilding entity databases from scratch.

State engine. Tracks everything across sessions — chapters, scores, decisions, handoffs. Without this, context is lost and the pipeline collapses. Use at the START and END of every book work session. The most critical piece of the system.

Final stage. Technical proofreading (spelling, grammar, consistency) + formatting for ebook and print. Two specialists in one. Use after all content revisions are complete, before publishing or submitting.

Builds the series bible — macro arc, canonical worldbuilding, inter-volume hooks, character consistency, and the "next book" that makes the reader buy. Series sell better than standalones. Use before writing Vol. 2 and whenever the series scope changes.

Create a comprehensive marketing plan — channels, messaging, content strategy, and growth tactics. Use when: planning marketing for a product launch, creating a content calendar, designing a go-to-market strategy.

Scan a codebase and auto-generate relevant diagrams from its structure

Change theme, output format, or check plugin dependencies

Generate a Mermaid diagram from a text description

Render .mmd or .md files to SVG images

Validate Mermaid syntax in .md files or directories

This skill should be used when the user asks to "show dev-setup config", "change the worktrees directory", "update the port pattern", "configure dev-setup settings", or wants to view or update settings in .claude/dev-setup.json.

This skill should be used when the user asks to "create a worktree", "set up an isolated workspace", "create a branch for a feature", "start working on a new branch", or before executing an implementation plan that needs an isolated git workspace.

Change theme, layout engine, sketch mode, or check plugin dependencies

Convert a Mermaid diagram to D2 format

Generate a D2 diagram from a text description

Render .d2 files to SVG or PNG images

Validate D2 syntax in .d2 files or directories

Generate dev server lifecycle scripts (start/stop/status/ports) from detected project structure

Use when checking Paperclip org health, reviewing agent efficiency, diagnosing token waste, verifying governance compliance, or before and after making org changes. Also use when agents seem idle or unproductive, costs spike, tasks stall, heartbeats fail silently, you see 409 conflicts, stale locks, blocked deadlocks, or suspect agents burning tokens with no progress.