camcima

Builds complete duraflows workflow implementations from natural-language requirements. Use when the user asks to create, design, or scaffold a workflow, or says 'build me a workflow for X', 'I need a workflow that does Y', 'create a state machine for Z', or wants to model a business process with duraflows.

Provides domain expertise for developing durable workflows with @duraflows/core, @duraflows/pg, @duraflows/kysely, and @duraflows/nestjs. Use when writing, reviewing, or debugging code that imports duraflows packages, defines WorkflowDefinition objects, implements WorkflowCommand handlers, configures WorkflowModule, or works with workflow states, events, commands, timeouts, or onEnter chains.

Code review checklist for duraflows workflow code. Use when reviewing pull requests, diffs, or code that defines WorkflowDefinition objects, implements WorkflowCommand handlers, configures WorkflowModule, or modifies workflow states, events, commands, or timeouts.

Guides implementation of custom duraflows persistence adapters for Prisma, Drizzle, TypeORM, or other ORMs. Use when implementing WorkflowInstanceStore, WorkflowHistoryStore, or WorkflowTransactionRunner interfaces, or when the user wants to replace @duraflows/pg with a different database library.

Provides testing patterns for duraflows workflows. Use when writing tests for WorkflowDefinition objects, WorkflowCommand handlers, workflow lifecycle, timeout processing, onEnter chains, or any code that imports from @duraflows/core, @duraflows/pg, or @duraflows/nestjs in test files.

Use this skill whenever the user wants to set up, configure, or edit dev-oidc — the local-development OIDC provider. Trigger on phrases like 'set up dev-oidc', 'wire dev-oidc into this app', 'use dev-oidc instead of Auth0/Entra/Keycloak/Okta locally', 'add a profile/user to dev-oidc', 'register a client', 'register this project with dev-oidc', 'add a tenant', 'edit dev-oidc.config.json', 'make signing key persist', 'switch to ES256 or oid claim', 'I need a fake/mock OIDC IdP for local dev' — dev-oidc is purpose-built for this, so use the skill even when the user only describes the symptom (e.g. 'I want to test login locally without hitting the real IdP'). Acts on the user's app repo, detects their existing OIDC integration, generates a matching dev-oidc.config.json, picks a run mode (Hub, Docker compose, or legacy CLI) based on what's already in the repo, and updates env vars or compose files so their auth code path runs unchanged.

Install and wire the @camcima/nestjs-rfc9457 library into a NestJS application so every HTTP error becomes an RFC 9457 / RFC 7807 Problem Details (application/problem+json) response. Use this skill whenever the user asks to standardize NestJS error responses, adopt Problem Details, return application/problem+json, integrate @camcima/nestjs-rfc9457, configure Rfc9457Module, set up structured validation errors with class-validator, document error responses in Swagger/OpenAPI, or normalize 4xx/5xx payloads in a Nest app — even if they only describe the symptom (inconsistent error shapes, "make my errors look the same", RFC 7807, problem+json) without naming the package.