codebase-audit

Process raw-extracted JSON files from PDF book extractions into clean, well-structured markdown. Use this skill whenever a user uploads a raw-extracted.json (or similar JSON with metadata and chunks arrays) from a PDF text extraction pipeline, or when they mention cleaning up, formatting, structuring, or organizing extracted book text. Also trigger when the user mentions OCR output, pypdf extraction, book chapters, or converting messy PDF extractions into readable markdown. This skill handles books with varying extraction quality — from clean text to garbled OCR — and adapts its approach accordingly.

This skill should be used when the user invokes /code-documentation, or asks to "write/generate/audit/update documentation", "write a README", "document this API or codebase", "write a tutorial / how-to / runbook", "write user help docs", "generate docstrings", "write an ADR or RFC", "create a changelog", "produce llms.txt or AGENTS.md", or "turn these docs into a doc site". Produces first-class documentation for any audience (end users, API consumers, contributors, operators, evaluators, AI agents) across all four Diátaxis modes, for the full lifecycle — authoring, generating from a codebase, auditing, and maintaining. Emits publish-ready Markdown or structured content for Docusaurus, MkDocs, Sphinx, Starlight, Mintlify, or Volume.

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.

Use when the user wants to brainstorm blog topics, generate or score article ideas, review/approve content ideas, track article status, or manage editorial planning — including mentions of "content calendar", "editorial calendar", "blog ideas", "article pipeline", "content backlog", or "publishing schedule".

Checklist for auditing architecture contracts in a develop-by-contract environment. Covers the failure modes most commonly found during contract review: status drift, AI-invented decisions, cross-contract fact drift, stale feature references, missing state specs, and business policy gaps.

Use when analyzing, auditing, reviewing, or explaining a codebase, system, or project state — whenever written claims could mix observed fact with interpretation.

Use when writing or reviewing implementation plans, roadmaps, tickets, or task lists that claim to be execution-ready — especially before handing work to another agent or session.

Use when creating or updating in-app help content — tooltips, empty states, contextual panels, help articles — or auditing help coverage, identifiers, and accuracy.

Automate QA regression testing with reusable test skills. Create login flows, dashboard checks, user creation, and other common test scenarios that run consistently.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Analyze a repository and generate a state-of-the-art README.md file. Use when user wants to create or update a README for their project, repository, or codebase. Triggers include requests to "create/write/generate/update a README", "document my repo", "make a README", or "I need documentation for my project". This skill scans the repository structure, analyzes code files, identifies key components, and produces a comprehensive, professional README following modern best practices.

Use when investigating, fixing, or improving an existing codebase — any task where refactoring temptation, scope creep, or architectural drift could exceed what was actually asked.

Use when running CLI commands in a harness WITHOUT reliable output capture — no built-in stdout/stderr or exit-code reporting. Not needed in Claude Code, whose shell tools already capture output and exit codes.

Use when doing sustained or multi-step work in any project — feature work, refactors, investigations, or anything touching multiple files or sessions. Defines the ticket body format, status lifecycle, and LOGBOOK.md conventions used across all projects.

Audits tickets/issues in a repo against the actual codebase — surfaces stale, silently-completed, or no-longer-relevant work plus format, dependency, status drift, and content quality problems. Auto-detects ticket source (GitHub Issues, Airtable, TICKETS.md). Do not use automatically; invoke explicitly via /tickets-audit when the user wants to audit their backlog.

Step-by-step process for migrating a project from a TICKETS.md file to GitHub Issues. Use when a project has an existing TICKETS.md and a GitHub remote and you want to convert to GitHub Issues for token-efficient tracking.

Use when assessing feature completeness, auditing UX or onboarding, or judging whether a feature is "done" — especially gap analyses, SOTA comparisons, and first-run/cold-start reviews.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

Use when the user asks to audit website performance, check PageSpeed scores, review Core Web Vitals (LCP/CLS/INP/FCP/TBT), find slow pages, or run a performance audit. Fetches real data from Google PageSpeed Insights API, maps each failing audit to the project codebase, then produces a prioritized split: immediate fixes (safe to apply now) vs. tickets (need planning). Triggers on phrases like 'pagespeed audit', 'check my performance score', 'why is my site slow', 'Core Web Vitals audit', 'PageSpeed report', or /pagespeed-audit.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Expert guidance on implementing state-of-the-art (SOTA) metadata for websites, including Schema.org (JSON-LD), Open Graph, Twitter Cards, Dublin Core, COinS, and Geo-JSON. Use when you need to optimize a website for search engines (SEO), social media sharing, or academic/bibliographic interoperability. Use also when generating structured data for articles, products, local businesses, or geographic features.