Run any Skill in Manus with one click

c11-debug-windows

Stars40

Forks8

UpdatedMay 18, 2026 at 19:31

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`).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Stage-11-Agentics

Stage-11-Agentics/c11

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	c11-debug-windows
version	1
description	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`).

c11 Debug Windows

Developer-focused workflow for the c11 macOS app's Debug menu (DEBUG builds only). Covers existing debug windows and menu wiring — do not add a new utility/debug control window unless the user asks explicitly.

Workflow

Verify debug menu wiring in Sources/c11App.swift under CommandMenu("Debug").
- Menu path in app: Debug → Debug Windows → window entry.
- The Debug menu only exists in DEBUG builds (./scripts/reload.sh --tag ...).
- Release builds (reloadp.sh, reloads.sh) do not show this menu.
Keep these actions available in Menu("Debug Windows"):

Sidebar Debug…
Background Debug…
Menu Bar Extra Debug…
Open All Debug Windows

Reuse existing per-window copy buttons (Copy Config) in each debug window before adding new UI.
For one combined payload, run:

skills/c11-debug-windows/scripts/debug_windows_snapshot.sh --copy

After code edits, run build + tagged reload:

xcodebuild -project GhosttyTabs.xcodeproj -scheme c11 -configuration Debug -destination 'platform=macOS' build
./scripts/reload.sh --tag <tag>

Key Files

Sources/c11App.swift: Debug menu entries and debug window controllers/views.
Sources/AppDelegate.swift: Menu bar extra debug settings payload and defaults keys.

Script

scripts/debug_windows_snapshot.sh

Purpose:

Reads current debug-related defaults values.
Prints one combined snapshot for sidebar/background/menu bar extra.
Optionally copies it to clipboard.

Examples:

skills/c11-debug-windows/scripts/debug_windows_snapshot.sh
skills/c11-debug-windows/scripts/debug_windows_snapshot.sh --copy
skills/c11-debug-windows/scripts/debug_windows_snapshot.sh --domain <bundle-id> --copy

More from this repository

same repository

c11

Stage-11-Agentics/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.

2026-07-1440

lattice-orchestrator

Stage-11-Agentics/c11

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.

2026-07-1440

sounding

Stage-11-Agentics/c11

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.

2026-07-0340

resonance

Stage-11-Agentics/c11

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.

2026-07-0340

chord-architect

Stage-11-Agentics/c11

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.

2026-07-0240

chord-initiation

Stage-11-Agentics/c11

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.

2026-07-0240

name	c11-debug-windows
version	1
description	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`).

c11 Debug Windows

Workflow

Verify debug menu wiring in Sources/c11App.swift under CommandMenu("Debug").
- Menu path in app: Debug → Debug Windows → window entry.
- The Debug menu only exists in DEBUG builds (./scripts/reload.sh --tag ...).
- Release builds (reloadp.sh, reloads.sh) do not show this menu.
Keep these actions available in Menu("Debug Windows"):

Sidebar Debug…
Background Debug…
Menu Bar Extra Debug…
Open All Debug Windows

Reuse existing per-window copy buttons (Copy Config) in each debug window before adding new UI.
For one combined payload, run:

skills/c11-debug-windows/scripts/debug_windows_snapshot.sh --copy

After code edits, run build + tagged reload:

xcodebuild -project GhosttyTabs.xcodeproj -scheme c11 -configuration Debug -destination 'platform=macOS' build
./scripts/reload.sh --tag <tag>

Key Files

Sources/c11App.swift: Debug menu entries and debug window controllers/views.
Sources/AppDelegate.swift: Menu bar extra debug settings payload and defaults keys.

Script

scripts/debug_windows_snapshot.sh

Purpose:

Reads current debug-related defaults values.
Prints one combined snapshot for sidebar/background/menu bar extra.
Optionally copies it to clipboard.

Examples:

skills/c11-debug-windows/scripts/debug_windows_snapshot.sh
skills/c11-debug-windows/scripts/debug_windows_snapshot.sh --copy
skills/c11-debug-windows/scripts/debug_windows_snapshot.sh --domain <bundle-id> --copy