Art & Design

Turn an idea or refined brief into an implementation-ready specification, combining /refine (grilling the plan) and /domain-modelling (consistent terms), then recording Architecture Decision Records for significant choices. Use when the user wants a full plan, system design, technical spec, design doc, or ADR before implementation.

Resolve consequential software design choices and produce evidence-backed architecture decision records (ADRs). Use when choosing system boundaries, data ownership, integration or consistency models, platform dependencies, or costly-to-reverse designs; comparing architectural alternatives; or revisiting an existing ADR. Distinguishes technical recommendations from approval and implementation authority.

>- Derive technical decisions from evidence, explicit constraints, and invariants instead of inherited patterns. Use when the user asks for first-principles reasoning, a design rests on disputed assumptions, a bug has competing causes, or a proposed rewrite, dependency, optimization, or architecture change needs justification. Do not activate for mechanical edits, formatting, or simple factual lookups unless explicitly requested.

設計或修改 Pour Decisions 的規則、材料（vial）、催化劑（catalyst）、計分公式、目標分數曲線、商店經濟、難度階梯、教學，或要跑平衡模擬、審查新卡/遺物時使用。

Apply engineering principles when implementing or reviewing code, researching technical facts, writing documentation or agent instructions, and designing architecture or UI. Selects on-demand guidance for implementation, review, research, writing, code, architecture, and frontend work.

Build and maintain the project's domain model — ubiquitous language, entities, value objects, aggregates, relationships, invariants, and bounded contexts — in a lean docs/domain.md (or an existing GLOSSARY.md). Use when new domain concepts appear, terms are used inconsistently, during design of a feature, or when the user asks to define, clarify, or update domain terms or entity boundaries.

Use when o Felipe pede para redesenhar skills de landing page, revisar aprendizados acumulados, processar feedbacks pendentes, atualizar o _regras-vivas.md, fazer a migração inicial das regras, ou quando o Passo 0 oferece a migração. Não use durante a construção de um cliente.

Use when SEMPRE durante o trabalho em uma landing page de cliente: ao entregar qualquer coisa (texto, foto, tela, deploy) e ao receber reação, correção, elogio ou aprovação do Felipe ou do cliente.

Use when designing a new REST API, reviewing endpoints, routes, controllers or an OpenAPI/Swagger spec, choosing status codes, pagination, versioning or error formats, or checking an API change for breaking changes.

Pour Decisions 的美術方向規範。用於定材料調色盤、落沙粒子上色與發光、URP 後處理（bloom、LUT、CRT）、Pixel Perfect Camera、Balatro 式計分 UI 與 juice、16–32px 圖示、Steam 膠囊圖，以及提交前的視覺 QA。只要工作涉及顏色、shader、UI 外觀、圖示或商店圖，就先讀這份。

House style for explanatory visuals drawn with mcp__visual__render_ui (diagrams, flows, small charts, animated explainers). Read once per session before the first explanatory render_ui call. Not for component prototypes; those follow the design the user gives.

>- Use when the user wants to improve or rethink a feature of one of their apps by learning from competitor products — "look at how Loom/Notion/Linear does it", "spin off agents to screenshot ours and competitors", "what can we learn from other apps for X", "benchmark our X against Y", "how can we improve the organization of X" — especially when they also want to SEE the proposal (a before/after design of the improvements, current UI beside the redesign with the new pieces highlighted) before anything gets built.

Run a full security, legal, privacy, pricing, accessibility and site-quality check of a business's website and apps, fix what is safe, and hand the owner one list of actions and questions. Use when asked to audit, review or "check everything" before launch, before taking payments, or on a schedule. Covers South Africa, the US, Australia, the EU and the UK, and works with any host, payment provider or framework.

Use when uma landing page está pronta para ir ao ar: publicar, fazer deploy, configurar domínio ou Cloudflare, limpar cache, ou conferir o site já publicado. Não use para construir a página (criar-landing-page).

Use when o 01-negocio-e-escopo.md está aprovado e falta escolher o estilo visual de uma landing page, ou quando uma tela interna (agenda, painel) de um cliente precisa de visual. Não use para levantar dados do negócio (landing-descoberta).

Use when começa um cliente novo de landing page sem 01-negocio-e-escopo.md aprovado, quando faltam dados do negócio, mídias, nomes ou perfis, ou quando o Felipe pede o questionário de entrada. Não use para escolher estilo visual (landing-direcao-visual).

Use when o Felipe pede para criar, montar, refazer ou retomar uma landing page ou site de uma página para um negócio ou cliente, ou abre uma pasta de cliente em criar-site/. Não use para redesenhar as próprias skills (landing-evoluir-skill).

Use when uma landing page precisa de software além da página estática: agenda ou reserva, painel, API, banco, e-mail transacional, notificação, ou qualquer serviço que roda no servidor ao lado de outro sistema. Não use para páginas só de HTML, CSS e JS.

Plan a new toy_process Process from a plain-language goal by breaking it into ordered steps and nested sub-processes. Use first whenever the user asks for a new process, workflow or pipeline, before writing any code.

Implement or review floating desktop UI such as dropdowns, popovers, tooltips, menus, comboboxes, and nested overlays under apps/desktop.

Write a new Process subclass with the toy_process package (set_parameters, set_steps, step methods, nested sub-processes), plus its test. Use when building a process, workflow or pipeline in process_package, after planning it with design-process.

Build an in-app help assistant for a web app - a panel on every screen that answers "how do I…?" with the app's exact labels, shows close-up screenshots that point at the button to press, links to the screens the user can open, and (optionally) reads the user's own data and prepares actions without executing them. Use when adding a help/support assistant or copilot to an existing product, when an existing agent must learn how the app's UI works, or when porting this pattern to another repo.

Create, repair, review, and improve QF-Test 11.0 test suites (.qft), component recognition, checks, procedures, scripts, and offline test runs. Use for QF-Test GUI automation and run-log diagnosis.

Expert guidance for hybrid AppKit-SwiftUI development. Covers NSViewRepresentable, hosting controllers, and state management between frameworks. Use when bridging AppKit and SwiftUI.