typeorm-schema-optimizer
Optimize TypeORM entities for performance, query efficiency, migration safety, and relationship design — analyze decorators, indexes, eager loading, and connection pooling.
What this skill does
# TypeORM Schema Optimizer Analyze TypeORM entities for performance issues, query inefficiencies, missing indexes, relationship design problems, and migration risks. Use when reviewing TypeORM schemas, optimizing slow queries, or preparing for production scale. ## Usage ``` "Optimize my TypeORM entities" "Check for N+1 queries in my TypeORM code" "Audit TypeORM indexes and relations" "Review migration safety for TypeORM changes" ``` ## How It Works ### 1. Entity Discovery ```bash # Find all TypeORM entities grep -rn "@Entity\|@ViewEntity\|@ChildEntity" src/ | head -20 # Find repositories grep -rn "extends Repository\|@InjectRepository\|getRepository" src/ | head -20 # Check TypeORM config cat ormconfig.json 2>/dev/null || cat data-source.ts 2>/dev/null ``` ### 2. Schema Analysis **Column optimization:** - Column types match actual data requirements - Unnecessary `nullable: true` on required fields - Missing `length` on string columns (default is VARCHAR(255) — wasteful or too short?) - Enum columns using string instead of native enum type - JSON columns where structured columns would be more queryable - Missing default values for common patterns **Index analysis:** - Columns used in WHERE clauses without indexes - Composite indexes for multi-column queries - Covering indexes for SELECT-heavy queries - Unique constraints for business rules - Partial indexes for filtered queries - Index on foreign key columns (TypeORM doesn't auto-create) **Relationship design:** - `eager: true` on relationships (loads every time, often unnecessary) - Missing `cascade` options where needed - Circular eager loading (infinite loops) - `@ManyToMany` without join table customization - Missing `onDelete` behavior (default is no action) - Polymorphic relationships using discriminators correctly ### 3. Query Performance - N+1 detection in repository methods - Missing `leftJoinAndSelect` where data is accessed post-query - `find` with deep relations instead of query builder - Missing pagination on list queries - Raw queries bypassing TypeORM benefits - Transaction usage for multi-step writes ### 4. Connection & Pool - Connection pool size appropriate for workload - Idle connection timeout configured - Read replicas configured for read-heavy workloads - Connection error handling and retry logic - Logging level appropriate for environment ### 5. Migration Safety - Entity changes that generate destructive migrations - Column type changes that lose data - Index changes that lock tables - Relationship changes that break foreign keys ## Output ``` ## TypeORM Schema Analysis **Entities:** 18 | **Relations:** 24 | **Indexes:** 12 ### 🔴 Critical (3) 1. **Eager loading loop** — User → Posts (eager) → Author (eager) → Posts... → Remove `eager: true` from at least one side 2. **Missing index on FK** — Order.userId has no index With 500K orders, joins on userId cause full table scans → Add `@Index()` on `userId` column 3. **N+1 in getOrders()** — orders.service.ts:34 Loads orders then iterates to access `order.items` individually → Use `relations: ['items']` or query builder with join ### 🟡 Improvements (4) 4. 6 entities with `eager: true` — performance risk at scale 5. VARCHAR(255) on `status` fields — use enum type (4 possible values) 6. Missing `onDelete: 'CASCADE'` on child entities 7. No read replica configured (DB CPU at 80%) ### ✅ Good Practices - Proper use of table inheritance for payment types - Transaction wrapping for order creation flow - Soft delete with `@DeleteDateColumn` ```
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.