state-machine
State Machine - Finite State Machines for Complex Flows
Description
Enforces deterministic, minimal state machines for any multi-step flow in NodeJS-Starter-V1. Codifies the project's existing patterns (TaskStatus, ExecutionStatus, NodeStatus) and provides a reusable framework for defining states, transition maps, guard conditions, and side effects across Python and TypeScript.
When to Apply
Positive Triggers
- Designing multi-step workflows with distinct status phases
- Adding new
Enumstatus fields to Pydantic models - Implementing UI components with loading/error/success states
- Reviewing state transitions for completeness and determinism
- Adding retry, escalation, or verification loops
- User mentions: "state machine", "status", "workflow state", "transitions", "FSM"
More from cleanexpo/unite-hub
tdd
Use when implementing any feature or bug fix. Hard gate — no production code without a failing test first. Applies to vitest (apps/web/) and pytest (apps/backend/). Triggers on "implement", "add feature", "fix bug", "new component", "new endpoint", or any code-writing task.
1idea-to-production
Plain-English pipeline from idea to production — routes user requests to the right phase and agent
1oauth-flow
OAuth 2.0 and OIDC integration with PKCE, Supabase Auth providers, and redirect URI validation
1health-check
>-
1csv-processor
>-
1vector-search
>-
1