frontend-implementation-protocol

スター2

フォーク0

更新日2026年7月10日 16:11

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

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

MathisVerstrepen

MathisVerstrepen/opencode-config

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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.

このリポジトリの他の Skills

同じリポジトリ

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.