# Skill catalog

Every skill below is installed as `av:<name>`. The counts and descriptions come from the release itself, so this page cannot drift from what `ariadnev list` reports.

**103** skills in this release.

## ai-ml (3)

### `av:ai-artist`

Generate product mockups, marketing assets, brand visuals, and concept art via Nano Banana with 129 curated prompts. Mandatory validation interview refines style/mood/colors (use --skip to bypass). 3 modes: search, creative, wild. Styles: Ukiyo-e, Bento grid, cyberpunk, cinematic, vintage patent.

Arguments: `[concept] [--mode search\|creative\|wild\|all] [--provider auto\|google\|openrouter] [--skip]`

### `av:ai-multimodal`

Analyze and generate image, audio, video, and document content through the pinned Multix CLI and live provider catalogs. Use for vision analysis, transcription, OCR, design extraction, and multimodal generation.

Arguments: `[file-path] [prompt]`

### `av:google-adk-python`

Build AI agents with Google ADK Python. Multi-agent systems, A2A protocol, MCP tools, workflow agents, state/memory, callbacks/plugins, Vertex AI deployment, evaluation.

Arguments: `[agent or feature]`

## backend (3)

### `av:backend-development`

Build backends with Node.js, Python, Go (NestJS, FastAPI, Django). Use for REST/GraphQL/gRPC APIs, auth (OAuth, JWT), databases, microservices, security (OWASP), Docker/K8s.

Arguments: `[framework] [task]`

### `av:better-auth`

Add authentication with Better Auth (TypeScript). Use for email/password, OAuth providers (Google, GitHub), 2FA/MFA, passkeys/WebAuthn, sessions, RBAC, rate limiting.

Arguments: `[auth-method or feature]`

### `av:payment-integration`

Integrate payments with SePay (VietQR), Polar, and Stripe. Checkout, webhooks, subscriptions, QR codes, and multi-provider orders.

Arguments: `[provider] [task]`

## database (1)

### `av:databases`

Design schemas, write queries for MongoDB and PostgreSQL. Use for database design, SQL/NoSQL queries, aggregation pipelines, indexes, migrations, replication, performance optimization, psql CLI.

Arguments: `[query or schema task]`

## dev-tools (30)

### `av:agent-browser`

Browser and desktop automation through the agent-browser CLI. Use for long autonomous browsing, compact page snapshots, screenshots, form filling, login/test flows without real Chrome profile state, scraping, exploratory QA, cloud browsers, Electron apps, Slack automation, and bug hunts.

Arguments: `[url or task]`

### `av:agentize`

Convert a codebase, feature, or module into an AI-agent-friendly CLI and/or MCP server. Covers npm packaging, stdio/SSE/Streamable HTTP surfaces, credential resolution, docs, tests, CI, and a companion Claude skill for users who need an existing capability exposed as a reusable agent tool.

Arguments: `[feature-or-module] [--both\|--mcp\|--cli] [--auto\|--ask] [--yagni]`

### `av:chrome-profile`

Target a real Google Chrome profile for browser automation through Chrome DevTools MCP. Provides the chrome-profile CLI, profile discovery, live DevTools probing guidance, setup playbooks, and URL-anchor tab selection.

### `av:deep-swe`

Benchmark a coding model on DeepSWE through Pier and OpenRouter. Use when users ask to run DeepSWE, score a model, or verify coding-agent benchmark results.

Arguments: `<OpenRouter model slug>`

### `av:docs-seeker`

Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.

Arguments: `[library-name] [topic]`

### `av:excalidraw`

Create Excalidraw diagrams — architecture, data flow, workflows, system design. Use when user wants to visualize, diagram, draw architecture, show data flow, create flowcharts, map components, or export .excalidraw files to PNG/SVG. Supports two modes: live MCP canvas (real-time) or file-based JSON + Playwright rendering. Also supports zero-config codebase auto-diagramming — just say "diagram this repo" or "visualize the architecture".

### `av:find-skills`

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Arguments: `[capability or task description]`

### `av:git`

Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges, stacked PRs. Auto-splits commits by type/scope. Security scans for secrets.

Arguments: `cm\|cp\|pr\|merge\|merge-pr\|stack [args]`

### `av:github`

Operate and manage GitHub projects fluently with the gh CLI — create/update/close issues with evidence-backed dedup checks, manage labels, PRs (create, review, rebase, auto-merge), GitHub Projects, Actions CI/CD, and org/repo/environment/secret administration. Use whenever the user asks to file an issue, triage issues, manage a PR lifecycle, inspect CI runs, or administer repositories via gh.

Arguments: `<task description or issue/PR ref> [--interactive] [--advice]`

### `av:gkg`

Semantic code analysis with GitLab Knowledge Graph. Use for go-to-definition, find-usages, impact analysis, architecture visualization. Supports Ruby, Java, Kotlin, Python, TypeScript/JavaScript.

Arguments: `[symbol or query]`

### `av:goal-warmup`

Outcome-locked preflight before long-running /goal or autonomous runs. Interview to a user-approved Outcome Contract, plan without silent scope drift, contract-preserving review, whole-plan preflight matrix, then Ready/Blocked/Decision handoff. Never auto-starts /goal. Use for goal warmup, goal prepare, long-running goal prep, outcome lock, execution readiness.

Arguments: `"<goal>" [--fast]`

### `av:graphify`

Build queryable knowledge graphs from code, docs, papers, and images. Use for codebase understanding, architecture analysis, cross-file relationship discovery, token-efficient navigation.

Arguments: `[path] [--mcp\|--report\|--watch]`

### `av:handover`

Hand off in-progress work to a specifically selected coding agent by first capturing a portable handoff, then dispatching one single-job orchestration spec that points that agent at the captured artifact. Thin composition over av:handoff and av:orchestrate.

Arguments: `[task] --agent <id> [--cwd PATH] [--task TEXT] [--handoff PATH] [--model NAME] [--yes]`

### `av:issue-to-plan`

Turn a GitHub issue into an audited, validated implementation plan. Reads the issue, scouts the codebase, runs a hard brainstorm gate, and only then plans with mandatory --html --wiki, validate, and red-team, before pushing a plan branch and handing off on the issue. Use to convert a GitHub issue into a validated plan that is ready for plan audit.

Arguments: `<github-issue-url \| issue-number> [--repo owner/name] [--plan-ready-label <name>] [--decision-label <name>]`

### `av:llms`

Generate llms.txt files from docs or codebase scanning. Follows llmstxt.org spec. Use for LLM-friendly site indexes, documentation summaries, AI context optimization.

Arguments: `[path\|url] [--full] [--output path]`

### `av:mcp-builder`

Build MCP servers for LLM-external service integration. Use for FastMCP (Python), MCP SDK (Node/TypeScript), tool design, API integration, resource providers.

Arguments: `[service or API to integrate]`

### `av:mintlify`

Build and maintain Mintlify documentation sites. Covers docs.json, MDX components, navigation, page frontmatter, theming, OpenAPI/AsyncAPI, AI docs assets such as llms.txt and skill.md, deployment targets, and local validation CLI commands.

Arguments: `[task] [path]`

### `av:orchestrate`

Coordinate staged or parallel jobs across live-verified coding-agent runtimes and in-session subagents, using capability- and risk-based routing, worktree-isolated writes, resumable state, capture, safety gates, and independent arbiter review.

Arguments: `<job-spec.yaml \| task description \| --resume <run-dir>> [--yes] [--internal]`

### `av:plans-kanban`

Open the ariadnev plans dashboard in the CLI config UI. Use for plan kanban views, progress tracking, timeline checks, and quick navigation into plan files.

Arguments: `[deprecated flags are accepted with warnings]`

### `av:repomix`

Pack repositories into AI-friendly files with Repomix (XML, Markdown, plain text). Use for new-project onboarding, codebase snapshots, LLM context preparation, security audits, third-party library analysis.

Arguments: `[path] [--style xml\|markdown\|plain\|json]`

### `av:scout`

Fast codebase scouting using native search, optional Explore agents, and user-permitted OpenCode probes. Use for file discovery, task context gathering, and scoped searches across directories.

Arguments: `[search-target] [ext]`

### `av:ship`

Ship pipeline: merge main, test, review, commit, push, PR. Single command from feature branch to PR URL. Use for shipping official releases to main/master or beta releases to dev/beta branches.

Arguments: `[official\|beta] [--skip-tests] [--skip-review] [--skip-journal] [--skip-docs] [--social] [--yes-post] [--yes-post-private] [--dry-run]`

### `av:skill-creator`

Create or update Claude skills. Use for new skills, skill scripts, references, packaging, metadata validation, and extending Claude's capabilities.

Arguments: `[skill-name or description]`

### `av:team`

Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.

Arguments: `<template> <context> [--devs\|--researchers\|--reviewers N] [--delegate]`

### `av:tech-graph`

Generate production-quality SVG+PNG technical diagrams — architecture, data flow, flowchart, sequence, agent/memory, or concept maps — across 7 visual styles. Use when user wants "generate diagram", "draw diagram", "visualize", "architecture diagram", "flowchart", or any system/flow they want illustrated. Pairs with /av:preview --diagram for visual self-review and /av:mermaidjs-v11 for inline-doc diagrams; this skill is the publish-grade output mode.

Arguments: `[diagram-type or system description]`

### `av:use-mcp`

Discover and execute MCP server tools through runtime-native capabilities or deterministic direct scripts. Use for MCP integrations, controlled tool execution, capability discovery, and persistent tool catalogs.

Arguments: `[task]`

### `av:vibe`

Run the full vibe pipeline from request intake to PR readiness, with optional merge and post-merge CI convergence. Orchestrates worktree, plan, cook/fix, code-review, ship, and review-pr. Supports dual-stage beta-then-stable ships via --both and kongming advisory supervision via --advice. Use for GitHub issues, feature requests, bug fixes, or autonomous ship runs.

Arguments: `[--ship] [--beta] [--both] [--advice] <github-issue-url \| feature request>`

### `av:web-testing`

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

Arguments: `[test-type] [target]`

### `av:worktree`

Create, inspect, and clean isolated git worktrees. Use for feature isolation, worktree health audits, stale cleanup, and monorepo or submodule workflows.

Arguments: `[feature-description] OR [project] [feature]`

### `av:xia`

Extract, compare, port, or adapt a feature from a GitHub repository or local repo path into the current project. Use when the user wants to copy behavior from another repo, study how another codebase implements something, compare implementations, or rewrite a feature in the local stack. Triggers on: 'port from', 'copy from repo', 'like how X does it', 'clone feature from', 'adapt from', 'bring feature from', 'borrow from', 'take from repo', 'xia', 'xi a', 'xia feature'.

Arguments: `<github-url-or-owner/repo\|local-path> [feature] [--compare\|--copy\|--improve\|--port] [--auto\|--fast]`

## frameworks (4)

### `av:mobile-development`

Build mobile apps with React Native, Flutter, Swift/SwiftUI, Kotlin/Jetpack Compose. Use for iOS/Android, mobile UX, performance optimization, offline-first, app store deployment.

Arguments: `[platform] [feature]`

### `av:shopify`

Build Shopify apps, extensions, themes with Shopify CLI. Use for GraphQL/REST APIs, Polaris UI, Liquid templates, checkout customization, webhooks, billing integration.

Arguments: `[extension-type] [feature]`

### `av:tanstack`

Build with TanStack Start (full-stack React framework), TanStack Form (headless form management), and TanStack AI (AI streaming/chat). Use when creating TanStack projects, routes, server functions, forms, validation, or AI chat features.

Arguments: `[framework] [feature]`

### `av:web-frameworks`

Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.

Arguments: `[framework] [feature]`

## frontend (13)

### `av:design`

Design brand identity, logos, banners, posters, and visual assets. Use for brand systems, design tokens, corporate identity programs, event/editorial/marketing posters, and visual campaign assets. Not for UI code patterns.

Arguments: `[design-type] [context]`

### `av:frontend-design`

Create polished frontend interfaces from designs/screenshots/videos. Use for web components, 3D experiences, replicating UI designs, quick prototypes, immersive interfaces, avoiding AI slop.

### `av:frontend-development`

Build React/TypeScript frontends with modern patterns. Use for components, Suspense, lazy loading, useSuspenseQuery, MUI v7 styling, TanStack Router, performance optimization.

Arguments: `[component or feature]`

### `av:html-video`

Create local MP4 videos from HTML/CSS/JS templates with nexu-io/html-video. Covers source checkout setup, template discovery, studio customization, preview, and render verification.

Arguments: `[video brief, source URL, repo, template id, or project id]`

### `av:hyperframes`

Wrap HeyGen HyperFrames CLI for HTML-first programmatic video generation. Use for short vertical/social videos, product-launch clips, motion graphics rendered from HTML composition. See also the installed remotion skill for a React-based alternative.

Arguments: `[composition or command]`

### `av:react-best-practices`

Apply React and Next.js performance optimization patterns from Vercel Engineering. Use for component optimization, rendering performance, bundle analysis.

Arguments: `[component or pattern]`

### `av:remotion`

Build video content with Remotion in React. Use for programmatic video creation, animated sequences, data-driven video rendering.

Arguments: `[video or component]`

### `av:shader`

Write GLSL fragment shaders for procedural graphics. Topics: shapes (SDF), patterns, noise (Perlin/simplex/cellular), fBm, colors (HSB/RGB), matrices, gradients, animations. Use for generative art, textures, visual effects, WebGL, Three.js shaders.

Arguments: `[effect or pattern]`

### `av:stitch`

AI design generation with Google Stitch. Generate UI designs from text prompts, export Tailwind/HTML/DESIGN.md, orchestrate design-to-code pipeline. Use for rapid prototyping, UI generation, design exploration.

Arguments: `[design prompt or action]`

### `av:threejs`

Build 3D web experiences with Three.js. Use for WebGL/WebGPU scenes, GLTF models, animations, physics, VR/XR. Supports 556 searchable examples.

Arguments: `[3D scene or feature]`

### `av:ui-styling`

Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.

Arguments: `[component or layout]`

### `av:ui-ux-pro-max`

UI/UX design intelligence for web and mobile: style selection, color systems, typography, layout, accessibility, interaction states, responsive behavior, forms, charts, design systems, and code review across React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS.

### `av:web-design-guidelines`

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".

Arguments: `[file-or-pattern]`

## infrastructure (2)

### `av:deploy`

Deploy projects to any platform with auto-detection. Use when user says "deploy", "publish", "ship", "go live", "push to production", "host this app", or mentions any hosting platform (Vercel, Netlify, Cloudflare, Railway, Fly.io, Render, Heroku, TOSE, Github Pages, AWS, GCP, Digital Ocean, Vultr, Coolify, Dokploy). Auto-detects deployment target from config files and docs/deployment.md.

Arguments: `[platform] [environment]`

### `av:devops`

Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.

Arguments: `[platform] [task]`

## multimedia (1)

### `av:media-processing`

Process media with FFmpeg (video/audio), ImageMagick (images), RMBG (AI background removal). Use for encoding, format conversion, filters, thumbnails, batch processing, HLS/DASH streaming.

Arguments: `[input-file] [operation]`

## other (1)

### `av:show-off`

Create preference-aware self-contained HTML pages to showcase work. Use for demos, visual presentations, interactive showcases.

Arguments: `[markdown-or-prompt]`

## security (1)

### `av:cti-expert`

Analyze cyber threat intelligence and OSINT cases. Use for exposure reviews, domain recon, breach checks, username/email/phone research, image forensics, blockchain tracing, darknet checks, cloud tenant recon, vulnerability lookup, threat modeling, and structured reports.

Arguments: `[target] [--yolo] [--case\|--sweep\|--query\|--flow]`

## uncategorized (5)

### `av:common`

Shared utilities and conventions used across other skills. Internal — invoke only when another skill loads it.

### `av:document-skills`

Read, create, and edit Office documents (docx, pdf, pptx, xlsx). Use for tables, forms, slides, spreadsheets.

### `av:help`

Open the ariadnev help index. Use when users ask how to use av, what skills are available, or which workflow to run.

### `av:obsidian-second-brain-note`

Create professional Obsidian second-brain notes. Use when saving knowledge, summaries, concepts, lectures, images, or important info into an Obsidian vault with tags, links, MOCs, and clean folders.

### `av:pm`

Track plan progress and keep plan files truthful. Use for status checks, plan sync-back after work sessions, progress reports, or cross-session handoffs.

Arguments: `[plan dir] [--report]`

## utilities (39)

### `av:advise`

Interview-driven advisory skill. Analyzes a prompt or URL (GitHub issue, spec, doc), scouts the codebase, interviews the user one question at a time to reframe the problem into exact requirements and goals, then delivers honest advice: what to do, what to avoid, better alternatives, benefits and trade-offs. Use when the user asks for advice, a second opinion, a sanity check, requirement reframing before committing to a direction, or wants an existing plan or design pressure-tested (grilled) one question at a time.

Arguments: `[prompt-or-url] [--html] [--md] [--wiki] [--github] [--agent] [--yagni]`

### `av:ariadnev`

Task router for ariadnev installs. Classifies the task, activates the right installed skills, chains them into the shortest workflow that fits, and spawns installed subagents at defined trigger points to raise output quality. Use at the start of multi-step, multi-domain, or ambiguous work, or when unsure which skill or agent applies.

Arguments: `[task to route]`

### `av:ask`

Answer technical and architectural questions with expert analysis. Use for design decisions, best practices evaluation, solution comparison.

Arguments: `[technical-question] [--yagni]`

### `av:autoresearch`

Route bounded, goal-directed iteration to the ariadnev skill that owns the desired outcome.

### `av:bootstrap`

Bootstrap new projects with research, tech stack, design, planning, and implementation. Modes: full (default interactive), auto (explicit autonomous), fast (skip research), parallel (multi-agent).

Arguments: `[requirements] [--full\|--auto\|--fast\|--parallel] [--yagni] [--skip-journal]`

### `av:brainstorm`

Turn unclear intent into an accepted outcome and compare viable approaches before delivery.

Arguments: `[topic or problem] [--advice] [--html] [--yagni]`

### `av:code-review`

Review code quality with evidence-based rigor. Supports input modes: pending changes, PR number, commit hash, and codebase scan. Focuses on bugs, regressions, maintainability, reliability, and verification gaps.

Arguments: `[#PR \| COMMIT \| --pending \| codebase [parallel]] [--yagni]`

### `av:codex-goal`

Guide long-running Codex goal work with a verifiable stop condition. Use when users mention /goal, goal mode, durable objectives, or autonomous multi-turn Codex runs.

Arguments: `<objective \| goal draft>`

### `av:coding-level`

Set coding experience level for tailored output. Use for adjusting explanation depth, code complexity, and response format to user expertise.

Arguments: `[0-5]`

### `av:context-engineering`

Check context usage limits, monitor time remaining, optimize token consumption, debug context failures. Use when asking about context percentage, rate limits, usage warnings, context optimization, agent architectures, memory systems.

Arguments: `[topic or question]`

### `av:cook`

Implement features, plans, and fixes with structured workflow. Use for feature development, plan execution, code implementation pipelines.

Arguments: `[task\|plan-path] [--interactive\|--fast\|--parallel\|--auto\|--no-test] [--tdd] [--advice] [--yagni] [--skip-journal]`

### `av:copywriting`

Conversion copywriting formulas, headline templates, email copy patterns, landing page structures, CTA optimization, and writing style extraction. Activate for writing high-converting copy, crafting headlines, email campaigns, landing pages, or applying custom writing styles from assets/writing-styles/ directory.

Arguments: `[copy-type] [context]`

### `av:debug`

Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation, log analysis, CI/CD failures, database diagnostics, system investigation.

Arguments: `[error or issue description]`

### `av:docs`

Analyze a codebase and create, refresh, summarize, or audit project documentation without imposing a fixed docs layout, including authoring and optimizing the root CLAUDE.md/AGENTS.md agent context file.

Arguments: `init\|update\|summarize\|agent-context`

### `av:fable-thinking`

Reasoning protocol distilled from Claude Fable 5. Makes any model reason like Fable — evidence-grounded claims, multi-hypothesis diagnosis, concrete simulation, adversarial self-review, calibrated outcome-first delivery. Its never-skipped Floor check catches simple-looking trick questions models answer confidently wrong, and its Constraint Loop mechanically verifies hard output constraints (banned letters, exact counts, strict formats) that models otherwise rubber-stamp. Use for debugging, review, analysis, decisions, constrained writing, or any task where being right matters more than being fast.

Arguments: `[task or question to reason through]`

### `av:fix`

Fix bugs, errors, test failures, and CI/CD issues with intelligent routing. Use for type errors, lint issues, log errors, UI bugs, code problems.

Arguments: `[issue] --auto\|--review\|--quick\|--parallel [--advice] [--skip-journal]`

### `av:folder-context`

Create a compact subfolder CLAUDE.md and linked AGENTS.md for durable local conventions. Use when a folder needs agent context beyond the project root.

Arguments: `<target-folder>`

### `av:handoff`

Create a portable, redacted Markdown continuation contract that a fresh coding agent can consume to resume in-progress work safely. Use when switching sessions, models, or runtimes, or when preserving decisions, verification state, and blockers.

Arguments: `[task focus] [--output PATH] [--include-diff] [--include-status] [--force]`

### `av:interview-docs`

Extract a user's vision and decisions into durable project documents through a guided interview. Use for README, ADR, strategy, principles, and structured-doc authoring.

Arguments: `<vision \| document-path \| topic>`

### `av:journal`

Write chronological technical journals for session reflection and change analysis. Journals preserve work history; they do not replace current docs or ADRs.

Arguments: `[topic or reflection]`

### `av:loop`

Autonomous iterative optimization loop — run N iterations against a mechanical metric, learn from git history, auto-keep/discard changes. Use for improving measurable metrics (coverage, performance, bundle size, etc.) through repeated experimentation.

Arguments: `[Goal/Metric description] or inline config block`

### `av:markdown-novel-viewer`

View markdown files in a calm, book-like reader served via HTTP. Use for long-form content review — RFCs, runbooks, design docs, reports, specs, novels — anywhere you want a distraction-free reading mode in the browser.

Arguments: `[file-or-directory]`

### `av:mermaidjs-v11`

Create diagrams with Mermaid.js v11 syntax. Use for flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, state diagrams, architecture diagrams, timelines, user journeys.

Arguments: `[diagram-type or description]`

### `av:plan`

Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation, editorial self-contained HTML plan artifacts with --html, and AgentWiki publishing with --wiki.

Arguments: `[task] [--fast\|--hard\|--deep\|--parallel\|--two] [--tdd\|--no-tasks] [--html] [--github] [--wiki] [--advice] [--yagni] [--skip-journal] OR [archive\|red-team\|validate]`

### `av:predict`

5 expert personas debate proposed changes before implementation. Catches architectural, security, performance, and UX issues early. Use before major features or risky changes.

Arguments: `<feature description or change proposal> [--files <glob>] [--chain reason\|probe]`

### `av:preview`

View files or generate visual explanations, slides, and diagrams. Use for code walkthroughs, architecture visualization, HTML/Markdown presentations.

Arguments: `[path] OR [--html] --explain\|--slides\|--diagram\|--ascii [topic] OR --html --diff\|--plan-review\|--recap`

### `av:problem-solving`

Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.

Arguments: `[problem description]`

### `av:project-management`

Track progress, update plan statuses, coordinate runtime work, generate reports, and preserve cross-session continuity.

Arguments: `[task: status, hydrate, sync, report]`

### `av:project-organization`

Organize files, directories, and content structure in any project. Use when creating files, determining output paths, organizing existing assets, or standardizing project layout.

Arguments: `[directories or files to organize]`

### `av:research`

Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.

Arguments: `[topic] [--yagni]`

### `av:research-prompt`

Draft a self-contained research brief for a human or AI researcher. Use when users ask for a research prompt, research brief, or a deep-research task to hand off.

Arguments: `<research topic \| decision>`

### `av:retro`

Generate data-driven sprint retrospectives from any git history. Use for sprint reviews, commit analysis, code-health indicators, team-velocity reporting, and quarterly engineering reviews. Works on solo or team repos.

Arguments: `[timeframe] [--compare] [--team] [--format html\|md]`

### `av:review-pr`

Review a GitHub pull request thoroughly — analyze diff for correctness, security, breaking changes, code quality, and AI-slop patterns. Supports --fix to auto-remediate findings, --reply to post the review back to GitHub via the gh CLI as a formal review, and --merge to merge a ready PR and watch post-merge CI to green.

Arguments: `<PR number or URL> [--fix] [--reply] [--merge] [--advice]`

### `av:scenario`

Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use for pre-implementation risk discovery, QA planning, regression design, and iterative saturation when coverage must be exhaustive.

Arguments: `<file path or feature description> [--iterations N] [--saturation]`

### `av:security`

STRIDE + OWASP-based security audit with optional red-team persona discovery loop and auto-fix. Scans code for vulnerabilities from multiple attacker perspectives (auth attacker, supply chain, insider, infrastructure), categorizes by severity, and can iteratively fix findings using av:autoresearch pattern.

Arguments: `<scope glob or 'full'> [--fix] [--red-team] [--iterations N]`

### `av:security-scan`

Scan codebase for security vulnerabilities, hardcoded secrets, dependency issues, and OWASP patterns. Use when asked to 'security scan', 'check for secrets', 'audit security', or before major releases.

Arguments: `[scope] [--secrets-only] [--deps-only] [--full]`

### `av:sequential-thinking`

Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.

Arguments: `[problem to analyze step-by-step]`

### `av:test`

Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.

Arguments: `[context] OR ui [url]`

### `av:watzup`

Generate short handoff reports from Git branches, remote refs, worktrees, unfinished plans, and roadmap docs. Surfaces priority-ranked next steps with checkbox progress and rationale. Use when the user asks what's in flight, wants progress/next steps, is in a fresh worktree or detached checkout, or needs end-of-session status.