cw/skills/project-setup/SKILL.md
One-time project setup for creative writing. Interviews you about your project, collects writing samples, proposes kb structure, and creates CLAUDE.md with project conventions.
npx skillsauth add haowjy/creative-writing-skills cw/skills/project-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guide the author through setting up their creative writing project. The goal
is a working CLAUDE.md and directory structure that all agents read for
project-specific conventions, plus initial style files if writing samples are
available.
Ask about:
Ask about writing samples: these are the foundation for style analysis:
Collect whatever they have. Save samples to kb/samples/ so they're available
for future style analysis. If they have enough material, offer to analyze
their style using the /style-analysis methodology: read the samples,
identify the voice dimensions, and produce initial style files in kb/styles/.
If they're starting fresh with no samples, capture their voice goals in CLAUDE.md so style files can be created from early drafts.
Based on what you learn, draft a CLAUDE.md section and show it to the
author. Cover:
kb/ and what they're
for. Suggest based on project complexity:
characters/, canon/, styles/, root vocab.mdtimeline/world/, issues/, and domain vocab files such as world/vocab.mdPresent the draft and let the author adjust. Iterate until they're satisfied.
Once approved:
CLAUDE.md with the agreed contentkb/ directories referenced in CLAUDE.mdkb/vocab.md when the project has named concepts agents must use
consistently; create domain vocab files when a domain already has enough
distinct termswork/ with standard subdirectories (outline/, drafts/,
critique-reports/, brainstorm/)kb/samples/kb/styles/If CLAUDE.md already has creative writing conventions, read it first and
suggest updates rather than overwriting.
data-ai
Team composition for writing workflows: which agents to spawn, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, dispatching researchers, staffing draft/revise loops, or setting up brainstorm fan-outs.
testing
Logging and referencing writing issues: craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review. Use when an agent identifies something worth tracking beyond a single critique report: repeated tics across chapters, inconsistencies that affect multiple scenes, structural problems that need the author's attention, or patterns that should be fixed in revision.
development
Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.
testing
Prose-level immersion patterns for narrative fiction. Use when writing or revising prose: the sentence-level and paragraph-level craft that pulls readers into the story. Project-specific voice comes from style files passed alongside this skill.