- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
jazz-testing
by garden-co
Use this skill when you need to write, review, or debug automated tests for applications built on the Jazz framework. This skill provides the correct architectural patterns for simulating local-first synchronization and multi-user environments without resorting to invalid mocking strategies.
benchmarking
by garden-co
Use this skill when writing or running performance benchmarks for Jazz packages. Covers cronometro setup, file conventions, gotchas with worker threads, and how to compare implementations.
playwright-testing
by fcakyon
This skill should be used when user asks about "Playwright", "responsiveness test", "test with playwright", "test login flow", "file upload test", "handle authentication in tests", or "fix flaky tests".
vitest-bdd-3layer
by solidSpoon
'DashPlayer 三层 Vitest-BDD 技能。Use when developers want business-readable BDD scenarios without coupling scenario writing to code implementation details. Triggers on: "BDD 三层", "行为测试分层", "给定当那么", "Vitest BDD", "不想在场景里写实现".'
External Project Reality Auditor
by majiayu000
The most comprehensive Claude Code skills registry Web Search: https://skills-registry-web.vercel.app
Spec Management workflow
by majiayu000
The most comprehensive Claude Code skills registry Web Search: https://skills-registry-web.vercel.app
node-logs
by scitix
Retrieve logs from a Kubernetes node. Supports journalctl (systemd units) and file-based logs. Use when you need to inspect node-level logs (containerd, kubelet, etc.). Execute via node_script tool.
mz-test
by MaterializeInc
This skill should be used when the user wants to "run tests", "run testdrive", "run sqllogictest", "run mzcompose", "run cargo test", "run pgtest", "rewrite test results", "add a test", "reproduce a bug", "write a regression test", or mentions testing, testdrive, sqllogictest, mzcompose, pgtest, cargo test, nextest, flaky tests, or test failures in the Materialize repository. Use this skill even if the user just says "test this" or "how do I verify this works" without naming a specific framework.
materialize
by MaterializeInc
Anvil
by simota
Terminal UIæ§ç¯ãCLIéçºæ¯æ´ãéçºãã¼ã«çµ±åï¼Linter/ãã¹ãã©ã³ãã¼/ãã«ããã¼ã«ï¼ãã³ãã³ãã©ã¤ã³ä½é¨ã®è¨è¨ã»å®è£ ãå¿ è¦ãªæã«ä½¿ç¨ãè¨èªéä¾åã§Node.js/Python/Go/Rustããµãã¼ãã
seq-wrangler
by ClawBio
Sequence QC, alignment, and BAM processing. Wraps FastQC, BWA/Bowtie2, SAMtools for automated read-to-BAM pipelines.
claw-semantic-sim
by ClawBio
Semantic Similarity Index for disease research literature using PubMedBERT embeddings
olore-t3-env-latest
by olorehq
Local t3-env documentation reference (latest). T3 Env documentation. Use for type-safe environment variable validation with Zod/Valibot, Next.js and Nuxt integration, and runtime env configuration.
olore-ms-agent-framework-latest
by olorehq
Local Microsoft Agent Framework documentation reference. Use when asked about Microsoft Agent Framework, building AI agents in .NET or Python, MCP servers/clients, durable agents, agent tools, Teams/WebChat adapters, or agent-to-agent communication.
olore-opencode-latest
by olorehq
Local OpenCode documentation reference (latest). Use when asked about OpenCode AI coding agent, agents, skills, tools, configuration, CLI, TUI, IDE integration, or MCP servers.
olore-vitest-latest
by olorehq
Local vitest documentation reference (latest). Vitest testing framework documentation. Use for unit testing, mocking, coverage, snapshots, and Vite-native test configuration.
olore-partykit-latest
by olorehq
Local PartyKit documentation reference (latest). PartyKit documentation. Use for real-time collaborative apps, WebSocket servers, multiplayer features, Y.js integration, and edge-deployed stateful backends.
ln-302-task-replanner
by levnikolaevich
Updates ALL task types (implementation/refactoring/test). Compares IDEAL plan vs existing tasks, categorizes KEEP/UPDATE/OBSOLETE/CREATE, applies changes in Linear and kanban.
ln-140-test-docs-creator
by levnikolaevich
Creates test documentation (testing-strategy.md + tests/README.md). Establishes testing philosophy and Story-Level Test Task Pattern. L2 Worker in ln-100-documents-pipeline workflow.
ln-404-test-executor
by levnikolaevich
Executes Story Finalizer test tasks (label "tests") from Todo -> To Review. Enforces risk-based limits and priority.
ln-500-story-quality-gate
by levnikolaevich
"Story-level quality orchestrator with 4-level Gate (PASS/CONCERNS/FAIL/WAIVED) and Quality Score. Delegates to ln-510 (quality) and ln-520 (tests), calculates final verdict."
add-provider
by tddworks
Guide for adding new AI providers to ClaudeBar using TDD patterns. Use this skill when: (1) Adding a new AI assistant provider (like Antigravity, Cursor, etc.) (2) Creating a usage probe for a CLI tool or local API (3) Following TDD to implement provider integration (4) User asks "how do I add a new provider" or "create a provider for X"
fix-bug
by tddworks
Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design. Use this skill when: (1) User reports a bug or unexpected behavior (2) Fixing a defect in existing functionality (3) User asks "fix this bug" or "this doesn't work correctly" (4) Correcting behavior that violates the user's mental model
implement-feature
by tddworks
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers