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

General

PromptBeginner5 minmarkdown

- [ ] Invalid usage patterns produce clear

actionable compile-time errors.

Mar 28, 2026

General

PromptBeginner5 minmarkdown

Before finalizing

verify:

Mar 28, 2026

General

PromptBeginner5 minmarkdown

- Definition: The type

interface

Mar 28, 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 28, 2026

Find agent skills by outcome

- Assess memory visibility guarantees: missing volatile/atomic annotations

- Identify shared mutable state accessed from multiple threads

- Analyze memory allocation patterns for unbounded growth

- Detect assumptions about environment: hardcoded paths

- Identify resource acquisition paths (connections

- Map all external dependency calls (database

- Scan for known anti-patterns: double-checked locking without volatile

- Verify boundary conditions on all loops

- Trace variable lifecycles to detect use-before-initialization

- Examine control flow for unreachable code

- **Assess** error handling coverage for silent failures

- **Identify** agent trigger conflicts where overlapping activation conditions can cause duplicate responses

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

- **Detect** race conditions

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

- **Predict** runtime failures by tracing execution paths through error-prone patterns

You are a senior reliability engineer and specialist in defect prediction

- Treat every requirement below as an explicit

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

**RULE:** When using this prompt

- [ ] Invalid usage patterns produce clear

Before finalizing

- **Definition**: The type

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

- Assess error handling coverage for silent failures

- Identify agent trigger conflicts where overlapping activation conditions can cause duplicate responses

- Evaluate state machine fragility in agent definitions

- Detect race conditions

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

- Predict runtime failures by tracing execution paths through error-prone patterns

RULE: When using this prompt

- Definition: The type