security-auditor
Expert security auditor specializing in comprehensive security assessments, compliance validation, and risk management. Masters security frameworks, audit methodologies, and compliance standards with focus on identifying vulnerabilities and ensuring regulatory adherence.
test-automator
Expert test automation engineer specializing in building robust test frameworks, CI/CD integration, and comprehensive test coverage. Masters multiple automation tools and frameworks with focus on maintainable, scalable, and efficient automated testing solutions.
ralph-gpu
Minimal WebGPU shader library for creative coding and real-time graphics. Provides fullscreen passes, particles, compute shaders, render targets, and ping-pong buffers with automatic uniform bindings and global time/resolution tracking.
shader-effects
Visual shader effects—glow/bloom, chromatic aberration, distortion, vignette, film grain, scanlines, glitch, dissolve, outline, and fresnel. Use when adding visual polish, post-processing effects, or stylized rendering to shaders.
shader-fundamentals
GLSL shader fundamentals—vertex and fragment shaders, uniforms, varyings, attributes, coordinate systems, built-in variables, and data types. Use when writing custom shaders, understanding the graphics pipeline, or debugging shader code. The foundational skill for all shader work.
shader-noise
Procedural noise functions in GLSL—Perlin, simplex, Worley/cellular, value noise, FBM (Fractal Brownian Motion), turbulence, and domain warping. Use when creating organic textures, terrain, clouds, water, fire, or any natural-looking procedural patterns.
shader-router
Decision framework for GLSL shader projects. Routes to specialized shader skills (fundamentals, noise, SDF, effects) based on task requirements. Use when starting a shader project or needing guidance on which shader techniques to combine.
webgl
WebGL shaders and effects for JARVIS 3D HUD
github-pr-comment-analyzer
Use when analyzing PR review comments to determine relevance, identify ambiguities, and generate a comprehensive report without making code changes. Useful for understanding feedback landscape and initiating collaborative Q&A discussions about unclear or potentially outdated comments.
resolving-github-pull-request-reviews
Describes the process of resolving pull request CI checks and review comments. Use when a pull request needs fixing, or has comments that suggest improvements. Results in fixed failing CI checks, Evaluates if review comments are worth actioning and responds to review comments.
writing-and-creating-git-commits
Create semantic git commits following best practices and Conventional Commits specification.
writing-github-pr-descriptions
Use when gh pr edit --body fails silently or returns no error but doesn't persist changes - provides fallback pattern using GitHub REST API directly for reliable PR description updates
software-design
Organizes reusable software design pattern skills, when choosing a structural, creational, or behavioral pattern, resulting in faster selection of the right pattern-specific skill.
abstract-factory
Use when you must create compatible sets of related objects without binding client code to concrete classes.
adapter
Use when an existing class has useful behavior but an incompatible interface blocks integration with client code.
bridge
Use when abstractions and implementations need to evolve independently without creating subclass explosion.
builder
Use when object construction requires many ordered or optional steps and constructor signatures are becoming brittle.
chain-of-responsibility
Use when multiple handlers may process a request and you need flexible routing without hard-coding sender-to-receiver coupling.
command
Use when operations must be represented as objects so execution, scheduling, undo, and logging can vary independently from invokers.
composite
Use when clients must treat individual objects and nested object groups uniformly through one interface.
decorator
Use when responsibilities must be added dynamically to objects without subclass proliferation.
facade
Use when a subsystem is too complex for clients and you need a focused, stable entry point.
factory-method
Use when object creation varies by context and you need to extend product types without rewriting client orchestration code.
flyweight
Use when huge numbers of similar objects cause memory pressure and shared intrinsic state can be externalized.
iterator
Use when clients must traverse aggregate data uniformly without exposing internal collection representation.
mediator
Use when many components communicate in tangled peer-to-peer paths and interactions should be coordinated through a central policy hub.
memento
Use when object state must be snapshotted and restored later without exposing internal representation details.
observer
Use when state changes in one object must notify many dependents while keeping publishers decoupled from subscriber implementations.
prototype
Use when object creation is expensive or dynamic and cloning existing configured instances is safer than rebuilding from scratch.
proxy
Use when access to an object must be controlled, deferred, secured, or monitored through a surrogate.
singleton
Use when exactly one coordinated instance is required and its lifecycle, access, and state boundaries can be strictly controlled.
state
Use when an object's behavior changes by internal mode and conditional branches are growing around state transitions.
strategy
Use when multiple interchangeable algorithms are needed and clients should switch behavior without branching on concrete implementations.
template-method
Use when an algorithm skeleton is stable but specific steps must vary across implementations without duplicating workflow structure.
visitor
Use when stable object structures need new operations added frequently without modifying each element class.
feature-arch
React feature-based architecture guidelines for scalable applications (formerly feature-architecture). This skill should be used when writing, reviewing, or refactoring React code to ensure proper feature organization. Triggers on tasks involving project structure, feature organization, module boundaries, cross-feature imports, data fetching patterns, or component composition.
framer-motion-animator
Creates smooth animations and micro-interactions using Framer Motion including page transitions, gestures, scroll-based animations, and orchestrated sequences. Use when users request "add animation", "framer motion", "page transition", "animate component", or "micro-interactions".
gsap-framer-scroll-animation
>-
playwright
Playwright testing best practices for Next.js applications (formerly test-playwright). This skill should be used when writing, reviewing, or debugging E2E tests with Playwright. Triggers on tasks involving test selectors, flaky tests, authentication state, API mocking, hydration testing, parallel execution, CI configuration, or debugging test failures.
react-hook-form
React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, and useFieldArray. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those).
react
React 19 performance optimization guidelines for concurrent rendering, Server Components, actions, hooks, and memoization (formerly react-19). This skill should be used when writing React 19 components, using concurrent features, or optimizing re-renders. This skill does NOT cover Next.js-specific features like App Router, next.config.js, or Next.js caching (use nextjs-16-app-router skill). For client-side form validation with React Hook Form, use react-hook-form skill.
shadcn-installing-components
Installs shadcn registry components into ui-foundation with monorepo-safe paths, when adding official or third-party shadcn components to pkgs/libs/ui-foundation, resulting in registry-folder placement, relative imports, explicit subpath exports, and no root barrel exports.
shadcn
shadcn/ui component library best practices and patterns (formerly shadcn-ui). This skill should be used when writing, reviewing, or refactoring shadcn/ui components to ensure proper architecture, accessibility, and performance. Triggers on tasks involving Radix primitives, Tailwind styling, form validation with React Hook Form, data tables, theming, or component composition patterns.
tailwind
Tailwind CSS v4 performance optimization and best practices guidelines (formerly tailwindcss-v4-style). This skill should be used when writing, reviewing, or refactoring Tailwind CSS v4 code to ensure optimal build performance, minimal CSS output, and correct usage of v4 features. Triggers on tasks involving Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
tdd
Test-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing test-first approaches. Triggers on "write tests first", "test before code", "red green refactor", "test driven development". This skill does NOT cover Vitest framework specifics (use vitest skill) or API mocking with MSW (use msw skill).
typescript
This skill should be used when the user asks to "optimize TypeScript performance", "speed up tsc compilation", "configure tsconfig.json", "fix type errors", "improve async patterns", or encounters TS errors (TS2322, TS2339, "is not assignable to"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.
ui-design
UI/UX and frontend design best practices guidelines (formerly frontend-design). This skill should be used when writing, reviewing, or designing frontend code to ensure accessibility, performance, and usability. Triggers on tasks involving HTML structure, CSS styling, responsive layouts, form design, animations, or accessibility improvements.
vitest
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
worktrunk
Guidance for Worktrunk (the `wt` CLI) — git worktree management, hooks, and config. Load when editing .config/wt.toml or ~/.config/worktrunk/config.toml; adding, modifying, or debugging hooks (post-merge, post-start, pre-commit, pre-merge, post-switch, etc.); configuring commit message generation or command aliases; or troubleshooting wt behavior. Also answers general worktrunk/wt questions.
wt-switch-create
Create a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it. Use when launching a session that should work in its own worktree (e.g. `/wt-switch-create my-branch -- <task>`, or `/wt-switch-create my-branch ~/workspace/other-repo -- <task>`), or mid-session to move work into a fresh branch.
Page 3 of 5 · 245 results