Types
Type checking and type generation
clickhouse-schema-design
by obsessiondb
"15+ schema rules for ClickHouse tables. ALWAYS LOAD when creating or modifying tables. Achieves sub-second queries, 10x compression, and automated data lifecycle."
vscode-extension-uiux
by kcchien
Build secure, elegant, and accessible VS Code extensions with excellent UI/UX. Covers the complete Extension API including webviews, tree views, custom editors, sidebars, panels, and activity bar integration. Use this skill when: (1) Creating new VS Code extensions, (2) Building webview-based UIs, (3) Implementing tree views or custom editors, (4) Adding sidebar/panel contributions, (5) Ensuring extension security (CSP, message validation), (6) Theming and accessibility compliance, (7) Reviewing or improving existing extension UI/UX.
typescript-style
by jpoutrin
TypeScript coding style enforcement (ESLint, type safety, React patterns). Auto-loads when writing or reviewing TypeScript/JavaScript code.
Formily Migration Guide
by whinc
This skill should be used when the user asks to "convert to formily", "formily migration", "migrate forms to formily", "convert react forms to formily", "formily vs other form libraries", or "replace existing forms with formily".
Formily Core Fundamentals
by whinc
This skill should be used when the user asks to "learn formily basics", "setup formily", "formily core concepts", "formily getting started", "formily fundamentals", "how to use formily", "formily installation", or "formily form state management".
iot-developer
by daffy0208
Expert in IoT development, microcontrollers, sensors, and MQTT protocols
search-knowledge
by mischasigtermans
Deep Laravel knowledge for code reviews. Provides detailed guidance on Eloquent, controllers, validation, routing, authorization, Blade, events, testing, and collections.
zod
by anivar
Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, and v3→v4 migration. Baseline: zod ^4.0.0. Triggers on: zod imports, z.object, z.string, z.infer, safeParse, mentions of "zod", "schema validation", "zod v4", or "z.enum".
flow-designer
by khgs2411
Design features through brainstorming and make architectural decisions. Use when user wants to brainstorm, design approach, make architecture choices, or update PLAN.md.
flow-architect
by khgs2411
Guide architectural decisions and PLAN.md updates using Flow framework. Use when user discusses "architecture", "how should we architect", "design patterns", "how should we structure", "how do we structure", "technology choice", "should we use", "DO/DON'T rules", "update architecture", or wants to update Architecture section in PLAN.md. Helps document architectural decisions, update DO/DON'T guidelines, define scope boundaries, and record technology choices during brainstorming.
your-skill-name
by khgs2411
Brief description of what this Skill does and when to use it. Include specific trigger phrases users would say. Use when user asks "trigger phrase 1", "trigger phrase 2", or wants to [outcome]. Max 1024 characters.
amazon-web-services
by oakoss
Core AWS services for application developers. Covers S3 (storage, presigned URLs, lifecycle), Lambda (functions, layers, cold starts), IAM (roles, policies, least privilege), DynamoDB (single-table design, GSI/LSI, streams), SQS/SNS (queues, topics, fan-out), CloudFront (CDN, caching), RDS/Aurora (Postgres/MySQL, connection pooling), ECR/ECS/Fargate (containers), Route 53 (DNS), Secrets Manager, and CDK v2 (TypeScript IaC, constructs, stacks, testing). Use when building AWS infrastructure, writing CDK stacks, configuring IAM policies, designing DynamoDB tables, setting up Lambda functions, creating S3 presigned URLs, deploying containers on ECS/Fargate, or configuring CloudFront distributions.
hono
by oakoss
'Hono ultrafast web framework for edge and server runtimes. Use when building APIs, middleware chains, or edge functions on Cloudflare Workers, Bun, Node.js, or Deno. Use for hono, api, routing, middleware, cloudflare-workers, edge, rpc, validator, context.'
bun-runtime
by oakoss
Bun JavaScript runtime, bundler, and package manager. Covers Bun.serve() HTTP server, Bun.file() I/O, SQLite, password hashing, Bun.build() bundler, bun:test runner, and package management. Use when building with Bun APIs, running scripts with Bun, bundling code, managing packages with bun install/add, or writing tests with bun:test.
api-testing
by oakoss
API testing patterns with supertest, MSW, and Vitest. Covers integration testing for REST APIs, HTTP request mocking with Mock Service Worker v2, response assertions, schema validation, test organization, and framework-specific patterns for Express, Fastify, and Hono. Use when writing integration tests for REST APIs, mocking HTTP requests, or testing API endpoints. Use for api-test, supertest, msw, mock-service-worker, integration-test, http-mock, endpoint-test, request-test.
architecture-auditor
by marcioaltoe
Architecture audit and analysis specialist for Modular Monoliths. ALWAYS use when reviewing codebase architecture, evaluating bounded contexts, assessing shared kernel size, detecting "Core Obesity Syndrome", or comparing implementation against ADR-0001 and anti-patterns guide. Use proactively when user asks about context isolation, cross-context coupling, or shared kernel growth. Examples - "audit contexts structure", "check shared kernel size", "find cross-context imports", "detect base classes", "review bounded context isolation", "check for Core Obesity".
typescript-type-safety
by marcioaltoe
TypeScript type safety including type guards and advanced type system features. ALWAYS use when writing ANY TypeScript code (frontend AND backend) to ensure strict type safety, avoid any types, and leverage the type system. Examples - "create function", "implement class", "define interface", "type guard", "discriminated union", "type narrowing", "conditional types", "handle unknown types".
requirements-gathering
by DauQuangThanh
Guides comprehensive requirements gathering and analysis including stakeholder interviews, user story creation, use case documentation, acceptance criteria, requirements prioritization, and traceability. Produces requirements documents, user stories, use cases, and development roadmaps. Use when gathering requirements, writing user stories, creating acceptance criteria, analyzing stakeholder needs, prioritizing features, or when users mention requirements analysis, business analysis, user stories, use cases, or requirements documentation.
project-workflow
by marcioaltoe
Development workflow and quality gates for the Bun + TypeScript stack. ALWAYS use before commits to ensure quality gates are met. Also use when starting development or when user asks about workflow process. Examples - "before commit", "quality gates", "workflow checklist", "bun commands", "pre-commit checks".
frontend-builder
by oakoss
'Builds modern React and Next.js frontends. Use when creating web applications, choosing frontend stack, structuring components, implementing UI/UX designs, or setting up project architecture. Use for React, Next.js, Tailwind CSS, shadcn/ui, server components, and component patterns.'
database-architect
by marcioaltoe
Expert database schema designer and Drizzle ORM specialist. Use when user needs database design, schema creation, migrations, query optimization, or Postgres-specific features. Examples - "design a database schema for users", "create a Drizzle table for products", "help with database relationships", "optimize this query", "add indexes to improve performance", "design database for multi-tenant app".
git-commit
by marcioaltoe
Automatically analyzes code changes and creates git commits with conventional commit messages when the user indicates they want to save/commit their work. Use when user mentions committing, saving work, or wants changes recorded in git history. Examples - "commit these changes", "save this work", "I'm done with this feature, let's commit", "create a commit for the auth updates".
naming-conventions
by marcioaltoe
Expert in naming conventions for files, directories, classes, functions, and variables. ALWAYS use when creating ANY files, folders, classes, functions, or variables, OR when renaming any code elements. Use proactively to ensure consistent, readable naming across the codebase. Examples - "create new component", "create file", "create folder", "name this function", "rename function", "rename file", "rename class", "refactor variable names", "review naming conventions".
clean-architecture
by marcioaltoe
Clean Architecture principles for Modular Monolith with bounded contexts and minimal shared kernel. ALWAYS use when working on backend code, ESPECIALLY when creating files, deciding file locations, or organizing contexts (auth, tax, bi, production). Use proactively to ensure context isolation and prevent "Core Obesity Syndrome". Examples - "create entity", "add repository", "where should this file go", "modular monolith", "bounded context", "shared kernel", "context isolation", "file location", "layer organization".