huxflux

Generate a commit message that explains WHAT changed and WHY in plain language. No code references. Humans read these, not machines.

Generate a PR description that explains WHAT is being built, WHY, and the high-level approach. Written for humans who will not read the code.

Create a new domains/<name>/ folder following the Huxflux domain pattern. Targets web, server, mobile, or shared. For server domains, also creates the routes plugin and registers it.

Run the structural check (check-domains) against the monorepo or a specific domain. Use after editing a domain to verify it still conforms.

Enter discussion mode. No code is written, no files are created or edited. Read the codebase to ground the conversation, reason through trade-offs, surface edge cases, brainstorm. Use when the user wants to think before building.

Establish shared understanding of a task before writing any code. Restate the ask, surface ambiguity, ask 1-3 structured questions, propose an approach with trade-offs, get sign-off. Use at the start of any non-trivial task.

Create a new domain-internal React component inside an existing domain. Produces a file that passes lint by construction (size cap, allowed icons, design-system colors).

Scaffold a new provider adapter at apps/server/src/domains/providers/service/<id>.ts following the existing pattern (claude, codex, gemini, claudeInteractive). Sets up the ProviderAdapter skeleton, extends ProviderId, registers in the registry.

Create a new TanStack Router route file (web) that delegates to a domain. The route stays thin — the actual UI lives in the domain.

Generate a Vitest test file collocated next to source under apps/server or packages/shared. Pulls in the standard harness, sets up the describe block, and leaves explicit TODO assertions so the next agent fills in real cases.