engineering-principles
/engineering-principles
Apply the default engineering bar to non-trivial coding work. Use when planning or changing software; keep trivial edits proportionate.
- Author
- voyager67 ↗
- Repository
- Agent-Workbench ↗
- Licence
- MIT
- Last repository change
- 08.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.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
Apply the default engineering bar to non-trivial coding work. Use when planning or changing software; keep trivial edits proportionate.
Original author description
Apply the default engineering bar to non-trivial coding work. Use when planning or changing software; keep trivial edits proportionate.
How it works
SKILL.md has no level-two headings · 15 lines, 186 words
SKILL.md preview
--- name: engineering-principles description: Apply the default engineering bar to non-trivial coding work. Use when planning or changing software; keep trivial edits proportionate. --- # Engineering Principles Use these as a quality bar, not as a rigid ceremony. Scale the process to the risk and size of the task. 1. **Understand before acting.** Inspect the relevant code, tests, conventions, user goal, and constraints. Surface material ambiguity instead of silently inventing requirements. 2. **Prefer the smallest complete solution.** Avoid speculative features, unnecessary abstractions, new dependencies, and broad rewrites. 3. **Make traceable changes.** Each meaningful edit should support the requested outcome. Preserve unrelated user work and existing conventions. 4. **Prove behavior.** Choose tests and checks that exercise the changed path. Inspect results rather than assuming a command passed. 5. **Debug causes, not symptoms.** Reproduce the issue, trace the failing path, and validate the causal explanation before fixing. 6. **Keep security in scope.** Protect secrets, validate trust boundaries, and seek approval before destructive or externally visible actions. 7. **Report honestly.** Separate completed work, attempted checks, unverified assumptions, and remaining risks. Never invent test results or performance gains. For an obvious one-line change, do not run a full project ceremony. For high-risk changes, increase verification and request human review at the relevant decision points.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · voyager67/Agent-Workbench | 86 | MIT |
| joeblackwaslike/agent-skills | 100 | MIT |
| wolfinApp/wolfin-senior | 100 | MIT |
| Cynnamoroll/factory-stack | 90 | MIT |
| johantor/brain | 86 | Apache-2.0 |
| ericwang200608-beep/LANYANT-Skills | 85 | MIT |
| jstarfilms/vibecode-protocol-suite | 85 | ISC |
Database snapshot: 13.11.2026 · package version edab6555df87 (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
- 100engineer-mode
fstack engineering execution. 23 playbooks, 24 principles, verified work, no slop. Use for /engineer-mode, /poteto-mode, or any non-trivial engineering task. - 90embedded-workbench
Use when starting any non-trivial coding task — loads risk-proportional workflows, engineering policies, and principles for embedded C/C++ firmware development. NOT for trivial single-line fixes, formatting-only changes, or read-only queries. - 100eng-change-checklist
Short checklist of engineering principles to apply before and after non-trivial work. Use when planning or reviewing a non-trivial change, debugging a stubborn failure, designing types or boundaries, or deciding how to sequence a migration. - 100show-diff
Open a tmux split running diffview.nvim so the user can review the agent's recent changes. Use proactively after non-trivial edits, or when the user asks to "show the diff", "open a diff viewer", or similar. - 100software-engineering
For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work,… - 90plan-feature
The Explore to Plan to Code to Commit workflow for any non-trivial change. Forces understanding and an explicit plan before edits, with a one-sentence skip heuristic for trivial work. Use when starting a feature, a refactor, or any change whose steps are not obvious. Pairs with plan mode.