project-setup
Skill2 starsChanged 8 months agoMITView on GitHub
Bootstrap a new project with SQWR standards. Detects stack, selects contracts, copies templates, and configures hooks.
- Reads credentials
48 other projects use a version of this.
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-companiontheir own version, first seen Nov 1, 2026
Used with
Projects with it also use creative-writing-craft, creative-writing-muse and 10 more.
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.
Abdullokh-NSkillcreative-writing-craft
Справочник ремесла: проза, сцена, стиль, голос. Загружать, когда нужно знание "как писать", а не режим производства.
Also in 3 projects that use this
Abdullokh-NSkillcreative-writing-muse
Точка входа в набор скилов для длинной прозы. Включается, когда автор просит спланировать, написать, продолжить, переписать или разобрать художественный текст — роман, повесть, цикл рассказов. Ведёт маршрут от замысла к готовому куску и держит базу знаний проекта.
Also in 3 projects that use this
badgidsSkillcharacter-sim
Pressure-test a character by speaking or reasoning strictly from that character's current voice, goals, relationships, emotional pressure, and knowledge boundary without creating canon by accident.
Also in 3 projects that use this
jpsweeney97Skillwriting-principles
Enforces writing principles for instruction documents (SKILL.md, skill supporting files, subagents, CLAUDE.md). Use when writing, reviewing, or editing any file in **/skills/**/*.md, **/agents/*.md, or **/CLAUDE.md. Triggers on skill creation, skill file updates, CLAUDE.md changes, subagent authoring, or instruction document review.
Also in 3 projects that use this
ItsSidharthaSkillstory-planning
Collaborative planning skill for a GitHub issue. Takes issue content and codebase context as input. Runs an iterative clarification loop until the user explicitly agrees to a plan, then saves it to docs/<story_number>/plan.md. Used by the user-story-implementation skill — load this skill at the start of Phase 1 and follow it completely before returning to the orchestrator.
Also in 3 projects that use this
badgidsSkillstory-review
Diagnose existing prose at a chosen editorial level, from whole-story and developmental problems through scene, line, copy, and proof passes, without rewriting until the diagnosis is accepted.
Also in 3 projects that use this
- +4 more from Abdullokh-N
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- codewithmukesh/dotnet-claude-kit★ 808same name
- karrioapi/karrio★ 799same name
- haowjy/creative-writing-skills★ 570same 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
38 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 repository11 other files it gives its agents.
- global/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- audit-runnerSkill
- auto-fixSkill
- brainstormSkill
- compliance-checkSkill
- contract-lookupSkill
- monthly-reviewSkill
- new-featureSkill
- pre-deploymentSkill
- risk-scoreSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
If any parameter is missing, prompt the user:
“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 — Project Setup
Usage: /project-setup [project name] [stack] [path]
Bootstraps a new project with SQWR standards.
Example: /project-setup my-app nextjs-supabase ~/Desktop/my-app
Step 1 — Gather parameters
From $ARGUMENTS, extract:
PROJECT_NAME: name of the projectSTACK: one ofnextjs-supabase,nextjs,python,ios,android,fullstackPATH: destination path (default:~/Desktop/$PROJECT_NAME)
If any parameter is missing, prompt the user:
- "What is the project name?"
- "Which stack? (nextjs-supabase / nextjs / python / ios / android / fullstack)"
- "Where should the project be created? (default: ~/Desktop/[name])"
Step 2 — Run init-project.sh
bash scripts/init-project.sh \
--name "$PROJECT_NAME" \
--stack "$STACK" \
--path "$PATH"This creates:
$PATH/CLAUDE.md— pre-filled AI contract$PATH/docs/contracts/— stack-relevant contracts$PATH/.claude/settings.json— hooks configuration$PATH/.claude/agents/— audit agents$PATH/CHANGELOG.md,.gitignore,.env.example
Step 3 — Verify the generated project
bash scripts/validate-claude-md.sh "$PATH/CLAUDE.md"
bash scripts/verify-project.sh "$PATH/CLAUDE.md"Fix any warnings before proceeding.
Step 4 — Post-setup instructions
Output a summary with:
- Contracts to activate: tell the user which contracts to check
[x]in CLAUDE.md - Hooks status: confirm
.claude/settings.jsonis configured - First steps:
cd $PATH git init && git add . && git commit -m "chore: initialize project with SQWR standards" - Next workflow: suggest running
/new-featurefor the first feature
Stack → contracts mapping
| Stack | Contracts included |
nextjs-supabase | TYPESCRIPT, SECURITY, TESTING, CICD, NEXTJS, SUPABASE, VERCEL, PERFORMANCE, ACCESSIBILITY, SEO, DESIGN, OBSERVABILITY, RESILIENCE |
nextjs | TYPESCRIPT, SECURITY, TESTING, CICD, NEXTJS, VERCEL, PERFORMANCE, ACCESSIBILITY, SEO, DESIGN, OBSERVABILITY |
python | PYTHON, SECURITY, TESTING, CICD, API-DESIGN, OBSERVABILITY |
ios | IOS, ACCESSIBILITY, SECURITY, TESTING, CICD |
android | ANDROID, ACCESSIBILITY, SECURITY, TESTING, CICD |
fullstack | All 29 contracts |
Reference
Script: scripts/init-project.sh
Validation: scripts/verify-project.sh
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.

