Individual skill
frontend-quality-auditor
Audit launch readiness; report ship/no-ship.
skills/frontend-quality-auditor/SKILL.md
Source commit 9922fa0af0aea32443cf7365ef5024dc7797382d
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 137
- Repository last updated
- Oct 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- accessibility Repository topic
- codex Repository topic
- codex-skills Repository topic
- frontend Repository topic
- motion Repository topic
- nextjs Repository topic
- react Repository topic
- tailwind Repository topic
- web-design Repository topic
- agent-skills Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,251 bytesSKILL.mdcore · 4,251 bytesagents/openai.yamlasset · 252 bytesreferences/audit-checklist.mddoc · 3,916 bytes
Read excerpt
# Frontend Quality Auditor
Use this skill to decide whether a frontend is ready to ship and what should be fixed first.
## Core Contract
Produce a concise, evidence-based quality report. Do not redesign the product unless the user explicitly asks for fixes. The default output is an audit, not a rebuild.
## Audit Workflow
1. Identify the project type, framework, entry routes, styling system, scripts, and available preview or deployment URL.
2. Inspect source structure first, then inspect rendered output when a browser or screenshot workflow is available.
3. Review desktop and mobile breakpoints before judging visual quality.
4. Check the launch-critical surfaces: hero or first screen, navigation, primary CTA, forms, media, interactive states, footer, error/loading/empty states, and any checkout, booking, pricing, or dashboard flows.