monorepo-bootstrap
Skill0 starsChanged 5 months agoMITView on GitHub
Scaffold a Turborepo + pnpm monorepo with shared config, a testing harness, and CI in one pass. Use at the start of a new multi-package project. Adaptable to Nx / other tooling.
In this repository7 other files it gives its agents.
- ai-proxy-guardSkill
- consent-complianceSkill
- context-checkpointSkill
- review-gateSkill
- rls-securitySkill
- security-reviewSkill
- test-and-fixSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 12
Add a shared config package: TypeScript config, lint/format presets, and any UI/style preset.
- Distinctive: line 14
Add CI (build + typecheck + lint + test on PR), build caching, and a pre-commit hook.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
monorepo-bootstrap
Stand up a clean multi-package project foundation so shared code is built once and reused.
Do
- Scaffold a Turborepo + pnpm workspace with
apps/(deployables) andpackages/(shared code). - Add a shared config package: TypeScript config, lint/format presets, and any UI/style preset.
- Set up a testing harness (unit + e2e + accessibility) with one passing sample test.
- Add CI (build + typecheck + lint + test on PR), build caching, and a pre-commit hook.
- Establish the rule: apps consume shared packages by workspace name — never copy/fork shared code into an app.
Adapting
The pattern holds for Nx, Lerna, or plain pnpm workspaces — what matters is: shared packages, one config source, a test harness, and CI gating every change. Swap the tool, keep the shape.
Done when
build, test, and lint pass across the empty workspace; CI is green on a trivial PR.
Token tactics
Mechanical — route to a cheap/mid model; verify once. Record the conventions you applied to
MEMORY.md so later tasks don't re-explain the project.
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.