- Home
- /
- Categories
- /
- Types
Types
Type checking and type generation
agentic-docs
by petekp
Write clear, plain-spoken code comments and documentation that lives alongside the code. Use when writing or reviewing code that needs inline documentation like file headers, function docs, architectural decisions, or explanatory comments. Works well for both human readers and AI coding assistants who see one file at a time.
aesthetic-guide
by petekp
Research a UI design aesthetic and produce exhaustive, implementation-ready design guidelines for coding agents. Use when the user names an aesthetic (brutalist, glassmorphism, retro-futuristic, Swiss modernist, Apple HIG, neumorphism, minimalism, cyberpunk, Material Design, art deco, vaporwave, etc.) and wants a complete style guide with exact CSS values, color palettes, component states, animations, and typography â detailed enough for a coding agent to faithfully implement the aesthetic with zero ambiguity.
api-design-patterns
by petekp
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices
airline-cargo-optimization
by kishorkukreja
When the user wants to optimize airline cargo operations, manage air freight, or improve cargo revenue. Also use when the user mentions "air cargo optimization," "cargo capacity management," "freight yield management," "ULD optimization," "cargo routing," "air freight network," or "belly cargo management." For passenger operations, see hotel-inventory-management (for yield management concepts). For tour operations, see tour-operations.
guillotine-cutting
by kishorkukreja
When the user wants to solve cutting problems with guillotine constraints, implement edge-to-edge cutting, or optimize guillotine cutting patterns. Also use when the user mentions "guillotine cuts," "edge-to-edge cutting," "straight cuts only," "two-stage cutting," "three-stage cutting," "n-stage guillotine," or "guillotine cutting stock problem." For general cutting, see 2d-cutting-stock or 1d-cutting-stock. For irregular shapes, see nesting-optimization.
olore-t3-env-latest
by olorehq
Local t3-env documentation reference (latest). T3 Env documentation. Use for type-safe environment variable validation with Zod/Valibot, Next.js and Nuxt integration, and runtime env configuration.
olore-rhf-latest
by olorehq
Local React Hook Form documentation reference (latest). Performant, flexible, and extensible forms with easy-to-use validation.
olore-neverthrow-latest
by olorehq
Local neverthrow documentation reference (latest). Neverthrow documentation. Use for type-safe error handling with Result and ResultAsync, railway-oriented programming, andThen/map chaining, and error aggregation in TypeScript.
olore-zod-3
by olorehq
Local Zod v3 documentation reference. Use when asked about Zod schema validation, TypeScript type inference, error handling, or migration from earlier versions.
olore-zod-latest
by olorehq
Local zod documentation reference (latest). Zod schema validation documentation. Use for TypeScript type inference, parsing, error handling, and schema composition.
olore-xstate-latest
by olorehq
Local XState documentation reference (latest). XState state machine documentation. Use for state machines, statecharts, actors, transitions, guards, context, React/Vue/Svelte integrations, and Stately Studio.
olore-trpc-latest
by olorehq
Local tRPC documentation reference (latest). tRPC documentation. Use for end-to-end typesafe APIs, React Query integration, Next.js adapters, subscriptions, and TypeScript RPC.
olore-tsf-1.27.6
by olorehq
Local TanStack Form documentation reference. Use when asked about TanStack Form features, form validation, form state management, field arrays, React/Vue/Solid/Angular/Svelte form integration, or form submission handling.
olore-langchain-latest
by olorehq
Local LangChain documentation reference (latest). Comprehensive documentation for LangChain and LangGraph frameworks in Python and JavaScript.
olore-tsf-1.27.7
by olorehq
Local TanStack Form documentation reference (1.27.7). Use when asked about form management, validation, field APIs, or framework-specific form implementations.
olore-drizzle-latest
by olorehq
Local Drizzle ORM documentation reference (latest). Use when asked about Drizzle ORM queries, schema definitions, migrations, column types, PostgreSQL/MySQL/SQLite dialects, Drizzle Kit, or database operations.
olore-prisma-latest
by olorehq
Local Prisma documentation reference. Use when asked about Prisma ORM, Prisma Client, Prisma Schema, migrations, database queries, Prisma Accelerate, or Prisma Postgres.
programming-in-react
by ed3dai
Use when writing or modifying React components, planning React features, or working with .jsx/.tsx files - provides modern React patterns with TypeScript, hooks usage, component composition, and common pitfalls to avoid
Bun Redis
by secondsky
Use when working with Redis in Bun (ioredis, Upstash), caching, pub/sub, session storage, or key-value operations.
wednesday-dev
by wednesday-solutions
Technical development guidelines for Wednesday Solutions projects. Enforces import ordering, complexity limits, naming conventions, TypeScript best practices, and code quality standards for React/Next.js applications.
wednesday-design
by wednesday-solutions
Design and UX guidelines for Wednesday Solutions projects. Covers visual design tokens, animation patterns, component standards, accessibility, and user experience best practices for React/Next.js applications. ENFORCES use of approved component libraries only.
test-driven-development
by romiluz13
"Internal skill. Use cc10x-router for all development tasks."
generic-fullstack-code-reviewer
by travisjneuman
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.
jscpd
by knoopx
Finds duplicate code blocks and analyzes duplication metrics across files. Use when identifying copy-pasted code, measuring technical debt, or preparing for refactoring.