Trace a request through a codebase
Follow one request from entry point to storage or external boundary with concrete file references.
Reusable instructions for compatible AI agents.
Counts cover every published resource in this section. A resource can belong to several fields and platforms.
Follow one request from entry point to storage or external boundary with concrete file references.
Reduce a reported defect to a small repeatable case before proposing a fix.
Inspect validation, error contracts, and authorization around one API endpoint.
Check transitions and side effects across loading, success, failure, and cancellation states.
Derive a focused verification set from changed behavior and affected callers.
Map a dependency upgrade's affected usage and verification needs before changing versions.
Analyze query correctness, parameter handling, and result assumptions using the supplied schema.
Check a supplied component's semantics, keyboard flow, and state announcements.
Find configuration drift without printing secret values or assuming every difference is wrong.
Separate the failing assertion, likely affected behavior, and evidence needed for diagnosis.
Build one user-visible feature slice while preserving repository conventions and existing work.
Restructure a bounded area while proving important observable behavior stays the same.
Try a broader search or clear some filters.
Platform labels describe intended use. Read each resource's author credits, requirements and available access methods.