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

May 11, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 28

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.

May 11, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 24

- Thoroughly understand the code's intent

data flow

May 11, 2026

Coding & Debugging

PromptBeginner5 minmarkdownQuality: 28

Add precise

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

May 11, 2026

Find agent skills by outcome

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

- Flag findings with no automated detection path (no test

- Check that memory read/write operations specify behavior for cold starts

- 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 non-atomic read-modify-write sequences on shared variables

- 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

- Treat every requirement below as an explicit

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

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

Add precise

- Hardcoded environmental assumptions: Paths

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

- Evaluate state machine fragility in agent definitions

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

RULE: When using this prompt