best-practices

Guide software engineering practices for programming, refactoring, system design, and code review.

17|1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/Parallel-7/FlashForgeWebUI --skill best-practices-parallel-7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: best-practices
Source: https://github.com/Parallel-7/FlashForgeWebUI/tree/main/.claude/skills/best-practices
Command: npx skills add https://github.com/Parallel-7/FlashForgeWebUI --skill best-practices-parallel-7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides universal guidance to improve code quality, maintainability, and reliability across all programming languages and projects, preventing common pitfalls and ensuring production-ready software.

Core Features & Use Cases

  • Fundamental Principles: Covers SOLID, DRY, KISS, YAGNI for robust design.
  • Architectural Patterns: Guides on SoC, SSOT, LoD, CQS, DbC for scalable systems.
  • Operational Reliability: Ensures ETC, PoLP, CoC, Idempotency for stable deployments.
  • Use Case: When refactoring a complex module, use this Skill to ensure adherence to SOLID principles and reduce technical debt.

Quick Start

Apply the KISS principle to the current coding task.

Frequently Asked Questions about best-practices

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

FAQPage Schema
What are the fundamental software engineering best practices for writing maintainable code?

Apply SOLID, DRY, KISS, and YAGNI principles to ensure clean, maintainable, and production-ready code quality across all languages and projects.

How do I apply SOLID principles and architectural patterns when refactoring a complex module?

Apply SOLID principles alongside architectural patterns like SoC, SSOT, LoD, CQS, and DbC to reduce technical debt and achieve scalable system design.

What architectural patterns should I use for scalable system design?

Use architectural patterns such as Separation of Concerns (SoC), Single Source of Truth (SSOT), Law of Demeter (LoD), Command-Query Separation (CQS), and Design by Contract (DbC).

Does this coding standards guidance work with any programming language?

Yes, these coding standards provide universal best practices applicable across all programming languages, ensuring operational reliability and maintainable code.

What operational reliability concepts ensure stable production deployments?

Operational reliability concepts ensuring stable deployments include Easier to Change (ETC), Principle of Least Privilege (PoLP), Convention over Configuration (CoC), and Idempotency.

When should I not use the KISS principle in software design?

While KISS applies universally, complex architectural patterns like SoC, SSOT, or CQS may be necessary when designing scalable systems requiring strict separation and operational reliability.