universal-audit-pattern
Universal Audit Pattern
Category: Quality Time Saved: 4+ hours per audit Battle-tested: Yes — applied to docs, code, security, architecture
The Problem
You need to audit something — documentation accuracy, code quality, security compliance, architectural drift. You start checking things randomly, fix some issues, get distracted, lose track of what you've reviewed.
Why Ad-Hoc Audits Fail
- No systematic coverage — you miss things
- No severity ranking — you fix minor issues while critical ones wait
- No completion criteria — you don't know when you're done
- No reproducibility — next audit starts from scratch
More from fabioc-aloha/alex_skill_mall
refactor
Systematic code refactoring to improve maintainability without changing behavior. Use when asked to "refactor this", "clean up this code", "improve code quality", "simplify this", "reduce complexity", or "eliminate code smells". Always preserves existing behavior.
1socratic-questioning
Help users discover answers, don't just deliver them.
1graphic-design
Patterns for visual design, SVG creation, layout composition, typography, and brand identity.
1deep-review
Adversarial code review with three parallel perspectives — Advocate, Skeptic, Architect — that create productive tension. Use for high-stakes PRs, architectural changes, or when single-pass review would miss issues. Surfaces findings through disagreement, not consensus.
1data-preparation
Data cleaning, profiling, transformation, and quality gates -- prepares raw data for visualization and analysis
1dashboard-design
Dashboard layout patterns, KPI card design, filter architecture, narrative flow through panels, and self-contained HTML generation
1