Loading...
Loading...
Found 2,225 Skills
Front-end development expert for this project. Responsible for handling all code writing, component modification, page construction and consulting tasks. **Please check if this Skill is loaded first** before handling related tasks; if not loaded, you **must** call it first. This Skill has built-in project-specific environment detection logic that automatically identifies the KWC LWC architecture (checks for .kd directory, etc.) and enforces mandatory development specifications (i.e., rule.md in this Skill's directory). Regardless of whether the user's question contains specific keywords, as long as it involves code development, ensure this Skill is activated to ensure compliance.
Agent Skill for Swift architecture design and implementation patterns, with architecture-specific playbooks and review checklists. Use when designing new features, refactoring existing modules, reviewing pull requests, or debugging maintainability issues in SwiftUI/UIKit projects and you need concrete guidance for MVVM, MVI, TCA, Clean Architecture, VIPER, or Reactive patterns.
Use this skill when building design systems, creating component libraries, defining design tokens, implementing theming, or setting up Storybook. Triggers on design tokens, component library, Storybook, theming, CSS variables, style dictionary, variant props, compound components, and any task requiring systematic UI component architecture.
Use this skill when designing presentations, slide decks, or pitch materials. Triggers on "create a presentation", "design slides", "build a deck", "structure my talk", "make a pitch deck", "data visualization for slides", or any request involving slide layout, storytelling frameworks (Pyramid Principle, Hero's Journey, Problem-Solution-Benefit), narrative arc, speaker notes, or chart selection for presentations. Covers slide structure, visual hierarchy, data-driven storytelling, and deck architecture from executive summaries to conference keynotes.
Use this skill when designing help center architecture, writing support articles, or optimizing search and self-service. Triggers on knowledge base, help center, support articles, self-service, article templates, search optimization, content taxonomy, and any task requiring help documentation design or management.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version focused on core proactive capabilities.
Scan the codebase and generate/update CLAUDE.md + reference files (exports, architecture, dev guide) with real project-specific patterns. Run after each coding session or major refactor to keep the AI context map current. Supports Laravel, Next.js, NestJS, Expo/React Native, and Node.js projects.
Monorepo tooling, task orchestration, and workspace architecture for JavaScript/TypeScript repositories. Use when setting up Turborepo, Nx, pnpm workspaces, or npm workspaces; designing package boundaries; configuring remote caching; optimizing CI for affected packages; managing versioning with Changesets; or untangling circular dependencies. Activate on "monorepo", "turborepo", "nx", "pnpm workspace", "task pipeline", "remote cache", "changesets", "CODEOWNERS", "circular dependency", "affected packages", "workspace". NOT for git submodules or multi-repo federation strategies, non-JavaScript monorepos (Bazel, Pants, Buck), or single-package repository setup.
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
Saves, retrieves, and searches structured context (reasoning, decisions, trade-offs) behind AI-generated code, linked to git commits. Use when the developer says "save this session with GitWhy", asks about past context or decisions, or wants to push context to a PR. Also use after significant implementation work, debugging sessions, or architecture decisions.
Multi-tenant architecture patterns. Database-per-tenant, schema-per-tenant, shared-schema with tenant ID, row-level security, tenant resolution, and data isolation. USE WHEN: user mentions "multi-tenant", "multitenancy", "SaaS architecture", "tenant isolation", "row-level security", "tenant ID", "subdomain routing" DO NOT USE FOR: general database design - use database skills; authentication - use auth skills
Implement multiplayer games with Unity Netcode, Mirror, or Photon. Masters client-server architecture, state synchronization, and lag compensation. Use for multiplayer features, networking issues, or real-time synchronization.