Testing
Unit tests, integration tests, test automation
accessibility-testing
by aj-geddes
Test web applications for WCAG compliance and ensure usability for users with disabilities. Use for accessibility test, a11y, axe, ARIA, keyboard navigation, screen reader compatibility, and WCAG validation.
app-store-deployment
by aj-geddes
Deploy iOS and Android apps to App Store and Google Play. Covers signing, versioning, build configuration, submission process, and release management.
go-testing
by cxuu
Go testing patterns from Google and Uber style guides including test naming, table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions. Use when writing or reviewing Go test code, creating test helpers, or setting up table-driven tests.
ag-dir
by kevinslin
Define and maintain an Agent Project Directory (AGD) with clear durable
dev.loop
by kevinslin
Drive a development task end-to-end from a user-stated goal through planning, context gathering, execution, verification. Use when the user asks to run a devloop, drive a task to completion, or wants a plan-gather-execute-verify workflow with phased commits and CI verification. Also use if user asks to invoke any individual phase of the devloop
sudocode
by kevinslin
Write consistent sudocode from real code. Use whenever sudocode needs to be written, including flow docs, specs, architecture docs, or code-to-sudocode transformations.
dev.code
by kevinslin
This skill should be used when performing any coding task including implementing features, fixing bugs, refactoring code, or making any modifications to source code. Provides best practices, security considerations, testing guidelines, and a structured workflow for development tasks.
rails-ai:testing
by zerobearing2
Use when testing Rails applications - TDD, Minitest, fixtures, model testing, mocking, test helpers
rails-ai:mailers
by zerobearing2
Use when sending emails - ActionMailer with async delivery via SolidQueue, templates, previews, and testing
rails-ai:project-setup
by zerobearing2
Setting up and configuring Rails 8+ projects - Gemfile dependencies, environment config, credentials, initializers, Docker, RuboCop, project validation
using-rails-ai
by zerobearing2
Rails-AI introduction - explains how rails-ai (Rails domain layer) integrates with superpowers (universal workflows) for Rails development
rails-ai:debugging-rails
by zerobearing2
Use when debugging Rails issues - provides Rails-specific debugging tools (logs, console, byebug, SQL logging) integrated with systematic debugging process
rails-ai:jobs
by zerobearing2
Use when setting up background jobs, caching, or WebSockets - SolidQueue, SolidCache, SolidCable (TEAM RULE #1 - NEVER Sidekiq/Redis)
typescript-backend-project-setup
by NTCoding
"Sets up NX monorepo for TypeScript backend projects optimized for AI-assisted development. Delegates to NX commands where possible, patches configs as last resort. Triggers on: 'set up typescript backend project', 'create backend project', 'initialize typescript backend', 'create monorepo', or when working in an empty project folder."
challenge-that
by NTCoding
"Force critical evaluation of proposals, requirements, or decisions by analyzing from multiple adversarial perspectives. Triggers on: accepting a proposal without pushback, 'sounds good', 'let's go with', design decisions with unstated tradeoffs, unchallenged assumptions, premature consensus. Invoke with /challenge-that."
concise-output
by NTCoding
"Enforces brevity and signal-over-noise in all outputs. Eliminates verbose explanations, filler phrases, and unnecessary elaboration. Triggers on: every response (governs output length and density when loaded)."
agile-sprint-planning
by aj-geddes
Plan and execute effective sprints using Agile methodologies. Define sprint goals, estimate user stories, manage sprint backlog, and facilitate daily standups to maximize team productivity and deliver value incrementally.
Obsidian CLI 探索记录
by openclaw
é»è®¤ Vaultï¼å»ºè®®å 设置é»è®¤ vaultï¼é¿å æ¯æ¬¡é½è¦æå® -v åæ°
playwright-debugging
by ed3dai
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
systematic-debugging
by ed3dai
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
finishing-a-development-branch
by ed3dai
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
testing-skills-with-subagents
by ed3dai
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
playwright-patterns
by ed3dai
Use when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakiness
test-driven-development
by ed3dai
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first