Discover Data & AI skills, compare source repositories and read the instructions for each workflow.
WHAT: Constants organization with naming conventions and type-safe as const assertions. WHEN: defining test IDs, animation durations, query keys, feature flags. KEYWORDS: constants, SCREAMING_SNAKE_CASE, Pascal...
Runs unit and E2E tests for API, analyzes failures, identifies flaky tests, checks coverage, and suggests fixes
Web application testing principles. E2E, Playwright, deep audit strategies.
Run appropriate tests based on changes using node:test, Testcontainers, and Playwright
Work on a kspec task with proper lifecycle - verify, start, note, submit, PR, complete.
E2E multiplayer testing using Playwright API with multi-client browser contexts. Validates server-authoritative patterns, state synchronization, and anti-cheat measures. Use when testing multiplayer features.
Generate unit tests using Jest with mocking, AAA pattern (Arrange-Act-Assert), and 80%+ coverage target. Use when testing business logic, handlers, or services in isolation.
WHAT: Test ID patterns with data-testid attribute for web testing. WHEN: E2E with Playwright/Cypress, component tests with Testing Library, targeting specific elements. KEYWORDS: data-testid, test ID, getByTest...
Generate integration tests for CQRS handlers with mocked dependencies and co-located fixtures using Jest. Use when testing handlers, database operations, or event publishing in isolation.
WHAT: Jest and @testing-library/react patterns for web component testing. WHEN: testing components with providers, user interactions, async content, form validation. KEYWORDS: testing-library, Jest, screen, use...
E2E test creation and execution for QA. Validates implementations using Playwright API tests that become persistent artifacts for regression.
Guidelines for running and writing unit and E2E tests. Use this when asked to run tests, write tests, debug test failures, or verify code changes. Also use this before performing any merge commands or pushing c...
Review code changes for bugs, logic errors, regressions, and missing tests. Use when the user asks for a code review, review of uncommitted files, or review of specific diffs/files/PR changes. Default to uncomm...
Auto-loads during /verify or when validating compositions
Evaluate upstream changes using Navigator's design frameworks to decide what to adopt, skip, or adapt
Safely sync navigator's agent-browser fork with upstream vercel-labs/agent-browser, analyze changes, and generate integration documentation
Manipulate Xcode projects and asset catalogs using XcodeProjectCLI (xcp) only. Use when editing .xcodeproj/.pbxproj files, adding/moving/renaming/deleting groups or files, changing target membership, reading or...
WHAT: Yarn scripts for React Native monorepo development. WHEN: running dev builds, testing, linting, code generation. KEYWORDS: yarn, dev:ios, dev:android, test, lint, typecheck, generate, turbo, build, clean.
Validates bead definitions against the original spec for self-containment, coverage, and dependency correctness. Automatically fixes issues and creates missing beads. Use after decompose-plan to ensure quality...
Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.
Git operations mastery. Atomic commits, rebase/squash, history search (blame, bisect, log -S). Triggers on 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
Migrate legacy CSS and SCSS to Genesis Ontological mixins. Convert raw CSS properties to semantic ontological patterns, ensure zero-CSS compliance in subdomain files, and maintain the three-tier architecture. U...
Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.
Prepare git commit messages following conventional commits. Activates on: commit, prepare commit, commit this, commit message, ready to commit, stage and commit
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.