TypeScript Development Standards FAQs

Question 1

Why are TODO markers strictly forbidden in this skill?

Accepted Answer

TODO markers are viewed as blocking signals indicating incomplete design or broken contracts. This skill requires addressing these gaps immediately to prevent the accumulation of technical debt and hidden bugs.

Question 2

How does this skill approach type-driven development?

Accepted Answer

It treats TypeScript types as mandatory contracts. Every type utility must be implemented fully with no 'type lies' or stubs, ensuring the implementation strictly delivers what the type signature promises.

Question 3

What happens when a complex task is encountered?

Accepted Answer

The skill triggers a 'Design Before Code' workflow where Claude must document the goal, approach, edge cases, and estimated complexity before writing any implementation logic.

Question 4

Does this skill support type-level testing?

Accepted Answer

Yes, it mandates comprehensive verification for both runtime logic and type-level computations using patterns like Expect and AssertEqual to ensure type safety.

Question 5

Is this skill only for the inferred-types repository?

Accepted Answer

While optimized for the inferred-types repo, its principles of completeness and rigorous TypeScript standards are applicable to any high-stakes TypeScript project.

TypeScript Development Standards

Características Principales

Casos de Uso

TypeScript Development Standards

Características Principales

Casos de Uso