- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
happy-dom-tests
by iulspop
Generates React component render tests using happy-dom and Testing Library with the "given/should" prose format. Use when writing tests for display components, hooks, user interactions, or accessibility checks.
ctrader-bridge
by aalfath
"Trade forex and gold on cTrader via ZMQ bridge. Autonomous trading with thesis-based position management."
pr-review
by mczkzk
Review GitHub PR <number> and identify issues and improvements
Playwright Browser Automation
by yousufjoyian
Claude agent skills and workspace configuration
Spike Codec & Loss Pack
by sovr610
This skill should be used when the user asks to "encode spikes", "decode spike trains", "add spike encoding", "implement rate coding", "implement latency coding", "implement TTFS", "add population coding", "add delta modulation", "decode spike counts", "first-spike decoding", "population decoding", "add SNN loss", "implement ProbSpikes", "spike rate regularization", "ISI regularization", "temporal consistency loss", "membrane regularization", "SNN loss pack", "loss composition", "spike-count cross-entropy", "AMP hardening for SNN", "mixed precision SNN", "spike tensor convention", "axis convention batch-first", "SpikeBatch", "deterministic inference for encoders", "round-trip encoding test", or mentions spike I/O semantics, SNN training objectives, or encoding/decoding pipelines for spiking neural networks.
spec-kit
by leobrival
Specification-Driven Development methodology from GitHub spec-kit. Use when users ask to create specifications, plan features, define requirements, write user stories, decompose tasks, establish project constitution, or follow SDD workflow.
verification-before-completion
by tomwangowa
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
skill-reviewer
by squirrel289
'Evaluate and compare AI agent skills with a structured, repeatable, objective, and data-driven process. Use when asked to review one or more skills, define scoring criteria, compare alternatives, compute platform-specific success scores, or recommend whether to select, improve, extend, compose, or build a new skill.'
writing-skills
by Cygnusfear
Use when creating new skills, editing existing skills, or verifying skills work before deployment
rust
by jyasuu
Rust programming language and Cargo package manager commands including build, test, and cross-compilation.
dd
by zkywalker
"Document-Driven Development (文档驱动开发). Use when: (1) /dd help — explain workflow and suggest next step based on project state, (2) /dd init — initialize doc-driven structure in a project, (3) /dd spec [requirement] — create temporary spec to align intent before development, (4) /dd dev [spec-path doc-path] — implement code following spec or doc (auto enters plan mode for spec-based dev), (5) /dd sync [--check --scope] — update living docs, archive spec, and audit consistency. Triggers on mentions of: document-driven, design document, doc-driven, spec-driven, 文档驱动, 设计文档, 规格, /dd."
testing
by htooayelwinict
Write and manage tests using TDD with Pest (PHP), Vitest (React), pytest (Python), and Playwright (E2E). Use when writing feature tests, unit tests, component tests, visual regression tests, or improving test coverage. EXCLUSIVE to testing-expert agent.
test-driven-development
by aleister1102
Use when implementing any feature or bugfix, before writing implementation code
enterprise-scala
by zhongjis
Enterprise Scala guardrails preventing common AI agent mistakes in production codebases. Use whenever working in a Scala codebase — editing .scala files, modifying sbt projects, writing traits/classes/objects, reviewing pull requests, or refactoring Scala code. Triggers on: any .scala file interaction, build.sbt edits, Scala code review, Scala refactoring, or any task involving Scala source code in work repositories.
pint
by markhamsquareventures
Laravel Pint syntax reference
godot-web-e2e
by Chen19007
End-to-end testing for any Godot Web export using Chrome DevTools and a local HTTP server. Use when verifying gameplay behavior in a Web build (not editor) and you need repeatable DevTools-driven input checks and console evidence.
fix-issue
by YPYT1
集合了所有的openclaw,claudecode,open等各个平台所有的skills