Tzeusy

Guide for discovering, analyzing, and pruning the Butlers test suite. Use when working on test condensation beads (Phase 1 epic bu-rhztl and Phase 2 epic bu-hg8rl both CLOSED; Phase 3 maintenance cycle underway 2026-06-21), assessing test bloat, identifying…

Generate a weekly home energy digest with trends, top consumers, and recommendations.

Orchestrate a UX redesign of a Butlers dashboard page (or sub-page set) using /project-direction as the spec+beads engine, with redesign-specific upfront phases for vision capture, asset ingestion, impact analysis, backend-contract derivation, LLM-cost…

When and how to ask another butler's domain a question via delegate_ask, and how to answer one routed to you

When and how to ask another butler's domain a question via delegate_ask, and how to answer one routed to you

Education-butler response-mode selection and worked examples for teaching, quizzes, progress, reviews, and topic abandonment.

Education domain memory taxonomy for concept entity resolution, predicates, permanence, tags, and example fact patterns.

Finance-butler response-mode selection and worked examples for transactions, bills, subscriptions, and finance questions.

Use for project-level engineering governance in any repository — bootstrap or audit the knowledge architecture (doctrine, specs, topology, standards), concretize a feature request into a spec delta, amend a spec found wrong mid-implementation, reconcile specs…

Use when analyzing or bootstrapping the five-pillar knowledge architecture of a software project: about/heart-and-soul (doctrine), about/legends-and-lore (RFCs/design contracts), about/lay-and-land (topology), about/craft-and-care (execution-quality…

Use for engineering-quality work on any change or codebase — holding an implementation or review to the engineering quality bar, code readability, test-suite rigor, module boundaries and dependency chains, diagnosing hard bugs and flaky failures to root…

Use when judging or improving the quality of tests — whether they assert behavior, cover edge and failure paths, protect against regressions, and stay trustworthy — in a diff, test suite, or review; also suite-level health: tier structure…

Use when auditing or designing module boundaries and dependency chains — dependency direction, layering, cycles, public surface area, and third-party dependency admission or upgrades — in a codebase, package, or proposed change.

Use when implementing or reviewing any non-trivial change and you need the canonical engineering quality bar — default biases, definition of done, and reviewable expectations — or when authoring a project's about/craft-and-care pillar that should reference…

Use for hygiene of this machine's AI-tooling harness — the ~/.dotfiles repo, the ai-bootstrap skills tree, and the installed tool homes (~/.claude, ~/.codex, ~/.gemini): auditing real skill usage from transcripts, archiving unused skills, reviewing dotfiles…

Use to re-run the harness's snapshot/mirror flows so installed state matches version-controlled source — skill symlinks into ~/.claude, ~/.codex, ~/.gemini tool homes, git submodule pointers, and shell plugin checkouts. Use after restructuring skills, when…

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…

Use for engineering-quality work on any change or codebase — holding an implementation or review to the engineering quality bar, code readability, test-suite rigor, module boundaries and dependency chains, diagnosing hard bugs and flaky failures to root…

Use when auditing or designing module boundaries and dependency chains — dependency direction, layering, cycles, public surface area, and third-party dependency admission or upgrades — in a codebase, package, or proposed change.

Use when judging or improving the quality of tests — whether they assert behavior, cover edge and failure paths, protect against regressions, and stay trustworthy — in a diff, test suite, or review; also suite-level health: tier structure…

CRITICAL — Load Syzygy's adopted doctrine before making architectural decisions, drafting RFCs or specs, proposing features, or rendering any project truth. Doctrine lives at .syzygy/governance/doctrine/ (NOT about/ — this repo uses the .syzygy canon): rules…

Use when the task is about technical contracts, subsystem design decisions, mutation boundaries, or RFC-level architecture.

Use when the task is about requirements, acceptance criteria, capability scope, or implementation sequencing from OpenSpec changes.

Use when the task is about product thesis, scope boundaries, non-goals, doctrine principles, or non-negotiable rules.

Use when the task is about system boundaries, runtime data flow, deployment topology, or component integration shape.