c11

c11 is a native macOS terminal multiplexer. Load this skill anytime any of the following attributes are hit: (1) session is inside c11 (`C11_SHELL_INTEGRATION=1`), (2) working with panes, surfaces, workspaces, splits, or tabs, (3) sending text or commands to another surface, (4) launching or orchestrating sub-agents, (5) declaring agent identity, setting title/description, or reporting sidebar status, (6) using the embedded browser or markdown surfaces, (7) any c11-specific command or troubleshooting question. When in doubt, load it.

Stage 4 of the Tone workflow and Stage 11's build engine — takes a complete build contract (SPEC.md, EVALUATION.md, BUILDPLAN.md, and where one exists a binding prototype + DESIGN.md), turns it into Lattice tickets, dispatches a delegator fleet that produces open PRs, and terminally audits the result against a spec its builders did not write. No planning interview — if contract artifacts are missing, run the Tone stage that produces them (tone-architect for spec/plan, tone-initiation for a raw idea). Invoke when the operator says "orchestrate this," "kick off the orchestration," "run the orchestrator," "set up an overnight run," or hands over a finished build contract.

The idea-generation sequence upstream of the Tone/Chord workflows — the operator brings a direction (a market, a hunch, a theme); Sounding arms it with evidence and explores it in dialogue, producing reads — concrete, carded takes on the direction — each ending in a try/not-try call. Where Tone begins with "a raw idea and a client," Sounding is where raw ideas come from. Invoke on "sounding," "take soundings," "sound this," "let's explore ideas," "what should we build next," or whenever the operator brings a direction that isn't yet an idea. Standalone; "try" reads feed venture-partner and the Tone/Chord commissions; composes with Scanner (/scan) for app-level evidence.

Stage 11's marketing-capability program — a working session that turns marketing intent into budgeted, pre-registered experiments and accumulates the verdicts into a playbook of plays with real numbers. Demand generation is the unsolved half of the autonomous-business loop; Resonance reps it daily the way agentic coding was repped in 2023–24. Invoke on "resonance," "make this resonate," "marketing," "get users for this," "demand probe," "test demand," or whenever marketing needs to produce a verdict, not a vibe. Standalone; its probe instruments serve Sounding "try" reads; its playbook feeds the distribution skill (per-project channel planning), which feeds every channel result back.

Stage 3 of the Chord workflow (chord-initiation → chord-prototype → chord-architect → lattice-orchestrator ×K) — codifies K loved designs into K build contracts under one shared rulebook, authors the pre-registered resolution book, then conducts the ×K build (fresh lattice-orchestrator run per candidate) through to the handoff of K live, instrumented probes. Inherits tone-architect by reference. Invoke when the operator says "chord architect," "codify the portfolio," "spec the candidates," or when a portfolio of loved prototypes needs its build contracts — and stay seated: this skill also owns the conductor's build-and-handoff playbook.

Stage 1 of the Chord workflow (chord-initiation → chord-prototype → chord-architect → lattice-orchestrator ×K) — Tone in plural: the portfolio initiation of one problem with several complete answers. Commission a portfolio, research to enumerate, generate ~N candidate bets, voice K uncorrelated ones with a champion each, and write the two-tier philosophy & stories. Inherits tone-initiation by reference. Invoke when the operator says "chord," "chord this," "portfolio this," "build several answers," or when a keystone fork resists resolution by research and dialogue.

Stage 2 of the Chord workflow (chord-initiation → chord-prototype → chord-architect → lattice-orchestrator ×K) — prototype discovery per candidate, run by each candidate's champion and iterated on a portfolio-wide board until the operator loves every surviving candidate's design. Inherits tone-prototype by reference; divergence was already spent at the candidate level, so takes are dialed down and iteration is batched. Invoke when the operator says "chord prototype," "prototype the portfolio," or when a voiced portfolio (PORTFOLIO.md with champions assigned) needs its designs discovered.

Distribution planning and execution for anything shipped — audience definition, channels classified by who can run them (agent-executable / operator-assisted / operator-only), credibility assets, instrumented funnels, and an execution cadence. Code without distribution is code nobody can use. Invoke on "distribution," "go-to-market," "GTM," "how does this reach users," "market this," or "nobody's using it." Standalone; composed once per project by Tone (from the architect stage onward), per candidate by Chord's champions, and retrofittable onto anything already shipped.

Stage 3 of the Tone workflow (tone-initiation → tone-prototype → tone-architect → lattice-orchestrator) — the technical-architecture dialogue that translates a validated prototype, philosophy, and stories into the build contract: EVALUATION.md, SPEC.md, and BUILDPLAN.md. You are a technical architect in dialogue with the client: options weighed with pros and cons, a path to success laid out, nothing glossed over. Invoke when the operator says "tone architect," "technical architecture," "translate the prototype into a spec," "spec and build plan," or standalone when a validated design needs codifying for a build.

Stage 1 of the Tone workflow (tone-initiation → tone-prototype → tone-architect → lattice-orchestrator) — the client-facing initiation of a project: commission, landscape research, idea refinement, economics, philosophy, and user stories. You are initiating a project with a client — part interviewer, part researcher, part product thinker; the largest, most dialogue-heavy stage of the pipeline. Invoke when the operator says "tone," "start a new project," "project initiation," "new project from scratch," or brings a raw idea at its very beginning. Each Tone stage is independently invocable when its inputs already exist.

Stage 2 of the Tone workflow (tone-initiation → tone-prototype → tone-architect → lattice-orchestrator) — prototype discovery: exploration directions pinned down with the client (by default three, each resting on a different core assumption), a clickable HTML prototype per direction on realistic mock data, iterated with the client until they love it. The full design, UX and UI, is discovered here; the build later reproduces it one-to-one. Invoke when the operator says "tone prototype," "prototype this," "prototype discovery," or standalone whenever a scoped idea needs its design discovered — even outside a full Tone run.

A venture-partner interview that pressure-tests an idea or business against evidence — demand reality, status-quo economics, the narrowest wedge — ending in signed premises. Direct to the point of discomfort, never sycophantic. Invoke on "venture partner," "pressure-test this idea," "office hours," "grill me on this," or before committing to build anything with a P&L. Standalone; composes naturally with the Tone workflow (run before or during initiation).

Hot-reload workflow for c11 development: initial setup, tagged Debug builds via reload.sh, Release variants, the debug event log, and the tagged-build reporting format. Use when building, rebuilding, or launching c11 during development.

Prepare and ship a c11 release end-to-end: choose the next version, curate user-facing changelog entries, bump versions, open and monitor a release PR, merge, tag, and verify published artifacts. Use when asked to cut, prepare, publish, or tag a new release.

Browser automation for c11 browser surfaces (WKWebView-backed). Use to open sites, interact with pages, wait for state changes, extract data, save/load auth state, and validate UI changes without leaving c11. Prefer this over Chrome MCP whenever c11 is running.

Manage c11 debug windows and related debug menu wiring for Sidebar Debug, Background Debug, and Menu Bar Extra Debug. Use this when the user asks to open/tune these debug controls, add or adjust Debug menu entries, or capture/copy a combined debug config snapshot. Applies to the c11 macOS app (binary `c11`).

Open markdown files in a c11 markdown surface with live reload. Use when you need to display plans, documentation, or notes alongside terminals and browser surfaces with rich rendering (headings, code blocks, tables, lists, Mermaid diagrams). Prefer this over external viewers when c11 is running.