Loading...
Loading...
Found 437 Skills
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
Apply billing and security best practices for payment/auth integrations. Invoke when: setting up Stripe/Clerk/auth, debugging payment issues, configuring webhooks, before prod deployment, after billing incidents.
Format Slack messages using Block Kit for rich, interactive layouts. Apply when sending any Slack message that should look polished.
Use when crafting or refreshing pages to align copy, UX, and conversion goals with target keywords.
Verify release readiness and guide the release process. Part of the Plot workflow. Use on /plot-release.
Test and debug Mom Factura Payment API integrations using QA environment and payment simulation. Use when setting up test environments, simulating payment outcomes (success, failure, timeout), debugging API errors, or validating integration before production.
Initialize repo-scoped code review policy files under .opencode/review. Use when setting up project-specific review rules for /code-review.
Propose a new spec-driven change. Scaffolds proposal.md, design.md, tasks.md, and questions.md for a named change, populated with project context.
Use when user mentions fantasy, magic system, or world-building for fantastical settings - provides fantasy genre conventions, magic system design patterns, and world-building frameworks
Manual QA testing — verify features end-to-end as a user would, using every tool available (browser, macOS, bash, APIs). Focuses on what formal test suites cannot capture: visual correctness, UX flows, usability judgment, integration reality, edge cases, and failure modes. Standalone or composable with /ship. Triggers: qa, qa test, manual test, test the feature, verify it works, exploratory testing, smoke test, end-to-end verification.
Review Go code for language and runtime conventions: concurrency, context usage, error handling, resource management, API stability, type semantics, and testability. Language-only atomic skill; output is a findings list.
Use this skill to review pull requests against coding standards and best practices. Invoke when reviewing code changes before merge.