copilot-tui-harness

Guide development of the Copilot SDK TUI Harness with layered, event-driven architecture.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/jim0thy/copilot-anvil --skill copilot-tui-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-tui-harness
Source: https://github.com/jim0thy/copilot-anvil/tree/main/.agents/skills/copilot-tui-harness
Command: npx skills add https://github.com/jim0thy/copilot-anvil --skill copilot-tui-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert guidance and architectural blueprints for developing and maintaining the Copilot SDK TUI Harness project, ensuring robust, layered, and event-driven terminal user interfaces.

Core Features & Use Cases

  • Architectural Guidance: Understand the strict separation of UI, Harness, and Adapter layers.
  • Event System Mastery: Learn to leverage the event-driven communication model for seamless interaction.
  • Plugin Development: Implement and integrate new features via the plugin system.
  • Use Case: A developer needs to add a new pane to the TUI to display real-time Git diffs. This Skill provides the exact file structure, event types, and patterns to follow for successful integration.

Quick Start

Use the copilot-tui-harness skill to help with adding a new pane to the TUI.

Frequently Asked Questions about copilot-tui-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new pane to a TypeScript TUI using an event-driven architecture?

Adding a new pane to a TypeScript TUI requires following strict separation between UI, Harness, and Adapter layers, leveraging the event-driven communication model to route updates. This Skill provides the exact file structure, event types, and patterns for seamless integration.

What is the correct way to manage event flow in a layered terminal user interface?

Managing event flow in a layered terminal user interface relies on an event-driven communication model ensuring strict separation between UI, Harness, and Adapter layers. This architecture enables seamless interaction and prevents direct coupling between components.

How do I develop plugins for a Copilot SDK terminal UI harness?

Developing plugins for a Copilot SDK terminal UI harness involves implementing new features via the integrated plugin system while adhering to strict architectural separation principles. This ensures plugins interact correctly through the event-driven framework.

Does the Copilot TUI Harness support integrating external SDKs via an adapter layer?

Yes, the Copilot TUI Harness supports integrating external SDKs through its Adapter layer, which maintains strict separation from the UI and Harness layers. This design enables SDK integration without disrupting the core event-driven framework.

What's the best way to debug UI issues in an event-driven TypeScript TUI harness?

Debugging UI issues in an event-driven TypeScript TUI harness requires tracing events across the strictly separated UI, Harness, and Adapter layers. This Skill provides expert architectural knowledge to identify event flow breakdowns and resolve integration errors.