browser-use

name	browser-use
description	Headful browser automation with natural language control. Use when use when automating browser tasks with natural language commands Triggers on keywords: browser, automation, playwright, testing.
allowed-tools	Read, Write, Bash, Edit, Grep, Glob
user-invocable	true
mcp-servers	["filesystem","github","docker"]

Browser Automation

context

Headful browser automation with natural language control. Navigate, click, type, screenshot, and extract data from web pages using structured commands. This skill provides structured workflows and production-ready patterns that ensure code quality, maintainability, and developer experience.

instructions

Step 1: Understand Requirements

1. Identify the core development task — new feature, bug fix, refactor, or integration
2. Determine technical constraints — language, framework, existing architecture patterns
3. Assess scope — is this a quick fix or a significant implementation?
4. Check for existing patterns in the codebase before writing new code

Step 2: Apply Development Framework

1. Plan — Break the task into small, testable units of work
2. Implement — Write clean, well-documented code following project conventions
3. Validate — Test the implementation against requirements and edge cases
4. Document — Add inline comments and update relevant documentation

Step 3: Generate Implementation

Structure output following this format:

## Implementation Plan

### Approach
Description of the chosen approach and why it was selected

### Code Changes
Files to modify/create with rationale for each change

### Testing Strategy
- Unit tests: what to test at the function level
- Integration tests: how components interact together
- Edge cases: boundary conditions and error states

### Dependencies
- New dependencies if any with justification
- Existing dependencies to leverage

Step 4: Quality Gates

Before completing any implementation:

• Code follows project style guide and conventions
• All new code has appropriate test coverage
• Error handling covers all failure modes
• Performance implications are documented
• Security considerations are addressed
• Documentation is updated

constraints

• NEVER skip error handling — every external call must handle failure gracefully.
• NEVER introduce breaking changes without explicit version bumps and migration guides.
• NEVER hardcode configuration — use environment variables or config files.
• ALWAYS write tests before or alongside implementation (not after).
• ALWAYS consider backward compatibility when modifying existing APIs.

examples

Example: Development Task

Input: "Use when automating browser tasks with natural language commands"

Output:

## Implementation Plan

### Approach
Use the established browser use pattern to implement the feature with minimal coupling and maximum testability.

### Code Changes
1. Create new module following project structure conventions
2. Add configuration to existing settings
3. Wire up dependency injection

### Testing Strategy
- Unit tests: Core logic with mocked dependencies
- Integration tests: Full workflow with real dependencies
- Edge cases: Empty inputs, concurrent access, error recovery