agent-skills

Route approved URLs, HTML, public Figma JSON, images, PDFs, PSD, AI, EPS, or PS through a configured any-to-design MCP; extract CSS-backed design systems, generate agent-ready artifacts, and bridge editable scenes to or from Figma. Use when users ask to convert a website or design source, reconstruct a design system, create editable Figma layers, compile design tokens or components for web, mobile, dashboards, presentations, PDFs, or documents, or explicitly use hosted code.to.design/anything.to.design APIs.

Single-vendor multi-agent coding pipeline with tiered model routing: your main session orchestrates and plans, a cheap Claude coder (e.g. Sonnet) implements standard items and a strong one (e.g. Opus) takes the hard ones, a strong-model subagent reviews adversarially, every finding passes an evidence-based TRIAGE before it can loop, and an orchestrator acceptance gate audits criteria-vs-evidence before merge. Use when the user wants an orchestrated implement→review→merge lifecycle WITHOUT a second vendor ("all-Claude", "anthropic-only", "no codex", or no Codex CLI installed), wants cost-tiered delegation (cheap coder on crisp briefs, strong coder on hard parts), or says "orchestrate this" in a Claude-only environment. Requires: git repo + a subagent-capable harness. If the OpenAI Codex CLI IS available and the work is high-stakes, prefer the sibling cross-vendor-orchestrator skill (uncorrelated review beats same-family review).

Maintain a personal knowledge base as an LLM Wiki (the Karpathy pattern): the human curates immutable raw sources and asks questions; the agent owns a wiki layer of summary/entity/concept pages, a catalog index, an append-only operation log, and a deterministic integrity gate that blocks bad commits. Use when the user wants a "second brain", personal wiki, or compounding notes vault; says "ingest this article/paper/link into my notes", "what does my knowledge base say about X", or "lint/health-check my vault"; or wants agent memory that a human can read and browse (Obsidian-compatible markdown + wikilinks). Includes the three operations (ingest / query / lint), page and provenance conventions, a runnable pre-commit check script, and scheduled-automation patterns.

Multi-agent coding pipeline with cross-vendor adversarial review: your main session orchestrates and plans, a Claude subagent (strongest coder, e.g. Opus) implements in an isolated tree, OpenAI Codex (GPT-5.6 Sol) adversarially reviews AND applies fix rounds, and nothing merges until an independent APPROVE plus an orchestrator merge gate that re-runs the artifact end to end. Use when the user wants orchestrated/delegated implementation with independent review ("orchestrate this", "cross-vendor review", "have GPT review Claude's code", "adversarial pipeline", "implement with review loop"), or hands over multi-file or risky work that deserves more than a single-model pass. Requires: git repo, a subagent-capable harness, and the OpenAI Codex CLI (`codex login` done). Not for trivial single-file edits.