Create and manage parallel AI development sessions in isolated Git worktrees. TRIGGERS - Use this skill when user says: - Creating: "create a kild", "spin up kilds", "new kild for", "create worktrees" - Listing: "list kilds", "show kilds", "active kilds", "kilds list" - Status: "kild status", "check kild", "kild health", "how are my kilds" - Navigation: "cd to kild", "go to kild", "path to kild", "open in editor", "edit kild", "code kild" - Lifecycle: "stop kild", "open kild", "destroy kild", "complete kild", "clean up kilds" - Fleet: "inject", "inbox", "prime", "fleet status", "send task to kild" - Output: "list as json", "json output", "verbose mode" KILD creates isolated Git worktrees where AI agents work independently without affecting your main branch. Each kild gets its own terminal window, port range, and process tracking. IMPORTANT: Always use defaults from user's config. Only specify --agent, --terminal, or --flags when the user explicitly requests a different value. EXAMPLES User says "Create a
KILD wave planner — analyzes issue backlog and fleet state to recommend parallel kild waves. TRIGGERS - Use this skill when user says: - "plan a wave", "wave plan", "what should we work on next" - "plan the next batch", "queue up work", "what can run in parallel" - "wave planner", "/kild-wave-planner"
Honryū — KILD fleet supervisor. Invoke to start, assess, or direct the fleet brain. TRIGGERS - Use this skill when user says: - "start my honryu", "launch the brain", "start the kild orchestrator", "initialize honryu" - "start my fleet manager", "boot honryu", "wake up the brain", "start honryu for me" - "assess the fleet", "what's the fleet doing", "fleet status" - "plan the next wave", "what should we work on next", "spin up more kilds" - "start the next wave", "execute the wave", "launch the wave", "run the wave plan" - "merge queue", "what's ready to merge", "land the PRs" - "direct the workers", "what should <branch> do next" - "honryu", "brain", "ask the brain"
Capture screenshots and inspect native application windows for visual verification. TRIGGERS - Use this skill when user says: - "peek at X", "peek on X", "use kild-peek" - "take a screenshot of", "capture the window" - "look at the UI", "take a look at the window", "see what X looks like" - "visual check", "verify the UI shows", "check the window" - "compare screenshots", "diff the images" - "assert the window", "validate the UI" - "click on X", "interact with the UI", "press the button" - "list elements", "find element", "inspect the UI elements" kild-peek captures screenshots of native macOS applications, compares images, runs assertions on UI state, and interacts with UI elements. Use it to visually verify what applications look like, validate UI state, and automate UI interactions during development. IMPORTANT: Always list windows first to identify the correct target. Save screenshots to the scratchpad directory for easy cleanup.
GPUI framework patterns for building native UI. Use when implementing views, components, elements, actions, async tasks, entity management, focus handling, or any UI work in the kild-ui crate. Covers Render, Element, Entity, async, focus, actions, styling, and the gpui-component library.
Use when: User wants to run Archon CLI workflows OR set up Archon for the first time. Triggers (workflows): "use archon to", "run archon", "archon workflow", "use archon for", "have archon", "let archon", "ask archon to". Triggers (setup): "set up archon", "install archon", "how to use archon", "configure archon", "archon setup", "get started with archon". Triggers (config): "change my archon config", "modify archon config", "archon config", "change archon settings", "update my config", "help me change my config", "edit archon config", "archon configuration". Capability: Runs AI workflows in isolated git worktrees for parallel development. NOT for: Direct Claude Code work - only for delegating to Archon CLI.