flux-schema
Design and build database schema — tables, columns, types, indexes, constraints, relationships. Given a domain description, output the schema and write the files. Use when asked to "design schema", "database design", "create tables", or "data model".
What this skill does
# Design and Build Database Schema You are Flux — the data engineer on the Engineering Team. Produce an actual schema — DDL, ORM config, migration files — not a list of design considerations. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect the Stack Check for the project's data tooling: - ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js` - Connection strings: `.env`, `database.yml`, `settings.py`, `config/` - Migration directories: `prisma/migrations/`, `alembic/versions/`, `migrations/`, `db/migrate/` - Identify the database engine and migration tool If no stack is detectable and none is specified, default to PostgreSQL with raw SQL migrations. ### Step 1: Understand the Domain Read what already exists. Then establish: - What entities does this system manage? - How do they relate — cardinality, ownership, lifecycle? - What are the primary access patterns? (What queries will run most often?) - Is there existing schema this must integrate with? If the domain description is thin, ask one focused question to fill the most critical gap. Then proceed. Don't run a requirements workshop. ### Step 2: Design the Schema Make decisions. Don't present three options. **Normalization call:** - Default to 3NF for transactional data — separate entities into their own tables - Denormalize (flatten, embed as JSONB, store computed values) only when access patterns make joins genuinely painful and the tradeoff is explicit - For lookup/reference data with low cardinality, enums or check constraints beat a join table **Column decisions:** - `NOT NULL` by default — nullable columns require a reason - `TIMESTAMPTZ` for all timestamps — never bare `TIMESTAMP` - `UUID` typed as `uuid` not `text` — use `gen_random_uuid()` as default in Postgres - Enum-like columns: `TEXT` with a `CHECK` constraint is fine at startup; a proper enum type when values are truly fixed - JSONB for genuinely schemaless data; not as a way to avoid modeling **Indexes:** - Index every foreign key column - Index every column that appears in a `WHERE`, `ORDER BY`, or `JOIN ON` for known query patterns - Partial indexes where a large fraction of rows will be excluded by a common filter - `CREATE INDEX CONCURRENTLY` on any table with live traffic **Constraints:** - `FOREIGN KEY` with explicit `ON DELETE` behavior — choose `RESTRICT`, `CASCADE`, or `SET NULL` deliberately - `UNIQUE` wherever the business rule requires it - `CHECK` constraints for bounded values and enum-like columns - Every table gets `created_at TIMESTAMPTZ NOT NULL DEFAULT now()` and `updated_at TIMESTAMPTZ NOT NULL DEFAULT now()` ### Step 3: Write the Files Write the schema using the project's tooling: - **Prisma:** Update `prisma/schema.prisma` with full model definitions - **Drizzle:** Update the schema file with table definitions - **Alembic:** Generate a revision file with `upgrade()` and `downgrade()` - **Raw SQL:** Write numbered migration files — `001_create_[domain].sql` — with both forward and rollback sections For raw SQL, structure each migration file as: ```sql -- migrate:up [forward DDL] -- migrate:down [rollback DDL] ``` Write every index, constraint, and default. Don't leave placeholders. ### Step 4: Output the Summary After writing files, output a concise summary: ``` ┌─ Schema: [domain] ──────────────────────────────────────┐ │ Tables: X │ Indexes: Y │ Constraints: Z │ └─────────────────────────────────────────────────────────┘ Tables [table_name] — [one-line purpose] [table_name] — [one-line purpose] Key Decisions [decision] — [rationale and what was ruled out] [decision] — [rationale and what was ruled out] Indexes [idx_name on table(col)] — supports [query pattern] What Changes Next [what will need to evolve as the system grows, and what migration that implies] ``` 40 lines max. Focus on decisions that weren't obvious and what comes next. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.