New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Creative Writing Setup

Project setup

by haowjy · Apache-2.0 license · ★ 506 on GitHub

Project setup cover

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.

---
name: project-setup
description: >
  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.
---

# Project Setup

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.

## Learn About the Project

Ask about:

- What kind of project: novel, short story collection, serial?

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add haowjy/creative-writing-skills --skill project-setup -g -a claude-code
Claude Code (degit)npx degit haowjy/creative-writing-skills/cw/skills/project-setup#main ~/.claude/skills/project-setup
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.4 KB
Read SKILL.md here
haowjy/main1 file shown
SKILL.md
Show the full text82 lines

Project Setup

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.

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 do they keep their writing? What's the existing layout?

Writing Samples and Style

Ask about writing samples: these 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. 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 /creative-writing-craft 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.

Propose and Iterate

Based on what you learn, draft a CLAUDE.md section 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's organized
  • KB structure: what subdirectories exist under kb/ and what they're for. Suggest based on project complexity:
    • Simple (short story, single POV): characters/, canon/, styles/, root vocab.md
    • Medium (novel, few POVs): add timeline/
    • Complex (series, large world): add world/, issues/, and domain vocab files such as world/vocab.md
  • Voice and style: what style files exist, what samples they're derived from, voice goals not yet captured
  • Conventions: anything project-specific: naming patterns, chapter numbering, POV tagging, spoiler handling
  • Shared vocabulary: early canonical terms, aliases, invented words, genre terms with project-specific meanings, and terms the author wants agents to avoid or distinguish

Present the draft and let the author adjust. Iterate until they're satisfied.

Create the Files

Once approved:

  1. Write or update CLAUDE.md with the agreed content
  2. Create the kb/ directories referenced in CLAUDE.md
  3. Create kb/vocab.md when the project has named concepts agents must use consistently; create domain vocab files when a domain already has enough distinct terms
  4. Create work/ with standard subdirectories (outline/, drafts/, critique-reports/, brainstorm/)
  5. Save any writing samples to kb/samples/
  6. If samples were provided and the author wants style analysis, produce initial style files in kb/styles/

Existing Projects

If CLAUDE.md already has creative writing conventions, read it first and suggest updates rather than overwriting.

1---
2name: project-setup
3description: >
4 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.
5---
6 
7# Project Setup
8 
9Guide the author through setting up their creative writing project. The goal
10is a working `CLAUDE.md` and directory structure that all agents read for
11project-specific conventions, plus initial style files if writing samples are
12available.
13 
14## Learn About the Project
15 
16Ask about:
17 
18- What kind of project: novel, short story collection, serial?
19- How far along: starting fresh, or existing chapters and worldbuilding?
20- Single POV or multiple? Linear or non-linear timeline? How much worldbuilding?
21- Where do they keep their writing? What's the existing layout?
22 
23## Writing Samples and Style
24 
25Ask about writing samples: these are the foundation for style analysis:
26 
27- Do they have sample chapters or scenes already written?
28- Do they have writing from other projects that captures the voice they want?
29- Are there published works they want to draw style inspiration from?
30- Voice goals: close third, omniscient, first person? Formal, colloquial?
31 
32Collect whatever they have. Save samples to `kb/samples/` so they're available
33for future style analysis. If they have enough material, offer to analyze
34their style using the `/creative-writing-craft` methodology: read the samples,
35identify the voice dimensions, and produce initial style files in `kb/styles/`.
36 
37If they're starting fresh with no samples, capture their voice goals in
38CLAUDE.md so style files can be created from early drafts.
39 
40## Propose and Iterate
41 
42Based on what you learn, draft a `CLAUDE.md` section and show it to the
43author. Cover:
44 
45- **Project overview**: what the project is, one paragraph
46- **Author's space**: where the author keeps their writing and how it's
47 organized
48- **KB structure**: what subdirectories exist under `kb/` and what they're
49 for. Suggest based on project complexity:
50 - Simple (short story, single POV): `characters/`, `canon/`, `styles/`, root `vocab.md`
51 - Medium (novel, few POVs): add `timeline/`
52 - Complex (series, large world): add `world/`, `issues/`, and domain vocab files such as `world/vocab.md`
53- **Voice and style**: what style files exist, what samples they're derived
54 from, voice goals not yet captured
55- **Conventions**: anything project-specific: naming patterns, chapter
56 numbering, POV tagging, spoiler handling
57- **Shared vocabulary**: early canonical terms, aliases, invented words,
58 genre terms with project-specific meanings, and terms the author wants
59 agents to avoid or distinguish
60 
61Present the draft and let the author adjust. Iterate until they're satisfied.
62 
63## Create the Files
64 
65Once approved:
66 
671. Write or update `CLAUDE.md` with the agreed content
682. Create the `kb/` directories referenced in CLAUDE.md
693. Create `kb/vocab.md` when the project has named concepts agents must use
70 consistently; create domain vocab files when a domain already has enough
71 distinct terms
724. Create `work/` with standard subdirectories (outline/, drafts/,
73 critique-reports/, brainstorm/)
745. Save any writing samples to `kb/samples/`
756. If samples were provided and the author wants style analysis, produce
76 initial style files in `kb/styles/`
77 
78## Existing Projects
79 
80If `CLAUDE.md` already has creative writing conventions, read it first and
81suggest updates rather than overwriting.
82 
View all files on GitHub →

Details

License
Apache-2.0
Stars on the repo
★ 506
Checked
Source
haowjy/creative-writing-skills ↗
Creator
haowjy · 22 listings
View creator

Similar skills

See all →

More from haowjy

Character Voice Simulatorhaowjy/creative-writing-skills · by haowjySpeak as a specified character from their current knowledge, voice, and emotional state. Use for skill-only workflows that need in-character conversation, voice discovery, or relationship pressure tests.★ 506 GitHub starsStory Research Assistanthaowjy/creative-writing-skills · by haowjyLoad when a story needs factual grounding the writer doesn't have: historical detail, cultural texture, domain accuracy, or how other authors handled similar material. Pass the question and story context; returns a sourced report the writer can draw from.★ 506 GitHub starsFiction Writing Craft Guidehaowjy/creative-writing-skills · by haowjyCraft references for writing fiction well: prose, scenes, style, voice, and genre/page-level technique. Load when a writer, critic, or muse needs how-to-write guidance rather than a production mode.★ 506 GitHub starsWriting Mode Guidehaowjy/creative-writing-skills · by haowjyCreative-writing addendum to /llm-writing. Load when putting prose on the page: draft, revise, bridge, vary, or polish.★ 506 GitHub starsMulti-Mode Writing Studiohaowjy/creative-writing-skills · by haowjyLoad when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.★ 506 GitHub starsOutput Information Hierarchyhaowjy/creative-writing-skills · by haowjyLoad for large human-facing outputs: reports, docs, multi-section explanations, artifacts. Choose the right form for each beat (prose, diagram, table, mockup) and put the answer first, depth behind it. If the medium allows, use progressive disclosure.★ 506 GitHub stars