Menu
Frontend implementation protocol. Use by frontend agents when editing assigned UI slices.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Onboard project or init project safely: prepare the active repository with agent state, a full persistent codebase-memory index, evidence-based AGENTS.md handling, and safe check reporting.
Backend implementation protocol. Use by backend agents when editing assigned server-side slices.
Code review protocol. Use when reviewing final diffs against .agents/PLAN.md.
Failure routing protocol. Use when routing test or review failures to the correct agent.
Performance review checklist. Use for database, API, rendering, caching, loops, network calls, bundle, and runtime risks.
Reviews .agents/PLAN.md for implementation readiness, correctness, scope, risk, and validation gaps.
| name | frontend-implementation-protocol |
| description | Frontend implementation protocol. Use by frontend agents when editing assigned UI slices. |
.agents/PLAN.md, .agents/TASK_CONTEXT.md if present, the assignment, and every assigned .agents/REVIEW_<type>-<n>.md#F<n> reference first..agents/TASK_CONTEXT.md or .agents/HANDOFF.md; otherwise return the same information in chat..agents/REVIEW.md template, or review artifacts, or use alternate tools to modify them.templates/TASK_CONTEXT.md for durable implementation-slice context. Treat it as a scoped working brief, not a replacement for .agents/PLAN.md.templates/HANDOFF.md when pausing, returning work to the Orchestrator, or handing a frontend slice to another agent.