Menu
Optimizes page-load speed until every route is under 50ms. Read-only — drafts candidate optimizations, never applies them.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | page-load-loop |
| description | Optimizes page-load speed until every route is under 50ms. Read-only — drafts candidate optimizations, never applies them. |
The prompt carries intent; this skill carries the procedure — keep it a checklist, not an essay. Adapted from Forward Future Loop Library #12 (Matthew Berman) to this library's L1-first, report-only shape.
Before beat 1: the human sets up page-load-loop-state.md with the fixed
test conditions — routes to measure, warm-up behavior, and a baseline
capture. Never start a beat without this; the source names this setup as
required, not optional.
page-load-loop-state.md.page-load-report.md: route, before/after load time, the
drafted change, the regression check result.page-load-loop-state.md's per-route history, append
one line to loop-run-log.md, commit both. Discard the throwaway
worktree.Reviews pending PRs, excludes stale/unfinished work, combines the rest into a release batch built from main. Read-only — reports the batch, never actually releases.
Writes a scoped spec packet for one ticket, reviewed by a genuinely independent adversarial pass that also regression-checks prior findings. Read-only outside the draft — never writes the canonical spec.
Defines every required outcome and its evidence before acting on long-running work, then audits each requirement as proved/weak/missing/ contradicted. Only run when explicitly asked for a completion audit.
General-purpose harness for scheduled repo work — stage in an isolated worktree, verify with a genuinely separate second session, ship only after a pass. Read-only — reports, never delivers.
Runs an adversarial review cycle against a PR (Claude implements/fixes, Codex or a subagent stand-in reviews), up to 5 iterations. Read-only on the real PR — drafts fixes, never pushes them.
Turns a ticket or bug report into a review-ready patch. Read-only — reproduces, roots out the cause, drafts a fix, reports it. Never opens a PR, never folds in unrelated refactors.