setup-project
Skill1 starsChanged 35 days agoMITView on GitHub
One-time setup of a repo for the dev-flow skills. Detects the stack, then writes the project profile (AGENTS.md), the justfile command contract, stack rules from packs, GitHub issue tracking (labels, ticket template, board script) and, for web UI, a design contract skeleton. Never edits skills. Use when starting a new repo or bringing an existing one into dev-flow.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- lohi-ai/babysittheir own version, first seen Nov 8, 2026
- roedyrustam/doku-gemini-mcptheir own version, first seen Nov 8, 2026
- ok-oldking/ok-scripttheir own version, first seen Nov 1, 2026
- OlliTapio/claude_skillstheir own version, first seen Oct 26, 2026
- MacroMan5/autotrain-yolotheir own version, first seen Oct 25, 2026
- boonkgim/setup-projecttheir own version, first seen Oct 20, 2026
Used with
Projects with it also use review-pr, tdd and 1 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.
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- ok-oldking/ok-script★ 831same name
- gricha/dangerous-skills★ 38same name
- MacroMan5/autotrain-yolo★ 8same name
- phatysddev/skills★ 8same name
- chav0/UnityFigmaMCP★ 7same name
- ByronFinn/dev-skills★ 4same name
- otaviobarros/agent-engineering★ 3same name
- beeltec/skills★ 2same name
- r2rka1/skills★ 2same name
- roedyrustam/doku-gemini-mcp★ 2same name
10 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 repository14 other files it gives its agents.
- skills/setup-project/templates/AGENTS.mdAGENTS.md
- grill-meSkill
- addressSkill
- conventional-commitsSkill
- design-packageSkill
- doneSkill
- implementSkill
- preview-prSkill
- researchSkill
- stop-previewSkill
- takeSkill
- ticketsSkill
- ui-from-referenceSkill
- visual-notesSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Look only at: package.json and lockfiles, pnpm-workspace.yaml, next.config.*, any convex/ folder, vitest.config.*, project.godot, *.csproj, …
“Common” is measured: kept by at least 6 in 10 of the 18 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
/setup-project
Skills stay global and unchanged. This skill writes the project's own facts once, from the templates and packs next to this file (<skill-dir> is the folder containing this SKILL.md).
1. Detect (read, don't ask)
Look only at: package.json and lockfiles, pnpm-workspace.yaml, next.config.*, any convex/ folder, vitest.config.*, project.godot, *.csproj, pyproject.toml, Cargo.toml, justfile, AGENTS.md, CLAUDE.md, .cursor/rules/, docs/, git remote -v. At most 15 reads; never node_modules. Match packs with <skill-dir>/packs/INDEX.md.
2. Ask once
One batch, at most 6 questions, each with your recommendation:
- The project in one sentence.
- Packs: confirm the detected list.
- Git: Graphite or plain git, and the base branch.
- Tracker: GitHub Issues with a project board (recommended) or local markdown; the board title.
- Models for tickets/take, implement, address/done, and when stuck.
- Web UI: write the design contract skeleton now? (Yes if the project has or will have screens.)
3. Write
Show the file list first, then write.
AGENTS.mdfromtemplates/AGENTS.md, the block under 60 lines. If it exists, replace only the block between<!-- dev-flow:start -->and<!-- dev-flow:end -->, or append the block. Keep every other tool's managed block as it is (Next.js writes one betweenBEGIN:nextjs-agent-rulesandEND:nextjs-agent-rules). If onlyCLAUDE.mdexists, add the lineSee AGENTS.md.to it.justfile: merge each pack'sjustfile.snippet, keeping existing recipes. Every contract recipe must exist:test-q,typecheck,lint,check,run,stop,task. A recipe with no tool for this stack becomes@echo "n/a for this stack"..cursor/rules/<rule>.mdcfrom each chosen pack'srules/, with every<<placeholder>>filled from detection. Packs never add always-on rules.- GitHub (if chosen):
docs/agents/issue-tracker.mdand.github/ISSUE_TEMPLATE/ticket.mdfromtemplates/;scripts/task.shandscripts/project-env.shfromtemplates/(make them executable); labels:gh label create status:todo --color ededed,gh label create status:in-progress --color fbca04,gh label create status:in-review --color 0e8a16(ignore "already exists"). docs/DECISIONS.mdfromtemplates/DECISIONS.mdif missing.- Web UI (if chosen):
docs/design/README.mdfromtemplates/design-contract.md,docs/design/screens.jsoncontaining[],scripts/shots.tsfrompacks/ui-web/, and.shots/in.gitignore. Then tell the human the references and tokens come from thedesign-packageskill, run with a strong model (Claude), not from this setup.
4. Hand over
Print the steps only the human can do, then stop:
gh auth refresh -s projectgh project create --owner <owner> --title "<board title>"; in its settings add a Status option namedIn Review; thenscripts/project-env.sh <owner> <project number>.- One milestone per phase:
gh api repos/<owner>/<repo>/milestones -f title="Phase 1". just checkonce; fix the setup (not the code) until it runs.
End with one line: Next: /tickets <spec section> on <model for tickets>.
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.

