session-review
Use when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness using Fullstory session recordings.
What this skill does
# Session Review Review Fullstory sessions to understand what happened — whether diagnosing a customer-reported bug or validating UI changes during development. ## When to Use - User reports a bug and provides a session URL - Investigating an error or unexpected behavior - Understanding user flow through the application - Debugging issues that are hard to reproduce - Validating UI changes locally after testing ## MCP Tools The tools follow this pattern: ``` fullstory:session_open → (fullstory:session_view | fullstory:session_diff)* → fullstory:session_close ``` 1. **`fullstory:session_open`**: Pass `session_url`. Returns event summaries and a `client_id`. 2. **`fullstory:session_view`**: Screenshot + component tree at a timestamp. Sequential calls with increasing timestamps are faster. 3. **`fullstory:session_diff`**: Highlights changes between two timestamps within a page. 4. **`fullstory:session_close`**: Always call when done to free resources. ## Workflow ### 1. Open the Session ``` fullstory:session_open(session_url="https://app.fullstory.com/ui/<org-id>/session/<device-id>:<session-id>") ``` Returns: event summaries (navigation, clicks, errors, custom events) and `client_id`. ### 2. Identify Key Moments Scan event summaries for: - **Page navigations** — entry points into different views - **Click events** — user interactions with buttons, links, forms - **Error events** — console errors, network failures, renderer errors - **Rage clicks / mouse thrash** — signs of UX friction - **Custom events** — application-specific telemetry ### 3. Visual Inspection At each key moment: ``` fullstory:session_view(client_id="<id>", page_id="<page>", timestamp=<ms>) ``` Check for: - Layout correctness (elements positioned properly) - Content rendering (text, images, icons present) - Responsive behavior (no overflow, proper sizing) - Empty/loading states handled ### 4. Compare States For before/after analysis: ``` fullstory:session_diff(client_id="<id>", page_id="<page>", from_ts=<before_ms>, to_ts=<after_ms>) ``` Returns screenshot with changed regions highlighted plus a text summary of component changes. ### 5. Report Findings Summarize what was observed: - What the user saw at each key moment - Any errors, visual regressions, or unexpected behavior - Root cause analysis if diagnosing a bug - Confirmation of correctness if validating changes ### 6. Cleanup Always close the session: ``` fullstory:session_close(client_id="<id>") ``` ## Example When a user reports "the checkout button didn't work" and provides a session URL: 1. Call `fullstory:session_open` with the session URL 2. Find the checkout-related events in the summaries (note the `page_id` and timestamps) 3. Use `fullstory:session_view` to see the UI state just before the button click 4. Use `fullstory:session_diff` to compare before/after the click attempt to see what changed (or didn't) 5. Report findings: what the user saw, any errors, why the action may have failed 6. Call `fullstory:session_close` to clean up ## Common Mistakes | Mistake | Fix | |---------|-----| | Forgetting to close session | Always call `fullstory:session_close` — even on errors | | Random timestamp access | Use sequential increasing timestamps for faster access | | Skipping diff tool | `fullstory:session_diff` highlights changes automatically — much faster than comparing two `fullstory:session_view` screenshots manually | | Not checking for error events | Scan event summaries for errors before visual inspection |
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.