Testing
Unit tests, integration tests, test automation
unit-test-philosophy
by open-agreements
Risk-based unit testing and Allure-readable behavioral spec style for open-agreements. Use when adding/updating tests, expanding coverage, or reviewing test quality across src, integration-tests, and workspace packages.
playwright-patterns
by ed3dai
Use when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakiness
test-driven-development
by ed3dai
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
executing-an-implementation-plan
by ed3dai
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage
qedgen
by QEDGen
Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions "qedgen", "lean proof", "formal proof", "verify my code", "prove correctness", "formal verification", or wants mathematical guarantees about their implementation.
journalist-analyst
by rysweet
Analyzes events through journalistic lens using 5 Ws and H, investigative methods, source evaluation, fact-checking, newsworthiness criteria, and ethical journalism principles. Provides insights on story angles, information gaps, credibility, public interest, and media framing. Use when: Breaking news, information verification, source analysis, story development, media criticism. Evaluates: Factual accuracy, source credibility, completeness, newsworthiness, bias, public interest.
llm-judge
by existential-birds
LLM-as-judge methodology for comparing code implementations across repositories. Scores implementations on functionality, security, test quality, overengineering, and dead code using weighted rubrics. Used by /beagle:llm-judge command.
llm-artifacts-detection
by existential-birds
Detects common LLM coding agent artifacts in codebases. Identifies test quality issues, dead code, over-abstraction, and verbose LLM style patterns. Use when cleaning up AI-generated code or reviewing for agent-introduced cruft.
feature-plan
by steveclarke
Create implementation plan documents with development phases, sequencing, and actionable tasks. Works through 3 phases (structure, approach, generation) following established feature development process. Use when creating plan.md documents from technical specs. Triggers on "create implementation plan", "plan this feature", "sequence the development".
code-review
by steveclarke
Conduct thorough code reviews with structured feedback on security, performance, architecture, and testing. Generates trackable review documents with prioritized issues (critical/required/suggestions) and educational content. Use when reviewing PRs or code changes. Triggers on "review this code", "code review", "review PR".
feature-vision
by steveclarke
Vision Document
goal
by steveclarke
Quick goal planning for technical tasks. Compressed vision-requirements-spec-plan into a single goal.md through a brief interview (3-6 questions). For tasks bigger than ad-hoc but not needing the full feature process.
code-refactoring
by baz-scm
The practice of restructuring and simplifying code continuously – reducing complexity, improving design, and keeping codebases clean.
ai-assisted-development
by baz-scm
Leveraging AI coding assistants and tools to boost development productivity, while maintaining oversight to ensure quality results.
testing-debugging
by baz-scm
Ensuring software correctness and reliability by writing automated tests, using quality assurance tools, and systematically debugging issues.
dev-test
by edwinhu
"This skill should be used when the user needs to 'debug web applications', 'test UI interactions', 'capture screenshots or network requests', 'test desktop automation', or needs to select between testing tools. Routes to platform-specific E2E testing skills: Chrome MCP for debugging, Playwright for CI/CD, Hammerspoon for macOS, Linux for X11/Wayland."
playwright-debugging
by ed3dai
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
zeabur-domain-url
by zeabur
Use when services need public URL for redirects or CORS. Use when WEB_URL or similar has trailing slash issues.
consult
by saadshahd
Use when asking "code like [expert]", "what would [expert] say", "idiomatic", "best practice", "panel", "debate", or needing domain guidance. Triggers on expert names, style requests, tradeoff questions, or "stuck on".
intent
by saadshahd
Turn rough ideas into iron-clad work orders. Use when request is vague like "add a button", "make it better", "fix the thing". Triggers on ambiguous or underspecified requests.
observe
by saadshahd
On-demand codebase health check. Use when "observe", "health check", "is the codebase healthy", "check for drift", "system status", or before starting a large feature.
sf-flow
by Jaganpro
Creates and validates Salesforce flows with 110-point scoring and Winter '26 best practices. Use when building record-triggered flows, screen flows, autolaunched flows, scheduled flows, or reviewing existing flow performance.
sf-apex
by Jaganpro
Generates and reviews Salesforce Apex code with 2025 best practices and 150-point scoring. Use when writing Apex classes, triggers, test classes, batch jobs, or reviewing existing Apex code for bulkification, security, and SOLID principles.
flutter-testing
by MADTeacher
Comprehensive Flutter testing guidance covering unit tests, widget tests, and integration tests. Use when working with Flutter applications to write unit tests for functions/methods/classes, create widget tests to verify UI components, develop integration tests for end-to-end testing, mock dependencies and plugin interactions, debug common testing errors, test Flutter plugins with native code, and run tests in different build modes (debug, profile, release)