Does this skill write implementation code?

No, this skill is specifically designed to write ADRs that constrain and guide implementation rather than producing the implementation code itself.

How does the skill handle different testing levels?

It categorizes tests into Level 1 (Unit/Logic), Level 2 (Integration/Tools), and Level 3 (E2E/External Services), requiring justification for each assignment in every ADR.

Why is 'mocking' discouraged in this skill's methodology?

The skill promotes dependency injection and testing real behaviors over simulations (mocks) to ensure that the test 'reality' matches the production environment.

What is an ADR in the context of this skill?

An Architecture Decision Record (ADR) is a document that captures an important architectural decision, including the context, the decision itself, and the trade-off consequences.

TypeScript Architecture & ADRs

Name: TypeScript Architecture & ADRs
Author: simonheimlicher

bysimonheimlicher

•

Learning & Documentation

Generates standardized Architecture Decision Records (ADRs) for TypeScript projects with a focus on testability and type safety.

About

This skill empowers developers to document architectural choices systematically using the Architecture Decision Record (ADR) format within TypeScript environments. It enforces critical engineering principles such as mandatory testing levels, dependency injection patterns to eliminate mocking, and strict type safety standards. By streamlining the creation of project-wide, capability-specific, and feature-specific decisions, it ensures architectural consistency across the entire codebase while integrating seamlessly with Technical Requirement Documents (TRDs).

Key Features

Enforcement of Dependency Injection patterns over mocking
Automated ADR generation using standardized templates
1 GitHub stars
Strict TypeScript type-safety guidelines and 'any' type justification
Hierarchical decision management (Product, Capability, and Feature levels)
Mandatory Testing Strategy section with 3-level assignments

Use Cases

Documenting technical trade-offs and consequences for complex feature implementations
Defining cross-component testing strategies and verification criteria
Establishing architectural standards and patterns for a new TypeScript project

About

Key Features

Enforcement of Dependency Injection patterns over mocking
Automated ADR generation using standardized templates
1 GitHub stars
Strict TypeScript type-safety guidelines and 'any' type justification
Hierarchical decision management (Product, Capability, and Feature levels)
Mandatory Testing Strategy section with 3-level assignments

Use Cases

Documenting technical trade-offs and consequences for complex feature implementations
Defining cross-component testing strategies and verification criteria
Establishing architectural standards and patterns for a new TypeScript project