agentleFS
amirbironamirbiron/claude-skills/skills/browser-measurement/SKILL.md

browser-measurement

Skill0 starsChanged 3 months agoNo licenceView on GitHub

מודד שינוי פרונטאנד מול דפדפן אמיתי במקום להסיק מהקוד — שרת בדיקה מקומי, מדידה ב-Playwright/CDP, ריצת בקרה על הקוד שלפני התיקון, ומוטציות שמוכיחות שהבדיקה מסוגלת להיכשל. Use whenever a change touches CSS, JS, a template, or anything a browser renders or consumes, and whenever you are about to report that a UI fix works. Hebrew phrasings that should trigger it - תבדוק בדפדפן, תמדוד את זה, תוכיח שזה עובד, תריץ ותראה, תבדוק שלא נשבר, למה זה לא עובד בנייד. Trigger it on your own initiative before claiming a frontend bug is fixed, even without being asked. Do NOT use for backend logic with no browser consumer, for pure refactors, or for picking an external API signature - that is source-driven-development. Use run to get the app started; this skill is the measurement discipline once it is up. It is the concrete browser protocol under verify-against-reality, not a replacement for it.

The file

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.