reviewing-typescript-architecture

Evaluate ADRs and architecture decisions against defined testing principles.

1|Updated Jan 6, 2026

Search Tags:#typescript #architecture #review #ADR #quality-assurance #dependency-injection #testing-principles

Ready to run

npx skills add https://github.com/simonheimlicher/spx-claude --skill reviewing-typescript-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewing-typescript-architecture
Source: https://github.com/simonheimlicher/spx-claude/tree/main/plugins/typescript/skills/reviewing-typescript-architecture
Command: npx skills add https://github.com/simonheimlicher/spx-claude --skill reviewing-typescript-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers ensure ADRs and architecture decisions conform to established testing principles, improving architectural integrity and reducing rework.

Core Features & Use Cases

ADR conformity checks: verify alignment with parent decisions and the product/capability/feature hierarchy, and confirm presence of a testing strategy.
Violation detection: identify contradictions to testing principles such as lack of traceability, improper mocking policy, or missing acceptance criteria.
Actionable remediation: provide concrete examples of correct ADRs and guidance to bring architecture in line with requirements.

Quick Start

To begin, supply the ADR text and project context to the skill and request an assessment against testing principles; The skill will output violations, corrective guidance, and example architectures.

Frequently Asked Questions about reviewing-typescript-architecture

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

FAQPage Schema

How do I review TypeScript architecture decisions against testing principles?▼

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.

What makes a good ADR for robust TypeScript architecture?▼

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.

How do I check ADR hierarchy consistency for a TypeScript project?▼

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.

Why does my TypeScript ADR review fail on testing strategy coverage?▼

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.

Can I use this skill to enforce dependency injection in TypeScript ADRs?▼

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.

What is the best way to ensure traceability in TypeScript architecture decisions?▼

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.