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

Business

PromptBeginner5 minmarkdown

- Approach: Strategy for typing (generics

unions

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

Creative

PromptBeginner5 minmarkdown

- Create utility types like DeepPartial

DeepReadonly for recursive property modification.

Mar 20, 2026

Creative

PromptBeginner5 minmarkdown

- Leverage built-in utility types (Partial

Required

Mar 20, 2026

Creative

PromptBeginner5 minmarkdown

- Add type annotations incrementally

starting with the most critical interfaces and working outward.

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

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

- **Hardcoded environmental assumptions**: Paths

- 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

- Assess infrastructure-as-code changes for resource sizing

- Check for data validation at trust boundaries: API inputs

- Audit third-party dependency versions for known bugs

- Evaluate backward compatibility risks in API changes

- Detect state corruption risks from concurrent transitions

- Map all external dependency calls (database

- Detect assumptions about environment: hardcoded paths

- 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

- **Approach**: Strategy for typing (generics

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

- Create utility types like DeepPartial

- Leverage built-in utility types (Partial

- Add type annotations incrementally

- Remediation: Specific code fix

- Scope: Code paths

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

- Hardcoded environmental assumptions: Paths

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

RULE: When using this prompt

- Approach: Strategy for typing (generics