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

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Thoroughly understand the code's intent

data flow

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

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

conditional types

Apr 2, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Add precise

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

Apr 2, 2026

Find agent skills by outcome

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

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

- **Hardcoded environmental assumptions**: Paths

- Flag findings with no automated detection path (no test

- 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

- Review async/await chains for dropped awaitables

- Detect assumptions about environment: hardcoded paths

- Map all external dependency calls (database

- Examine control flow for unreachable code

- **Evaluate** state machine fragility in agent definitions

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

- Assign each task a stable ID (e.g.

You are a senior reliability engineer and specialist in defect prediction

- Treat every requirement below as an explicit

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

- Thoroughly understand the code's intent

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

Add precise

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

- Hardcoded environmental assumptions: Paths

- Evaluate state machine fragility in agent definitions

- 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