Cargando...
Instrucciones repetitivas para agentes de código
55 recursos publicados
Loops para compilar, testear y desplegar
Loops para linting, tipos y accesibilidad
Loops para migraciones e índices
Loops para auditoría y hardening
Run lint and typecheck, fix reported issues, and loop until the codebase is clean.
Run your test suite, fix the smallest root cause on failure, and repeat until every test passes.
Implement from a written spec.md checklist — each iteration completes one unchecked requirement with verification.
Rebase or merge target branch, resolve conflicts file by file, and loop until the branch is current and tests pass.
Write a small throwaway script to reproduce a bug, run it, read output, and iterate until the root cause is proven.
Run Playwright or Percy visual snapshots on UI changes; fix unintended diffs until baselines match intentionally.
Run end-to-end tests, fix UI and integration failures, and loop until the E2E suite passes.
Run the production build, fix compile and bundling errors, and loop until the build succeeds.
Add focused tests until coverage meets your threshold (e.g. 80%), without changing production behavior unnecessarily.
Implement on a branch, run tests, push, open a PR, wait for CI, and loop until checks pass and the PR is ready to merge.
Loop until API responses match the OpenAPI or JSON Schema contract — catch drift between docs and implementation.
Revisa dependencias vulnerables.
Verifica headers de seguridad en todas las rutas.
Fix high/critical npm audit findings one at a time with test verification — not a blind npm audit fix --force.
Analiza queries lentas y anade indices.
Aplica migraciones pendientes una a una.
Run database migrations, fix schema issues, and loop until migrations apply cleanly in dev.
Crea stories para componentes sin documentacion.
Corrige problemas de a11y uno a uno.
Elimina errores de TS sin any ni ignore.
Arregla errores de lint uno a uno.
Run automated accessibility checks on changed routes, fix violations, and repeat until the audit is clean.
After code changes, find affected docs and update README, API references, and inline comments to match.
After implementation, run a cleanup pass: remove debug code, tighten naming, delete dead branches, and align with project conventions.
