engineering-principles
Skill2 starsChanged 9 days agoNo licenceView on GitHub
Apply the 24 engineering principles to concrete design, implementation, testing, measurement, refactoring, and delegation decisions. Use when a user names a principle, another skill points to one, or a multi-step engineering task needs a rule for a real tradeoff. Read the triggered leaf before citing it, and name the decision it changed.
22 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- SwiftyJunnos/skillstheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- Azure/agent-app-mcptheir own version, first seen Nov 8, 2026
- the-inconvenience-store/skillsedited, first seen Nov 6, 2026
- Azure/gpt-rag-mcptheir own version, first seen Nov 2, 2026
- sreejithraman/SreeStacktheir own version, first seen Nov 1, 2026
Used with
Projects with it also use component-release, how and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
jaydubya818Skillhow
Use for runtime, ownership, layering, code-walkthrough, and placement questions.
Also in 3 projects that use this
- jaydubya818Skill
why
Use when design rationale must be recovered from source history and available records.
Also in 3 projects that use this
MicrosoftSkillwriting-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Also in 4 projects that use this
- MicrosoftSkill
release
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 9 projects that use this
GoogleSkillcodebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Also in 4 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- the-inconvenience-store/skills★ 115% same
Wrote their own version · 21
- Azure/agent-landing-zone★ 1.2ksame name
- Azure/GPT-RAG★ 1.2ksame name
- Azure/agent-app-ingestion★ 188same name
- Azure/gpt-rag-ingestion★ 188same name
- Azure/agent-app-orchestrator★ 107same name
- Azure/gpt-rag-orchestrator★ 107same name
- Azure/agent-app-mcp★ 22same name
- Azure/gpt-rag-mcp★ 22same name
- Azure/bicep-ptn-aiml-landing-zone★ 19same name
- Azure/agent-app-ui★ 10same name
11 more not listed
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 repository28 other files it gives its agents.
- adversarial-reviewSkill
- ask-ericSkill
- bug-diagnosisSkill
- business-discoverySkill
- codebase-investigationSkill
- decision-mappingSkill
- delivery-planningSkill
- delivery-proofSkill
- feature-implementationSkill
- idea-assessmentSkill
- issue-triageSkill
- multi-agent-deliverySkill
- performance-investigationSkill
- pr-deliverySkill
- process-improvementSkill
- project-environmentSkill
- project-maintenanceSkill
- project-principlesSkill
- project-releaseSkill
- refactoringSkill
- session-continuitySkill
- standards-spec-reviewSkill
- system-verificationSkill
- technical-designSkill
- technical-writingSkill
- test-driven-developmentSkill
- verification-harnessSkill
- workflow-prototypeSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
0
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 measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “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.