- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
plan
by whawkinsiv
"Use this skill when the user needs to turn an idea into a buildable spec, write a project scope, create feature requirements, or define an MVP. Covers quick feature specs (10-15 min) for immediate AI builds and full project scopes (1-2 hours) for planning and contractor estimates."
finances
by whawkinsiv
"Use this skill when the user needs to build a financial model, calculate unit economics, understand MRR/ARR/churn, or figure out their quit number. Covers SaaS metrics, CAC/LTV, burn rate, cash flow modeling, and making unit economics legible for non-finance founders."
angular-testing
by analogjs
Write unit and integration tests for Angular v21+ applications using Vitest or Jasmine with TestBed, component harnesses, and modern testing patterns. Use for testing components with signals, OnPush change detection, services with inject(), and HTTP interactions. Triggers on test creation, testing signal-based components, mocking dependencies, or setting up test infrastructure.
conversion
by whawkinsiv
"Use this skill when the user needs to improve conversion rates, reduce funnel drop-off, optimize signup flows, or increase trial-to-paid conversion. Covers funnel analysis, friction reduction, behavioral psychology, social proof, and A/B testing strategies."
payments
by whawkinsiv
"Use this skill when the user needs to set up Stripe, implement subscriptions, handle billing, configure payment plans, manage failed payments, deal with refunds, set up tax collection, or troubleshoot payment issues. Covers Stripe configuration, subscription lifecycle, dunning, tax compliance, and billing operations for bootstrapped SaaS."
integrations
by whawkinsiv
"Use this skill when the user needs to connect third-party services, set up APIs, add OAuth, configure webhooks, or integrate tools like Slack, Zapier, email providers, or payment processors. Covers API integration patterns, auth flows, webhook handling, and building integrations that non-technical founders can maintain."
build
by whawkinsiv
"Use this skill when the user needs to build features with AI coding tools, choose between Claude Code, Lovable, Replit, or Cursor, write effective prompts for code generation, or iterate on AI-generated code. Covers tool selection, prompting strategies, and development workflows for non-technical founders."
test
by whawkinsiv
"Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders."
validate
by whawkinsiv
"Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders."
esphome-devices
by tonylofgren
Use when user EXPLICITLY requests "ESPHome", "ESP32", "ESP8266", or device firmware. NOT for: Home automations (use home-assistant or node-red skill).
Oracle ADK Expert
by frankxai
Build production agentic applications on OCI using Oracle Agent Development Kit with multi-agent orchestration, function tools, and enterprise patterns
Oracle Agent Spec Expert
by frankxai
Design framework-agnostic AI agents using Oracle's Open Agent Specification for portable, interoperable agentic systems with JSON/YAML definitions
discover
by AsiaOstrich
"[UDS] Assess project health, architecture, and risks before adding features"
economic-order-quantity
by kishorkukreja
When the user wants to calculate optimal order quantities, minimize total inventory costs using EOQ models, or determine the economic lot size. Also use when the user mentions "EOQ," "Wilson formula," "economic lot size," "order quantity optimization," "production batch size," "quantity discounts," "EPQ" (Economic Production Quantity), "backorder models," or "reorder point calculations." For multi-echelon systems, see multi-echelon-inventory. For stochastic models, see stochastic-inventory-models.
energy-storage-optimization
by kishorkukreja
When the user wants to optimize battery storage systems, manage energy storage operations, or plan storage deployment. Also use when the user mentions "battery optimization," "BESS," "energy storage management," "battery dispatch," "storage arbitrage," "grid-scale storage," "battery sizing," or "storage scheduling." For renewable integration, see renewable-energy-planning. For grid operations, see power-grid-optimization.
kargo-skill
by julianobarbosa
Comprehensive Kargo GitOps continuous promotion platform skill. Use when implementing progressive delivery pipelines, promotion workflows, freight management, ArgoCD integration, warehouse configuration, stage pipelines, verification templates, or any Kargo-related tasks. Covers installation, core concepts, patterns, security, and complete YAML examples.
speckit-checklist
by dceoy
Generate a custom checklist for the current feature based on user requirements.
coverage
by AsiaOstrich
"[UDS] Analyze test coverage and provide recommendations"
Testing Guide
by AsiaOstrich
Testing pyramid and test writing standards for UT/IT/ST/E2E. Supports ISTQB and Industry Pyramid frameworks. Use when: writing tests, discussing test coverage, test strategy, or test naming. Keywords: test, unit, integration, e2e, coverage, mock, ISTQB, SIT, 測試, 單元, 整合, 端對端.
migrate-to-rstest
by rstackjs
Migrate Jest or Vitest test suites and configs to Rstest. Use when asked to move from Jest/Vitest to Rstest, replace framework APIs with @rstest/core, translate test config to rstest.config.ts, or update test scripts and setup files for Rstest equivalents.
Bun Jest Migration
by secondsky
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.
feature-dev
by sd0xdev
"Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate."
post-dev-test
by sd0xdev
"Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report."
feasibility-study
by sd0xdev
"Feasibility analysis from first principles. Use when: evaluating solutions before tech-spec, comparing approaches, risk assessment. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: quantitative comparison + recommendation."