WeAreHausTech

Draft and gate Architecture Decision Records (ADRs) when changes are decision-worthy. Use when `haus decisions suggest` fires, when adding deps/schema/auth/API changes, or when the user asks why a choice was made. Machine drafts; human approves.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when picking up a user-gate task OR when a hook demands re-validation. Runs the "do I know HOW?" self-check; if the HOW is clear, executes the verification and posts evidence; if not, hands off to specifying-gates. Kept deliberately separate from executing-plans so that without the opt-in hook, the main flow stays untouched.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when a user-gate task has requiresUserSpecification=true OR the agent's "do I know HOW?" self-check returns no. Locks down verification mechanics through a short AskUserQuestion sequence and writes the answers back into the task's metadata. Does NOT run the verification itself.

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Database router for PostgreSQL, MariaDB, MySQL, MSSQL, Elasticsearch, and Redis data/model/query/cache changes.

NestJS GraphQL router. Use for modules, resolvers, DTOs, guards, and schema behavior.

Nx 21 monorepo router. Use for project graph, targets, generators, and workspace orchestration changes.

Package manager router for Yarn 4 and pnpm 8.9 workspaces, constraints, and lockfile behavior.

Router for release readiness: config parity, migrations, rollback, and validation evidence.

Router for bounded security review using Haus guardrails and evidence-first output.

TypeScript router. Use for type contracts, API boundaries, generics, and strictness-safe refactors.

Vendure app router. Use for app-level config, workers, jobs, and API extensions in a Vendure application.

Haus all-in-one workflow skill. Handles project setup, re-init, update, catalog refresh, health checks, and CLAUDE.md regeneration. Invoke with a task name or without to get a menu.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when a user-gate task has requiresUserSpecification=true OR the agent's "do I know HOW?" self-check returns no. Locks down verification mechanics through a short AskUserQuestion sequence and writes the answers back into the task's metadata. Does NOT run the verification itself.

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.