Menu
SkillsMP has collected 12 skills from Tzeusy/tze-hud. Open a skill to review its source and details.
Showing 12 of 12 collected skills.
Use when validating a cross-machine HUD flow where Butler deploys/runs the full Windows app over SSH+SCP (tailnet default host), then publishes configurable test messages to HUD zones via MCP `publish_to_zone`.
Use when an already-running LLM session should project itself onto the HUD, attach to a text-stream portal, publish live output, consume HUD input, or detach. Trigger phrases include project this session to the HUD, attach this agent to HUD, and check HUD…
CRITICAL — This skill provides the foundational doctrine for tze_hud, an agent-native presence engine. Every agent working in this repository MUST consult relevant soul doctrine before making architectural decisions, writing code, designing APIs, creating…
Use when publishing content to a user's HUD display, showing notifications or status on screen, sending text/color/alerts to tze_hud display zones, or giving an LLM visual presence on a user's GUI via MCP zone publishing.
Use when running deep performance and throughput investigations for HUD publishing paths (widgets/zones/tiles), including MCP HTTP benchmarks and gRPC bidi stream benchmarks. The canonical gRPC widget publish-load benchmark is…
Use when you need to deploy a freshly-built tze_hud.exe to the Windows host and launch the TRANSPARENT overlay HUD in one deterministic command — kill the stale instance, scp + checksum-verify the exe, launch it as a scheduled task (exe-direct, so overlay…
Use when an already-running Codex, Claude, opencode, or other LLM session should project itself onto the HUD, show its output or status on screen, attach to a text-stream portal, publish live transcript, poll HUD-originated operator input, acknowledge input,…
Load the project's engineering quality bar before writing, reviewing, or merging code. The about/craft-and-care/ directory defines testing standards, performance budgets, code quality conventions, review expectations, observability requirements, and…
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Load the project's topology maps to understand where components live, how they connect, and what boundaries exist. The about/lay-and-land/ directory contains component inventories, data flow diagrams, dependency maps, deployment topology, and operational…
Load tze_hud RFC design contracts to contextualize implementation work. The about/legends-and-lore/ directory contains 13 RFCs that define the wire-level contracts, data models, state machines, protobuf schemas, and quantitative budgets for the tze_hud…
Ground all tze_hud implementation work in the v1 MVP capability specifications (openspec/). The 13 capability specs are the single source of truth for feature planning and development. Use this skill: (1) before implementing any feature — to identify and load…