engineering-standards

Name: engineering-standards
Availability: InStock
Author: LetPeopleWork

Detect SOLID, DRY, YAGNI, and KISS violations with refactoring guidance.

16|4|Updated Feb 10, 2024

Search Tags:#refactoring #DRY #KISS #engineering #code-quality #SOLID #code-review

Ready to run

npx skills add https://github.com/LetPeopleWork/Lighthouse --skill engineering-standards-letpeoplework

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: engineering-standards
Source: https://github.com/LetPeopleWork/Lighthouse/tree/main/.github/.github/agents/skills/engineering-standards
Command: npx skills add https://github.com/LetPeopleWork/Lighthouse --skill engineering-standards-letpeoplework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Core software engineering principles guide teams to write maintainable, scalable code by enforcing disciplined design and preventing technical debt.

Core Features & Use Cases

Detects and guides improvements for SOLID, DRY, YAGNI, and KISS in codebases.
Provides practical refactoring guidance and patterns for common debt scenarios.
Use during code reviews, architectural planning, and debt remediation to raise code quality.

Quick Start

Load the engineering-standards skill during reviews and run a quick scan on a module with multiple responsibilities to identify improvement opportunities. Then apply the suggested refactor patterns from the references catalog.

Frequently Asked Questions about engineering-standards

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

FAQPage Schema

How do I detect SOLID, DRY, and KISS violations during a code review?▼

To detect SOLID, DRY, and KISS violations during code review, scan the module for multiple responsibilities and duplicated logic, then apply concrete detection patterns to identify specific design flaws and technical debt.

What are the best refactoring patterns for resolving technical debt?▼

The best refactoring patterns for technical debt remediation target specific violations of SOLID, DRY, YAGNI, and KISS principles, providing concrete guidance to restructure code, eliminate duplication, and simplify complex modules.

When do I need to enforce software engineering principles in my codebase?▼

You need to enforce software engineering principles during code reviews, architectural planning, and debt remediation to prevent technical debt, ensure maintainability, and guide teams in writing scalable, clean code.

Can I use these engineering standards for architectural planning?▼

Yes, you can use these engineering standards for architectural planning to evaluate module responsibilities against SOLID, DRY, YAGNI, and KISS principles, ensuring disciplined design and scalable code structure before implementation.

How do I scan a module with multiple responsibilities for improvement opportunities?▼

To scan a module with multiple responsibilities, load the engineering standards guidelines to identify violations of SOLID and KISS principles, then apply the suggested refactoring patterns from the references catalog to improve code quality.

Does YAGNI apply to technical debt remediation?▼

YAGNI applies to technical debt remediation by identifying unnecessary functionality that adds complexity, helping teams enforce disciplined design and remove unused code components during refactoring sessions.