e2e-test-design
Design E2E tests following user-story-driven patterns with verification checkpoints. Use when creating end-to-end tests, validating complete user journeys, or designing Playwright/Cypress test patterns.
What this skill does
# E2E Test Design Skill Design end-to-end tests that validate complete user journeys. ## When to Use - Creating E2E tests for new features - Designing regression tests for critical paths - Building automated user flow validation - Documenting expected user behavior ## E2E Test Specification Template ```markdown # E2E Test: [Test Name] ## User Story As a [user type] I want to [action] So that [benefit] ## Test Steps 1. Navigate to [URL] 2. Take screenshot of initial state 3. **Verify** [element/condition] is present 4. [Action] - Click/Enter/Select 5. Take screenshot of [state] 6. **Verify** [expected result] 7. [Continue steps...] ## Success Criteria - [ ] [Criterion 1] - [ ] [Criterion 2] - [ ] [Criterion 3] ``` ## Design Workflow ### Step 1: Define User Story Start with the user's perspective: ```markdown ## User Story As a registered user I want to reset my password So that I can regain access to my account ``` ### Step 2: Map the User Journey Identify each step the user takes: 1. User navigates to login page 2. User clicks "Forgot Password" 3. User enters email 4. User submits form 5. User receives confirmation message 6. User checks email (out of scope for E2E) ### Step 3: Add Verification Points Mark critical checkpoints with **Verify**: ```markdown ## Test Steps 1. Navigate to /login 2. Take screenshot of login page 3. **Verify** "Forgot Password" link is visible 4. Click "Forgot Password" link 5. **Verify** password reset form appears 6. Enter email: "[email protected]" 7. Take screenshot of filled form 8. Click "Send Reset Link" button 9. **Verify** success message appears 10. Take screenshot of confirmation ``` ### Step 4: Define Success Criteria Clear pass/fail conditions: ```markdown ## Success Criteria - [ ] Forgot password link is accessible - [ ] Form accepts valid email - [ ] Success message displayed after submission - [ ] No error states encountered - [ ] 3 screenshots captured ``` ### Step 5: Add Structured Output Define the expected result format: ```json { "test_name": "Password Reset Flow", "status": "passed|failed", "screenshots": [ "screenshots/01_login_page.png", "screenshots/02_filled_form.png", "screenshots/03_confirmation.png" ], "error": null } ``` ## Common E2E Test Patterns ### Authentication Flow ```markdown # E2E Test: User Login ## User Story As a user, I want to log in so I can access my account. ## Test Steps 1. Navigate to /login 2. **Verify** login form is visible 3. Enter username 4. Enter password 5. Click "Login" button 6. **Verify** redirected to /dashboard 7. **Verify** user name displayed in header ``` ### Form Submission ```markdown # E2E Test: Contact Form ## User Story As a visitor, I want to submit a contact form. ## Test Steps 1. Navigate to /contact 2. **Verify** form has all required fields 3. Fill name, email, message 4. Click "Submit" 5. **Verify** success message appears 6. **Verify** form is reset ``` ### Error Handling ```markdown # E2E Test: Invalid Login ## User Story As a user, I want to see clear errors for invalid credentials. ## Test Steps 1. Navigate to /login 2. Enter invalid credentials 3. Click "Login" 4. **Verify** error message appears 5. **Verify** still on login page 6. **Verify** password field is cleared ``` ### Security Boundary ```markdown # E2E Test: SQL Injection Protection ## User Story As a user, I should be protected from injection attacks. ## Test Steps 1. Navigate to search page 2. Enter: "'; DROP TABLE users; --" 3. Click search 4. **Verify** error or sanitized response 5. **Verify** no database damage ``` ## Screenshot Best Practices 1. **Capture at key states**: Initial, after action, final 2. **Name descriptively**: `01_initial_state.png`, `02_after_click.png` 3. **Organize by test**: `screenshots/test-name/` 4. **Keep for debugging**: Screenshots help diagnose failures ## E2E Test Output Format For automation and resolution: ```json { "test_name": "User Login", "status": "passed", "screenshots": [ "screenshots/user-login/01_login_page.png", "screenshots/user-login/02_dashboard.png" ], "error": null, "duration_ms": 3450 } ``` For failures: ```json { "test_name": "User Login", "status": "failed", "screenshots": [ "screenshots/user-login/01_login_page.png" ], "error": "Step 6 failed: Expected redirect to /dashboard, got /error", "failed_step": 6, "duration_ms": 2100 } ``` ## Memory References - @e2e-test-patterns.md - Full E2E pattern documentation - @closed-loop-anatomy.md - Using E2E in feedback loops - @validation-commands.md - Integrating E2E into validation stack ## Version History - **v1.0.0** (2025-12-26): Initial release --- ## Last Updated **Date:** 2025-12-26 **Model:** claude-opus-4-5-20251101
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.