engineering-principles

Applies Clean Code, SOLID, and Clean Architecture standards during implementation, review, and refactoring.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/bbenefield89/skills --skill engineering-principles-bbenefield89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-principles
Source: https://github.com/bbenefield89/skills/tree/main/skills/engineering-principles
Command: npx skills add https://github.com/bbenefield89/skills --skill engineering-principles-bbenefield89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Codebases drift toward inconsistent quality when teams lack shared, concrete engineering standards. This Skill supplies a common vocabulary of Clean Code, SOLID, and Clean Architecture rules so implementation, code review, and refactoring all follow the same proportional quality constraints. ## Core Features & Use Cases - Branch-based workflow: Selects between implementation, review, explicit refactor, or scope-clarification modes depending on the task context. - Structured review findings: Reports each violation with severity, location, principle, impact, and the smallest useful fix using a defined checklist format. - Proportional design guidance: Applies principles as constraints without speculative abstraction or architecture ceremony, respecting repository-specific conventions. - Use Case: During a pull request review, invoke this Skill to inspect the changed files and receive a findings list naming each violated principle, its maintainability impact, and a concrete minimal correction. ## Quick Start Use the engineering-principles skill to review the changes in this branch and report any Clean Code or SOLID violations with suggested fixes.

Frequently Asked Questions about engineering-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply SOLID principles during code review?

Use the review branch of this Skill to inspect the requested scope against the review checklist covering SRP, OCP, LSP, ISP, and DIP. Each material finding is reported with severity, location, principle, impact, and the smallest useful fix.

How to enforce Clean Code standards without over-engineering?

Apply principles proportionally by preferring the smallest design that gives clear responsibility, testability, and change leverage. Introduce abstractions only for demonstrated variation, test leverage, or locality, never for speculative generality.

Does this Skill modify code during a review?

No. In review mode it only inspects the requested scope and reports material violations without editing files. Code changes happen only in implementation or explicit refactor branches within an approved scope.

Is a function over 12 lines automatically a violation?

No. Length alone is not a violation. A function over roughly 12 logical lines only triggers scrutiny for mixed responsibilities, mixed abstraction levels, or extractable policy, and findings must explain the actual problem.

When do repository conventions override these principles?

Repository-specific standards override generic guidance when the project deliberately chooses another convention. A proportional exception requires a concrete reason and a stated tradeoff.