reviewing-typescript-architecture

Review TypeScript architecture decisions by evaluating ADRs for consistency and traceability across product, capability, and feature hierarchies. This skill checks alignment with testing principles, dependency injection, and acceptance criteria, returning violations and concrete corrective guidance.

A good ADR for TypeScript architecture includes explicit trade-offs, dependency-injection-friendly designs, clear acceptance criteria, and a defined testing strategy. It must align with parent decisions and enforce a no-mocking policy to ensure traceability and architectural integrity.

Check ADR hierarchy consistency by verifying that feature-level decisions trace back to capability and product decisions. This skill evaluates spec-driven work items, identifies contradictions like improper mocking policies, and outputs a verdict with suggested corrections.

TypeScript ADR reviews fail on testing strategy coverage when acceptance criteria are missing, mocking policies are improper, or designs lack dependency injection. This skill detects these violations against defined testing principles and provides example architectures for remediation.

Yes, you can enforce dependency injection in TypeScript ADRs with this skill. It evaluates submitted ADR text and project context, confirms dependency-injection-friendly designs, checks for explicit trade-offs, and returns actionable corrections if violations are found.

The best way to ensure traceability in TypeScript architecture decisions is to review ADRs against established testing principles. This skill checks spec-driven work items for consistency across the ADR hierarchy, detects missing acceptance criteria, and provides corrective guidance.