zaq

Turn a plain-text description of a business workflow into a ZAQ workflow use-case module (a `Zaq.Engine.Workflows.UseCases.*` module that builds a DAG of nodes + edges). Every step is mapped to a real tool from `lib/zaq/agent/tools` (resolved through `Zaq.Agent.Tools.Registry`) or a workflow Step like `HumanInTheLoop`. When a described step has no matching tool, the generated module gets a `missing_tools/0` function describing the tools that must be built first. Use when the user pastes/says a workflow they want as code.

Migrate legacy ZAQ web UI (components, LiveViews, layouts) styling to the --zaq-* token system. Reads DESIGN.md and CSS catalog (foundations, semantics, text-styles, btn, form, modal, table, layout, styles) before proposing changes. Accepts a Figma frame URL (design-led), a file path (audit), or --audit-all (full sweep). Typical position in workflow: after extract, before replace.

Build or extend ZAQ back-office UI using the --zaq-* design system. Read DESIGN.md first, consult Storybook, then use extract, design-migrate, or replace as appropriate. Human confirmation required before apply steps in each skill.

Find cohesive UI slices, cross-check against existing reusable components, report candidates for human approval, copy approved slices into new (or extended) ZaqWeb.Components.DesignSystem modules (original call-site code stays intact), and add or update Storybook. Does not wire LiveViews and never invokes replace — flag replace candidates in the report for a human follow-up after design-migrate. Use before design-migrate when markup lives under lib/zaq_web/live/.

Applies human feedback to an in-progress feature by updating the PRD, then re-running ux-design and prototype. Use after the initial pm-senior → ux-design → prototype pass when the reviewer sends changes, corrections, or new scope on the PRD, UX plan, or staged BO screens.

Stages UX-plan features on real BO routes using static fixtures. May update DSM (DesignSystem.*), existing components, CSS, router, and sidebar. Never touches backend (lib/zaq/**, NodeRouter, migrations). Use after /ux-design; hand off to /design for production-ready DS patterns and data wiring.

Find inline UI that matches an existing reusable component under lib/zaq_web/components/, report replacement candidates for human approval, wire approved components into LiveViews (imports, component calls, remove dead markup), and verify with e2e or ExUnit. Use after extract and design-migrate when call sites still duplicate markup.

Translates a PRD into structured user flows, text wireframes, and a UI designer handoff plan. Use when given a PRD, product spec, or feature brief and the user wants wireframes, user flows, IA, screen specs, or a UX plan before visual design or implementation.

Review pull requests for correctness, regressions, security issues, maintainability, and missing tests.

Set up a git worktree with an isolated dev database and full developer environment for a branch.

Evaluate PR code review comments for relevancy and priority

Make sure produced code is of high quality and properly documented

Plan for test scenarios for uncovered code lines

Produce test code for given scenarios and make sure they pass