polaris

Initialize or improve CLAUDE.md for the current project. If no CLAUDE.md exists, creates one with the full 12-rule behavioral baseline + project-specific context. If CLAUDE.md already exists, audits it and fills any gaps.

Use for systematic codebase audits and large-scale refactoring. Conducts a full four-category analysis (security, performance, architecture, directory structure) before making any changes, then presents findings with severity ratings and a fix plan. Best triggered when the user says "analyze the project", "audit the codebase", "find problems", or "refactor the project". Examples: <example>user: "See this project, analyze it thoroughly and report security loopholes, performance bottlenecks, architecture flaws, and directory structure flaws" assistant: "I'll use the audit-refactor agent to conduct a full four-category analysis."</example> <example>user: "The codebase has gotten messy, do a full audit" assistant: "Dispatching audit-refactor agent for a structured analysis before any changes."</example>

Use for a post-generation quality pass before PR review, or after AI-assisted coding sessions. Applies a comprehensive checklist covering TypeScript, architecture, naming, slop removal, inline type extraction, and import hygiene. Examples: <example>user: "Clean up the code I just wrote for the dashboard feature" assistant: "I'll use the code-cleanup agent to apply full quality standards to the recent changes."</example> <example>user: "Review this before I push" assistant: "Running code-cleanup agent across the changed files."</example>

Use when starting a new feature, component, page, or API endpoint in a Next.js project. Implements via strict data-flow sequence with version-aware docs fetching. Examples: <example>user: "Build the user profile settings page" assistant: "I'll use the feature-builder agent to implement this following the correct data flow."</example> <example>user: "Add a create order endpoint with optimistic updates" assistant: "Dispatching feature-builder — will fetch current Next.js/React 19 docs, then implement from types through to UI."</example>

Use to remove AI-generated artifacts from code: redundant comments, type escape hatches, abnormal defensive checks, debug logging, inline complex types, process journals, and all other patterns inconsistent with how a careful human developer writes code. Examples: <example>user: "Remove all the AI slop from this PR" assistant: "I'll use the slop-remover agent to systematically identify and remove all AI-generated artifacts."</example> <example>user: "The code has too many comments explaining obvious things" assistant: "Dispatching slop-remover — will scan for all slop patterns and remove them."</example> <example>user: "Remove AI code slop" assistant: "Using slop-remover to clean up the codebase."</example>

Use when writing browser automation, E2E tests, or interaction validation with Playwright; when the user asks to test a UI flow, automate a browser action, check responsive layouts, validate form submissions, or verify link integrity. Requires Playwright installed in the project: npm install -D @playwright/test && npx playwright install.

Use when creating a new UI component, page, screen, or layout from scratch; building a landing page, dashboard, SaaS UI, portfolio, or any greenfield frontend interface. Do NOT use for auditing or polishing existing UI — use ui-polish for that. After completing UI generation, always invoke ui-polish for a quality pass.

Use when reviewing, auditing, critiquing, polishing, or improving existing UI; checking a component for design issues; iterating on styling quality. Also runs automatically as the second step of the ui-new pipeline after generating new UI. Commands: audit, polish, critique, shape, craft, animate, harden, and 16 more.

Use when creating interactive prototypes, HTML slide decks, motion graphics, GIF or MP4 animations, or infographics; when presenting design directions or comparing design variations; when the user wants to visualize ideas without writing production code. Do NOT use for standard component or page development — use ui-new for that.

1 hook across 1 event