key-guidelines

Standardize software development with DRY, KISS, YAGNI, SOLID, and TDD.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/gendosu/agent-skills --skill key-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: key-guidelines
Source: https://github.com/gendosu/agent-skills/tree/main/skills/key-guidelines
Command: npx skills add https://github.com/gendosu/agent-skills --skill key-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Core development principles and standards to ensure consistent, high-quality code across teams and projects.

Core Features & Use Cases

  • Establishes and enforces DRY, KISS, YAGNI, SOLID, and TDD
  • Guides micro-commit workflows and disciplined documentation
  • Improves code reviews and long-term maintainability

Quick Start

Audit your codebase against the guidelines and start applying DRY, KISS, YAGNI, SOLID, and TDD in daily tasks.

Frequently Asked Questions about key-guidelines

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

FAQPage Schema
What are the core coding standards for maintaining high-quality software?

Core coding standards for maintaining high-quality software involve applying DRY, KISS, YAGNI, SOLID, and TDD principles. These guidelines standardize development practices to ensure consistent code design, reviews, and long-term maintainability across teams.

How do I apply SOLID principles and TDD in my development workflow?

To apply SOLID principles and TDD in your development workflow, audit your codebase against established guidelines and integrate test-driven development into daily tasks. This approach guides code design from feature inception to deployment using a micro-commit workflow.

When should I use YAGNI and KISS principles in code reviews?

Use YAGNI and KISS principles in code reviews when evaluating code complexity and unnecessary features. These coding standards enforce high-quality, consistent code by ensuring developers only implement what is needed and keep solutions simple.

Can I use these coding guidelines across different teams and projects?

Yes, you can use these coding guidelines across different teams and projects. The standards are designed to be universally applicable, guiding task planning, code design, and reviews from feature inception to deployment while emphasizing documentation and security.

What is the best way to enforce DRY and micro-commit workflows in software engineering?

The best way to enforce DRY and micro-commit workflows in software engineering is to standardize development practices with strict guidelines. Auditing your codebase against DRY, KISS, YAGNI, SOLID, and TDD ensures disciplined documentation and consistent code quality.

Why does my codebase lack consistency despite having development guidelines?

Your codebase lacks consistency if development guidelines do not strictly enforce DRY, KISS, YAGNI, SOLID, and TDD. Standardizing software development practices across teams and applying a micro-commit workflow improves code reviews and long-term maintainability.