Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

backend-implementation-protocol

Estrelas2

Forks0

Atualizado10 de julho de 2026 às 16:11

Backend implementation protocol. Use by backend agents when editing assigned server-side 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	backend-implementation-protocol
description	Backend implementation protocol. Use by backend agents when editing assigned server-side slices.

Backend 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 backend scope.
Follow existing route, service, validation, repository, model, and error patterns.
Avoid unrelated refactors.
Do not edit frontend files unless assigned.
Do not run tests by default.
Add backend tests only when explicitly assigned.
Report changed files, 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 backend slice to another agent.
Keep backend-specific details in the filled content: API/validation/persistence/error behavior, contract changes, edge cases, and suggested backend 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

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

frontend-implementation-protocol

MathisVerstrepen/opencode-config

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

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	backend-implementation-protocol
description	Backend implementation protocol. Use by backend agents when editing assigned server-side slices.

Backend 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 backend scope.
Follow existing route, service, validation, repository, model, and error patterns.
Avoid unrelated refactors.
Do not edit frontend files unless assigned.
Do not run tests by default.
Add backend tests only when explicitly assigned.
Report changed files, 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 backend slice to another agent.
Keep backend-specific details in the filled content: API/validation/persistence/error behavior, contract changes, edge cases, and suggested backend checks.