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

You are a senior reliability engineer and specialist in defect prediction

runtime failure analysis

Apr 2, 2026

General

PromptBeginner5 minmarkdown

- Definition: The type

interface

Apr 2, 2026

Find agent skills by outcome

- Review error propagation across service boundaries for information loss

- Evaluate backward compatibility risks in API changes

- Analyze agent persona definitions for contradictory instructions

- Enumerate boundary values: empty collections

- Detect state corruption risks from concurrent transitions

- Verify that every state has a defined timeout

- Assess memory visibility guarantees: missing volatile/atomic annotations

- Analyze memory allocation patterns for unbounded growth

- Identify shared mutable state accessed from multiple threads

- Detect assumptions about environment: hardcoded paths

- Identify resource acquisition paths (connections

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

- Map all external dependency calls (database

- Trace variable lifecycles to detect use-before-initialization

- Verify boundary conditions on all loops

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

- Examine control flow for unreachable code

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

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

- **Detect** race conditions

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

**RULE:** When using this prompt

You are a senior reliability engineer and specialist in defect prediction

- **Definition**: The type

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

- Assess error handling coverage for silent failures

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

- Detect race conditions

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

RULE: When using this prompt

- Definition: The type