frontend-quality
Skill6 starsChanged 49 days agoMITView on GitHub
Gate frontend changes on quality contracts: a universal build + lint pass, plus opt-in Lighthouse, accessibility (axe), and bundle-size budgets that run only when the project declares them with an explicit command and threshold. The frontend counterpart to a backend test gate. Use before merging any frontend change.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- sivaguru-2113/Agent-personatheir own version, first seen Aug 18, 2026
- Xipher-Labs/walter-ostheir own version, first seen May 21, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Xipher-Labs/walter-os★ 8same name
- sivaguru-2113/Agent-persona★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- atomic-reportSkill
- board-validateSkill
- data-modelSkill
- delivery-hygieneSkill
- dev-reportSkill
- dev-setupSkill
- gcSkill
- git-branchSkill
- land-and-archiveSkill
- orchestration-healthSkill
- orchestratorSkill
- pipeline-qualitySkill
- plan-updateSkill
- project-planSkill
- release-gateSkill
- repo-auditSkill
- scaleSkill
- security-reviewSkill
- swarmSkill
- test-coverageSkill
- tpmSkill
- trackerSkill
- worktree-cleanupSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Very specific: line 18
Run the frontend area's test command from context.md (the same command the release gate uses) from the project root.
- Distinctive: line 21
Must exit 0 with no type errors.
- Very specific: line 26
Use the lint command the project wires into its frontend gate (often part of the command above, e.g.
- Distinctive: line 44
When a budget is not declared, record it as SKIPPED and move on.
≈ “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.
Files
Frontend Quality
Validates frontend changes against quality contracts. Build and lint are universal — they run on every frontend change. Lighthouse, accessibility (axe), and bundle-size budgets are opt-in: they run only when the project has declared them with an explicit command and threshold, and are otherwise skipped, not failed. An unconfigured budget must never block a merge — a gate nobody agreed to isn't a gate, it's a surprise.
Universal checks (always run)
1. Build
Run the frontend area's test command from context.md (the same command the release gate
uses) from the project root.
- Must exit 0 with no type errors.
- A build failure is a blocking defect.
2. Lint
- Use the lint command the project wires into its frontend gate (often part of the command
above, e.g.
npm run lint). - Zero new lint errors. A change that adds errors is a blocking defect. Pre-existing errors on the default branch are not this change's responsibility — but do not add to them.
Opt-in budgets (run only when declared)
Each budget runs only when the project's context.md declares it under a
Frontend quality budgets heading with a command and a threshold, e.g.:
## Frontend quality budgets
- Lighthouse: `npm run lighthouse:ci`, min score 90
- Accessibility (axe): `npm run test:a11y`, zero serious/critical
- Bundle size: `npm run bundle:report`, max 250 KB gzippedWhen a budget is not declared, record it as SKIPPED and move on.
- Lighthouse — run the declared command; fail if the score is below the declared minimum.
- Accessibility (axe) — run the declared command; fail on any serious/critical violation (or the project's declared threshold).
- Bundle size — run the declared command; fail if the measured size exceeds the declared budget.
Output
=== Frontend Quality ===
Build: PASS / FAIL
Lint: PASS / FAIL (<n> new errors)
Lighthouse: PASS / FAIL / SKIP (<score> vs threshold)
Accessibility: PASS / FAIL / SKIP (<n> serious/critical)
Bundle size: PASS / FAIL / SKIP (<size> vs budget)
BLOCKERS:
- <description>
WARNINGS:
- <description>
VERDICT: SHIP / BLOCKA SKIP never contributes to BLOCK. A BLOCK sends the ticket back to build with the specific
failure — same contract as the release-gate skill.
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
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.