agentleFS
Sign inStart free
almax000almax000/claude-skills/dev-console/SKILL.md

dev-console

Skill1 starsChanged 7 months agoMITView on GitHub

In-browser UI review + DOM annotation tool for frontend quality feedback loops. Runtime paths (created by init command, gitignored): - .claude/plugins/ — plugin runtime copies - .claude/feedback/annotations.json — annotation data

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    All resources served via /__dev-console/ middleware routes, nothing written to dist/

    line 8

≈ “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

Dev Console

In-browser UI review + DOM annotation tool for frontend quality feedback loops.

Safety Guarantee

  • Vite plugin uses apply: 'serve' — zero production footprint
  • All resources served via /__dev-console/ middleware routes, nothing written to dist/
  • Annotation data persists to .claude/feedback/annotations.json (gitignored)

Commands

CommandDescription
/dev-console-initFirst-time setup: copy plugin files + inject into vite.config
/dev-consoleEnable/disable the Dev Console

Modules

ModuleDescription
annotationDOM element annotation + notes, state machine IDLE→SELECTING→FORM_OPEN→IDLE
component-boundariesVue component boundary visualization
css-varsCSS variable viewer/editor

Architecture

plugin/                          # Source files (Git tracked, portable)
├── vite-plugin-dev-console.mjs  # Vite plugin entry (apply: 'serve')
├── dev-console-shell.js         # Shadow DOM host + panel UI
├── dev-console-shell.css        # Panel styles (dark/light themes)
├── dev-console-i18n.js          # Bilingual EN/ZH
├── dev-console-theme.js         # Theme system
└── modules/                     # Feature modules
    ├── annotation.js
    ├── component-boundaries.js
    └── css-vars.js

Runtime paths (created by init command, gitignored):

  • .claude/plugins/ — plugin runtime copies
  • .claude/feedback/annotations.json — annotation data

Workflow

/dev-console-init              # First time: copy plugin/ → .claude/plugins/ + inject vite.config
npm run dev                    # Start dev server, Console auto-loads
Browser bottom-right ● button  # Open/close Dev Console drawer
Annotate DOM elements + notes  # Data saved to .claude/feedback/annotations.json
Claude reads annotations       # Feedback loop closed

Requirements

  • Vite — any Vite-powered project (Vue, React, Svelte, etc.)
  • Node.js >= 18

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