Establish frontend design context before implementation, including creator intent and preserve-theirs constraints. Use when a project lacks a clear PRODUCT.md or DESIGN.md, when the model needs to distinguish brand surfaces from product UI, or when design direction keeps drifting because audience, intent, register…
Create, inspect, and apply DESIGN.md brand kits for brand-aware frontend work. Use when building or reviewing landing pages, frontend UI, pitch pages, redesigns, client audits, brand-matched prototypes, or researching a potential client/company where website identity, design tokens, typography, layout, components, or…
Debug coding failures through reproduction, ranked hypotheses, narrow fixes, and verification. Use when a bug, regression, flaky test, performance failure, or inconsistent behavior is broken, slow, throwing, or hard to reproduce and the task needs disciplined diagnosis instead of guessed fixes.
Stress-test a plan, feature, or design against the repo's existing docs, domain language, ADRs, and context files. Use when a task is ambiguous, terminology is fuzzy, architecture trade-offs matter, or the user wants alignment before implementation. Ask one question at a time, inspect the codebase when answers are…
Evaluate whether Doc-to-LoRA is the right path for turning documents into parametric memory, and guide a safe proof-of-concept before investing in a full plugin or training pipeline. Use when a user wants to internalize long documents, reduce repeated context costs, compare Doc-to-LoRA against RAG or long-context…
Keep repo-local agent context accurate after code and workflow changes. Use when docs/ai, AGENTS.md, runbooks, or context entrypoints have drifted from the codebase, after major feature work, after architecture changes, or when an agent keeps rediscovering the same repo facts. Refresh durable context, split groups…
Plan and run large Codex tasks with compact dynamic workflow packets, risk gates, integration, and verification. Use when the user explicitly asks for dynamic workflows, packets, subagents, swarm, orchestration, long-running audits, multi-track coding/research work, job or client search agent design, migrations…
Shape editorial and reading-first surfaces with strong hierarchy, readable measure, and disciplined media rhythm. Use for articles, guides, books, blog indexes, featured/recent cards, and other longform or text-heavy public surfaces.
Research and answer evidence-sensitive questions with source, date, unit, and operand discipline. Use for web research, PDF/document QA, policy or finance facts, tables, time series, calculations from retrieved evidence, exact-answer extraction, and any task where wrong source selection, stale facts, nearby table…
Use files as durable context without polluting the live prompt. Apply when a task needs scratchpads, plan persistence, retained outputs, proposal folders, handoffs, or repo-local context that agents can discover and audit later.
Build or review gesture-driven web interactions such as drag, swipe, sheets, carousels, and draggable panels. Use when pointer tracking, interruption, velocity handoff, momentum projection, hysteresis, rubber-banding, spatial continuity, or motion/transparency/contrast fallbacks materially affect the interaction.
Build or improve frontend pages, apps, landing pages, pitch pages, redesigns, dashboards, and prototypes with strong hierarchy, responsive layout, real visual assets, ergonomic controls, and verification. Use when frontend quality, brand fit, product clarity, or design implementation matters.
Set and review a bounded, creator-aware visual direction for marketing, editorial, portfolio, and brand-forward frontend work. Use when a surface needs an explicit design read, creator-intent check, calibrated composition/motion/density, preservation-first redesign, layout-rhythm review, or…
Create or review minimal Git-native project context using only adr, rfc, rule, spec, plan, rnd, and cpat documents; human-gated draft/accepted/rejected lifecycle; implements, dependson, extends, and related relations; and evidence-backed code-change patterns. Use when a project needs durable decisions, specifications…
Compile a raw agent goal into a bounded loop harness before execution. Use before launching long Codex, Claude Code, MiMo Code, or local-LLM coding loops when the goal needs clearer stop rules, verification rubric, judge prompt, budget policy, retry limits, memory policy, and portable YAML/JSON/Mermaid artifacts.
Reduce repository-reading token waste by navigating code through symbols, entrypoints, dependencies, changed files, and blast radius instead of broad whole-tree or whole-file reading. Use on medium-to-large repos, PR reviews, architecture questions, onboarding, debugging across modules, or long-running audits.
Create compact handoff documents for another agent, session, or human to continue work. Use when a task is long-running, context is about to compact, work must pause, an audit needs resumable state, or the user asks for a handoff, continuation note, checkpoint, or next-session brief.
Create a self-contained HTML brief for plans, status updates, PR summaries, incident notes, research explainers, or other structured narrative deliverables. Use when the user wants a polished standalone artifact instead of markdown, slides, or a full frontend.
Create a self-contained HTML artifact for architecture, stack, and system-flow explanation using SVG-first diagrams and minimal prose. Use when the user needs a standalone visual deliverable that makes a system, request path, ownership map, or execution flow click quickly.
Generate diverse hypotheses, explanations, or solution candidates before evidence review. Use for research, incident analysis, market or product reasoning, adversarial review, and SkillOpt proposal generation when first-answer mode collapse would hide alternatives.
Route an idea, vague feature request, or agent-built product change through delivery gates from intent to release. Use when work needs more discipline than a readiness check: clarify the spec, slice the work, protect architecture boundaries, gather proof, converge through review, and prepare release without turning…
Enrich a Markdown knowledge base with durable tags, source provenance, existing-note links, and reviewed wiki synthesis while keeping raw notes read-only by default. Use when organizing Obsidian-style notes, refreshing generated wikis, or preparing source-grounded context for agents.
Restructure agent-facing docs so the always-loaded context stays small and the rest is loaded on demand. Use when a repo has bloated AGENTS.md or CLAUDE-style docs, too many always-loaded notes, stale session history, oversized runbooks, or high startup token waste for coding agents.
Select and tune a local LLM inference engine for the user's hardware. Use when setting up or auditing local/private model serving, choosing between MLX, llama.cpp, Ollama, and vLLM, estimating model fit, deciding cache/storage policy, tuning batching and KV cache flags, running smoke benchmarks, or exposing an…