スキル一覧に戻る
robertlupo1997

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.

0🍴 0📅 2026年1月12日
GitHubで見るManusで実行

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

  1. Create project from assets/starter-template/ if none exists
  2. Write code in React/TypeScript (or HTML/CSS if simpler)
  3. Launch with dev_server.py to see live preview
  4. Capture screenshot to verify visual output
  5. Iterate based on user feedback

Design Research

  1. User provides inspiration URL or description
  2. Use web_researcher.py to capture reference designs
  3. Analyze layout, colors, typography
  4. Adapt patterns to user's project

Scripts Reference

ScriptPurposeDefault Output
dev_server.pyLaunch Vite dev server + open browser1 line status
screen_capture.pyScreenshot current pageFile path
page_analyzer.pySemantic element analysis5-10 lines
web_researcher.pyBrowse URL + captureScreenshot + summary
visual_diff.pyCompare two screenshotsDiff 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:

  1. Show screenshots of changes
  2. Use plain language: "I moved the button to the right"
  3. Offer correction phrases: "Say 'make it bigger' or 'change the color'"
  4. Reference references/MINIMUM_KNOWLEDGE.md for teaching moments

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 AI
  • references/PROJECT_TEMPLATES.md - Dashboard, Landing Page, Web App guides
  • references/COMMON_FIXES.md - Frequent mistakes and solutions

スコア

総合スコア

70/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です