Testing
Unit tests, integration tests, test automation
opencode-docs
by jasonz-ncc42
Local OpenCode documentation reference. Use when asked about OpenCode features, tools, agents, MCP servers, plugins, CLI, TUI, or IDE integration.
systematic-debugging
by hxk622
"遇到任何 bug、测试失败或意外行为时使用，在提出修复方案之前进行系统化调试。Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Follow the four phases: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation."
ai-product
by ngxtm
"Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt ..."
image-assistant
by ssdiwu
配图助手 - 把文章/模块内容转成统一风格、少字高可读的信息图提示词；先定"需要几张图+每张讲什么"，再压缩文案与隐喻，最后输出可直接复制的生图提示词并迭代。
subagent-driven-development
by hxk622
"在当前会话中执行包含独立任务的实施计划时使用。每个任务派送新的子Agent，并进行两阶段审查。Use when executing implementation plans with independent tasks - dispatch fresh subagent per task + two-stage review (spec then quality)."
anti-ai-writing
by cdeistopened
Transform AI-assisted drafts into authentic, human-sounding content. This skill provides patterns to detect and eliminate AI tells, frameworks for natural writing, and techniques for creating prose that reads as genuinely human. Use when reviewing any AI-generated content or when writing content that must not appear AI-assisted.
ignore-files-workflow
by ilude
Ignore file management for .gitignore, .dockerignore, and .specstory directories. Includes synchronization, alphabetical ordering, organization, best practices, and testing guidelines. Activate when working with .gitignore, .dockerignore, .specstory files, or managing version control and Docker build context.
ab-test-setup
by ngxtm
"Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness."
opencode-docs
by jasonz-ncc42
Local OpenCode documentation reference. Use when asked about OpenCode features, tools, agents, MCP servers, plugins, CLI, TUI, or IDE integration.
makefile-workflow
by ilude
Makefile best practices for project automation and build systems. Covers command usage, target organization (PHONY vs file targets), variable management (:=, ?=, =), platform detection, common development targets (clean, test, lint, format, run), DevContainer integration, version management with semantic versioning, Docker integration, output control, error handling, and advanced patterns. Activate when working with Makefiles, make commands, .PHONY targets, build automation, or development workflows.
specification-refiner
by ddunnock
Systematic analysis and refinement of specifications, requirements, architecture designs, and project plans. Use when the user wants to identify gaps, weaknesses, inefficiencies, or complications in a proposed plan, specification, or design document. Triggers on gap analysis, specification review, requirements analysis, architecture critique, design validation, plan assessment, weakness identification, assumption auditing, or when users share specs/plans asking for feedback. Produces actionable findings with remediations and maintains analysis state across iterations. Features sequential clarification with one question at a time, recommended answers, and immediate integration.
writing-plans
by hxk622
"当有多步骤任务的规格或需求时使用，在动代码之前。编写全面的实施计划，假设工程师对代码库零上下文。Use when you have a spec or requirements for a multi-step task, before touching code. Write comprehensive implementation plans."
maestro-e2e
by raphaelbarbosaqwerty
E2E UI testing with Maestro for iOS, Android, Flutter, React Native, and Web
ci-monitoring
by troykelly
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
kotlin-coroutines
by pluginagentmarketplace
Kotlin coroutines - structured concurrency, Flows, exception handling
btt
by sablier-labs
Write bulloak tree specifications (.tree files) for smart contract integration tests. Trigger phrases - write a tree, create test tree, BTT spec, bulloak tree, Branching Tree Technique, or when writing integration tests for contract functions.
testing-workflow
by ilude
Testing workflow patterns and quality standards. Activate when working with tests, test files, test directories, code quality tools, coverage reports, or testing tasks. Includes zero-warnings policy, targeted testing during development, mocking patterns, and best practices across languages.
bach-exploratory-testing
by copyleftdev
Test software in the style of James Bach, pioneer of exploratory testing and context-driven testing. Emphasizes skilled human investigation, heuristics-based test design, and adapting to context rather than following rigid scripts. Use when designing test strategies, performing exploratory testing, or building thinking testers.
geniml
by hxk622
This skill should be used when working with genomic interval data (BED files) for machine learning tasks. Use for training region embeddings (Region2Vec, BEDspace), single-cell ATAC-seq analysis (scEmbed), building consensus peaks (universes), or any ML-based analysis of genomic regions. Applies to BED file collections, scATAC-seq data, chromatin accessibility datasets, and region-based genomic feature learning.
react-workflow
by ilude
React framework workflow guidelines. Activate when working with React components (.jsx, .tsx), React hooks (useState, useEffect), or React-specific patterns.
speckit-require
by akiojin
GitHub Spec Kit (https://github.com/github/spec-kit) を使って要件定義や仕様作成（仕様策定・仕様書作成・仕様設計を含む）を新規作成または既存仕様へ追記し、spec.md/plan.md/tasks.mdまで生成・更新する。要件定義、要件追加/変更、TDD前提の要件整理、仕様の明文化、Spec Kitのspecify/clarify/plan/tasksフロー実行が求められるときに使用。
devops-patterns
by webdevtodayjason
DevOps patterns including CI/CD pipeline design, GitHub Actions, Infrastructure as Code, Docker, Kubernetes, deployment strategies, monitoring, and disaster recovery. Use when setting up CI/CD, deploying applications, managing infrastructure, or creating pipelines.
kotlin-multiplatform
by pluginagentmarketplace
Kotlin Multiplatform - shared code, expect/actual, iOS integration
lamport-distributed-systems
by copyleftdev
Design distributed systems using Leslie Lamport's rigorous approach. Emphasizes formal reasoning, logical time, consensus protocols, and state machine replication. Use when building systems where correctness under concurrency and partial failure is critical.