Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

cap4k-authoring

Estrelas3

Forks0

Atualizado6 de junho de 2026 às 13:48

Route cap4k business-authoring work through the self-contained cap4k skill system. Use when the user asks to discover a business slice, model DDD boundaries, write cap4k technical design, author generator inputs, review plan or generated output, implement handwritten business logic, design service integration, or verify cap4k work.

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

LDmoxeii

LDmoxeii/cap4k

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

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	cap4k-authoring
description	Route cap4k business-authoring work through the self-contained cap4k skill system. Use when the user asks to discover a business slice, model DDD boundaries, write cap4k technical design, author generator inputs, review plan or generated output, implement handwritten business logic, design service integration, or verify cap4k work.

Cap4k Authoring Router

This is the entry router for cap4k business-authoring agents. It is not the rulebook.

Always Read

routing.yaml
../shared/workflows/forced-rollback.md

Session Discipline

Re-read this file and routing.yaml for every new user task.
Do not use public docs, analysis maps, issues, Context7, or historical specs as runtime instructions.
Route to the current phase skill before acting.
For structural creation or modification, make sure the routed workflow loads ../shared/workflows/skeleton-generation-gate.md.
For a spec-level end-to-end example, use the content-studio-dry-run route in routing.yaml.

Routing Source

routing.yaml is the only routing source of truth. Do not maintain a second route table in Markdown.

Priority

Current user instruction and explicit project scope.
routing.yaml phase and specialist route.
Routed skill rules and workflows.
Existing business project conventions.
Human audit remains required for domain decisions.

Mais deste repositório

mesmo repositório

cap4k-generator-inputs

LDmoxeii/cap4k

Use when projecting an approved cap4k technical design into generator inputs such as DB/schema, design JSON, manifests, Gradle extension settings, addons/options, or template override decisions.

2026-07-183

cap4k-tactical-modeling

LDmoxeii/cap4k

Use when a coherent cap4k business brief needs tactical DDD decisions mapped to cap4k carriers, generator input expectations, rollback notes, and the next technical design phase.

2026-06-043

cap4k-service-integration

LDmoxeii/cap4k

Use for cap4k business service interaction design and implementation: Open Host Service entries, Published Language, external capability clients, external fact entries, inbound/outbound integration events, callbacks, message listeners, and command/query routing across service boundaries.

2026-06-043

cap4k-handwritten-implementation

LDmoxeii/cap4k

Use when implementing cap4k handwritten business logic inside approved generated skeletons after human generated-output review: command handlers, query handlers, subscribers, jobs, controllers, factories, specifications, domain services, Repository access, Mediator routing, and UoW persistence.

2026-06-043

cap4k-verification-audit

LDmoxeii/cap4k

Use for cap4k verification and audit claims: static review, focused local evidence, full evidence, generated-versus-handwritten ownership checks, skipped-check disclosure, rollback targeting, and final evidence summaries.

2026-06-043

cap4k-generation-review

LDmoxeii/cap4k

Use to review cap4k plan evidence, generated output ownership, conflict policies, template IDs, addon artifacts, generation drift, and the stop point before handwritten implementation.

2026-06-043

name	cap4k-authoring
description	Route cap4k business-authoring work through the self-contained cap4k skill system. Use when the user asks to discover a business slice, model DDD boundaries, write cap4k technical design, author generator inputs, review plan or generated output, implement handwritten business logic, design service integration, or verify cap4k work.

Cap4k Authoring Router

This is the entry router for cap4k business-authoring agents. It is not the rulebook.

Always Read

routing.yaml
../shared/workflows/forced-rollback.md

Session Discipline

Re-read this file and routing.yaml for every new user task.
Do not use public docs, analysis maps, issues, Context7, or historical specs as runtime instructions.
Route to the current phase skill before acting.
For structural creation or modification, make sure the routed workflow loads ../shared/workflows/skeleton-generation-gate.md.
For a spec-level end-to-end example, use the content-studio-dry-run route in routing.yaml.

Routing Source

routing.yaml is the only routing source of truth. Do not maintain a second route table in Markdown.

Priority

Current user instruction and explicit project scope.
routing.yaml phase and specialist route.
Routed skill rules and workflows.
Existing business project conventions.
Human audit remains required for domain decisions.