audit

Name: audit
Author: heyhank-app

30stars13forks

How to install audit?

heyhank-app/heyhank/audit

$npx -y skills add heyhank-app/heyhank --skill audit

Installs into the current project.

Summary

Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.

Files · 1

View on GitHub

SKILL.md

1	Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Don't fix issues - document them for other commands to address.
2
3	First: Use the frontend-design skill for design principles and anti-patterns.
4
5	## Diagnostic Scan
6
7	Run comprehensive checks across multiple dimensions:
8
9	1. Accessibility (A11y) - Check for:
10	- Contrast issues: Text contrast ratios < 4.5:1 (or 7:1 for AAA)
11	- Missing ARIA: Interactive elements without proper roles, labels, or states
12	- Keyboard navigation: Missing focus indicators, illogical tab order, keyboard traps
13	- Semantic HTML: Improper heading hierarchy, missing landmarks, divs instead of buttons
14	- Alt text: Missing or poor image descriptions
15	- Form issues: Inputs without labels, poor error messaging, missing required indicators
16
17	2. Performance - Check for:
18	- Layout thrashing: Reading/writing layout properties in loops
19	- Expensive animations: Animating layout properties (width, height, top, left) instead of transform/opacity
20	- Missing optimization: Images without lazy loading, unoptimized assets, missing will-change
21	- Bundle size: Unnecessary imports, unused dependencies
22	- Render performance: Unnecessary re-renders, missing memoization
23
24	3. Theming - Check for:
25	- Hard-coded colors: Colors not using design tokens
26	- Broken dark mode: Missing dark mode variants, poor contrast in dark theme
27	- Inconsistent tokens: Using wrong tokens, mixing token types
28	- Theme switching issues: Values that don't update on theme change
29
30	4. Responsive Design - Check for:
31	- Fixed widths: Hard-coded widths that break on mobile
32	- Touch targets: Interactive elements < 44x44px
33	- Horizontal scroll: Content overflow on narrow viewports
34	- Text scaling: Layouts that break when text size increases
35	- Missing breakpoints: No mobile/tablet variants
36
37	5. Anti-Patterns (CRITICAL) - Check against ALL the DON'T guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).
38
39	CRITICAL: This is an audit, not a fix. Document issues thoroughly with clear explanations of impact. Use other commands (normalize, optimize, harden, etc.) to fix issues after audit.
40
41	## Generate Comprehensive Report
42
43	Create a detailed audit report with the following structure:
44
45	### Anti-Patterns Verdict
46	Start here. Pass/fail: Does this look AI-generated? List specific tells from the skill's Anti-Patterns section. Be brutally honest.
47
48	### Executive Summary
49	- Total issues found (count by severity)
50	- Most critical issues (top 3-5)
51	- Overall quality score (if applicable)
52	- Recommended next steps
53
54	### Detailed Findings by Severity
55
56	For each issue, document:
57	- Location: Where the issue occurs (component, file, line)
58	- Severity: Critical / High / Medium / Low
59	- Category: Accessibility / Performance / Theming / Responsive
60	- Description: What the issue is
61	- Impact: How it affects users
62	- WCAG/Standard: Which standard it violates (if applicable)
63	- Recommendation: How to fix it
64	- Suggested command: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /critique, /colorize — or other installed skills you're sure exist)
65
66	#### Critical Issues
67	[Issues that block core functionality or violate WCAG A]
68
69	#### High-Severity Issues
70	[Significant usability/accessibility impact, WCAG AA violations]
71
72	#### Medium-Severity Issues
73	[Quality issues, WCAG AAA violations, performance concerns]
74
75	#### Low-Severity Issues
76	[Minor inconsistencies, optimization opportunities]
77
78	### Patterns & Systemic Issues
79
80	Identify recurring problems:
81	- "Hard-coded colors appear in 15+ components, should use design tokens"
82	- "Touch targets consistently too small (<44px) throughout mobile experience"
83	- "Missing focus indicators on all custom interactive components"
84
85	### Positive Findings
86
87	Note what's working well:
88	- Good practices to maintain
89	- Exemplary implementations to replicate elsewhere
90
91	### Recommendations by Priority
92
93	Create actionable plan:
94	1. Immediate: Critical blockers to fix first
95	2. Short-term: High-severity issues (this sprint)
96	3. Medium-term: Quality improvements (next sprint)
97	4. Long-term: Nice-to-haves and optimizations
98
99	### Suggested Commands for Fixes
100
101	Map issues t

People who liked this also viewed

6 picks

Type

lark-openapi-explorer飞书/Lark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。SkillsJul 2026378k16k
lark-skill-maker创建 lark-cli 的自定义 Skill。当用户需要把飞书 API 操作封装成可复用的 Skill（包装原子 API 或编排多步流程）时使用。SkillsJul 2026377k16k
azure-cost-optimizationOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026209k1.3k
vercel-react-native-skillsVercel's official collection of agent skillsSkillsJul 2026172k29k
mcp-builderGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate externaSkillsJul 202693k163k
gws-sharedgws CLI: Shared patterns for authentication, global flags, and output formatting.SkillsJul 202653k30k

audit

30stars13forks

View on GitHub

How to install audit?

heyhank-app/heyhank/audit

$npx -y skills add heyhank-app/heyhank --skill audit

Installs into the current project.

Summary

Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.

Files · 1

View on GitHub

SKILL.md

1	Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Don't fix issues - document them for other commands to address.
2
3	First: Use the frontend-design skill for design principles and anti-patterns.
4
5	## Diagnostic Scan
6
7	Run comprehensive checks across multiple dimensions:
8
9	1. Accessibility (A11y) - Check for:
10	- Contrast issues: Text contrast ratios < 4.5:1 (or 7:1 for AAA)
11	- Missing ARIA: Interactive elements without proper roles, labels, or states
12	- Keyboard navigation: Missing focus indicators, illogical tab order, keyboard traps
13	- Semantic HTML: Improper heading hierarchy, missing landmarks, divs instead of buttons
14	- Alt text: Missing or poor image descriptions
15	- Form issues: Inputs without labels, poor error messaging, missing required indicators
16
17	2. Performance - Check for:
18	- Layout thrashing: Reading/writing layout properties in loops
19	- Expensive animations: Animating layout properties (width, height, top, left) instead of transform/opacity
20	- Missing optimization: Images without lazy loading, unoptimized assets, missing will-change
21	- Bundle size: Unnecessary imports, unused dependencies
22	- Render performance: Unnecessary re-renders, missing memoization
23
24	3. Theming - Check for:
25	- Hard-coded colors: Colors not using design tokens
26	- Broken dark mode: Missing dark mode variants, poor contrast in dark theme
27	- Inconsistent tokens: Using wrong tokens, mixing token types
28	- Theme switching issues: Values that don't update on theme change
29
30	4. Responsive Design - Check for:
31	- Fixed widths: Hard-coded widths that break on mobile
32	- Touch targets: Interactive elements < 44x44px
33	- Horizontal scroll: Content overflow on narrow viewports
34	- Text scaling: Layouts that break when text size increases
35	- Missing breakpoints: No mobile/tablet variants
36
37	5. Anti-Patterns (CRITICAL) - Check against ALL the DON'T guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).
38
39	CRITICAL: This is an audit, not a fix. Document issues thoroughly with clear explanations of impact. Use other commands (normalize, optimize, harden, etc.) to fix issues after audit.
40
41	## Generate Comprehensive Report
42
43	Create a detailed audit report with the following structure:
44
45	### Anti-Patterns Verdict
46	Start here. Pass/fail: Does this look AI-generated? List specific tells from the skill's Anti-Patterns section. Be brutally honest.
47
48	### Executive Summary
49	- Total issues found (count by severity)
50	- Most critical issues (top 3-5)
51	- Overall quality score (if applicable)
52	- Recommended next steps
53
54	### Detailed Findings by Severity
55
56	For each issue, document:
57	- Location: Where the issue occurs (component, file, line)
58	- Severity: Critical / High / Medium / Low
59	- Category: Accessibility / Performance / Theming / Responsive
60	- Description: What the issue is
61	- Impact: How it affects users
62	- WCAG/Standard: Which standard it violates (if applicable)
63	- Recommendation: How to fix it
64	- Suggested command: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /critique, /colorize — or other installed skills you're sure exist)
65
66	#### Critical Issues
67	[Issues that block core functionality or violate WCAG A]
68
69	#### High-Severity Issues
70	[Significant usability/accessibility impact, WCAG AA violations]
71
72	#### Medium-Severity Issues
73	[Quality issues, WCAG AAA violations, performance concerns]
74
75	#### Low-Severity Issues
76	[Minor inconsistencies, optimization opportunities]
77
78	### Patterns & Systemic Issues
79
80	Identify recurring problems:
81	- "Hard-coded colors appear in 15+ components, should use design tokens"
82	- "Touch targets consistently too small (<44px) throughout mobile experience"
83	- "Missing focus indicators on all custom interactive components"
84
85	### Positive Findings
86
87	Note what's working well:
88	- Good practices to maintain
89	- Exemplary implementations to replicate elsewhere
90
91	### Recommendations by Priority
92
93	Create actionable plan:
94	1. Immediate: Critical blockers to fix first
95	2. Short-term: High-severity issues (this sprint)
96	3. Medium-term: Quality improvements (next sprint)
97	4. Long-term: Nice-to-haves and optimizations
98
99	### Suggested Commands for Fixes
100
101	Map issues t

People who liked this also viewed

6 picks

Type