factory-kit
01Plugin Claude Code
Portable Factory Kit workflows for software delivery.
Plugin Claude Code
Portable Factory Kit workflows for software delivery.
Plugin Claude Code
Portable software-factory skills, Claude compatibility workflows, and Linear integration.
MCP server Claude CodeCodexCursor +2
Linear's hosted MCP server: lets the agent read and update issues, projects and cycles. Remote server at mcp.linear.app.
Agent
Use when designing or implementing API endpoints — server actions, tRPC procedures, REST routes for external consumers. Carries the factory's API conventions — the server actions vs tRPC decision, procedure tier stacking, per-mutation Zod schemas, central router composition with manual registration, pagination…
Agent
Use when wiring auth into a new project, switching auth providers, or adding role/org features. Carries the factory's auth conventions — the provider decision matrix (Better Auth + orgs primary, Supabase + RLS for RLS-heavy cases, Clerk for consumer/SSO), the unified requireAuth / requireRole / withOrgContext wrapper…
Agent
Use to review a PR, diff, or recently-written code against the factory's conventions. Read-only — outputs structured review, not diffs. Carries the full factory-pitfalls digest as a PR checklist plus the conventions from every other factory-.md skill. Flags anti-patterns, missing conventions, security risks, and…
Agent
Use when designing or implementing data ingestion, CSV imports, time-series storage, Python services that sit alongside Next.js, simulation pipelines, or external-API integration with submit/poll/fetch shapes. Carries the factory's data-pipeline conventions — TS scripts with Papa Parse, JSONB envelopes for…
Agent
Use when planning or executing a destructive change against a production database — schema migrations with backfills, periodic data imports, one-shot RPCs, drop-constraint operations, anything that mutates prod tables and cannot be trivially undone. Sister agent to db-schema-architect (schemas) and…
Agent
Use when designing or modifying database schemas, migrations, multi-tenant data models, or polymorphic table structures. Carries the factory's data-layer conventions — Drizzle with domain-partitioned schema modules, shared.ts with timestamps helper and pgTableCreator, org-keyed FKs with cascade delete, JSONB envelope…
Agent
Use to turn a vague client ask into a buildable feature spec — scoping, decisions-needed identification, skill routing, risk surfacing. Carries the factory's decision-criteria stack (Mantine vs shadcn, server actions vs tRPC, auth provider, etc.) and routes to the right specialist skills. Outputs a structured spec …
Agent
Use when building multi-step forms, complex intake flows, drawer-CRUD forms, or anything beyond a one-shot Mantine form. Carries the factory's form conventions — react-hook-form + Zod via resolver, three Zod variants (server strict / client lenient / patch), modular section files from day one, field registry for…
Agent
Use when scaffolding any frontend surface that touches lists, forms, drawers, tables, or entity editing. Carries the factory's CRUD conventions — DataTable + drawer with mode union, RowActions primitive, per-context Zod schema variants, query-key naming, format helpers as single source, tier-based heading components…
Agent
Use when building LangGraph workflows, agents, RAG systems, structured-output nodes, streaming chat surfaces, or anything LLM-driven with state. Carries the factory's LLM conventions — TypedDict state schemas, node factory closures, named conditional-edge routers, JSON-schema structured output, local-prompt-fallback…
Agent
Use to threat-model a feature, audit AI-generated code, design sensitive-data handling, or review auth/authz boundaries. Carries the factory's security conventions — KMS encryption at rest, BAA verification for PHI, safe URL redirects, admin-client bypass guardrails, in-memory rate-limiter caveats…
Agent
Use to design the verification strategy for a change — what would prove it correct, given its blast radius, and what is currently unverifiable. Read-only — outputs a verification plan and a gap list, not a review and not code. Sister to code-reviewer (which finds defects in a diff) and the generalization of…
Command
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree.
Command
Load a Linear issue into context and enter plan mode for a focused session.
Command
Measure the factory-kit's token footprint — baseline vs on-demand, heaviest assets, trim candidates.
Command
Convert a rough ask into a structured XML-tagged prompt using the factory-prompting vocabulary.
Command
Cut a release with synchronized versions, notes, commit, tag, push, GitHub Release, and npm publication gates.
Command
Configure .factory-kit/linear.json for the portable Linear workflows.
Command
Dev standup — open Linear tickets grouped by in-flight, top priority, and backlog.
Command
Move the current branch's Linear issue to In Review.
Skill Claude CodeCodex
Motion discipline distilled across builds. Attention as a fixed per-viewport budget, figure/ground separation (calm the ground, load motion into the figure), one focal point of motion per screen, diegetic-over-decorative test, trigger-on-intent-then-settle over perpetual loops, and the prefers-reduced-motion fallback.…