w159

MANUAL skill covering the full atlas lifecycle outside of task work: onboard (scaffold the docs/ SSOT plus .atlas/ internal state, inventory skills, recommend what to run next), install (verify and wire claude-mem, context-mode, hooks, project config), connectors (guided vendor MCP connector setup across domain plugins), and repair (fix a broken atlas install: marketplace, rollbacks, hooks, assets). Run with no args for onboarding plus recommendations; run with --fix to auto-repair.

Atlas architect: boot the workspace. Verify claude-mem and context-mode, scan the project, recommend tooling (confirm first), wire hooks, seed the docs/ SSOT.

This skill should be used when the user asks to "audit my codebase against The Pragmatic Programmer", run a "pragmatic audit", "check what pragmatic principles are implemented", "review codebase for pragmatic practices", "find what's missing from the pragmatic programmer in this project", or wants a structured review of a codebase/project/monorepo against the book's principles, tips, and practices. Produces a ranked report of what is implemented, partially implemented, and missing, each finding cited to the book concept and to file:line evidence. Supports --chapters to scope dimensions and --report to set output path.

This skill should be used when the user is "designing a module", "deciding an architecture", "debugging a bug", "refactoring code", "writing tests", "naming things", "handling concurrency", "decoupling components", "choosing inheritance vs composition", "adding error handling", asks "what does The Pragmatic Programmer say about X", "is this DRY", "should I use inheritance or composition", "how should I structure this", or otherwise wants the relevant Pragmatic Programmer principles, tips, or practices surfaced for the work in progress. Surfaces 1-4 relevant principles with book tip numbers and citations to the concept files.

Create or modify a reusable component that survives latency, cancellation, and partial failure (progress modal, upload widget, job panel), handling every backend state with all six interaction states rendered.

Read-only database audit via parallel subagents: inventory a live schema, reconcile it against the code, and check privileges and naming before any change.

Reproducible bug, exception, stack trace, or bad output: root-cause fix with evidence, not a patch over. Use when you want the actual cause fixed, not the symptom hidden.

Build or refactor screens, flows, or components on a single design system (shadcn/ui + Tailwind + Radix) with every state handled and verified live in the browser.

Atlas architect: boot the workspace. Verify claude-mem and context-mode, scan the project, recommend tooling (confirm first), wire hooks, seed the docs/ SSOT.

Measure atlas's own run health, audit context/asset waste, and mine session transcripts. Three lenses: RUN HEALTH reads the observability DB for metrics (wall-clock, dispatches, verifier coverage) and baseline->target goals; ASSET AUDIT scores each context-loaded skill/agent/plugin by token cost and relevance to flag disable/relocate; SESSION FORENSICS mines transcripts for unused tools and unverified claims into rules. No args reports trends.

Use to map a codebase into feature-grouped flowcharts, find architectural duplication across features, and propose the simplest unified architecture - discovery-first and zero-arg. Runs as a Workflow that fans out one explorer per feature, hunts duplication, and synthesizes a unification proposal with file:line evidence. Use before a refactor, to "find the ideal path," or to unify duplicated systems.

Generate or improve a company-specific data analysis skill by extracting tribal knowledge from analysts. BOOTSTRAP MODE - Triggers: "Create a data context skill", "Set up data analysis for our warehouse", "Help me create a skill for our database", "Generate a data skill for [company]" -> Discovers schemas, asks key questions, generates initial skill with reference files ITERATION MODE - Triggers: "Add context about [domain]", "The skill needs more info about [topic]", "Update the data skill with [metrics/tables/terminology]", "Improve the [domain] reference" -> Loads existing skill, asks targeted questions, appends/updates reference files Use when data analysts want Claude to understand their company's specific data warehouse, terminology, metrics definitions, and common query patterns.

QA an analysis before sharing with stakeholders - methodology checks, accuracy verification, and bias detection. Use when reviewing an analysis for errors, checking for survivorship bias, validating aggregation logic, or preparing documentation for reproducibility.

Build self-contained interactive HTML dashboards with Chart.js, dropdown filters, and professional styling. Use when creating dashboards, building interactive reports, or generating shareable HTML files with charts and filters that work without a server.

Audit designs and code for WCAG 2.1 AA compliance. Trigger with "is this accessible", "accessibility check", "WCAG audit", "can screen readers use this", "color contrast", or when the user asks about making designs or code accessible to all users.

Refactor and reorganize codebases using SOLID principles, clean architecture, strict naming conventions, and defensive programming. Trigger with "refactor this codebase", "reorganize the code", "clean up the project structure", "fix the naming", "audit the codebase", "code organization", or when someone needs help restructuring, renaming, deduplicating, or improving code quality across a project.

Full-stack web development with Impeccable design language. Provides 17 design commands (audit, polish, normalize, animate, etc.) plus 6 enterprise skills (progress-modal, enterprise-webapp, frontend-refactor, codebase-refactor, readme-generator, refactoring-plan). Use this skill to get an overview of all available commands.

Systematic codebase refactoring and reorganization following SOLID principles, strict naming conventions (with banned patterns), DRY consolidation, defensive programming, mirrored frontend/backend structure, async error handling, and a phased refactoring process with deliverables checklist.

Full-stack enterprise web application development guide covering frontend architecture (React, design systems, state management, forms), backend patterns (layered architecture, REST API, validation), async processing, caching (cache-aside, write-through, write-behind), auth/authz (JWT, RBAC/ABAC), security, accessibility (WCAG 2.1 AA), performance, observability, testing strategy, error handling, database patterns, and CI/CD.

Refactor any frontend into a modern, production-grade interface using shadcn/ui, Tailwind CSS, and Radix UI. Covers design philosophy, token systems, component architecture (atomic design), layout patterns, progress feedback tiers, error/empty states, animation standards, dark mode, and a 10-step refactoring process with deliverables checklist.

Build a production-grade, accessible, reusable progress modal component for multi-step backend operations. Covers visual design, TypeScript interfaces, backend event contracts, cancellation architecture, accessibility (WCAG 2.1 AA), extensibility, and complete testing requirements.

Generate a complete, professional, enterprise-grade README.md with collapsible deep-dives, architecture diagrams, environment setup, API docs, data models, testing strategy, security, contributing guide, and troubleshooting. Uses expandable sections to keep high-level docs concise while detailed documentation is expandable.

Multi-phase refactoring and optimization plan with strict validation gates. Covers knowledge acquisition, API rationalization, project structure cleanup, code quality implementation (ruff, mypy, black), security and cost optimization, documentation, and emergency rollback protocols.

Save useful artifacts from the current conversation into the Clippy clipboard manager. Use when the user says "save that", "clip this", "add this to clippy", or asks to keep a command, code snippet, URL, or other text for later reuse.

Organize the user's Clippy clipboard history. Use when the user asks to clean up, sort, categorize, or triage their clipboard, or says things like "organize my clips", "my clipboard is a mess", or "file these clips into categories".