philosophy-compliance-workflow

Review code and architecture against minimalist philosophy compliance criteria.

1|Updated Nov 14, 2025

Search Tags:#architecture #minimalism #compliance #philosophy #review #ruthless simplicity #brick

Ready to run

npx skills add https://github.com/rysweet/AzureHayMaker --skill philosophy-compliance-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: philosophy-compliance-workflow
Source: https://github.com/rysweet/AzureHayMaker/tree/main/.claude/skills/philosophy-compliance-workflow
Command: npx skills add https://github.com/rysweet/AzureHayMaker --skill philosophy-compliance-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code and architecture align with Amplihack's ruthlessly simple, brick-based, Zen-inspired philosophy, preventing unnecessary complexity.

Core Features & Use Cases

Systematic philosophy review of architecture and module designs
Criteria for necessity, simplicity, modularity, regenerability, and value
Severity-based violations with actionable recommendations

Quick Start

Initiate a philosophy review for a component or architecture before implementation.

Frequently Asked Questions about philosophy-compliance-workflow

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

FAQPage Schema

How do I conduct a philosophy compliance review for my architecture?▼

Philosophy compliance reviews systematically validate that code and architecture follow ruthless simplicity, single responsibility, and brick principles. Initiate a review before implementation or during refactoring to catch over-engineering, verify well-defined contracts, and ensure regenerability within your modules.

What is Zen-like minimalism and brick philosophy in software design?▼

Zen-like minimalism and brick philosophy emphasize ruthless simplicity, necessity-driven design, and modularity. These principles eliminate unnecessary complexity, enforce single responsibility, define clear public contracts, and ensure components remain simple enough to rebuild—preventing architectural bloat and technical debt.

When should I use architecture reviews before implementation?▼

Conduct architecture reviews before implementation to prevent over-engineering and misaligned design decisions. Pre-merge checks catch violations early, validate module design against simplicity criteria, and ensure your components meet necessity, modularity, and regenerability standards before code ships.

Can I apply philosophy compliance checks during code refactoring?▼

Yes, philosophy compliance reviews validate refactoring work by checking that simplifications maintain single responsibility, preserve public contracts, and improve regenerability. Use severity-based violation reports to guide refactoring decisions and confirm architectural alignment with ruthless simplicity principles.

How do I detect over-engineering in my codebase?▼

Philosophy compliance reviews detect over-engineering by evaluating necessity, simplicity, modularity, and regenerability criteria. Severity-based violations reveal where components lack clear purpose, have bloated interfaces, violate single responsibility, or become too complex to rebuild—with actionable recommendations to restore balance.

What makes a module design regenerable?▼

Regenerability means a module is simple and well-understood enough to rebuild from scratch if needed. Philosophy compliance reviews verify this by checking single responsibility, well-defined public contracts, minimal dependencies, and absence of hidden complexity—ensuring your design stays maintainable and adaptable.