Agent skill
dash-audit
Audit Dash apps for callback hazards, state flow risks, layout and accessibility issues, and Dash-specific UX regressions. Use when the user asks for a Dash callback review, Dash UI audit, Dash web-interface audit, or a read-first remediation plan for a Dash app. Do not use for generic React or Next.js UI review.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/dash-audit
SKILL.md
Dash Audit
Use this skill for read-first Dash audits. It owns Dash callback review, Dash UI/state review, and prioritized remediation guidance.
Workflow
- Read the repo
AGENTS.md. - Run
/home/bjorn/.codex/skill-support/bin/ui-audit-preflight dash-callback-map --cwd <repo> --out <json>. - Read only the Dash references you need:
references/dash-callbacks.mdfor callback graph and state hazards.references/dash-ui.mdfor layout, responsiveness, accessibility, and interaction review.
- Inspect only the files surfaced by the preflight plus any directly implicated layout, component, or callback modules.
- Report grouped findings with the highest-risk callback and regression issues first.
- If the user asks for fixes, keep remediation scoped and verify the affected path with repo-native commands.
Use When
- The task is a Dash callback audit.
- The task is a Dash web UI, state, or layout review.
- The user wants a read-first remediation plan for a Dash app.
Do Not Use When
- The task is a general web or Next.js UI audit.
- The task is platform architecture with no Dash review need.
- The task is only backend, dependency, or docs work.
Outputs
- executive summary
- grouped findings by category and file
- prioritized fixes
- callback graph or regression-risk notes when useful
- scorecard or risk summary when useful
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?