Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add haowjy/creative-writing-skills --skill project-setup -a claude-code
Open on GitHub

What 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.md and kb/.
  • Review the existing AGENTS.md and 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-code

2Manually: put the files in place

~/.claude/skills/project-setup/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/project-setup/

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.

project-setup codewithmukesh project-setup recommends .NET tech stack defaults for databases, auth, caching, and messaging. Helps pick stack defaults or review dependencies before writing code. CX Codex +1 4,000installs project-setup haowjy project-setup is a Claude Code skill that interviews the author, collects writing samples, and creates AGENTS.md with project conventions. It runs during initial project setup. CX Codex +1 608installs project-memory jamditis project-memory generates project instruction files like AGENTS.md or CLAUDE.md to pass institutional knowledge to AI agents without generic clutter. CX Codex +1 180installs novel-revision jwynia Manages multi-level novel revisions while preventing narrative plot breaks. It tracks how changes ripple through theme, structure, and prose. CX Codex +1 702installs genre-craft danjdewhurst genre-craft — a skill for Claude Code, Codex, Cursor, and other agents that loads structural craft rules for a specific fiction genre. CX Codex +1 533installs key-moments jwynia key-moments — a skill that builds a story around its key emotional scenes instead of a mechanical outline. Useful when plotting feels flat. CX Codex +1 524installs discovery-drafting danjdewhurst discovery-drafting drafts fiction without an upfront outline and reconciles characters, promises, and chapter diffs back into the story bible retrospectively. CX Codex +1 466installs bmad-project-context bmad-code-org bmad-project-context is a Claude Code skill that builds, audits, and maintains verified agent instructions in AGENTS.md. It records past agent mistakes as explicit pitfalls. CX Codex +1 17,200installs

From the same set32

The whole set →
story-review story-review evaluates existing prose across five editorial levels, from plot structure down to copyediting. Useful when a draft needs diagnostic critique instead of automated rewrites. CX Codex +1 773installs story-planning story-planning — a Claude Code skill for creative direction, brainstorming, and story architecture before drafting prose. Activates when shaping plot beats or structuring scenes. CX Codex +1 763installs reader-sim reader-sim reads a draft through the eyes of a specified first-time reader and reports the experience as it unfolds. Use it when you want a reader’s response rather than a craft critique. CX Codex +1 634installs character-sim character-sim speaks as a specific fictional character during story moments, using their vocabulary, current emotional state, and knowledge limits. CX Codex +1 612installs project-setup project-setup is a Claude Code skill that interviews the author, collects writing samples, and creates AGENTS.md with project conventions. It runs during initial project setup. CX Codex +1 608installs story-memory The story-memory Claude Code skill preserves and retrieves information from a fiction project. It comes into play when passing context between writing tasks or maintaining persistent story notes. CX Codex +1 606installs intent-modeling intent-modeling — a skill that makes an AI agent work out what you meant before it acts on what you literally said. CX Codex +1 586installs shared-dao shared-dao — a Claude Code skill that enforces terminology consistency across project files. Triggers when introducing new terms, encountering overloaded words, or reconciling naming collisions. CX Codex +1 581installs

Project sponsors

Companies that keep this analytics open