full-stack-auditlisted

Comprehensive website and web app audit covering security, UX, performance, accessibility, SEO, compliance, and revenue protection. Use this skill whenever the user asks to audit, review, check, or score a website or web application. Also use when the user says 'full-stack audit', 'UX audit', 'security audit', 'launch checklist', 'is my site ready to launch', 'check my site', 'review my code for issues', 'what did I miss', or any variation of wanting a comprehensive quality review before or after launch. This skill catches the issues that AI-built and vibe-coded sites consistently get wrong: client-side paywalls, exposed database tables, missing security headers, broken mobile layouts, and trust gaps that kill conversion. Triggers even if the user only asks about one area (e.g., 'check my security') because problems compound across categories.
osbertunawakened431/full-stack-audit · ★ 0 · Code & Development · score 62

Install: claude install-skill osbertunawakened431/full-stack-audit

# Full-Stack Website Audit A 90-checkpoint audit for websites and web apps. Covers security, revenue protection, UX, performance, accessibility, SEO, compliance, and infrastructure. Designed for solo founders, indie hackers, and developers shipping products built with AI assistance. ## Before Starting 1. Read every file in the project. Not just the pages — read API routes, middleware, config files, environment examples, database schemas, and package.json. 2. Check the live site if a URL is provided. Open it in a browser and test the actual user flow. 3. Do NOT ask the user questions. Audit everything, score every checkpoint, then report. ## How Scoring Works Each checkpoint is PASS, FAIL, or N/A. Every FAIL must include: - What's wrong (specific, not vague) - Why it matters (impact on users, security, or revenue) - How to fix it (concrete steps, not general advice) Score each category, then total. Categories with N/A items: adjust denominator. --- ## PART 1: FULL-STACK AUDIT (50 checkpoints) ### CATEGORY 1: VISUAL DESIGN & FRONTEND (5 checks) 1.1 **Typography hierarchy** FAIL if there's no clear distinction between headings, body, and labels. FAIL if more than 2 font families are used without reason. FAIL if font sizes are inconsistent across similar elements. PASS requires: Clear heading/body/label hierarchy. Maximum 2 font families. Consistent sizing system. 1.2 **Colour system** FAIL if colours are hardcoded throughout instead of using CSS variables or a theme.