Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

design

Estrelas1

Forks0

Atualizado6 de julho de 2026 às 12:32

Use when the user wants epic-level technical design at .agency/work/{epic}/design.md, walking-skeleton or TDD design, or design review before tasks. Pass epic slug or ID (CHK01). Cite solution.md — do not re-narrate architecture. Do NOT use for product backlog or epics (backlog), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), code implementation (implement), or doc-only sprint-end pass (docs refine).

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

carinyaparc

carinyaparc/digital-agency

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

7 arquivos

SKILL.md

readonly

name	design
description	Use when the user wants epic-level technical design at .agency/work/{epic}/design.md, walking-skeleton or TDD design, or design review before tasks. Pass epic slug or ID (CHK01). Cite solution.md — do not re-narrate architecture. Do NOT use for product backlog or epics (backlog), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), code implementation (implement), or doc-only sprint-end pass (docs refine).
license	MIT
allowed-tools	["Read","Write","Glob","Grep"]
argument-hint	<mode: write\|review> <epic> [--mode walking-skeleton\|tdd] [--context <notes>]

Design

Conventions

Read ../../references/web-development-conventions.md when resolving {epic} or checking artefact boundaries.

Artefact

.agency/work/{epic}/design.md — implementation specification for one epic (walking-skeleton or TDD).

Path resolution

Default: .agency/work/{epic}/design.md. User-named paths under .agency/work/ override.

Gotchas

Do not copy solution.md — cite solution.md §{N.M} instead.
Task Gherkin belongs in tasks.md, not design (gates/slice scope only).
walking-skeleton is 2–4 pages; tdd is 5–10 — do not mix section sets.
§4 Out of scope must list what this epic explicitly did not ship.

Supporting files

Router

Mode: write or review.
Resolve {epic}.
prompts/write.prompt.md | prompts/review.prompt.md.

write — --mode walking-skeleton|tdd.

Mais deste repositório

mesmo repositório

setup

carinyaparc/digital-agency

Web development practice setup interview — detects or creates .agency/target.json binding, reads instance profile from `/agency-hub:setup`, interviews tech stack, deployment platform, connectors, and persona preference (six engineering personas vs merged), writes practice profile. Use on first install after `/agency-hub:setup`, when the user says "set up web development" or "bind target repo", or to redo engineering defaults only.

2026-07-071

ralph

carinyaparc/digital-agency

Use when the user wants to run a Ralph loop: an autonomous, self-referential delivery loop that drives a whole epic through implement, code review, fix, UX review, validate, commit, and merge request, one task per iteration, until a completion promise is emitted (ralph setup, ralph start), or to inspect or stop a running loop (ralph status, ralph cancel). Also supports simple ad-hoc loops that repeat a single prompt until done. Do NOT use to implement a single task once (implement), review a diff (code-review), or sign off an epic (validate) — the loop orchestrates those skills.

2026-07-071

ux-design-review

carinyaparc/digital-agency

Use when the user wants a UX/design review of implemented UI — frontend components, pages, or flows — against the design source of truth (Figma via MCP, mockups, tokens, or style guide, whatever the repo provides), covering design fidelity, accessibility (WCAG 2.2 AA), interaction states, responsiveness, and design-system conformity; or to address UX review findings (ux-design-review fix, optionally scoped to an action tier). Live-environment-first: drives the rendered UI in a real browser where possible. Works with any framework or design tooling. Do NOT use for code correctness/security review (code-review), to review a design.md document (design), or to implement features (implement).

2026-07-071

merge-request-review

carinyaparc/digital-agency

Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open or babysit an MR (merge-request), or to implement changes (implement).

2026-07-071

merge-request

carinyaparc/digital-agency

Use when the user wants to open a merge request or pull request for the current branch (merge-request create — the default — with a generated title, description, labels, and reviewer suggestions), or to babysit an open MR/PR to a merge-ready state (merge-request babysit) by watching CI, review comments, and merge conflicts. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise, and plain git as a last resort. Do NOT use to review code or an MR as its reviewer (code-review, merge-request-review) or to implement changes (implement).

2026-07-071

code-review

carinyaparc/digital-agency

Use when the user wants a code review of a branch, PR, or diff against its acceptance criteria and declared scope (whatever form they take in this repo), or to address review feedback without changing behaviour (code-review fix, optionally scoped to a blocking or warning action tier). Works with any language, delivery process, or issue tracker. Do NOT use to implement code, sign off completion of a larger body of work, or review rendered UI/UX (design fidelity, accessibility — use ux-design-review).

2026-07-071

name	design
description	Use when the user wants epic-level technical design at .agency/work/{epic}/design.md, walking-skeleton or TDD design, or design review before tasks. Pass epic slug or ID (CHK01). Cite solution.md — do not re-narrate architecture. Do NOT use for product backlog or epics (backlog), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), code implementation (implement), or doc-only sprint-end pass (docs refine).
license	MIT
allowed-tools	["Read","Write","Glob","Grep"]
argument-hint	<mode: write\|review> <epic> [--mode walking-skeleton\|tdd] [--context <notes>]

Design

Conventions

Read ../../references/web-development-conventions.md when resolving {epic} or checking artefact boundaries.

Artefact

.agency/work/{epic}/design.md — implementation specification for one epic (walking-skeleton or TDD).

Path resolution

Default: .agency/work/{epic}/design.md. User-named paths under .agency/work/ override.

Gotchas

Do not copy solution.md — cite solution.md §{N.M} instead.
Task Gherkin belongs in tasks.md, not design (gates/slice scope only).
walking-skeleton is 2–4 pages; tdd is 5–10 — do not mix section sets.
§4 Out of scope must list what this epic explicitly did not ship.

Supporting files

Router

Mode: write or review.
Resolve {epic}.
prompts/write.prompt.md | prompts/review.prompt.md.

write — --mode walking-skeleton|tdd.