stack-conventions
Skill0 starsChanged 5 months agoMITView on GitHub
Per-technology conventions and the exact lint/typecheck/test/build commands the squad agents must run. Use when you need the idiomatic rules and verify commands for a project's stack (TypeScript, Vue, NestJS, Go, PHP, plain HTML/JS).
In this repositoryOne other file it gives its agents.
- methodSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
Read-only signals, in priority order:
≈ “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
Stack conventions
This skill carries the conventions and verify commands for each stack the squad supports. Don't apply generic advice — detect the project's actual stack, then read the matching file(s) below. A repo can be polyglot (e.g. a Vue frontend with a Go or NestJS backend); load every file that applies.
How to detect the stack
Read-only signals, in priority order:
CLAUDE.md/README.md— a declared stack and house rules. These override anything here when they conflict.package.jsondeps →typescript(tsconfig.json),vue→ vue.md,@nestjs/*→ nestjs.md, otherwise Node/plain JS → html-js.md + typescript.md.go.mod→ go.md.composer.json→ php.md.- Confirm with
nest-cli.json,vite.config.*,*.vue,phpstan.neon,.golangci.yml, the test runner in use.
Reconcile with the repo
The commands below are the standard for each stack, but always prefer the repo's own configured scripts when they exist (package.json scripts, composer.json scripts, Makefile, CI workflow) — they encode the real flags/paths. Use these files to know what to check (typecheck, lint, format, test, build) and fall back to these commands when the repo defines no script. If a tool isn't installed, say so and give the install command — never silently skip a gate.
Files
- typescript.md — TypeScript (any TS project)
- vue.md — Vue 3 SFC apps
- nestjs.md — NestJS services
- go.md — Go modules
- php.md — modern PHP
- html-js.md — plain HTML + JS / Node
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.