This skill should be used when the user asks for "browser tests", "playwright tests", "end-to-end testing", "test user flows", "E2E coverage", "integration tests for UI", "page object pattern", "/e2e command", or discusses automated browser testing. Covers the E2E test loop workflow, Playwright patterns, page objects, and selector strategies.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Current branch: !git branch --show-current 2>/dev/null || echo "not in git repo"
The E2E test loop uses a 2-phase workflow with Dex task tracking for persistent, cross-session browser test development.
| Phase | Name | Purpose |
|---|---|---|
| 1 | Flow Analysis | Identify critical user flows |
| 2 | Dex Handoff | Create epic + tasks per flow |
After Phase 2, use /complete <task-id> for each E2E test task.
/e2e "Cover checkout flow" # Basic
/e2e "Test auth and settings flows" # Multiple flows
Focus on:
Output: <phase_complete phase="1"/>
Create Dex epic, then tasks for each flow:
# Create epic
dex create "E2E Test Coverage" --description "Critical user flow coverage"
# For each flow
dex create "E2E: checkout flow" --parent <epic-id> --description "
Flow: Browse → Cart → Checkout → Confirmation
Steps:
1. Add product to cart
2. Proceed to checkout
3. Fill payment form
4. Complete purchase
Files:
- e2e/checkout.e2e.page.ts
- e2e/checkout.e2e.ts
Acceptance:
- [ ] Page object with semantic locators
- [ ] Test covers happy path
"
Output: <phase_complete phase="2"/> or <promise>E2E SETUP COMPLETE</promise>
Use Dex + /complete workflow:
dex list --pending # See what's ready
dex start <id> # Start working
/complete <id> # Run reviewers and complete
e2e/
├── checkout.e2e.page.ts # Page object (locators, setup, actions)
├── checkout.e2e.ts # Test file (concise tests)
├── auth.e2e.page.ts
└── auth.e2e.ts
| Priority | Locator | Example |
|---|---|---|
| 1 | getByRole | page.getByRole('button', { name: 'Submit' }) |
| 2 | getByLabel | page.getByLabel('Email address') |
| 3 | getByText | page.getByText('Welcome back') |
| 4 | getByTestId | page.getByTestId('submit-btn') - last resort |
// checkout.e2e.page.ts
export class CheckoutPage {
constructor(private page: Page) {}
// Locators
readonly emailInput = this.page.getByLabel('Email')
readonly submitButton = this.page.getByRole('button', { name: 'Complete' })
// Actions
async fillEmail(email: string) {
await this.emailInput.fill(email)
}
async submit() {
await this.submitButton.click()
}
}
// checkout.e2e.ts
test('user can complete checkout', async ({ page }) => {
const checkout = new CheckoutPage(page)
await checkout.fillEmail('user@example.com')
await checkout.submit()
await expect(page.getByText('Order confirmed')).toBeVisible()
})
// Auto-waiting (built into actions)
await page.getByRole('button').click() // Waits until clickable
// Explicit wait for state
await expect(page.getByText('Loaded')).toBeVisible()
// Wait for network
await page.waitForResponse('**/api/data')
/e2e "prompt" # Start flow analysis
/cancel-e2e # Cancel loop
/complete <task-id> # Complete task with reviewers
/complete - Run reviewers and mark Dex task completedex list - View pending tasksdex-workflow skill - Full Dex usage patternsNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
This skill should be used when the user asks about "parallel agents", "background tasks", "run_in_background", "non-blocking agents", "check agent progress", "TaskOutput", "retrieve agent results", or discusses running multiple agents concurrently. Covers patterns for launching agents in background, monitoring progress, and retrieving results.
The English summary is being prepared. Showing the original description.
Creates and manages Biome GritQL custom lint rules to enforce coding patterns. Use when creating linter rules, enforcing code conventions, preventing anti-patterns, or when the user mentions Biome, GritQL, custom lint rules, or AST-based linting.
The English summary is being prepared. Showing the original description.
Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.
The English summary is being prepared. Showing the original description.
This skill should be used when implementing features from a PRD spec, tracking implementation progress, or resuming work across sessions. Covers Dex task management for PRD story execution, daily workflows, and skill auto-loading.
The English summary is being prepared. Showing the original description.
Manage git worktrees using a centralized worktrees folder. Use for parallel development, PR reviews, or isolated work.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "plan a feature", "create PRD", "interview me about requirements", "define stories", "write a spec", "break down feature into tasks", "create implementation plan", "help me scope this feature", "what questions should I answer", or discusses feature planning. Covers the PRD interview process, spec structure, story atomization, and 4-phase workflow from idea to Dex tasks.
The English summary is being prepared. Showing the original description.