Menu
Capture a screenshot and snapshot of the current browser page when an error is encountered during e2e testing. Saves to docs/e2e/<slug>/screenshots/.
Research-driven brainstorming for feature design. Use when designing a new feature, exploring approaches, or making design decisions. Automatically researches competitors before asking design questions. Triggers on "brainstorm", "design a feature", "how should we build X", or any request to explore approaches for a feature.
Research-driven feature design with implementation plan. Combines brainstorming and planning into one flow. Use when designing a new feature. Triggers on "design", "brainstorm", "plan a feature", "how should we build X".
Execute implementation plans task by task with verification. Use after /plan to implement the feature. Follows each task exactly, runs verifications, commits frequently. Triggers on "execute the plan", "implement the plan", "run the plan", or after /plan approval.
End-to-end feature development orchestrator. Composes /research, /brainstorm, /plan, and /execute into a single workflow. Use when building a new feature from scratch. Triggers on "build a feature", "implement X from scratch", "full feature development for Y".
Create detailed implementation plans from design specs. Use after brainstorming to create step-by-step implementation plans. Each task is 2-5 minutes of work with exact code and commands. Triggers on "plan the implementation", "create a plan for", "write the implementation plan", or after /brainstorm approval.
Survey best practices from competitor ERPs and point solutions for a given feature. Use when designing new features, evaluating approaches, or understanding industry patterns. Triggers on "research best practices", "how do competitors do X", "survey the market for Y", "what's the industry standard for", or any request to understand how other systems handle a feature.
| name | error |
| description | Capture a screenshot and snapshot of the current browser page when an error is encountered during e2e testing. Saves to docs/e2e/<slug>/screenshots/. |
Capture diagnostic artifacts when the browser shows an error during e2e testing. This skill is a building block — other skills (e.g. /smoke-test) invoke it when they detect a failure.
Call this whenever an agent-browser snapshot reveals:
Read .env.local in the project root and extract the CARBON_WORKTREE value.
mkdir -p docs/e2e/${CARBON_WORKTREE}/screenshots
Use a descriptive filename with the module/route name and a timestamp:
agent-browser screenshot docs/e2e/${CARBON_WORKTREE}/screenshots/${module}-$(date +%Y%m%d-%H%M%S).png
For example: docs/e2e/my-worktree/screenshots/accounting-20260606-143022.png
Save the element snapshot alongside the screenshot for debugging without a browser:
agent-browser snapshot -i > docs/e2e/${CARBON_WORKTREE}/screenshots/${module}-$(date +%Y%m%d-%H%M%S).txt
After capturing, log the file paths and continue — do not stop the calling skill. The caller decides whether to abort or continue.
Two files saved to docs/e2e/<slug>/screenshots/:
{module}-{timestamp}.png — visual screenshot{module}-{timestamp}.txt — element snapshot textThese paths are gitignored (docs/e2e in .gitignore).