project-setup · haowjy — Claude Code skill: setup and install
The project-setup Claude Code skill gathers details about a creative writing project and prepares its working files. The author starts it once at the beginning of a project.
Apache-2.0 608 installs ★ 601 updated 2026-11-16
npx skills add haowjy/creative-writing-skills --skill project-setup -a claude-codeWhat project-setup does
The skill interviews the author about the project, existing material, and intended voice. It drafts an AGENTS.md and a kb/ layout, then revises the draft with the author. For an existing project, it reads the current AGENTS.md first and preserves established decisions.
It saves writing samples in kb/samples/ and, with the author’s approval, creates style files in kb/styles/. For sample analysis, it can offer /creative-writing-craft; it uses /story-memory to shape the knowledge-base layout. Outside Meridian, it also creates folders for outlines, drafts, critique reports, and brainstorming. Meridian assigns a separate work directory to each task.
What it helps with
- draft project conventions in
AGENTS.md - organize project knowledge under
kb/ - save writing samples and create style files
Example prompts for the agent
- Set up my novel: ask about its story, existing material, and voice, then draft
AGENTS.mdandkb/. - Review the existing
AGENTS.mdand suggest changes without replacing settled decisions. - Save my chapters in
kb/samples/and offer a style analysis with/creative-writing-craft.
How to install project-setup
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill project-setup -a claude-code2Manually: put the files in place
~/.claude/skills/project-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/project-setup/
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill project-setup -a codex2Manually: put the files in place
.agents/skills/project-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill project-setup -a cursor2Manually: put the files in place
.cursor/skills/project-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install haowjy/creative-writing-skills skills/project-setup2Manually: put the files in place
.github/skills/project-setup/SKILL.md1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill project-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/haowjy/creative-writing-skills --path skills/project-setupManually: put the files in place
.devin/skills/project-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill project-setup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about project-setup
How do I install project-setup in Claude Code?
Run npx skills add haowjy/creative-writing-skills --skill project-setup -a claude-code. The skill file is installed at ~/.claude/skills/project-setup/SKILL.md.
What does project-setup do?
It interviews the author, drafts AGENTS.md and a kb/ layout, then creates the approved files and saves writing samples.
How does project-setup choose a knowledge-base layout?
It loads /story-memory and selects a simple, medium, or complex layout to match the project.
Source text
SKILL.md · Apache-2.0
--- name: project-setup description: > One-time project setup for creative writing: interview the author about the project, writing samples, and voice, then create the AGENTS.md, kb/ layout, and style files every writing agent reads. User-invoked; run it once when starting a project. model-invocable: false metadata: type: checkpoint --- # Project Setup Set up a project once so every later session starts with the conventions it needs: an `AGENTS.md`, a `kb/` layout, and style files when the author has samples. ## First, Load One Environment Walkthrough Ask the author where they work, or infer it from the session, then read exactly one of these and follow its setup and walkthrough: - `resources/meridian-cli.md` — meridian-cli, with the package installed by `mars add`. - `resources/claude-code.md` — Claude Code with this plugin. - `resources/claude-desktop.md` — claude.ai, Claude Desktop, or Cowork. - `resources/other-harnesses.md` — Codex, Cursor, OpenCode, or Grok. Do not load the others. ## Learn About the Project Ask about: - What kind of project: novel, short story collection, serial? - How far along: starting fresh, or existing chapters and worldbuilding? - Single POV or multiple? Linear or non-linear timeline? How much worldbuilding? - Where they keep their writing? What is the existing layout? ## Writing Samples and Style Writing samples are the foundation for style analysis: - Do they have sample chapters or scenes already written? - Do they have writing from other projects that captures the voice they want? - Are there published works they want to draw style inspiration from? - Voice goals: close third, omniscient, first person? Formal, colloquial? Collect whatever they have and save it to `kb/samples/`. If there is enough material, offer to analyze it with `/creative-writing-craft`: read the samples, identify the voice dimensions, and write initial style files to `kb/styles/`. Style files are the most impactful thing to get right early; every writing agent depends on them. If they are starting fresh, capture their voice goals in `AGENTS.md` so style files can be created from the first drafts. ## Propose and Iterate Draft `AGENTS.md` and show it to the author. Cover: - **Project overview**: what the project is, one paragraph. - **Author's space**: where the author keeps their writing and how it is organized. Agents read from here; they do not write to it. - **KB structure**: which subdirectories exist under `kb/` and what each is for. Load `/story-memory`; its `resources/kb-layout.md` has the layers, page conventions, and the default layout. Pick the subset this project needs: simple (short story, single POV), medium (novel, a few POVs), or complex (series, large world). - **Voice and style**: which style files exist, which samples they came from, and which voice goals are not captured yet. - **Conventions**: naming patterns, chapter numbering, POV tagging, spoiler handling, anything else project-specific. - **Shared vocabulary**: early canonical terms, aliases, invented words, genre terms with project-specific meanings, and terms agents should avoid or distinguish. Present the draft and let the author adjust until they are satisfied. ## Create the Files Once approved: 1. Write or update `AGENTS.md` with the agreed content. 2. Create the `kb/` directories it names. 3. Create `kb/vocab.md` when the project has named concepts agents must use consistently; add domain vocab files when a domain already has enough distinct terms. 4. Outside Meridian, which gives each task its own work directory, create `work/` with `outline/`, `drafts/`, `critique-reports/`, and `brainstorm/`. 5. Save the writing samples to `kb/samples/`. 6. If samples were provided and the author wants it, produce initial style files in `kb/styles/`. ## Existing Projects If `AGENTS.md` already has creative writing conventions, read it first and propose updates. Do not overwrite the author's decisions.
© haowjy · Apache-2.0 · haowjy/creative-writing-skills
Similar skills
All skills for Agent setup: memory, context, orchestration →project-setup by other authors comes first.