Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

frontend-implementation-protocol

Estrelas2

Forks0

Atualizado10 de julho de 2026 às 16:11

Frontend implementation protocol. Use by frontend agents when editing assigned UI slices.

Instalação

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ê.

Executar no Manus

Fonte

MathisVerstrepen

MathisVerstrepen/opencode-config

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	frontend-implementation-protocol
description	Frontend implementation protocol. Use by frontend agents when editing assigned UI slices.

Frontend Implementation Protocol

Read .agents/PLAN.md, .agents/TASK_CONTEXT.md if present, the assignment, and every assigned .agents/REVIEW_<type>-<n>.md#F<n> reference first.
Stay within assigned frontend scope.
Follow existing component, route, state, style, and API-client patterns.
Respect backend contracts in the plan.
Avoid unrelated refactors.
Do not edit backend files unless assigned.
Do not run tests by default.
Add frontend tests only when explicitly assigned.
Report changed files, UI behavior, risks, and suggested checks.
If the Orchestrator asks for file-based state, write/update only the assigned sections of .agents/TASK_CONTEXT.md or .agents/HANDOFF.md; otherwise return the same information in chat.
Read review artifacts directly and report references addressed. Do not edit the plan, .agents/REVIEW.md template, or review artifacts, or use alternate tools to modify them.

State templates

Use templates/TASK_CONTEXT.md for durable implementation-slice context. Treat it as a scoped working brief, not a replacement for .agents/PLAN.md.
Use templates/HANDOFF.md when pausing, returning work to the Orchestrator, or handing a frontend slice to another agent.
Keep frontend-specific details in the filled content: route/component/state/API-client/style/a11y behavior, backend contract expectations, UI states, manual checks, and suggested frontend checks.

Mais deste repositório

mesmo repositório

onboard-project

MathisVerstrepen/opencode-config

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.

2026-07-122

backend-implementation-protocol

MathisVerstrepen/opencode-config

Backend implementation protocol. Use by backend agents when editing assigned server-side slices.

2026-07-102

code-review-protocol

MathisVerstrepen/opencode-config

Code review protocol. Use when reviewing final diffs against .agents/PLAN.md.

2026-07-102

failure-routing

MathisVerstrepen/opencode-config

Failure routing protocol. Use when routing test or review failures to the correct agent.

2026-07-102

performance-review-protocol

MathisVerstrepen/opencode-config

Performance review checklist. Use for database, API, rendering, caching, loops, network calls, bundle, and runtime risks.

2026-07-102

plan-review-checklist

MathisVerstrepen/opencode-config

Reviews .agents/PLAN.md for implementation readiness, correctness, scope, risk, and validation gaps.

2026-07-102

name	frontend-implementation-protocol
description	Frontend implementation protocol. Use by frontend agents when editing assigned UI slices.

Frontend Implementation Protocol

Read .agents/PLAN.md, .agents/TASK_CONTEXT.md if present, the assignment, and every assigned .agents/REVIEW_<type>-<n>.md#F<n> reference first.
Stay within assigned frontend scope.
Follow existing component, route, state, style, and API-client patterns.
Respect backend contracts in the plan.
Avoid unrelated refactors.
Do not edit backend files unless assigned.
Do not run tests by default.
Add frontend tests only when explicitly assigned.
Report changed files, UI behavior, risks, and suggested checks.
If the Orchestrator asks for file-based state, write/update only the assigned sections of .agents/TASK_CONTEXT.md or .agents/HANDOFF.md; otherwise return the same information in chat.
Read review artifacts directly and report references addressed. Do not edit the plan, .agents/REVIEW.md template, or review artifacts, or use alternate tools to modify them.

State templates

Use templates/TASK_CONTEXT.md for durable implementation-slice context. Treat it as a scoped working brief, not a replacement for .agents/PLAN.md.
Use templates/HANDOFF.md when pausing, returning work to the Orchestrator, or handing a frontend slice to another agent.
Keep frontend-specific details in the filled content: route/component/state/API-client/style/a11y behavior, backend contract expectations, UI states, manual checks, and suggested frontend checks.