Designer Workflow

Initialize the Designer Workflow in the current project — set where sandbox apps live, draw the production isolation boundary, check required tools/MCPs, and confirm the design + supabase-integration skills are ready. Run this once per project after installing the plugin.

Plan an app or feature before building it — clarify the idea with questions, write a technical spec to /docs/plan, and open a designer-language GitHub epic + child-story issues, then (on your okay) build it autonomously story by story. The explicit way to kick off the planning pipeline when auto-trigger is borderline.

Build ONE app or story full-stack from an already-agreed plan — backend, UI, assets, and wiring inside an isolated sandbox branch, then run it and open a PR. Normally called by goal-loop once per child story; use directly only for a single explicit one-off build. For any fresh change request — building OR editing/restyling/fixing — use plan-and-spec FIRST, not this. Responds only in plain product language and a working app, never raw code.

Use after plan-and-spec to build a planned change to completion. Scales to size: a small single-issue change is built directly (one story, verify, one PR); a new/large epic is walked one child story at a time (build via design, verify in a browser, open one PR per story), then reports. Triggered by plan-and-spec ONLY after the user has confirmed the FILED GitHub issue is correct; or use directly when a spec (/docs/plan) and a filed, user-approved issue already exist. Execution only — it does not plan or file issues.

Use whenever a visual or media ASSET is needed for an app or page — an image, icon, logo, illustration, hero/background, avatar, texture, video clip, sound effect, or voiceover. Higgsfield is the ONE path for generating assets: never use stock photos, emoji, placeholder boxes, hand-drawn SVGs, or another generator, and never ask the user to go find assets. AUTO-TRIGGER on asset intent: 'add an image/icon/logo/illustration', 'needs a hero', 'a background for…', 'generate a picture/video/sound', or any build step that requires visual/media content. Scope is assets ONLY — do NOT use this for code, data, schema, copywriting, or UI layout.

You MUST use this before ANY change to the project's code or UI — building something new, OR editing, restyling, tweaking, fixing, or refactoring anything that already exists — before you touch any file. Clarifies the change through questions, writes a technical spec to /docs/plan, and ALWAYS files a GitHub issue with gh, then hands off to goal-loop to build. Skip ONLY for pure questions, explanations, or read-only code review with no change.

Wire a Supabase backend into a freshly created app the right way the first time — schema, RLS, auth, migrations, and type-safe client — driven by the Supabase MCP. Use when the /design app-creation flow (or any task) needs to give a new app a working, secure Postgres backend. Triggers: 'add a backend', 'store data', 'save submissions', 'log in', 'user accounts', 'database', Supabase, RLS, migrations, auth, edge functions. Respond to designers/PMs in plain language; do the engineering underneath.

2 hooks across 2 events