cypress
Assists with end-to-end testing of web applications using Cypress. Use when writing E2E tests, setting up component testing, configuring CI pipelines with parallelization, or building custom test commands. Trigger words: cypress, e2e testing, end-to-end, cypress run, cy.get, integration testing, browser testing.
What this skill does
# Cypress
## Overview
Cypress is an end-to-end testing framework for web applications that runs tests directly in the browser for fast, reliable feedback. It provides element selection, network interception, component testing, and CI integration with parallelization and video recording.
## Instructions
- When selecting elements, use `data-testid` or `data-cy` attributes with `cy.get("[data-testid='submit']")` instead of CSS classes or IDs for resilient selectors.
- When testing interactions, use `cy.get().type()`, `.click()`, `.select()`, and `.check()` for user actions, and chain `.should()` assertions for expected outcomes.
- When handling API calls, use `cy.intercept()` to stub external APIs with fixtures or spy on requests, and `cy.wait("@alias")` after actions that trigger calls instead of `cy.wait(ms)`.
- When writing custom commands, use `Cypress.Commands.add()` for reusable patterns like login, database seeding, and common workflows, with TypeScript declarations for IntelliSense.
- When testing components, use `cy.mount()` with framework-specific mounting libraries (`@cypress/react`, `@cypress/vue`) to test components in isolation.
- When configuring CI, use `cypress run --record --key` for Cypress Cloud integration with `--parallel` to split tests across machines, and `--browser` to specify the browser.
- When setting up the project, configure `cypress.config.ts` with `baseUrl`, viewport dimensions, timeouts, and environment variables.
## Examples
### Example 1: Write E2E tests for a checkout flow
**User request:** "Add Cypress tests for our e-commerce checkout process"
**Actions:**
1. Set up test with `cy.visit("/products")` and select a product
2. Intercept the cart API with `cy.intercept("POST", "/api/cart")` and alias it
3. Fill in shipping form using `cy.get("[data-testid='email']").type(...)`
4. Assert order confirmation with `cy.url().should("include", "/confirmation")`
**Output:** A reliable E2E test covering the full checkout flow with stubbed API responses.
### Example 2: Set up component testing for React
**User request:** "Configure Cypress component testing for our React project"
**Actions:**
1. Install `@cypress/react` and configure component testing in `cypress.config.ts`
2. Create stories for key components using `cy.mount(<Component />)`
3. Test interactions with `cy.get().click()` and assert DOM changes
4. Add to CI pipeline alongside E2E tests
**Output:** Isolated component tests running in a real browser with full Cypress API.
## Guidelines
- Use `data-testid` attributes for test selectors; never rely on CSS classes, text content, or DOM structure.
- Keep tests independent: each test should set up its own state (login, seed data).
- Use `cy.intercept()` to stub external APIs; do not let tests depend on third-party service availability.
- Add `cy.wait("@alias")` after actions that trigger API calls; do not use `cy.wait(ms)` for timing.
- Write tests from the user's perspective: "fill in the form, click submit, see confirmation."
- Use fixtures for large API response data; inline small responses in `cy.intercept()`.
- Run Cypress in CI with `--record` for test replay, screenshots, and video on failure.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.