meta-suite

Design the context strategy for a project or working session — what knowledge to keep, where it lives, what to load when, how to compress it, and how to hand it off — so work stays grounded and compounds across sessions instead of starting cold every time. Use whenever someone wants their setup to remember and reuse context: "set up memory for this project", "what context should the agent have", "stop re-explaining everything", "organize my project knowledge", "design a CLAUDE.md / context file", "session handoff", "context engineering", "meta-context", or "/meta-context". Task-agnostic. Produces a durable substrate plan, a load/compression policy, a persistence & handoff policy, a discoverability index, and a starter substrate scaffold — in plain language. Do NOT use for a one-off question with no project or continuity.

Apply the discipline of craft — building things that survive contact with reality and stay easy to change — to any project, and emit a project-specific craft constitution plus a Definition of Done. Use whenever someone wants work done to a senior standard rather than a quick-and-dirty one: "do this properly", "make it production-grade", "what's the craft standard here", "give me a definition of done", "review this for quality", "clear not clever", "avoid slop", "meta-craft", or "/meta-craft". Task-agnostic — works for code, writing, design, analysis, or operations. Produces a tailored set of craft rules, a slop-vs-craft contrast for the work at hand, and an evidence-based completion checklist, in plain language. Do NOT use for genuinely disposable throwaway work where polish has no value.

Derive a typed, medium-specific DESIGN SCHEMA from any design brief, then execute it into an audited, self-contained artifact plus the design system that generates it. Use whenever the user wants to design — but design rigorously and reusably rather than by imitation — teaching material, slides, animations, web pages, dashboards, or adjacent media. Triggers include "meta-design", "/meta-design", "derive a design system for X", "design schema", "build the system then all the instances", "make a design generator not a one-off", "audited design with WCAG predicates", "tokens + component library + composed artifact", or any request to map a brief into a structure-preserving design meta-prompt. This skill operates one level up: it emits the medium-specific schema that designs the whole category the brief belongs to, executes it through a render-and-verify loop, and refines via critique edit-scripts until convergence. Do NOT use for a single ad-hoc visual with no reuse and no audit requirement.

Turn a minimal prompt — even one line — into a complete, WOW-grade deliverable bundle, right-sized to the domain and scope: grounded research, a project vision, a reusable meta-prompt, an execution plan, a grounded data model, and the production-quality artifacts that fit the work (interactive dashboards for a data/pitch/ops product, a report or doc site, an API/spec, a prototype — whatever the domain needs), plus an optional animated explainer with custom SVG. Research-grounded, mobile-ready, and adapts on call to different business/domain needs. Use when the user says meta-mvp, build an MVP or vision or prototype for something, go from this one-liner to something I can show, make me the full pitch, or spin up a new project for a client. Resolves its own scoping by default (never interrogates you — it studies the task's structure and, for high-stakes ambiguity, cross-checks with a small agent panel) and asks only if you opt in. Optionally composes meta-prompting, meta-planning, research-synthesis, user-resea

Generate a customized META-PLAN — a typed, example-agnostic planning scaffold — before any complete plan is written, for agentic tasks executed by one or many agents. Bridges /meta-prompting (generic tasks) to agentic planning (ultraplan-class capability). Use whenever the user wants to plan work that agents will execute, orchestrate subagents, decompose a complex build, decide what can run in parallel vs. in sequence, hand context-complete work packets to fresh agents, or asks for "meta-plan", "/meta-planning", "ultraplan", "plan the plan", "deep planning", "map the domain before planning", or "a plan another agent can execute without me". Also use when the input TASK is itself a meta-prompt (operating from meta-meta-prompt space), or when the user wants anti-slop quality gates and kaizen-style iterative execution baked into a plan. Do NOT use for simple single-agent to-do lists a direct plan would serve.

Generate a structured, example-agnostic META-PROMPT from any input task — a reusable "how to think" scaffold rather than worked examples. Use this whenever the user wants to design a prompt/system prompt for a CATEGORY of tasks, build a prompt template or reasoning harness, turn a one-off prompt into a reusable structure, create an "expert persona" system prompt with typed slots, or apply Meta Prompting / Recursive Meta Prompting (RMP). Triggers include "write a meta-prompt", "design a system prompt for X tasks", "make a reusable prompt template", "prompt that works for any category of problem", "structure the reasoning for this task", "self-improving prompt", "functor/typed-slot prompt", or any request to map an input task into a valid meta-prompt. This skill maps the meta-meta-prompt space: given a task, it emits the meta-prompt that solves the whole category.

Run a rigorous, task-agnostic research scaffold — decompose a question, fan out across sources, triage by credibility, cross-verify claims adversarially, and synthesize a cited answer with explicit confidence — then leave behind reusable knowledge atoms. Use whenever someone needs something investigated properly rather than answered off the cuff: "research X", "look into Y", "what's the latest on Z", "find sources for", "verify this claim", "compare these options with evidence", "deep dive", "meta-research", or "/meta-research". Task-agnostic across any subject. Produces a structured, sourced brief with confidence levels and open questions, plus 1-3 durable knowledge atoms for reuse. Do NOT use for questions answerable from common knowledge with no need for sources or verification.

Derive the right set of review lenses for any deliverable and run an adversarial, multi-perspective review that returns prioritized findings plus a reusable lesson — so the same problem gets caught automatically next time. Use whenever someone wants something checked rigorously before it ships: "review this", "what's wrong with this", "tear this apart", "is this ready", "red-team this", "find the problems", "critique my plan/code/doc/design", "meta-review", or "/meta-review". Task-agnostic — works for code, writing, plans, designs, analyses, or decisions. Produces P1/P2/P3 findings with rationale, the author's blind-spot probes, an ordered fix list, and a durable lesson atom. Do NOT use to generate new content from scratch (use the relevant maker skill first, then review its output).