lean-senior-engineering
/lean-senior-engineering
Implement or review a clear code change using existing patterns and focused tests. Use when desired behaviour is known; route unexplained failures to systematic-debugging first.
- Author
- RaditteAnggoro ↗
- Repository
- skill-for-lazy-developer ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement or review a clear code change using existing patterns and focused tests. Use when desired behaviour is known; route unexplained failures to systematic-debugging first.
Original author description
Implement or review a clear code change using existing patterns and focused tests. Use when desired behaviour is known; route unexplained failures to systematic-debugging first.
How it works
- Choose the change
- Work at the requested level
- Implement and check
- Review, audit, and debt requests
- Finish
SKILL.md preview
--- name: lean-senior-engineering description: "Implement or review a clear code change using existing patterns and focused tests. Use when desired behaviour is known; route unexplained failures to systematic-debugging first." --- # Lean Senior Engineering Deliver the requested behaviour with as little additional complexity as the codebase allows. Explicit user requirements and repository conventions take precedence over this skill. Minimum code means a complete, readable solution, including affected callers and tests. ## Choose the change Inspect the affected code, callers, and nearest tests. Expand the search only as dependencies require. Account for configuration, fixtures, exports, and contracts that must change with it. Prefer the first adequate option: 1. Existing behaviour or configuration that already solves the request. 2. An existing project helper, component, service, or pattern. 3. A standard library or native platform feature, when it fits project conventions. 4. An already installed dependency. 5. A small, direct implementation. 6. A new dependency or abstraction, only when it solves a demonstrated need. Readable code and correct behaviour outrank line count. Preserve validation, useful error handling, accessibility, compatibility, and data integrity. Avoid new options or extension points for hypothetical future features. ## Work at the requested level Use `full` by default. Honour a level requested in plain language for the current conversation; do not claim a persistent setting was saved. - `lite`: implement the user's chosen approach; mention a materially simpler option briefly when useful. - `full`: choose the smallest complete approach within the request. - `ultra`: challenge costly assumptions with concrete alternatives before substantial work; the user's explicit choice still wins. - `off`: stop applying this skill's preferences, retaining normal project instructions. ## Implement and check For a fix, establish the failing behaviour and inspect other callers of the changed code. For a feature, identify acceptance criteria before implementation. Do not turn clear, small requests into a design interview. Use short feedback cycles. Add focused behaviour tests for meaningful logic or regression risk. Read [test-design.md](references/test-design.md) when choosing test boundaries, using mocks, or writing a regression test. Low-impact text or styling edits need proportionate inspection, not artificial tests. Run relevant existing checks after the final change. Report their actual scope and outcome. Keep unrelated improvements out of the diff; mention a serious adjacent issue separately. ## Review, audit, and debt requests Read [review-and-debt.md](references/review-and-debt.md) for reviews, audits, and debt inventories. These requests produce findings; implement only when the user also asks for changes. ## Finish Lead with the result. Include a short verification statement and material gaps. Never invent test execution, performance gains, token savings, or an independent review. A requested implementation is complete only when the requested behaviour and necessary checks are addressed or a concrete blocker is reported.
Files in this package (4)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/review-and-debt.md 2 KB
- references/test-design.md 2 KB
Versions
The database has no other skills named lean-senior-engineering.
Database snapshot: 13.11.2026 · package version 341a07ae4df1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100senior-qa
This skill should be used when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality". Use for React/Next.js testing with Jest, React… - 100code-review-senior
Senior code review skill. Analyze code changes for security, performance, code quality, architecture, and testing. Use when reviewing code changes. - 90systematic-debugging
Plan, implement, or review systematic debugging work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests systematic debugging work. - 90lean
Lean coding - smallest working change, least code, short answers. Use when asked to keep it lean or cheap. - 100senior-qa
Testing for React/Next.js with Jest, React Testing Library, and Playwright. Use when generating tests, writing unit tests, analyzing coverage, scaffolding E2E tests, configuring Jest, or improving test quality. - 100lean-workflow
Route Lean 4 work through a repository's Mathlib/Lake conventions. Use when editing Lean files, checking source fidelity or axioms, searching dependencies, validating focused targets, or protecting dependency build artifacts.