Testing
Unit tests, integration tests, test automation
automating-browser
by sumik5
Browser Agent CLIによるブラウザ操作自動化（セマンティックロケーター、状態永続化、ネットワーク傍受）。 Use when automating browser interactions via agent-browser CLI (NOT for E2E testing). E2Eテストは testing-e2e-with-playwright スキルを参照。
execute-plan
by shuymn
"Executes one user-selected task from an approved plan bundle using TDD, or rechecks DoD independently (mode=implement dod-recheck). Use when the user specifies a task ID to implement, e.g. \"execute Task 3\" or \"implement task 5\", after decompose-plan review PASS. Also use with dod-recheck mode when the user says \"recheck task DoD\", \"verify task completion\", or \"dod-recheck\"."
adversarial-verify
by shuymn
"Adversarial verification of a completed task — tries to break the implementation through edge cases, error paths, security probes, and concurrency attacks. Required for Critical/Sensitive tiers (conditionally for Standard with impl files). Use after execute-plan dod-recheck PASS."
building-nextjs-saas
by sumik5
Builds full-stack AI SaaS applications with Next.js App Router. Use when implementing SaaS features like authentication, payment integration, credit-based billing, or AI API integration. For Next.js fundamentals, use developing-nextjs; for enterprise multi-tenancy, use building-multi-tenant-saas instead.
implementing-design
by sumik5
General design implementation principles for translating any visual design into production-ready code. Covers design system integration, visual parity validation, responsive implementation, accessibility, and component organization. Use when implementing designs from any source (screenshots, mockups, specs). For Figma-specific workflows with Figma MCP, use implementing-figma instead. For design system architecture, pattern language theory, and organizational adoption strategy, use building-design-systems instead.
designing-training
by sumik5
Training program design and facilitation methodology covering needs analysis (participant analysis, stakeholder mapping), KSA framework, instructional design theory (ADDIE, TOTE, Gagné, mastery learning), objective setting, activity catalog, training operations (instructor, space, logistics), brain science principles (7±2 rule, long-term memory, habit formation), learner-centered facilitation (90/20/8 rule, EAT), online/hybrid delivery, skill map creation, and training material development. Use when designing training programs, facilitating workshops, creating training materials, building skill maps, or managing training operations. For behavior design→applying-behavior-design. For presentation content→improving-presentations. For design thinking process methodology (empathize/define/ideate/prototype/test)→practicing-design-thinking.
developing-mcp
by sumik5
Comprehensive MCP (Model Context Protocol) development guide covering architecture (Host/Client/Server roles, Tools/Resources/Prompts, Control Segregation), server and client implementation with TypeScript SDK, protocol specification (JSON-RPC 2.0, stdio/Streamable HTTP), and security threats (Tool Poisoning, Shadowing, Rug Pull, Prompt Injection). MUST load when building MCP servers or clients. For Claude Code plugin MCP configuration, use plugin-dev:mcp-integration instead. For MCP integration with Vercel AI SDK in web apps, see integrating-ai-web-apps.
crisis-manager
by famaoai-creator
Provides rapid response during production incidents or critical security breaches. Coordinates diagnostics, temporary fixes, and post-mortem data collection.
evo-writing-plans
by rockcookies
Use when you have a spec or requirements for a multi-step task, before touching code
systematic-debugging
by buildrtech
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
troubleshoot
by laststance
Diagnose and fix issues in code, builds, deployments, and system behavior. Always traces root cause, forms hypotheses before fixing, and validates after. Operates with introspection markers and hypothesis-driven debugging. Use when: - User reports a bug, error, or unexpected behavior - Build or compilation is failing - Tests are failing or flaky - Performance has degraded - Deployment or environment issues - User says "fix", "debug", "broken", "failing", "not working", "error" Keywords: troubleshoot, debug, fix, error, bug, failing, broken, crash, exception, not working
implementing-as-tachikoma
by sumik5
Operates as Tachikoma Agent (Implementation Worker) performing actual code implementation. Use when receiving task assignments from Claude Code for implementation work, test creation, or documentation. Adapts to frontend, backend, or testing roles based on task assignment.
backlog-connector
by famaoai-creator
Specialized connector for Nulab Backlog API. Automatically resolves Project IDs and handles pagination for fetching issues and wikis.
spec-interview
by huminglong
深度访谈以完善技术规格或用户指定的文档说明书。当存在 plan.md 或者用户指定文档需要通过系统性提问来完善需求时使用，涵盖技术实现、UI/UX设计、边缘情况、风险考量、权衡取舍和架构决策。触发词包括"帮我完善这个plan"、"问我关于项目的问题"，或当草稿规格需要全面细化时。
subagent-driven-development
by Kodria
Use when executing implementation plans with independent tasks in the current session
openspec
by samChang72
OpenSpec - Fission AI 的輕量級 Spec-Driven Development 框架，支援 20+ AI 工具，適合快速迭代。
relationship-events
by Semprini
Use this skill when connecting entities with relationships, when modelling what happens when something changes (business events), when cardinality or ownership questions arise, when the user asks "what happens when X" or "who initiates Y", or when deciding whether something is a relationship attribute vs. an entity attribute. Also use when the user asks about event payloads, downstream impacts, or temporal sequencing of business state changes.
developing-api-spec-first
by sumik5
API Spec First development methodology covering spec writing, E2E test framework architecture, technical debt repayment, and defensive programming for APIs. Use when adopting spec-first API development, building E2E test frameworks for backend services, documenting undocumented APIs, or writing comprehensive API specifications. For HTTP REST API design patterns, use designing-web-apis instead. For testing strategy and test pyramid, use testing-web-apis instead.
git-bisect
by manastalukdar
Automated git bisect for bug hunting with test script execution
ab-test-setup
by samChang72
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
prd-generator
by oyi77
Generate detailed Product Requirement Documents (PRDs) from feature descriptions. Create structured specifications ready for implementation.
literate-programming
by dbosk
"CRITICAL: ALWAYS activate this skill BEFORE making ANY changes to .nw files. Use proactively when: (1) creating, editing, reviewing, or improving any .nw file, (2) planning to add/modify functionality in files with .nw extension, (3) user asks about literate quality, (4) user mentions noweb, literate programming, tangling, or weaving, (5) working in directories containing .nw files, (6) creating new modules/files that will be .nw format. Trigger phrases: 'create module', 'add feature', 'update', 'modify', 'fix' + any .nw file. Never edit .nw files directly without first activating this skill to ensure literate programming principles are applied. (project, gitignored)"
developing-react
by sumik5
React 19.x development guide covering internals (rendering, reconciliation, Fiber), performance optimization (47+ react-doctor rules, memoization, bundle size), UI animation patterns (CSS transitions, easing, hover/touch), and React Testing Library (RTL queries, interactions, TDD patterns). Use when package.json contains 'react' (without 'next'), or when working on React-specific concerns in any framework. For Next.js-specific features (App Router, Server Components, Cache Components), use developing-nextjs instead. For E2E testing with Playwright, use testing-e2e-with-playwright. For general testing methodology, use testing-code.
apex-development
by david-sfdev
Expert guidance for Apex development on Salesforce Platform following NimbleUser style guide standards. Use this skill when working with Apex classes, triggers, test classes, or when the user mentions Salesforce Apex, .cls files, .trigger files, or Apex-specific concepts like SOQL, DML, governor limits, or test coverage.