nonlinear-xyz
- 41 skills
- 0 followers
- 6 hours ago last updated
- ▌ Factory CI · nonlinear-xyzCI and pull-request review conventions. One canonical `.github/workflows/ci.yml` is the merge gate (typecheck, lint, test, build, claude-review); branch protection's required-checks list matches the job list 1:1; `anthropics/claude-code-action@v1` reviews every PR against the `factory-pitfalls.md` checklist as a required check, not advisory. Deploy workflows live separately and never gate merge. Read at project kickoff and whenever wiring CI on a new repo.
- ▌ Factory API · nonlinear-xyzAPI conventions for both server actions and tRPC builds. Covers the decision between them, per-mutation Zod input schemas, central router composition, pagination shape, multi-field search via Drizzle `ilike` + `or()`, mutation lifecycle hooks, conditional query enabling, stale-time defaults, error response shape and custom error class taxonomy, mutation-boundary audit logging, fetch adapter for tRPC routes. Read when designing or implementing any data-mutation endpoint.
- ▌ Factory Auth · nonlinear-xyzAuth and authorization conventions distilled across builds with three different auth stacks (Better Auth + orgs, Supabase Auth + RLS, Clerk). Covers the provider decision matrix, the unified wrapper interface (`requireAuth` / `requireRole` / `withOrgContext`), procedure tier stacking, session handling, OAuth callback safety, plugin composition with Better Auth, and the anti-patterns (hardcoded allowlists, admin client at module scope, triple-fallback auth surfaces).
- ▌ Factory Close · nonlinear-xyzClose out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree
- ▌ Factory Entry · nonlinear-xyzLoad a Linear issue into context and enter plan mode for a focused session
- ▌ Factory Forms · nonlinear-xyzForm conventions distilled across builds. react-hook-form + Zod via resolver (Mantine or shadcn variant), three Zod schema variants (server strict / client lenient / patch), drawer-CRUD with mode union, field-registry pattern for multi-step forms, declarative conditional visibility with auto-cleanup, debounced auto-save with dirty tracking, masked inputs for sensitive fields with KMS encryption-at-rest, dynamic field arrays with constraints, S3 presigned-URL upload flow. Read when scaffolding any form — single-step CRUD or multi-step complex intake.
- ▌ Factory Stack · nonlinear-xyzCross-build locked stack decisions and decision criteria for divergent choices. Read at the start of any new project. Covers runtime, language, ORM, auth provider, component library, deployment, and observability — what's a hard pick, what depends on context, and the criteria for context-driven picks.
- ▌ Factory Voice · nonlinear-xyzCommunication voice for Claude Code — senior software architect, first-principles framing, crisp English. Governs how Claude writes to Linear (issue comments, summaries, status updates), commits, PRs, and how it talks in terminal sessions. Read on session start and before any external write.
- ▌ Factory Design · nonlinear-xyzDesign-system discipline distilled across builds. Semantic token vocabulary (name intent, not palette position), CSS variables bridged into Tailwind, dark/light as a variable swap, single- vs two-layer token systems, component primitives as token consumers, when to promote a repeated utility cluster into a primitive, and the vocabulary-sprawl failure mode. Read whenever you touch styling — marketing surface, internal app, or design-system repo. Paired with factory-frontend, which delegates here for visual coherence.
- ▌ Factory Prompt · nonlinear-xyzConvert a rough ask into a structured XML-tagged prompt using the factory-prompting vocabulary
- ▌
- ▌ Factory Commits · nonlinear-xyzCommit message and branch convention — Conventional Commits format with a Linear issue reference required in subject or body. Includes the canonical commitlint.config.cjs, Husky hook snippet, and opencommit configuration. Read whenever setting up a new project or wiring AI-assisted commits.
- ▌ Factory Release · nonlinear-xyzCut a new release — bump package.json + VERSION in lockstep, commit, tag with a per-version breakdown since the last published baseline, push, publish a GitHub Release, and publish to npm. Five approval gates; the user edits release notes in their preferred editor.
- ▌ Factory Standup · nonlinear-xyzDev standup — open Linear tickets grouped by in-flight, top priority, and backlog
- ▌ Factory Testing · nonlinear-xyzTesting conventions across builds. Vitest + Playwright as the locked stack; tests co-located in `__tests__` next to the code they verify; shared test primitives (provider wrappers, mock factories) centralized in `src/lib/test-utils.tsx`; coverage thresholds enforced at the merge gate (CI ownership lives in `factory-ci.md`). Read at project kickoff and whenever you write or review a test.
- ▌ Factory Frontend · nonlinear-xyzFrontend conventions distilled across builds. CRUD shape (DataTable + drawer with mode union), RowActions primitive, format helpers, heading tiers, semantic color tokens, query-key naming, component-library decision criteria (Mantine vs shadcn). Read when scaffolding any UI surface that touches lists, forms, or entity editing.
- ▌ Factory Pitfalls · nonlinear-xyzCross-skill index of observed failure modes. Each skill carries its own Failure mode blocks under the Principle they violated; this file is the flat scan across all of them, plus process-level pitfalls that don't have a skill home. Read at project kickoff and during code review.
- ▌ Factory Security · nonlinear-xyzSecurity conventions for builds that touch sensitive data, regulated industries, or AI-generated code paths. Covers KMS encryption at rest, BAA verification for PHI in email/SMS, safe URL redirects, admin-client bypass guardrails, in-memory rate-limiter caveats, the "read-only by default" stance for AI-generated code, mandatory-review-queue pattern, and request tracing for support workflows.
- ▌ Factory Animation · nonlinear-xyzMotion 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. Recipe pairs Astro with a Remotion video kit (rendered assets in public/). Read whenever you add motion to a marketing surface or any page where movement competes with reading. Paired with factory-design, which owns the static visual vocabulary motion sits on top of.
- ▌ Factory Kit Audit · nonlinear-xyzMeasure the factory-kit's token footprint — baseline vs on-demand, heaviest assets, trim candidates
- ▌ Factory Prompting · nonlinear-xyzStructured prompting with XML tags. A small named vocabulary (`instructions`, `context`, `input`, `output_format`, `examples`, `constraints`, `role`, `thinking`) that turns a prose ask into something the model can parse without ambiguity. Read whenever you're authoring a prompt by hand, designing a prompt template for production, or rewriting a flaky ask. Paired with `/prompt`, which converts a rough ask into the structured form.
- ▌ Factory Data Layer · nonlinear-xyzDatabase schema, ORM, and migration conventions across builds. Drizzle as default with domain-partitioned schema modules, shared `timestamps` helper, multi-tenancy keys with cascade delete, `pgTableCreator` prefixing, JSONB for flexible attributes, schema-derived type exports, polymorphic table patterns, ESLint Drizzle rules. Covers when to escape to raw SQL or Supabase auto-types.
- ▌ Factory Deployment · nonlinear-xyzDeployment and infrastructure conventions across builds. Vercel + Neon for web (with PR branch DBs), Cloud Run for Python services (one service per entry-point variant), GitHub Actions matrix-deploy on merge, Terraform with environments/modules layout for AWS / compliance customers, RDS IAM authentication for AWS DBs, Docker per Python entry point, env vars via t3-oss/env-nextjs, and the single-tenant customer-cloud deployment model (per the factory thesis). Migrations in CI, never at runtime.
- ▌ Factory DB Migration · nonlinear-xyzThe operational discipline for running a destructive change against a production database — schema migrations, data backfills, one-shot RPCs, historical seed imports. Adjacent to `factory-data-layer.md` (schema design) and `factory-deployment.md` (where migrations execute in CI) — this skill is about the runbook around the act of mutating prod. Covers the three-stage write contract (preflight → mutate → verify → rollback), idempotency by natural key, layered backup independence (Layer C from `factory-security.md` / KAI-126 doctrine), human-gated execution, bidirectional update semantics, validation-at-parse-not-at-constraint, and the failure modes a senior DB engineer pattern-matches before opening a migration PR.
- ▌ Factory Setup Linear · nonlinear-xyzConfigure portable Linear workflow settings in `.factory-kit/linear.json`, migrating legacy `.claude/linear.json` settings when present.
- ▌ Factory Verification · nonlinear-xyzHow we know the software the factory produces is correct, and how we know the kit's own conventions are followed. Defines the four-tier eval spectrum (CLI rule / test / agent / human gate), the rule that evals graduate downward to their cheapest home, the banded coverage score with severity-aware disclosure, and the delta-gated GitHub Action that guards the PR boundary without disrupting the inner loop. The recipe locks to `factory-kit-check` + GitHub Actions; the principles are stack-agnostic. Read at project kickoff, when wiring the conformance gate, and whenever asking "how do we know the agent did this right?"
- ▌ Factory Code Reviewer · nonlinear-xyzUse 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 inconsistencies with prior builds. Invoke after writing nontrivial code, before merge, or when on-boarding a contractor.
- ▌ Factory Forms Builder · nonlinear-xyzUse 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 AI-context-aware multi-step forms, declarative conditional visibility with auto-cleanup, debounced auto-save with dirty tracking, masked inputs for sensitive fields, dynamic field arrays, S3 presigned upload, `useTransition` for async submission, question numbering via context, review section with gap detection. Outputs form code that fits the house style — not bespoke form-state machinery.
- ▌ Factory LLM Workflows · nonlinear-xyzLLM workflow conventions distilled from production agent/RAG work. Covers LangGraph TypedDict state schemas, node factory closures, conditional edge routing, structured output via JSON schema, prompt fallback patterns with optional PromptHub override, hybrid search with confidence gating + fallback supplement, SSE streaming with event dispatch, hexagonal ports/adapters when scale justifies. Read when building any LLM-driven workflow with state, tool calls, or streaming UX.
- ▌ Factory Observability · nonlinear-xyzObservability conventions across builds. PostHog + Sentry on day one (non-negotiable per the factory thesis — easiest to start early, most expensive to backfill). Request tracing with propagated trace IDs, structured logging, activity-log audit table, event tagging by tool/feature for per-tool usage queryability, PostHog ingest-URL rewrite to avoid ad-blocker breakage. What to log, what NOT to log (PII).
- ▌ Factory Data Pipelines · nonlinear-xyzData ingestion and pipeline conventions for projects that import CSVs, run simulations, or operate Python services alongside Next.js. Covers Papa Parse for CSV imports, JSONB envelope storage for time-series data, the three-entry-point Python service pattern (CLI / Cloud Run API / Pub/Sub), YAML config for service-level data, geopandas/shapely for geospatial work, and deployment via Cloud Run + ephemeral Neon DBs.
- ▌ Factory Feature Architect · nonlinear-xyzUse 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 — not code. The first agent to invoke when a client request lands; outputs become the input to other specialist subagents.
- ▌ Factory Frontend Engineer · nonlinear-xyzUse 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, semantic color tokens. Picks Mantine vs shadcn per project criteria. Returns code that fits the house style — not a generic React component.
- ▌ Factory Security Engineer · nonlinear-xyzUse 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, read-only-by-default for AI-generated code, mandatory review queue, request tracing, audit logging at the mutation boundary. Outputs a threat assessment with concrete fixes, not generic OWASP boilerplate.
- ▌ Factory API Route Engineer · nonlinear-xyzUse 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 (limit/offset/orderBy default; cursor only when needed), multi-field search via `ilike` + `or()`, aggregated stats in list queries, mutation lifecycle hooks, stale-time defaults, custom error class taxonomy, fetch adapter for tRPC in App Router. Outputs endpoints that fit the house style — not bespoke per-route handlers.
- ▌ Factory DB Schema Architect · nonlinear-xyzUse 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 for non-query-driving data, polymorphic table patterns (shared base + variant tables), schema-derived type exports, ESLint Drizzle WHERE-enforcement, soft-delete mixin (Python). Produces schema files that fit the house style — not generic Postgres tables.
- ▌ Factory DB Migration Engineer · nonlinear-xyzUse 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 `data-pipeline-engineer` (ingestion); this agent owns the *runbook discipline* — preflight / mutate / verify / rollback, idempotency by natural key, layered backup independence (Layer C of `factory-security.md`), bidirectional update semantics, validation-at-parse-not-at-constraint, human-gated execution. Outputs a runbook + gating criteria, not raw SQL. Refuses to auto-run any DB command.
- ▌ Factory LLM Workflow Engineer · nonlinear-xyzUse 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 with optional PromptHub override, hybrid search with confidence gating and one-attempt fallback, SSE streaming with shared event-name registry. Cothon is the reference repo.
- ▌ Factory Verification Engineer · nonlinear-xyzUse 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 `db-migration-engineer`'s verify-stage discipline to all changes. Carries the four-tier eval spectrum and the score model from `factory-verification.md`. Invoke before merging a nontrivial change, when onboarding a risky area, or when asking "how would we know this is right?"
- ▌ Factory Auth Wiring Specialist · nonlinear-xyzUse 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 interface, procedure tier stacking, OAuth callback safety (`safeNext`), JWT signature verification with fallback user-linking, admin-client bypass guardrails, role-conditional post-login redirects. Produces auth code that fits the house seam — provider is a swap point, not a leak.
- ▌ Factory Data Pipeline Engineer · nonlinear-xyzUse 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 time-series, the three-entry-point Python pattern (CLI / Cloud Run API / Pub/Sub), YAML config for service-level data, converter/service split, Cloud Run + ephemeral Neon deployment.