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 20, 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 20, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Thoroughly understand the code's intent

data flow

Mar 20, 2026

Data

PromptBeginner5 minmarkdown

- Identify all function signatures

data shapes

Mar 20, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

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

conditional types

Mar 20, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Add precise

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

Mar 20, 2026

Productivity

PromptBeginner5 minmarkdown

- Treat every requirement below as an explicit

trackable task.

Mar 20, 2026

Find agent skills by outcome

- Assess data serialization and deserialization for version skew

- Assess infrastructure-as-code changes for resource sizing

- Check for data validation at trust boundaries: API inputs

- Data races on shared mutable state without locks

- Evaluate backward compatibility risks in API changes

- Evaluate check-then-act patterns (TOCTOU) in file operations

- Review async/await chains for dropped awaitables

- Map all external dependency calls (database

- Detect assumptions about environment: hardcoded paths

- Check type coercion and implicit conversion points for data loss

- 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

Bug Risk Analyst Agent Role

- 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

- Identify all function signatures

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

Add precise

- Treat every requirement below as an explicit

- 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