/snapshot-test
Generate snapshot tests for UI components or serializable outputs.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/snapshot-test
Context preview
What this command does when you run it.
Generate snapshot tests for UI components or serializable outputs.
Command definition
snapshot-test.mdGenerate snapshot tests for UI components or serializable outputs.
Steps
1. Identify the target component or function from the argument. 2. Detect the testing framework and snapshot support (Jest snapshots, Vitest, pytest-snapshot). 3. Analyze the component props or function parameters to determine meaningful test cases. 4. For each component or function:
- Create a snapshot test with default props/arguments.
- Create snapshot tests for each significant visual state (loading, error, empty, populated).
- Create snapshot tests for responsive variants if applicable.
5. For React/Vue components, use the appropriate renderer:
- `@testing-library/react` with `render` for DOM snapshots.
- `react-test-renderer` for tree snapshots if needed.
6. Run the tests to generate initial snapshots. 7. List all generated snapshot files and their locations.
Format
Generated: <N> snapshot tests in <file>
Snapshots:
- <ComponentName> default rendering
- <ComponentName> loading state
- <ComponentName> error state
- <ComponentName> with data
Snapshot file: <path to .snap file>
Rules
- Snapshot tests should capture meaningful visual states, not implementation details.
- Avoid snapshotting entire page trees; focus on individual components.
- Use inline snapshots (`toMatchInlineSnapshot`) for small outputs under 20 lines.
- Add a comment explaining what each snapshot verifies.
- Do not snapshot timestamps, random IDs, or other non-deterministic values; use serializers to strip them.
Read more
Generate snapshot tests for UI components or serializable outputs.
Steps
1. Identify the target component or function from the argument. 2. Detect the testing framework and snapshot support (Jest snapshots, Vitest, pytest-snapshot). 3. Analyze the component props or function parameters to determine meaningful test cases. 4. For each component or function:
- Create a snapshot test with default props/arguments.
- Create snapshot tests for each significant visual state (loading, error, empty, populated).
- Create snapshot tests for responsive variants if applicable.
5. For React/Vue components, use the appropriate renderer:
- `@testing-library/react` with `render` for DOM snapshots.
- `react-test-renderer` for tree snapshots if needed.
6. Run the tests to generate initial snapshots. 7. List all generated snapshot files and their locations.
Format
Generated: <N> snapshot tests in <file> Snapshots: - <ComponentName> default rendering - <ComponentName> loading state - <ComponentName> error state - <ComponentName> with data Snapshot file: <path to .snap file>
Rules
- Snapshot tests should capture meaningful visual states, not implementation details.
- Avoid snapshotting entire page trees; focus on individual components.
- Use inline snapshots (`toMatchInlineSnapshot`) for small outputs under 20 lines.
- Add a comment explaining what each snapshot verifies.
- Do not snapshot timestamps, random IDs, or other non-deterministic values; use serializers to strip them.
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

