agentleFS
Sign inStart free
oocxoocx/tfplan2md/.claude/skills/website-devtools/SKILL.md

website-devtools

Skill174 starsChanged 2 months agoMITView on GitHub

Use browser tools to inspect rendering and troubleshoot website issues with the Maintainer.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ensure the site is available via the VS Code preview server (http://127.0.0.1:3000/website/dist/), then open the relevant page with …

    line 34
  2. Very specific:

    Use browser/readPage, browser/clickElement, browser/hoverElement, browser/typeInPage, browser/runPlaywrightCode, and screenshots as needed …

    line 35
  3. Distinctive:

    When a shared layout, component, partial, or client-side module is under investigation, validate more than one consuming page.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Instructions

Purpose

Provide a repeatable way to use browser tools during website work to validate rendering, diagnose layout or CSS issues, and troubleshoot together with the Maintainer.

Hard Rules

Must

  • Use the browser/* tools when diagnosing rendering, layout, or interaction issues.
  • Capture concrete findings (console errors, computed styles, DOM structure) and summarize them in the PR/issue.

Must Not

  • Do not guess at rendering behavior when you can verify it in the browser preview.

Golden Example

Use browser tools to:
- Inspect computed styles and layout for a problematic element
- Check console for errors
- Verify responsive behavior by simulating viewports

Actions

  1. Ensure the site is available via the VS Code preview server (http://127.0.0.1:3000/website/dist/), then open the relevant page with browser/openBrowserPage.
  2. Use browser/readPage, browser/clickElement, browser/hoverElement, browser/typeInPage, browser/runPlaywrightCode, and screenshots as needed to inspect:
    • DOM structure and element attributes
    • Computed CSS and layout metrics
    • Console logs and runtime errors
    • Network requests (if applicable)
  3. When a shared layout, component, partial, or client-side module is under investigation, validate more than one consuming page.
  4. Share findings with the Maintainer and propose the smallest fix.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free