elysium-audit
Audit web project files against specific style and quality guidelines without auto-fixing.
Install
mkdir -p .claude/skills/elysium-audit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16501" && unzip -o skill.zip -d .claude/skills/elysium-audit && rm skill.zipInstalls to .claude/skills/elysium-audit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Audit HTML/CSS/JS files for code quality violations per CLAUDE.md rules. Reports issues grouped by file without auto-fixing.Key capabilities
- →Audit HTML files for inline styles and missing attributes
- →Audit CSS files for hardcoded values and duplicate selectors
- →Audit JavaScript files for console.log statements and global variable pollution
- →Audit assets for broken src paths and incorrect image formats
How it works
The skill reads specified HTML, CSS, and JS files and checks them against a predefined set of code quality rules. It then reports findings grouped by file, distinguishing between critical and polish issues.
Inputs & outputs
When to use elysium-audit
- →Audit HTML/CSS quality
- →Check web accessibility
- →Review style standards
About this skill
Elysium Audit
Run a read-only code quality audit on the specified page(s). Report findings only — do not auto-fix.
Scope
Audit one or more of: index.html, pages/games/arc-raiders.html, pages/games/valorant.html, and their associated CSS/JS files.
What to Check
HTML
- Inline styles (
style="..."attributes) - Images missing
altattribute - Non-hero images missing
loading="lazy" - Scripts missing
defer - Hardcoded prices in HTML
- Missing
<title>or<meta name="description"> - Inconsistent nav/footer across pages
CSS
- Hardcoded hex/rgb values not using
global.cssvariables - Duplicate selectors within the same file
- Page-specific styles placed in
global.cssorcomponents.css - Stacked
backdrop-filterlayers - Missing
@property --arc-trace-anglewhen travelling line is used
JavaScript
console.logstatements- Page-specific logic in
main.jsor shared logic in page JS - Global variable pollution (non-const top-level declarations)
- Page JS files exceeding ~300 lines
Assets
- Broken
srcpaths (referenced files that don't exist) - Non-WebP images that should be WebP
- Non-PNG icons that need transparency
- Audio files present (none should exist)
- References to
orderpanelbg.webp(removed permanently)
Workflow
- List all HTML, CSS, and JS files to confirm scope.
- Read each file in scope.
- Check against every rule above.
- Report findings grouped by file.
- Separate critical (broken paths, missing assets, inline styles) from polish (missing lazy, missing alt on decorative images).
- Do not modify any files.
- Do not commit.
Output Format
## Audit Results — [page name]
### Critical
- [file:line] description
### Polish
- [file:line] description
### Clean
- [rule] — no issues found
When not to use it
- →When auto-fixing of code quality violations is required
- →When the audit scope is outside of HTML, CSS, JS, or specified assets
- →When the task involves modifying files
Limitations
- →The skill does not auto-fix any identified issues
- →The audit is limited to specific HTML, CSS, JS files and asset types
- →It does not commit any changes
How it compares
This skill systematically audits web files against specific quality rules and reports findings without making any modifications, unlike manual code reviews or tools that auto-fix issues.
Compared to similar skills
elysium-audit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| elysium-audit (this skill) | 0 | 2mo | No flags | Beginner |
| accessibility-compliance | 45 | 2mo | No flags | Intermediate |
| frontend-code-review | 11 | 2mo | No flags | Advanced |
| frontend-developer | 0 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
accessibility-compliance
wshobson
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
frontend-code-review
langgenius
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
frontend-developer
bonnguyenitc
Use when building web UI, designing component architecture, or reviewing frontend code — regardless of framework (React, Vue, Svelte, etc.)
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.
shadcn-ui-setup
maneeshanif
Install and configure Shadcn/ui component library with Radix UI primitives, Aceternity UI effects, set up components, and manage the component registry. Use when adding Shadcn/ui to a Next.js project or installing specific UI components for Phase 2.
typescript-review
metabase
Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.