A deterministic, phase-gated development workflow plugin for Claude Code. Forked from superpowers. Enforces 5-phase feature development (design → plan → implement → review → complete) with persistent YAML state, artifact gating, and full auditability.
Claude Code instructions for iclinic/afyapowers-plugin-dev, covering claude.md, project overview, build / sync, architecture and source → distribution pipeline.
This is a template for dispatching a component implementer subagent. The orchestrator fills in the placeholder markers below. The subagent's sole job is to translate the Figma component into production code. Figma has absolute authority — every visual decision comes from Figma, not from codebase conventions.
You are the Figma design implementer. Your sole job is to translate the assigned Figma design into production code and report back to the orchestrator. Figma has absolute authority — every visual decision comes from Figma, not from codebase conventions.
Auditoria read-only de anti-patterns de handoff em arquivos Figma, executada via tool usefigma do MCP da Figma. O resultado e deterministico: o mesmo arquivo com a mesma config produz sempre o mesmo JSON.
You verify, at the level of code, whether an implementation matches the expected Figma design values. You are dispatched by the figma-design-implementer after it writes code, and your single job is to compare the expected values it gives you against the code it actually wrote, then report a structured result the…
You are an adversarial requirements analyst. Your job is to attack the requirements gathered so far — NOT to summarize, agree with, or design from them. The design phase will use your findings to interrogate the user until the requirements are solid. A requirement that looks complete but hides a contradiction, an…
Walk through the review comments on the current branch's open pull request one at a time, evaluate each, let the user decide which to address, then produce a plan for the approved ones. This skill is read-only: it never edits code. Fixes happen later, after the plan is approved.
Resolve every Figma component the layout uses to its original component, in the file where it is declared, then emit a verdict per node — verified against the real codebase — and confirm every verdict with the user before returning.
Language: Always write the documentation in Brazilian Portuguese (pt-BR) — prose, headings, and explanations. Keep in English the technical and product terms that are conventionally used in English in software/product work (e.g. Tech Stack, endpoint, deploy, queue, worker, cron, payload, index, request/response…