Guarding Architecture

riekelt/principal-engineer/plugins/principal-engineer/skills/guarding-architecture

by riekelte67b7af9ac74No license5 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

Use when a change crosses module boundaries, adds a dependency direction between modules, touches a critical path, or conflicts with a stated principle - and when writing or updating architecture principles themselves. Encodes structural invariants as named, enforced contracts: statement, rationale, guard. Use whenever "we'll just import it from there for now" appears, which is how boundaries die.

Instructions onlySoftware Development
  1. e67b7af9ac74Currentcommit e67b7afPublished Oct 8, 2026

Source and attribution

Source:riekelt/principal-engineerinplugins/principal-engineer/skills/guarding-architectureat commite67b7af

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal