philosophy-review

Guide architectural decision-making and code review with a five-layer analysis framework.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/ChanningHe/dotfiles --skill philosophy-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: philosophy-review
Source: https://github.com/ChanningHe/dotfiles/tree/main/claude/skills/philosophy-review
Command: npx skills add https://github.com/ChanningHe/dotfiles --skill philosophy-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through architectural decision-making and rigorous code review, promoting pragmatic design and consistent quality.

Core Features & Use Cases

  • Architectural Tenets: emphasizes data-structure-first thinking, backward compatibility, simplicity, and pragmatism to prevent over-engineering.
  • Structured Review Framework: five-layer analysis (Data Structures, Special Cases, Complexity, Impact, Pragmatism) to diagnose design quality and risks.
  • Output Templates: standardized review format that surfaces recommended improvements and rationale.

Quick Start

Provide a structured architectural review and code critique for a given code proposal.

Frequently Asked Questions about philosophy-review

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

FAQPage Schema
How do I perform a structured code review for architectural design proposals?

Perform a structured code review by applying a five-layer analysis framework covering data structures, special cases, complexity, impact, and pragmatism. This approach diagnoses design quality, surfaces trade-offs, and generates standardized templates capturing decisions and actionables.

What is the best way to evaluate software complexity and prevent over-engineering in architecture?

Evaluate software complexity and prevent over-engineering by emphasizing data-structure-first thinking, backward compatibility, and pragmatism. This principled evaluation framework identifies unnecessary design risks and guides teams toward pragmatic, simplified architectural decisions.

Can I use a standardized review template to capture architectural decisions and trade-offs?

Yes, you can use a standardized review template to capture architectural decisions, trade-offs, and actionables. The template surfaces recommended improvements and rationale, ensuring consistent quality and rigorous evaluation across software projects.

How do you analyze data structures and special cases during a code critique?

Analyze data structures and special cases by applying the initial layers of the five-layer analysis framework. This method prioritizes data-structure-first thinking to rigorously diagnose design quality and identify edge-case risks in code proposals.

When do I need a principled architectural evaluation framework for my software project?

You need a principled architectural evaluation framework when guiding teams through complex decision-making and rigorous code review at scale. It delivers consistent quality by applying structured analysis to complexity judgments and design proposals.