plan-orchestrator

Route hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb table, intent classifier, and 3-stage routing pipeline.

apply-fix

Apply an approved Obelus plan file to the paper source.

judge

Blind evaluation pattern. Agent spawns an independent judge to evaluate an idea, plan, strategy, statement, or implementation. The judge sees the repo but not the conversation. Verdict goes to a shared markdown file.

blog

Full-lifecycle blog engine with 17 commands, 12 content templates, 5-category 100-point scoring, and 4 specialized agents. Optimized for Google rankings (December 2025 Core Update, E-E-A-T) and AI citations (GEO/AEO). Writes, rewrites, analyzes, outlines, audits, and repurposes blog content with answer-first formatting, sourced statistics, Pixabay/Unsplash/Pexels images, AI image generation via Gemini, built-in SVG chart generation, JSON-LD schema generation, and freshness signals. Supports any platform (WordPress, Next.js MDX, Hugo, Ghost, Astro, Jekyll, 11ty, Gatsby, HTML). Use when user says "blog", "write blog", "blog post", "blog strategy", "content brief", "editorial calendar", "analyze blog", "rewrite blog", "update blog", "blog SEO", "blog optimization", "content plan", "blog outline", "seo check", "schema markup", "repurpose", "geo audit", "blog audit", "citation readiness".

SAVORDISH

AI-powered recipe platform: 18 MCP tools for meal planning, grocery lists & Instacart.

codex-implementation-loop

Delegate implementation work to Codex (via the codex-companion runtime), then review its diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex to write code, mentions handing off / delegating implementation to Codex, asks to work through a plan or spec unit-by-unit with Codex doing the coding, or wants a review-and-merge loop wrapped around Codex output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: Codex runs in the real environment with effectively read-only git, must not be pointed at a full test suite by default, accepts only specific --effort values, and its self-report is a claim rather than evidence.

human-brainstorm

Brainstorm approaches for a ticket or topic before planning

cloud-sql-mysql-data

Use these skills when you need to explore your database schema, execute SQL queries to interact with your data, and inspect how MySQL plans to execute your statements.

technical-seo-audit

Comprehensive technical SEO audit skill that analyses crawl data to identify issues, prioritise actions by business impact, and produce a detailed report plus actionable spreadsheet. Use this skill whenever the user wants to: run a technical SEO audit, analyse a website's technical health, review crawl data from Screaming Frog or Sitebulb, crawl a site via API (Firecrawl or similar), find indexability or crawlability issues, check Core Web Vitals, audit structured data or schema markup, detect cannibalisation or thin content, review redirect chains, find orphan pages, assess site architecture, or produce a prioritised list of SEO fixes. Also trigger when the user uploads a CSV from any crawl tool and asks for analysis, mentions "technical SEO", "site audit", "crawl audit", "SEO health check", or wants to understand why pages are not ranking from a technical perspective. This skill handles everything from data ingestion through to a business-impact-prioritised action plan.

Theorist

You maintain a per-repo narrative document at `THEORY.MD` that captures the operating theory of the work being done. This is not a plan, not a log, not a task list. It is a living essay that describes *why* the work exists, *what* the systematic strategy is, and *how* the current approach connects t

page-generator — 페이지 코드 생성

스펙 문서 기반으로 코드를 생성합니다. 컨텍스트를 깔끔하게 유지하고 정확한 코드를 생성하기 위해 **한 번에 하나의 feature만 처리**합니다. "v1 visit-planning 구현해줘" 요청 시 사용합니다.

Schematic

Manage companies, plans, features, and billing through SchematicHQ

alpha-insights

Business Analyst Skill. Triggered when users ask about business analysis, industry research, competitive analysis, product analysis, business model analysis, business opportunity discovery, market entry strategy, investment decisions, strategic planning, due diligence, and other strategic topics. Delivers in-depth, decision-grade HTML research reports through a seven-stage workflow (Briefing → Framing → Planning → Research → Insights → Report → Iteration).

prompt-patterns

Practical prompt patterns and techniques for effective Claude Code usage. Reference when crafting prompts, planning workflows, or debugging interactions.

cinematic-ui

Design and build websites with film-inspired visual systems, director-driven art direction, storyboard-first layout planning, and cinematic motion. Use when the user asks for a cinematic site, movie-style landing page, director-inspired UI, film-noir, sci-fi, romance, thriller, action, animation, or a movie-like website aesthetic, including requests phrased in Chinese. Do not use for generic web design unless the user explicitly wants a film or director reference.

antipattern-detector

Detect common technical and organizational anti-patterns in proposals, architectures, and plans. Use when strategic-cto-mentor needs to identify red flags before they become problems.

gcal-api-research

Expert research tool for Google Calendar API implementations. PROACTIVELY use when (1) reviewing PRs adding calendar features, (2) planning new event/attendee/recurring event functionality, (3) investigating calendar API issues, (4) validating timezone handling or batch operations. Specializes in recurring events, timezone conversions, multi-calendar support, and edge case identification.

roadmap-planning-views

Creates and organizes focused planning views from a subset of roadmap tasks. Use when the user wants to build a task graph, analyze dependencies, identify ready or blocked work, or group near-term and future work into a focused planning workspace.

flutter-architecture-expert

Architecture guidance for Flutter apps using the flutter_it construction set (get_it, watch_it, command_it, listen_it). Covers Pragmatic Flutter Architecture (PFA) with Services/Managers/Views, feature-based project structure, manager pattern, proxy pattern with optimistic updates and override fields, DataRepository with reference counting, scoped services, widget granularity, testing, and best practices. Use when designing app architecture, structuring Flutter projects, implementing managers or proxies, or planning feature organization.

intent

Extract the underlying intent behind a request, issue, PR, or diff. Focus on problem and desired outcome; do not propose implementation, testing strategy, or rollout plans.

agent-handoff-planning

Structure a clean handoff between workflow agents with explicit outputs, open questions, and next-owner guidance.

product-architect

Complete product development system with 31 specialized agents and 23 frameworks. Use when user asks to build a product, write a PRD, create a roadmap, plan an MVP, design an app, do a security audit, create a financial model, plan hiring, launch a product, set up operations, prepare for IPO, or write a compliance policy. Also triggers on help me plan, product strategy, go-to-market, fundraising, pitch deck, unit economics, competitive analysis, user personas, sprint planning, SOP, checklist for, or how do I start a company. Do NOT use for general knowledge questions, coding tutorials, or creative writing unrelated to product development.

learning-goal

Guide the learner through a structured goal-setting exercise grounded in research on Mental Contrasting with Implementation Intentions (MCII). The exercise helps developers set concrete learning goals, visualize meaningful outcomes, anticipate realistic obstacles, and build if-then plans to overcome them.

claw-orchestrator

Manage persistent coding sessions across Claude Code, Codex, Gemini, and Cursor engines. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, or switching models/tools at runtime. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "switch model", "multi-agent", "coding session", "session inbox", "cursor agent".

detail

Internal skill for creating implementation plans. Invoked by /arc:implement, not directly. Creates detailed plans with exact file paths, test code, and TDD cycles.

daily-review

End of day review - compare planned vs actual, update task statuses. Part of chief-of-staff system.

planning-with-teams

Manus-style context engineering for Agent Teams. Coordinate multiple Claude Code instances with shared planning files. Use when complex tasks need parallel work (code review, debugging, feature development). Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.

Skill Plan: HA alignment improvements

Goal - Improve HA best-practice alignment and UX without introducing regressions.

adopt

Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.

better-harness

Use when /better-harness reviews the outer coding-agent Harness for lifecycle controls, repeated work, project feedback, agent assets, session outcomes, repair planning, durable reports, finding-bound fixes, or manual direct fixes. Invoke only via slash command.

accountant

Senior Accountant & Strategic CFO with 20+ years experience in tech sector. Use for tax planning, VAT/sales tax compliance, financial forecasting, contractor assessments, or accounting app logic design. Auto-triggers tax warnings and savings opportunities. Adapts to user's jurisdiction.

semantic-anchor-translator

Bi-directional translator between verbose descriptions and established terminology (semantic anchors). Use when (1) user describes a concept verbosely and you want to identify the precise term, or (2) user asks for methodology/approach and you want to suggest relevant anchors. Covers 50+ terms across testing, architecture, design principles, problem-solving, requirements, documentation, and strategic planning.

breaking-change-analysis

Assesses the impact of API changes before implementation to understand what code would break and plan appropriate migration paths. Use when removing methods, changing interfaces, or planning deprecations.

communication-style

Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.

askme

Verbalized Sampling (VS) protocol for deep intent exploration before planning. Use when starting ambiguous or complex tasks, when multiple interpretations exist, or when you need to explore diverse intent hypotheses and ask maximum clarifying questions before committing to an approach.

Auto Create PR (loop)

Turn a free-form brief into an execution plan, implement it **one commit per Step** in an isolated worktree, batch verification proofs at checkpoints, keep a live handoff doc and append-only notification log, and open a labeled PR against the configured base branch.

Brain-Jam Planning Methodology

isomux-grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

ielts-listening-review

Review IELTS Listening or dictation errors from transcripts, answers, and timestamps, then generate targeted replay drills and a validated Listening Error Notebook DOCX. Use when a learner asks why they missed listening answers, wants a dictation review, provides a transcript or answer key, or needs a focused listening repair plan.

lazyllm-skill

LazyLLM framework for building multi-agent AI applications. Use when task mentioned LazyLLM or AI program for: (1) Flow orchestration - linear, branching, parallel, loop workflows for complex data pipelines, (2) Model fine-tuning and acceleration - finetuning LLMs with LLaMA-Factory/Alpaca-LoRA/Collie and acceleration with vLLM/LMDeploy/LightLLM. Includes comprehensive code examples for all components, (3) RAG systems - knowledge-based QA with document retrieval, vectorization, and generation, (4) Agent development - single/multi-agent systems with tools, memory, planning, and web interfaces.

schematic

Reverse engineer a detailed product and technical specification document from a git branch's implementation. Use when: (1) a branch has shipped or is in-progress and needs documentation, (2) you need to understand what a branch does at product and architecture level, (3) onboarding to someone else's feature branch, (4) creating PR descriptions or design docs after the fact, (5) user asks to "analyze this branch", "write a spec from the code", or "document what this branch does". Produces a structured markdown spec covering problem statement, product requirements, architecture, technical design, file inventories, testing strategy, rollout plan, and risks.

Website Search

Write better IR reports, improve security writing, and plan cybersecurity product strategy.

graflow-workflow

Create Python workflow pipelines using Graflow with a structured plan-implement-review process. Use when building task graphs, parallel pipelines, LLM workflows, or any Graflow-based automation. Triggers on requests for "workflow", "pipeline", "task graph", "Graflow", or when user wants to build an automated data/AI pipeline.

agtx

Use when planning features, decomposing work into tasks, creating or managing tasks on a kanban board, coordinating parallel coding agent sessions across git worktrees, or when the user wants to sweep/push conversation results to the agtx board. Also use when asked about agtx setup, MCP configuration, or task workflow.

ImmoStage Virtual Staging

AI virtual staging for real estate — stage rooms, beautify floor plans, classify images.

cycle-plan

Plan Linear cycles using velocity analytics. Suggests scope based on historical capacity, identifies dependency risks, balances workload.

ads-creative-development

How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.

content-experimentation-best-practices

Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.

Compound Planning Analysis

You are conducting a comprehensive research analysis of a user's Plannotator plan archive. The goal: extract patterns from their denied plans and annotations, reduce them into actionable insights, and produce an elegant HTML dashboard report.

accessibility-guide

Use when planning, assessing, governing, or operating accessibility across web, mobile, desktop, documents, content, and service journeys. Triggers on WCAG version or level selection, applicable criteria, inclusive design, keyboard or assistive-technology evaluation, accessibility evidence, release gates, conformance claims, exceptions, remediation, monitoring, or exact-revision reassessment, even when the user doesn't say 'accessibility assurance'.