skills.rest
outcomeeng
outcomeengOFFICIAL
Explore all skills by this author →
WebsiteGitHub

reviewing-typescript-architecture

Audit ADRs to enforce atemporal voice and testing principles.

1|Updated Jan 6, 2026
Search Tags:#architecture#adr#review#principles#software-design#atemporal
One-click install
npx skills add https://github.com/outcomeeng/claude --skill reviewing-typescript-architecture-outcomeeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-typescript-architecture
Source: https://github.com/outcomeeng/claude/tree/main/plugins/typescript/skills/reviewing-typescript-architecture
Command: npx skills add https://github.com/outcomeeng/claude --skill reviewing-typescript-architecture-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review ADRs and architectural decisions to enforce testing principles and an atemporal voice, rejecting any narration of code state.

Core Features & Use Cases

  • Enforces atemporal voice in ADRs and ensures references align with the decision hierarchy.
  • Flags violations related to testing principles, such as no-mocking, dependency injection, and the need for a defined Testing Strategy.
  • Supports loading complete ADR/PDR hierarchy for spec-driven work items and verifies consistency with parent decisions.

Quick Start

Provide an atemporal rewrite of an ADR to conform to durable architectural principles.

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 ADRs to ensure they follow atemporal architectural principles?▼

To review ADRs for atemporal architectural principles, audit the decisions to reject any narration of current code state, ensuring references align with the decision hierarchy and enforce invariants over file states.

What is an atemporal voice in software design and why does it matter for ADRs?▼

An atemporal voice in software design ensures ADRs reference durable invariants rather than current code, migration plans, or file states, preventing documentation from becoming obsolete as the codebase evolves.

How do I enforce a testing strategy in an architectural decision record?▼

Enforcing a testing strategy in an architectural decision record requires flagging violations related to testing principles like no-mocking and dependency injection, while verifying an explicit testing strategy is defined.

Can I verify ADR consistency against a parent decision hierarchy for spec-driven work?▼

Yes, you can verify ADR consistency by loading the complete ADR and PDR hierarchy for spec-driven work items, checking that individual architectural decisions align with parent decisions.

What are the limitations of reviewing architectural decisions using an atemporal approach?▼

The limitation of an atemporal review approach is that it strictly rejects references to migration plans or current file states, requiring all architectural decisions to be rewritten as durable invariants.

Related Skills

Explore More Software Engineering Skills→
simonheimlichersimonheimlicher
1

reviewing-typescript-architecture

Evaluate ADRs and architecture decisions against defined testing principles.

Community
Advanced
outcomeengineeringoutcomeengineering
1

reviewing-python-architecture

Review Architecture Decision Records against testing principles and parent PDR constraints.

Official
Intermediate
wachawowachawo

tdd

Enforces vertical-slicing, behavior-driven tests with red-green-refactor workflow for software engineering tasks.

Community
Intermediate
outcomeengoutcomeeng
1

reviewing-python-architecture

Review ADRs against testing principles, Atemporal voice rules, and PDR constraints.

Official
Advanced