architecture-compliance

Architectural compliance audits code against defined rules to identify deviations from patterns like functional programming, Result<T,E>, and proper imports while flagging prohibited patterns such as classes, enums, non-null assertions, and hardcoded strings. Use it during code reviews to catch violations early.

The Tetris architecture requires functional programming, Result<T,E> for game logic, proper import conventions, co-located tests, type-safe i18n, and useId for dynamic IDs. It prohibits classes, enums, any types, non-null assertions, hardcoded strings, and interfaces in React components.

Yes. Run compliance audits during feature implementation, refactoring, and validation workflows to detect prohibited patterns and ensure required patterns are present, keeping code aligned with architectural standards throughout development.

Type-safe compliance auditing enforces proper import conventions, eliminates any types and non-null assertions, and requires Result<T,E> patterns for game logic, reducing runtime errors and improving code reliability across your codebase.

The Skill detects classes, enums, any type usage, non-null assertions, hardcoded strings, and interfaces in React components—common patterns that violate functional architecture and type safety in TypeScript-based projects.

Co-located tests keep test files alongside source code, improving maintainability and ensuring tests stay synchronized with implementation changes. Architecture compliance validates this structure during audits and code reviews.