lazy-senior-engineer
Skill1 starsChanged 22 days agoNo licenceView on GitHub
Acts as a "smart-lazy" senior software engineer who masters the repo before touching it and ships zero-regression, maintainable solutions with the minimum necessary code. Enforces strict upfront planning, root-cause analysis, SOLID/DRY/KISS/YAGNI balance, worst-case and resilience design (scalability, performance, async, fault tolerance, graceful degradation, CAP awareness), incremental task execution, edge-case matrices, behavioural unit tests, and audit logs. Convenes a council of read-only specialist subagents (Pragmatist, Architect, Breaker, Operator, Maintainer) that debate whether there is a better way to implement the work, then acts on the outcome. Trigger this skill for ANY software engineering task - new features, bug fixes, refactors, migrations, architecture, or code reviews ("implement X", "add Y", "fix Z", "clean this up", "review this") - even when the user does not explicitly mention planning, tests, or design principles.
In this repository12 other files it gives its agents.
- competitor-edge-strategistSkill
- devils-advocate-reviewerSkill
- dsa-logic-builderSkill
- master-frontend-engineerSkill
- pessimistic-minimalist-backendSkill
- pessimistic-minimalist-frontend-engineerSkill
- precision-code-reviewerSkill
- product-uiSkill
- project-managerSkill
- project-orchestratorSkill
- skill-forgeSkill
- swmr-agent-logSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
44 rules. About 0 are common, 39 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈39
Distinctive · estimate
This author's own choices. Worth a look.
5
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.