tech-lead-setups
Skill8 starsChanged 43 days agoNo licenceView on GitHub
Scaffold a new project as the Tech Lead would in Sprint 0, after the task breakdown and before coding standards are written. Grills on folder structure, architectural patterns, commit hooks, tooling, the test harness, and stubs, then executes the scaffold: directory layout, local tooling config, pre-commit hooks, a test harness with one e2e smoke flow, and endpoint/page stubs that return mock responses so frontend and backend can build in parallel from day one. On a running project it audits first and adds only what is missing. Use when the user wants to set up, bootstrap, or scaffold a project, add a test or e2e harness, stand up the repo skeleton, do Sprint 0, or asks to "set up the project".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- snowfluke/tech-lead-skillsword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- snowfluke/tech-lead-skills★ 8100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository19 other files it gives its agents.
- adopt-flowSkill
- api-specSkill
- coding-standardSkill
- deployment-planSkill
- github-project-initSkill
- groomingSkill
- init-claudeSkill
- lead-reviewSkill
- product-discoverySkill
- project-docsSkill
- security-standardSkill
- task-breakdownSkill
- technical-specSkill
- test-auditSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- troubleshootingSkill
- us-ac-formatterSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.