Testing

triage

by weegigs

Interactive issue discovery session. Use when walking through an application to capture issues, then batch-evaluate severity and complexity.

test-driven-development

by liauw-media

"Use when adding features or fixing bugs. Follow RED/GREEN/REFACTOR cycle. Write failing test first, implement minimal code to pass, then refactor."

dotnet-test

by icartsh

dotnet CLI를 사용하여 .NET 테스트를 실행합니다. 유닛 테스트 실행, 코드 커버리지 리포트 생성 또는 벤치마크 수행 시 사용합니다.

spec-writing

by Linaqruf

This skill should be used when the user wants to create project specifications, feature specifications, design system documentation, or update existing specs. Triggers on "create spec", "plan project", "design system", "plan feature", "write specification", "generate SPEC.md", "document my project", "scaffold a spec", "plan my app", "spec out a feature", "create a project plan", "create a CLAUDE.md", "document architecture", "set up my project", "bootstrap a new app", "help me plan", "redesign my UI", "audit my design", "update my spec", or "revise the spec". Covers interview-based specification workflow with codebase analysis, tech stack recommendations, gap analysis, design audit, and optional SPEC/ supplements.

code-review

by HJewkes

Unified code review system — dispatches the right review agents for the situation. Use when reviewing code for quality, bugs, compliance, or before merging.

uv-tdd

by gali-leilei

A development process for Python code that uses Test Drivern Development (TDD) to iterate on a new project based around uv. Use when creating a new Python project, writing Python code with tests, or working on Python development using test-driven development practices with the uv package manager.

platform

by pluginagentmarketplace

Android core components lifecycle, Activities, Fragments, Services, Intent system.

Refactoring Strategies

by AmnadTaowsoam

testing-anti-patterns

by martin-janci

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

php-testing

by pluginagentmarketplace

PHP testing mastery - PHPUnit 11, Pest 3, TDD, mocking, and CI/CD integration

unity-reusable-systems

by eyenpi

Use when building reusable Unity game systems, creating UPM packages, or designing ScriptableObject-based modular architecture for gameplay systems like inventory, combat, dialogue, quests, or save/load. Also use when connecting multiple independent Unity packages that need to communicate without direct dependencies.

spec

by weegigs

Prepare any work for execution planning. Routes to work-type specific workflow.

Claude Code Expert

by mamba-mental

Provide accurate, actionable guidance based on the loaded references and official documentation.

database-backup

by liauw-media

"Backup database before tests, migrations, or other database operations"

artifact-management

by pluginagentmarketplace

Artifact repositories with Nexus, Artifactory, and container registries for build artifact storage

research-question-refiner

by GhostScientist

Helps transform a vague research interest into a concrete, tractable research question. Use when asked to refine a research idea, develop a research question, scope a research project, or figure out what to work on. Walks through systematic refinement with feasibility analysis.

Risk Assessment

by AmnadTaowsoam

Risk assessment is a systematic process of identifying, analyzing, and

test-specialist

by mamba-mental

This skill should be used when writing test cases, fixing bugs, analyzing code for potential issues, or improving test coverage for JavaScript/TypeScript applications. Use this for unit tests, integration tests, end-to-end tests, debugging runtime errors, logic bugs, performance issues, security vulnerabilities, and systematic code analysis.

Websocket Patterns

by AmnadTaowsoam

WebSocket is a communication protocol that provides full-duplex communication

openspec-writing-plans

by AnthemFlynn

"OpenSpec-integrated plan writing. Use INSTEAD of superpowers:writing-plans when project has openspec/ directory. Reads design from OpenSpec change, writes plan to OpenSpec change."

spec-writer

by vibery-studio

Transform conversations and ideas into structured technical specifications. Outputs: User stories, acceptance criteria, technical requirements, edge cases. Use when user wants to document requirements before coding. Triggers: write spec, create user stories, document requirements, /spec

5d-spec

by tapania

"Convert refined plan into technical specification with architectural decisions. Use when: (1) After REFINE phase in 5D-SDD workflow, (2) User is ready for technical design, (3) Moving from 'what' to 'how,' (4) User asks for 'technical spec,' 'architecture,' or 'design doc.' This phase bridges business intent and implementation detail."

spec-feature

by weegigs

Feature specification workflow. Use when specifying new features to generate user stories with EARS acceptance criteria.

arcium-program-development

by sicmundu

Build, refactor, and debug Arcium MXE program code across Arcis circuits (encrypted-ixs) and Anchor programs (programs/*). Use when implementing confidential instructions, wiring init_comp_def/queue_computation/callbacks, deriving Arcium PDAs and callback accounts, handling encrypted I/O and offsets, parsing generated callback output structs, building permission-gated flows, integrating offchain circuit sources, testing with @arcium-hq/client, deploying MXEs, or migrating Arcium versions.