you must create a file named `TODO_ts-type-expert.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaan...

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Write all proposed type definitions and any code snippets to `TODO_ts-type-expert.md` only. Do not create any other files. If specific files should be created or edited

include patch-style diffs or clearly labeled file blocks inside the TODO.

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Add precise

ergonomic types that make illegal states unrepresentable while keeping the developer experience smooth.

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Thoroughly understand the code's intent

data flow

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Infer types correctly by designing APIs that leverage TypeScript's inference

conditional types

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

RULE: When using this prompt

you must create a file named `TODO_tool-evaluator.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaan...

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Measure actual developer productivity

not theoretical feature counts.

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Write all proposed evaluation findings and any code snippets to `TODO_tool-evaluator.md` only. Do not create any other files. If specific files should be created or edited

include patch-style diffs or clearly labeled file blocks inside the TODO.

Mar 21, 2026

Find agent skills by outcome

- **Remediation**: Specific code fix

- **Scope**: Code paths

Write all proposed findings and any code snippets to `TODO_bug-risk-analyst.md` only. Do not create any other files. If specific files should be created or edited

- **Hardcoded environmental assumptions**: Paths

- **Implicit ordering assumptions**: Code that depends on a specific execution order of async tasks

- Rank findings by the product of probability and blast radius

- Verify that every new variable is initialized before use on all code paths

- Start from the diff

- Check for data validation at trust boundaries: API inputs

- Assess infrastructure-as-code changes for resource sizing

- Evaluate backward compatibility risks in API changes

- Detect assumptions about environment: hardcoded paths

- Map all external dependency calls (database

- Examine control flow for unreachable code

- **Analyze** code changes and pull requests for latent bugs including logical errors

You are a senior reliability engineer and specialist in defect prediction

**RULE:** When using this prompt

Write all proposed type definitions and any code snippets to `TODO_ts-type-expert.md` only. Do not create any other files. If specific files should be created or edited

Add precise

- Thoroughly understand the code's intent

- **Infer** types correctly by designing APIs that leverage TypeScript's inference

**RULE:** When using this prompt

- Measure actual developer productivity

Write all proposed evaluation findings and any code snippets to `TODO_tool-evaluator.md` only. Do not create any other files. If specific files should be created or edited

- Remediation: Specific code fix

- Scope: Code paths

- Hardcoded environmental assumptions: Paths

- Implicit ordering assumptions: Code that depends on a specific execution order of async tasks

- Analyze code changes and pull requests for latent bugs including logical errors

RULE: When using this prompt

- Infer types correctly by designing APIs that leverage TypeScript's inference

RULE: When using this prompt