project-setup
Skill570 starsChanged 7 days agoApache-2.0View on GitHub
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.
48 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- codewithmukesh/dotnet-claude-kittheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- ErikaAX08/erikas-skillstheir own version, first seen Nov 8, 2026
- Pagepro/nexitytheir own version, first seen Nov 8, 2026
- celestialdust/achilles-skillstheir own version, first seen Nov 1, 2026
- FiredMosquito831/my-writing-companionedited, first seen Nov 1, 2026
Used with
Projects with it also use authentication and ci-cd.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillauthentication
Wire this in whenever the app uses or connects to data — records, a database, entities, per-user data, row-level security — or when the user wants sign-in, accounts, login, or protected pages. Rayfin data is always accessed as an authenticated user, so **data implies auth**; only a static page over public data skips it. The starter ships as a no-auth "hello world" that previews with no backend, and the full Fabric auth scaffolding is already in the project — this skill wires it in: AuthProvider + bootstrapAuth in main.tsx, the route guard in App.tsx, the sign-in page, sign-out, and the env/deploy requirement. Triggers: auth, authentication, sign in, sign-in, login, log in, sign out, logout, account, user, identity, protect route, require login, gated page, data, database, records, per-user, row-level security, who is the current user, Fabric auth, Entra.
Also in 3 projects that use this
JohnJBorenSkillci-cd
CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies
Also in 4 projects that use this
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- FiredMosquito831/my-writing-companion★ 212% same
Wrote their own version · 47
- codewithmukesh/dotnet-claude-kit★ 808same name
- karrioapi/karrio★ 799same name
- Resgrid/Core★ 238same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- fltman/project-scaffolder★ 88same name
- markshust/hcf★ 79same name
- vaayne/agent-kit★ 54same name
- dleerdefi/claude-code-construction★ 53same name
- wolverin0/claude-skills★ 41same name
37 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- character-simSkill
- creative-researchSkill
- creative-writing-craftSkill
- creative-writing-museSkill
- reader-simSkill
- story-memorySkill
- story-planningSkill
- story-reviewSkill
- story-workflowSkill
- writing-principlesSkill
- writing-staffingSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Ask the author where they work, or infer it from the session, then read exactly one of these and follow its setup and walkthrough:
- Distinctive: line 29
Do not load the others. Meridian Flow, the writing app, has no setup path yet: it will import packages once its importer ships, so use the …
- Distinctive: line 46
Do they have sample chapters or scenes already written?
- Distinctive: line 47
Do they have writing from other projects that captures the voice they want?
- Distinctive: line 57
If they are starting fresh, capture their voice goals in AGENTS.md so style files can be created from the first drafts.
- Distinctive: line 86
Write or update AGENTS.md with the agreed content.
- Very specific: line 87
Create the kb/ directories it names.
- Very specific: line 88
Create kb/vocab.md when the project has named concepts agents must use consistently.
- Very specific: line 91
Create work/ with outline/, drafts/, critique-reports/, and brainstorm/.
- Very specific: line 94
If samples were provided and the author wants it, produce initial style files in kb/styles/.
- Distinctive: line 99
If AGENTS.md already has creative writing conventions, read it first and propose updates.
“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 bymars 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. Meridian Flow, the writing app, has no setup path yet: it will import packages once its importer ships, so use the environment you are in.
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; itsresources/kb-layout.mdhas 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:
- Write or update
AGENTS.mdwith the agreed content. - Create the
kb/directories it names. - Create
kb/vocab.mdwhen the project has named concepts agents must use consistently; add domain vocab files when a domain already has enough distinct terms. - Create
work/withoutline/,drafts/,critique-reports/, andbrainstorm/. - Save the writing samples to
kb/samples/. - 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.