project-setup
Skill12 starsChanged 20 days agoMITView on GitHub
Load this skill before you add a layer that a project lacks, such as auth or hosting, migrate a project to the user's stack, replace a layer with the stack's choice, or start a new project. Covers the stack table, what each choice replaces, the migration order, the new-project files, .worktreeinclude, the global package store, the file templates, and the done checks.
- Reads credentials
52 other projects use a version of this.
Adopted by
Most recently taken up by
- mikejhill/agent-skillstheir own version, first seen Nov 15, 2026
- GravionLabs/skillstheir own version, first seen Nov 15, 2026
- dvy1987/agent-loomtheir own version, first seen Nov 15, 2026
- wolverin0/claude-skillstheir own version, first seen Nov 11, 2026
- codewithmukesh/dotnet-claude-kittheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 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 versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- codewithmukesh/dotnet-claude-kit★ 808same name
- karrioapi/karrio★ 799same name
- haowjy/creative-writing-skills★ 590same 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
42 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
- prSkill
- writing-for-agentsSkill
- adversarial-councilSkill
- diagnoseSkill
- explore-subagentsSkill
- github-writingSkill
- mise-reviewSkill
- optimize-skillSkill
- prSkill
- t3-pr-review-webhookSkill
- audit-website-copySkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
4
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
- Distinctive: line 34
When a task needs a layer, or a part of one such as auth, that the project lacks, use the table's choice.
- Distinctive: line 46
Keep the behavior the same, and keep fixes and features out of it.
- Distinctive: line 47
After each layer, run the app and the checks.
- Distinctive: line 53
Ask about layers the table doesn't cover.
- Very specific: line 91
Start each file from its template in this skill's assets/ folder.
“Common” is measured: kept by at least 6 in 10 of the 44 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
The stack table is the target for the user's own projects. Use it for a layer that a project lacks, for a migration, and for a new project. A change inside a tool the table already names is ordinary work. Run only the layers the user asked for.
The stack
| Layer | Choice | Replaces |
| Packages and monorepo | Bun, bun.lock, workspace catalogs, mise tasks. Turborepo only for its cache or for runs in the changed packages | npm, yarn; Turborepo for plain task runs |
| Web app | TanStack Start, Vite, React, Tailwind 4, shadcn/ui | Next.js |
| Mobile app | Expo, Expo Router, dev client, EAS; Uniwind with DESIGN.md tokens | NativeWind, StyleSheet |
| API | Bun and Elysia for a long-running server; TanStack Start server routes for web app endpoints | Express, NestJS; Next.js API routes |
| Data and auth | Convex with Clerk; for SQL, Drizzle with Neon and Better Auth | Firebase, Supabase |
| Hosting | Cloudflare (Workers, Pages, R2) through Alchemy; Coolify for Docker | Vercel |
| Code checks | oxlint, oxfmt, tsrs (TypeScript 7), hk hooks, fallow, react-doctor | ESLint, Prettier, Biome; tsc, tsgo; lefthook, husky; knip |
| Formal verification | tla-ts, for TLA+ models of state machines and async flows | |
| Tests | bun test in Bun projects; otherwise Vitest. Vitest where convex-test needs it. e2e with agent-device (iOS) and agent-browser (web) | Maestro, Playwright, Detox |
| CI and commits | GitHub Actions on Blacksmith runners, with mise-action; Conventional Commits; Renovate for dependency updates | GitHub-hosted runners |
| Env and secrets | Infisical for environment variables; Varlock for agent access | |
| Agent workspace | T3 Code, T3 worktrees, a t3.json per repo, and a .worktreeinclude |
Add a missing layer
When a task needs a layer, or a part of one such as auth, that the project lacks, use the table's choice. Add only that layer, in the task's own PR.
Migrate a project
- Compare the project with the stack table. List what to replace, and what
the project lacks, such as formal verification, the global package store,
or
.worktreeinclude. Give the order, then wait for the user's pick. Skip the wait when the user already named the layers. - For a move into mise, load
mise-reviewand stop at its plan. It is read-only. Do the move after the user approves the plan. - Move one layer per PR. Use the versions that the global
AGENTS.mdsets. Keep the behavior the same, and keep fixes and features out of it. - After each layer, run the app and the checks. Then remove the old tool completely: its config, scripts, and dependency. Remove the old lockfile only when the package manager changes.
Start a new project
- Ask about layers the table doesn't cover. Ask before you create the GitHub repo. The first commit on the default branch needs no question.
- From day one, the project has:
mise.tomlwith pinned tools,worktrunkamong them, andsetupandchecktasks- repo config that turns on the global store of the package manager in use, so a new worktree or a teammate's clone doesn't download every package again
- hk hooks and CI
.worktreeinclude: the gitignored files and folders that a new worktree copies from the main checkout. List the.envfiles,.claude/settings.local.json,mise.local.toml,plans/,.scratch/, and any other local file the work needs. Leave out a file that must differ per worktree, such as an env file that points at one backend deployment. Write a folder asplans/, neverplans/*: Worktrunk copies whole ignored folders, soplans/*copies nothing, and a!line inside a listed folder has no effect.t3.json, with aSetupscript that runs when T3 creates a worktree ("runOnWorktreeCreate": true). Its command iswt step copy-ignored --require-include && mise install && mise run setup. T3 doesn't read.worktreeinclude, sowtcopies the listed files from the main checkout first. It never overwrites a file. Claude Code and the Codex app read.worktreeincludethemselves..github/pull_request_template.md, from theprskill's templateAGENTS.md, and aCLAUDE.mdthat holds only@AGENTS.md- the other files in "Templates" that apply
- Make one real path work end to end. No sample pages, demo data, or placeholder code.
- It's done when
mise run setupandmise run checkpass. Check this on a fresh clone, and in a new worktree fromdelegate_taskwithisolation: "worktree". That worktree holds the.worktreeincludefiles.
For a project with a runnable app, also add a dev task and one E2E check.
It's done only when mise run dev serves the app and its ready check passes.
A library, a template, or a skills repo has no dev task and no E2E check.
Templates
Start each file from its template in this skill's assets/ folder. Replace
every <…> placeholder with a fact from the project. Delete a section or a
line that has no fact yet. A file is done when no placeholder is left.
| Project file | Template | Holds |
.worktreeinclude | worktreeinclude | The local files that a new worktree copies from the main checkout. |
t3.json | t3.json | The Setup script that T3 runs when it creates a worktree. |
AGENTS.md | AGENTS.template.md | Short always-on rules, then pointers such as "Before you do X, read docs/agents/x.md". |
docs/agents/*.md | docs/agents/ | How-tos for agents: git workflow, dev runtime, and verification. Add one only when the repo has facts for it. |
GLOSSARY.md | GLOSSARY.md | Domain terms. Create it when it gets its first term. The domain-modeling skill owns its rules. |
DESIGN.md | DESIGN.md | The visual system of a project with UI. |
PRODUCT.md | PRODUCT.md | Product intent. |
docs/adr/ holds decisions and has no template. The domain-modeling skill
owns its format. Create the folder with the first decision. In a migration,
GLOSSARY.md and docs/adr/ replace CONTEXT.md.
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.

