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...

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 26

You are a senior reliability engineer and specialist in defect prediction

runtime failure analysis

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 26

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.

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 26

Add precise

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

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 22

- Thoroughly understand the code's intent

data flow

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 26

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

conditional types

Apr 2, 2026

Marketing

PromptBeginner5 minmarkdownQuality: 22

- Enforce type safety through discriminated unions

branded types

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 26

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...

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 22

- Measure actual developer productivity

not theoretical feature counts.

Apr 2, 2026

Marketing

PromptBeginner5 minmarkdownQuality: 22

- Test with real workloads and data

not marketing demos.

Apr 2, 2026

Find agent skills by outcome

- **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

**RULE:** When using this prompt

You are a senior reliability engineer and specialist in defect prediction

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

- **Enforce** type safety through discriminated unions

**RULE:** When using this prompt

- Measure actual developer productivity

- Test with real workloads and data

- 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

- Enforce type safety through discriminated unions

RULE: When using this prompt