renaissance-architecture

First-principles software design involves identifying core constraints and proposing a minimal architecture that satisfies requirements. This skill guides teams to create genuinely new architectures by evaluating choices based on fundamental needs rather than derivative patterns.

First-principles thinking in software design breaks down complex system requirements into fundamental constraints. It provides a framework for evaluating architecture choices, resolving conflicts, and ensuring human-legible systems through clear reasoning and documentation.

Document architecture decisions by recording the reasoning, constraints, and criteria used during design. This skill encourages documenting clear decision rationale and cloud or local defaults to accelerate team onboarding and simplify future system maintenance.

Yes, first-principles design applies across feature planning, brainstorming, and strategy discussions. It supports these processes by providing clear decision criteria for evaluating architecture choices, local-first design, and cloud pragmatics.

Derivative patterns should be avoided when teams need genuinely new solutions. This skill prevents commentary-only approaches by guiding exploration of new architectures using first-principles thinking, focusing on simplicity where it matters most.

Evaluating local-first design versus cloud pragmatics requires applying first-principles thinking to identify core constraints. This skill provides a framework with clear decision criteria to choose the most minimal, human-legible architecture that satisfies project requirements.