a-safe-pulse

Express API route implementation patterns with validation and error handling. Use when creating Express routes, implementing CRUD endpoints, adding server-side validation, handling webhooks, or implementing error handling. This project uses Express.js with direct pg queries -- no Next.js, no ORM.

Frontend UI patterns. DORMANT -- not currently active in a-safe-pulse (CLI + API only).

Database migration creation with mandatory RLS policies and ARCHitect approval workflow. Use when creating migrations, adding tables, or planning data migrations. Migrations are raw SQL files in `src/db/migrations/` with `XXX_description.sql` naming, registered in `index.ts`, auto-run on startup.

Pattern library discovery for pattern-first development. Use BEFORE implementing any new feature, creating components, writing API routes, or adding database operations. Ensures existing patterns are checked first.

Row Level Security patterns for database operations. Use when writing any database query, creating API routes that access data, implementing webhooks that write to the database, or working with user data. This project uses direct pg (node-postgres) queries with raw SQL -- no ORM.

Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, breaking down user stories, or translating business requirements to technical specs. Do NOT use for implementation work -- this is for planning and specification only.

Payment integration patterns. DORMANT -- not currently active in a-safe-pulse.

Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers team creation, messaging, shared task lists, and SAFe gate enforcement. Do NOT use for single-agent or simple subagent workflows.

Testing patterns for Jest unit and integration tests. Use when writing tests, setting up test fixtures, or validating implementations. Jest only -- no no E2E framework. Tests live in `tests/` directory.

Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.

Express API route implementation patterns with Zod validation and error handling. Use when creating Express routes, implementing endpoints, or adding server-side validation. This project uses Express.js with direct pg queries -- no Next.js, no ORM.

Documentation templates for ADRs, runbooks, and architecture docs. Use when creating architectural decision records, operational runbooks, or technical documentation.

Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.

Frontend UI patterns. DORMANT -- not currently active in a-safe-pulse (CLI + API only).

Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing branches, debugging with bisect, cherry-picking commits, or resolving complex merge conflicts.

Database migration creation with mandatory RLS policies and ARCHitect approval workflow. Use when creating migrations, adding tables, or altering schemas. Raw SQL files in `src/db/migrations/` with `XXX_description.sql` naming.

Agentic orchestration patterns for long-running tasks. Implements evidence-based delivery and Simon Willison's agent loop. Use when managing multi-step work, coordinating subagents, or orchestrating PR workflows.

Pattern library discovery for pattern-first development. Use BEFORE implementing any new feature, creating API routes, or adding database operations. Ensures existing patterns are checked first before writing new code.

PR creation, CI/CD validation, and release coordination patterns. Use when creating pull requests, running pre-PR validation, checking CI status, or coordinating merges.

Row Level Security patterns for database operations. Use when writing database queries, creating Express API routes that access data, or implementing webhooks. This project uses direct pg (node-postgres) queries with raw SQL -- no ORM.

SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating branches, writing PR descriptions, or asking about contribution guidelines.

RLS validation, security audits, OWASP compliance, and vulnerability scanning. Use when validating data isolation, auditing Express API routes, or scanning for security issues.

Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, or breaking down user stories.

Payment integration patterns. DORMANT -- not currently active in a-safe-pulse.

Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers TeamCreate, SendMessage, shared TaskList, and SAFe gate enforcement.

Testing patterns for Jest unit and integration tests. Use when writing tests, setting up test fixtures, or validating implementations. Jest only -- tests in `tests/` directory.

Express API route implementation patterns with Zod validation and error handling. Use when creating Express routes, implementing endpoints, or adding server-side validation. This project uses Express.js with direct pg queries -- no Next.js, no ORM.

Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.

Frontend UI patterns. DORMANT -- not currently active in a-safe-pulse (CLI + API only).

Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing branches, debugging with bisect, cherry-picking commits, or resolving complex merge conflicts.

Database migration creation with raw SQL files and ARCHitect approval workflow. Use when creating migrations, adding tables, or altering schemas. Raw SQL in `src/db/migrations/` with `XXX_description.sql` naming.

Agentic orchestration patterns for long-running tasks. Implements evidence-based delivery and iterative agent loops. Use when managing multi-step work, coordinating workflows, or orchestrating PR workflows.

Pattern library discovery for pattern-first development. Use BEFORE implementing any new feature, creating components, writing API routes, or adding database operations. Ensures existing patterns are checked first.

Row Level Security patterns for database operations. Use when writing database queries, creating Express API routes that access data, or implementing webhooks. This project uses direct pg (node-postgres) queries with raw SQL -- no ORM.

Data isolation validation, security audits, OWASP compliance, and vulnerability scanning. Use when validating query safety, auditing Express API routes, scanning for security issues, or reviewing code for vulnerabilities.

Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, or breaking down user stories.

Payment integration patterns. DORMANT -- not currently active in a-safe-pulse.

Testing patterns for Jest unit and integration tests. Use when writing tests, setting up test fixtures, or validating implementations. Jest only -- tests in `tests/` directory.

Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialist agents, managing blockers across agents, coordinating multi-agent workflows, escalating issues, or verifying the pre-implementation gate. Do NOT use for direct implementation work.

Documentation templates for ADRs, runbooks, architecture docs, and knowledge transfer documents. Use when creating Architecture Decision Records, writing operational runbooks, documenting system architecture, or creating technical specifications. Do NOT use for code implementation or ticket management.