erikstmartin
43 verified skills645 total stars
code-review-excellence
Use when conducting code reviews or establishing review standards. Not for requesting or receiving review.
development15
deslop
Use after AI-generated code to remove slop (excess comments/defensive checks). Not for general refactors.
development15
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing15
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
data-ai15
vite
Use for Vite config, plugins, SSR, or Vite 8/Rolldown migration. Not for Vitest testing.
tools15
agent-browser
Use for automated browser tasks (navigation, form filling, scraping, screenshots, web app testing). Not for simple one-off browsing.
development15
agents-md
Use when asked to write or review AGENTS.md/CLAUDE.md/LLMs.md context files.
documentation15
audio-dsp
Use when implementing real-time DSP algorithms, audio thread architecture, or offline spectral analysis in C++/Rust. Covers filters, STFT pipelines, lock-free concurrency, and RT safety. Not for JUCE plugin lifecycle wiring or ffmpeg.
tools15
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
development15
skills/global/.agents/skills/cartography
--- name: cartography description: Use to map or understand a repository: generate codemaps, architecture overviews, or codebase documentation. Triggers include "map the codebase", "codemap", or "architecture overview". --- # Cartography Skill You help users understand and map repositories by creating hierarchical codemaps. ## When to Use - User asks to understand/map a repository - User wants codebase documentation - Starting work on an unfamiliar codebase ## Workflow ### Step 1: Check fo
development15
cpp-testing
Use when writing or fixing C++ tests, configuring GoogleTest/CTest, or adding coverage/sanitizers.
development15
skills/catalog/csharp/csharp
--- name: csharp description: Use for .NET 8+ C# apps: ASP.NET Core APIs, Blazor, EF Core, minimal APIs, async patterns, CQRS with MediatR, and Dapper. --- # C# / .NET 8+ ## When to Use This Skill - Building ASP.NET Core APIs (Minimal or Controller-based) - Implementing EF Core or Dapper data access - Creating Blazor web applications (Server / WASM) - Optimising .NET performance with `Span<T>`, `Memory<T>`, AOT - Implementing CQRS with MediatR - Setting up authentication / authorisation - Red
development15
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
testing15
ffmpeg
Use when programmatically processing video/audio with libffmpeg C API. Not for command-line ffmpeg operations.
development15
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
development15
godot-architecture
Use when making system design decisions in Godot 4.x — ownership, signal topology, performance trade-offs, scene boundaries, or large-scale feature architecture. Not for routine scripting tasks (use godot-core).
development15
skills/catalog/frontend/vitest
--- name: vitest description: Use for Vitest tests: mocking, coverage, fixtures, filtering, and setup. Not for non-Vitest testing frameworks. --- # Vitest Vitest 3.x testing workflow — Jest-compatible API with Vite-native transforms. ## Workflow 1. **Setup** — `vitest.config.ts` or inline in `vite.config.ts` with `test` key 2. **Write tests** — `describe`/`it`/`expect` (Jest-compatible), use `.test.ts` or `.spec.ts` 3. **Mock** — `vi.mock()` for modules, `vi.fn()` for functions, `vi.spyOn()`
development15
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development15
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
testing15
godot-core
Use when writing GDScript, creating scenes, adding nodes, or doing day-to-day Godot 4.x development. Covers project structure, script patterns, signals, resources, and MCP tools.
tools15
cybersecurity
Use for security audits, vulnerability remediation, hardening configs, and secure coding patterns. Not for compliance frameworks or policy writing.
development15
rust-best-practices
Use when writing or refactoring Rust for idioms, ownership/borrowing choices, Result-based error handling, performance, and tests/docs.
development15
terraform
Use when writing, reviewing, or refactoring Terraform HCL — covers project setup, resource authoring, module development, and pre-commit validation.
development15
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development15
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
tools15
skills/catalog/audio/juce-framework
--- name: juce-framework description: Use for JUCE audio apps/plugins: AudioProcessor lifecycle, VST3/AU targets, parameter systems, and thread separation. Requires audio-engineering-principles. Not for game-audio middleware or non-JUCE frameworks. --- Requires: audio-engineering-principles May use: dsp-algorithms, audio-systems ## Purpose Builds production-quality JUCE-based software: standalone apps, plugin targets (VST3/AU), shared DSP cores, parameter systems, UI wiring, and host/device in
tools15
postgres
Use when working with PostgreSQL — schema design, indexing, query optimization (EXPLAIN/ANALYZE), connection pooling, VACUUM/autovacuum, migrations, and performance troubleshooting.
data-ai15
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
development15
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
development15
skills/catalog/rust/rust-async-patterns
--- name: rust-async-patterns description: Use for async Rust with Tokio: tasks, channels, error handling, concurrency patterns, and debugging async issues. --- # Rust Async Patterns Production patterns for async Rust programming with Tokio runtime, including tasks, channels, streams, and error handling. ## When to Use This Skill - Building async Rust applications - Implementing concurrent network services - Using Tokio for async I/O - Handling async errors properly - Debugging async code is
development15
simplify
Use after manual code changes to improve clarity/readability without changing behavior. Not for AI slop cleanup.
development15
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development15
sqlite
Use when working with SQLite databases — schema design, migrations, query tuning, WAL/locking, pragma configuration, and file-based deployment.
devops15
shadcn-ui
Use when setting up or using shadcn/ui components (install, configure, themes, forms, dialogs, tables). Not for non-React UI frameworks.
development15
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
development15
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
tools15
audio-engineering-principles
Use for real-time audio code safety, determinism, and numeric hygiene. Required foundation for DSP, audio analysis, audio systems, and JUCE work. Not for game-audio middleware or ffmpeg/video tasks.
development15
cpp-development
Use when writing, reviewing, or refactoring C++ code — covers workflow, essential patterns, and pre-commit checklist for modern C++17/20.
development15
skills/catalog/frontend/tailwind-design-system
--- name: tailwind-design-system description: Use for Tailwind v4 design systems: tokens, component libraries, and responsive patterns. --- # Tailwind Design System (v4) Build a production design system with Tailwind CSS v4 using CSS-first configuration, semantic tokens, and CVA components. ## 1. Design System Setup **Step 1 — Install dependencies:** ```bash npm install tailwindcss@next @tailwindcss/vite clsx tailwind-merge class-variance-authority ``` **Step 2 — Replace tailwind.config.ts
development15
docker-expert
Use for Dockerfiles, multi-stage builds, image optimization, Compose, container security, and runtime debugging. Not for Kubernetes/Helm or cloud-specific container services.
development15
godot-audio
Use for Godot game-audio and middleware integration — AudioBus routing, Wwise/FMOD events, adaptive music, and procedural sound systems. Not for DSP, JUCE, ffmpeg, or offline audio pipelines.
development15
kubernetes-specialist
Use when deploying or managing Kubernetes workloads requiring cluster configuration, security hardening, or troubleshooting. Invoke for Helm charts, RBAC policies, NetworkPolicies, storage configuration, performance optimization.
testing15
skills/catalog/ruby/ruby-rails
--- name: ruby-rails description: Use for Rails apps: ActiveRecord/models, migrations, controllers/routes, background jobs, caching, and Hotwire. Not for non-Rails Ruby. --- # Ruby on Rails Idiomatic Rails development — conventions, ActiveRecord, and production patterns. ## Workflow 1. **Model** — schema + migrations + validations + scopes 2. **Controller** — thin controllers, strong params, respond_to 3. **Background** — ActiveJob with Sidekiq, idempotent + retry-safe 4. **Performance** — N
development15