skizzles

Coordinate work through a bounded native Codex MultiAgentV2 task graph. Read before the first subagent spawn or orchestration action in a task. Use for complexity-aware model dispatch, behavioral roles, task messaging, worker-to-worker ownership delegation, dependency fan-out, review loops, goal checkpoints, warm handoffs, synchronization, and recovery. Do not use for routine single-agent work or communication across unrelated top-level Desktop tasks.

Choose, install, diagnose, update, or uninstall Skizzles from its canonical repository. Use when a user wants plain Codex skills, the complete Skizzles plugin harness, source-linked hot reload, an isolated copied install, optional Container Lab compatibility checks, or help making a new task pick up an installed version.

Use Skizzles' bundled Container Lab launcher to create, run attached commands in, inspect, synchronize, and destroy disposable Docker Compose labs with isolated Git workspaces. Use when Docker/Compose isolation, reproducible experiments, or guarded file synchronization would help.

Stage, inspect, and validate the Skizzles versioned plugin from its canonical source tree. Use when changing plugin inputs, checking generated-plugin drift, preparing a reviewable package checkpoint, or diagnosing packaging validation failures.

Prepare a safe, versioned Skizzles release from canonical source. Use when an approved release version must be aligned across package metadata, rebuilt into the plugin, validated, and handed off for a separate tag, publication, or live cutover decision.

Preserve authentication, authorization, session, permission, access-control, and availability semantics. Use when changing login/session flows, permission checks, API auth errors, gated UI, role-based access, token refresh, logout behavior, unavailable states, or security-sensitive user access paths.

Profile and reduce Rust/Cargo build times through measured, behavior-preserving optimization campaigns. Use when a Rust workspace has slow cold builds, slow warm rebuilds, giant crates, duplicate dependencies, expensive macros/codegen, poor Cargo parallelism, or when asked to apply the fasterthanli.me Rust build profiling methodology, split crates for build speed, inspect cargo timings, or run a long-running /goal-driven build optimization effort.

Author and maintain repo-local Codex project tooling. Use when configuring project-level .codex/config.toml, hooks, subagent roles under .codex/agents, repo-local MCP servers, Bun/FastMCP scaffolding, paired MCP skills, trusted-project behavior, linked worktree behavior, or repo-specific Codex automation conventions.

Convert user intent, approved plans, and subagent handoffs into explicit completion contracts. Use when Codex is planning implementation, spawning subagents, setting or refining a /goal, defining acceptance criteria, avoiding scope shrink, deciding fan-out boundaries, or reviewing whether a claimed result satisfies the requested outcome.

Apply a coding version of the scientific method when first-answer bias could produce a superficial or inferior result. Use for competing architectures, major refactors, performance work, UI/product alternatives, migrations, risky changes, and bug diagnosis or repair when the cause or durable fix is uncertain, multiple causal paths fit the evidence, recurrence or systemic risk matters, or an earlier fix failed review. Skip only when reproduction and evidence isolate one straightforward mechanical correction.

Require screenshot-backed proof and production UI quality for frontend, product UI, Flutter, web, design-system, and UX work. Use when implementing, reviewing, or accepting visual changes, layout changes, design polish, responsive screens, component styling, empty/loading/error states, or user-facing copy.

Pilot local iOS Simulators for UI/design/QA work on macOS, especially Flutter or native iOS visual verification. Use explicitly when Codex needs to list booted simulators, launch or stop a simulator app, run or hot reload Flutter through a background unified_exec terminal, inspect accessibility hierarchy with idb, tap/type/swipe, capture screenshots, crop screenshots, or provide visual proof from an iOS Simulator.

Remove obsolete behavior, tooling, docs, config, tests, scripts, flags, generated artifacts, wrappers, aliases, compatibility paths, and tombstones cleanly. Use when replacing an old system, deleting old harnesses, renaming/removing entrypoints, migrating configs, or preventing legacy code from surviving as disabled or documented leftovers.

Preserve Flutter Rinf architecture boundaries in projects that use Rinf. Use when changing Flutter UI, Dart state, Rust backend logic, signals/messages, generated Rinf files, networking, persistence, or cross-boundary data flow in a Rinf-based app.