- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
obsidian-bases-manager
by richfrem
"Read and manipulate Obsidian Bases (.base) files - YAML-based database views that render as tables, cards, and grids inside the vault. Use when reading, appending rows, or updating cells in a Base file."
ileap
by way-platform
iLEAP technical specs for exchanging logistics emissions data (ISO 14083 / GLEC Framework) via the PACT protocol. Use when implementing iLEAP APIs, data models (ShipmentFootprint, TCE, TOC, HOC, TAD), PACT DataModelExtensions, or conformance testing. Language-agnostic.
cap
by arisng
Comprehensive guidance for implementing distributed transactions and event bus patterns using DotNetCore.CAP library. Use when working with CAP for microservices event-driven architecture, message publishing/subscribing, outbox pattern implementation, and integration with message queues like RabbitMQ, Kafka, Azure Service Bus, and databases like SQL Server, PostgreSQL, MongoDB.
repository-analyzer
by Toowiredd
Analyzes codebases to generate comprehensive documentation including structure, languages, frameworks, dependencies, design patterns, and technical debt. Use when user says "analyze repository", "understand codebase", "document project", or when exploring unfamiliar code.
test-automation
by Logos-Liber
Test automation strategies and best practices
asset-optimization
by Logos-Liber
Polygon reduction, LOD creation, texture compression, and real-time optimization
Debugging and Troubleshooting
by ShunsukeHayashi
Systematic error diagnosis and debugging workflow for Rust code. Use when code isn't working, tests fail, or runtime errors occur.
TDD Workflow
by ShunsukeHayashi
Test-Driven Development workflow for Miyabi. Red-Green-Refactor cycle with Rust-specific patterns. Use when implementing new features, fixing bugs, or writing tests.
Debugging and Troubleshooting
by ShunsukeHayashi
Systematic error diagnosis and debugging workflow for Rust code. Use when code isn't working, tests fail, or runtime errors occur.
TDD Workflow
by ShunsukeHayashi
Test-Driven Development workflow for Miyabi. Red-Green-Refactor cycle with Rust-specific patterns. Use when implementing new features, fixing bugs, or writing tests.
acceptance-criteria-verification
by troykelly
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
openspec-apply
by chyiiiiiiiiiiii
Implement a change proposal following the OpenSpec SDD workflow. Use after a proposal is approved and ready for implementation.
local-service-testing
by troykelly
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks
clean-commits
by troykelly
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
test-driven-development
by aiaiohhh
Use when implementing any feature or bugfix, before writing implementation code
oauth-providers
by vanman2024
Configure OAuth authentication providers for Clerk (Google, GitHub, Discord, Apple, Microsoft, Facebook, LinkedIn, Twitter, and 11+ more). Use when setting up social login, configuring OAuth providers, implementing authentication flows, generating redirect URLs, testing OAuth connections, or when user mentions Clerk OAuth, social authentication, provider setup, or multi-provider auth.
writing-plans
by aiaiohhh
Use when you have a spec or requirements for a multi-step task, before touching code
billing-integration
by vanman2024
Clerk Billing and Stripe subscription management setup. Use when implementing subscriptions, configuring pricing plans, setting up billing, adding payment flows, managing entitlements, or when user mentions Clerk Billing, Stripe integration, subscription management, pricing tables, payment processing, or monetization.
a2a-mcp-integration
by vanman2024
Integration patterns for combining Agent-to-Agent (A2A) Protocol with Model Context Protocol (MCP) for hybrid agent communication. Use when building systems that need both agent-to-agent communication and agent-to-tool integration, implementing composite architectures, or when user mentions A2A+MCP integration, hybrid protocols, or multi-agent tool access.
superpowers
by founderjourney
Structured software development framework for coding agents. Composable skills enforcing planning, testing, and systematic execution. Prevents code-first chaos.
Tightener Ecosystem Agent Skills
by zwettemaan
Note: This skill structure is designed to be consumed by AI agents and human developers alike. Each referenced document contains detailed technical information specific to its domain.
storyblok-best-practices
by bartundmett
Comprehensive Storyblok CMS development best practices for agency developers. Covers content modeling, SDK integration (React, Vue, Nuxt, Next.js), Visual Editor configuration, field plugins, API usage, internationalization, webhooks, and deployment patterns. Triggers on tasks involving Storyblok components, Visual Editor setup, content fetching, field plugin development, or headless CMS integration.
App Platform Deployment Skill
by vanman2024
```
session-management
by vanman2024
Clerk session handling, JWT verification, token management, and multi-session workflows. Use when implementing session validation, JWT claims customization, token refresh patterns, session lifecycle management, or when user mentions session errors, authentication tokens, JWT verification, multi-device sessions, or session security.