
web-browser-skill
by robertlupo1997
Text-prompted object detection + segmentation with Grounding DINO + SAM 2. ~265–490 ms/img on RTX 3070. COCO eval + Streamlit demo.
SKILL.md
name: web-browser-skill description: AI-driven frontend development with live browser preview and visual verification. Use when building web UIs (dashboards, landing pages, web apps), when previewing/testing frontend code, when researching web designs for inspiration, or when the user wants AI to "see" what it built. Works on Windows/Mac/Linux. Enables semantic navigation, screenshot verification, and design research.
Web Browser Skill
Build, preview, and verify frontend code with real browser interaction. Inspired by ios-simulator-skill's semantic navigation philosophy, adapted for web browsers.
Quick Start
# 1. Launch dev server + browser for current project
python scripts/dev_server.py
# 2. Capture what's on screen
python scripts/screen_capture.py --output screenshot.png
# 3. Analyze page structure
python scripts/page_analyzer.py
# 4. Research a design
python scripts/web_researcher.py --url "https://example.com" --capture
Core Workflow
Building Frontend
- Create project from
assets/starter-template/if none exists - Write code in React/TypeScript (or HTML/CSS if simpler)
- Launch with
dev_server.pyto see live preview - Capture screenshot to verify visual output
- Iterate based on user feedback
Design Research
- User provides inspiration URL or description
- Use
web_researcher.pyto capture reference designs - Analyze layout, colors, typography
- Adapt patterns to user's project
Scripts Reference
| Script | Purpose | Default Output |
|---|---|---|
dev_server.py | Launch Vite dev server + open browser | 1 line status |
screen_capture.py | Screenshot current page | File path |
page_analyzer.py | Semantic element analysis | 5-10 lines |
web_researcher.py | Browse URL + capture | Screenshot + summary |
visual_diff.py | Compare two screenshots | Diff highlights |
All scripts support --verbose for details, --json for parsing.
Token Efficiency
Default output is minimal:
✓ Dev server running at http://localhost:5173
✓ Screenshot saved: ./screenshots/page-2024-01-15-143022.png
Use --verbose only when debugging.
Working with Beginners
When user doesn't understand code:
- Show screenshots of changes
- Use plain language: "I moved the button to the right"
- Offer correction phrases: "Say 'make it bigger' or 'change the color'"
- Reference
references/MINIMUM_KNOWLEDGE.mdfor teaching moments
Playwright MCP Integration (Recommended)
Prefer Playwright MCP for direct browser control - it's faster and uses less context than writing scripts:
# Install once:
claude mcp add playwright -- npx @playwright/mcp@latest
Playwright MCP handles:
- Direct page interaction (clicks, typing, navigation)
- Form testing and validation
- Screenshots and visual verification
- Multi-page workflows
Use this skill's scripts when:
- MCP is unavailable or not configured
- You need dev server lifecycle management
- Complex custom automation logic is required
Project Structure
For new projects, copy assets/starter-template/:
project/
├── src/
│ ├── App.tsx # Main component
│ ├── components/ # Reusable pieces
│ └── main.tsx # Entry point
├── index.html
├── package.json
├── vite.config.ts
└── tailwind.config.js
See Also
references/MINIMUM_KNOWLEDGE.md- What beginners need to correct AIreferences/PROJECT_TEMPLATES.md- Dashboard, Landing Page, Web App guidesreferences/COMMON_FIXES.md- Frequent mistakes and solutions
Score
Total Score
Based on repository quality metrics
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
Reviews
Reviews coming soon