t1-route-tracing

Estrellas0

Forks0

Actualizado14 de julio de 2026 a las 01:00

T1 codebase route-tracing playbook. Use for unfamiliar, cross-file, stateful, or side-effecting implementation work before changing code.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

lebobo88

lebobo88/orchestrator

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	t1-route-tracing
description	T1 codebase route-tracing playbook. Use for unfamiliar, cross-file, stateful, or side-effecting implementation work before changing code.
user-invocable	false

Route tracing

Trace the requested behavior from entry point to observable effect before editing.

Locate the trigger: UI event, API route, CLI command, queue handler, scheduled job, or public function.
Follow call/data flow through validation, authorization, domain logic, persistence, external calls, and response/rendering boundaries.
Identify state reads/writes, error paths, retries, idempotency expectations, and existing analogous patterns.
Record the smallest affected surface, no-touch boundaries, and the test seam that proves the behavior.
If the route cannot be grounded from local evidence or needs external/current documentation, return a research escalation rather than guessing.

Más de este repositorio

mismo repositorio

browser-validator-core

lebobo88/orchestrator

Screenshot-first visual end-to-end validation policy for browser-rendered UI and webview jobs after verifier approval.

2026-07-180

build

lebobo88/orchestrator

Default engineering workflow. Classify a technical request, route it through the native T1/T2/T3 engineering fleet, and return only independently verified completion to the orchestrator.

2026-07-180

claude-operations

lebobo88/orchestrator

Safely operate Claude Code's opt-in advanced capabilities—sessions, worktrees, agent teams, Skills, MCP, plugins, hooks, Channels, schedules, goals, and Agent SDK integrations—when the user explicitly asks for one. Do not use for an ordinary build request.

2026-07-170

cross-vendor-judging

lebobo88/orchestrator

Routes selective local Codex plan, code, verification, and visual judgment with evidence-backed blocking and strict cost caps.

2026-07-170

design-core

lebobo88/orchestrator

Shared evidence, accessibility, context, and handoff rules for the local design-agent fleet.

2026-07-170

design-direction

lebobo88/orchestrator

Produces contextual creative theses and bounded visual directions without generic model defaults.

2026-07-170

name	t1-route-tracing
description	T1 codebase route-tracing playbook. Use for unfamiliar, cross-file, stateful, or side-effecting implementation work before changing code.
user-invocable	false

Route tracing

Trace the requested behavior from entry point to observable effect before editing.

Locate the trigger: UI event, API route, CLI command, queue handler, scheduled job, or public function.
Follow call/data flow through validation, authorization, domain logic, persistence, external calls, and response/rendering boundaries.
Identify state reads/writes, error paths, retries, idempotency expectations, and existing analogous patterns.
Record the smallest affected surface, no-touch boundaries, and the test seam that proves the behavior.
If the route cannot be grounded from local evidence or needs external/current documentation, return a research escalation rather than guessing.