Tzeusy

@Tzeusy

GitHub

93 Skills

0 Total Stars

March 2026 Joined

Public Skills

generate-grafana-dashboards

by Tzeusy

Generate or update Grafana dashboard JSONs for the Butlers application. Use when asked to create, refresh, or expand Grafana dashboards. Queries live Prometheus and Tempo to discover actual metric/trace data before generating any JSONs. Knows where instrumentation source code lives, where dashboards are stored, and the OTel→Prometheus naming conventions for this project.

API Dev 0 3mo ago

progress-digest

by Tzeusy

Generate weekly learning progress digests from analytics snapshots and recent trends.

Code Review 0 3mo ago

eod-tomorrow-prep

by Tzeusy

Daily tomorrow-prep briefing, review tomorrow's calendar and fold in today's cross-butler specialist highlights into a multi-domain preparation summary sent via Telegram (sent at the end of the day, 23:00 SGT, to prepare for the day ahead)

Automation 0 3mo ago

butler-memory

by Tzeusy

Memory classification framework — entity resolution, permanence levels, tagging strategy, and extraction philosophy

Finance 0 4mo ago

signal-extraction

by Tzeusy

Multi-butler signal extraction contract for switchboard ingestion. Produces strict JSON extraction arrays that map directly to target butler tool calls.

Processing 0 4mo ago

butler-test-condensation

by 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 pruning targets, or rewriting tests to be contract-driven. Triggers on test reduction, test pruning, test consolidation, or condensation tasks for this project. Also use when a fresh session needs to assess test health, create new condensation beads, or resume in-progress condensation work.

Testing 0 4mo ago

fact-extraction

by Tzeusy

7-step Conversational Fact Extraction Pipeline — resolve person mentions to entities, apply disambiguation policy, extract and store facts, log interactions, and update domain records. Routes registry-relational edges to relationship_assert_fact(); reserves memory_store_fact() for narrative edges. Includes question answering flow and 8 complete examples.

Design 0 4mo ago

bill-reminder

by Tzeusy

Workflow for reviewing, triaging, and managing upcoming bills and payment reminders

Automation 0 4mo ago

update-architectural-diagrams

by Tzeusy

Regenerate the project's Excalidraw architecture documentation by surveying the current codebase, diffing against existing diagrams in docs/diagrams/, and emitting a beads epic whose children each instruct a worker to produce or update one diagram via /excalidraw-diagram. Use when architecture has changed, new butlers or modules have been added, or the user asks to refresh, regenerate, or update architectural diagrams.

Design 0 4mo ago

reconcile-spec-to-project

by Tzeusy

Deep-dive reconciliation between OpenSpec specifications and the actual codebase implementation. Identifies feature gaps in both directions: (1) implemented but not documented in specs — creates new spec documents, (2) specified but not implemented — creates beads issues via /beads-writer. Use when auditing project completeness, after a milestone, before a release, or when the user asks to reconcile, audit, or compare specs vs. implementation.

Code Gen 0 4mo ago

craft-and-care

by Tzeusy

MANDATORY for all non-trivial implementation work. Use when implementing, reviewing, or validating changes in this repository and the question is how the work should be executed well. Load before choosing test scope, deciding whether specs or manifesto updates are required, running quality gates, assessing change hygiene, or checking whether a change meets the Butlers engineering bar.

Automation 0 4mo ago

legends-and-lore

by Tzeusy

Load design contracts (RFCs) to contextualize implementation work. The about/legends-and-lore/ directory contains numbered RFCs defining wire-level contracts, data models, state machines, and integration points. Consult relevant RFCs before implementing features, modifying protocols, designing state machines, or resolving cross-subsystem integration questions. Selectively load ONLY the RFCs relevant to your current task.

Database 0 4mo ago

lay-and-land

by Tzeusy

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, and deployment topology. Consult before: adding new components, modifying integration points, changing deployment, or when unsure where something lives in the system. Use proactively when onboarding or when work crosses component boundaries.

File Ops 0 4mo ago

heart-and-soul

by Tzeusy

CRITICAL -- Load the project's foundational doctrine before making architectural decisions, writing code, designing APIs, creating tests, or proposing features. The about/heart-and-soul/ directory contains prime directives: what Butlers is, what it is not, non-negotiable rules, and v1 scope. Selectively load ONLY the documents relevant to your current task. Use proactively at the start of substantive work, when making design decisions, or when unsure about project conventions.

Automation 0 4mo ago

relationship-extractor

by Tzeusy

Extract structured relationship data from incoming messages. Teaches the Switchboard's runtime instance how to identify contacts, interactions, life events, dates, facts, sentiments, gifts, and loans — and produce structured JSON that maps directly to Relationship butler tools.

Code Gen 0 4mo ago

investigation-notes

by Tzeusy

Emit a structured investigation_notes.json artifact at terminal state. Load when you are an investigation agent finishing a fix or unfixable verdict. The dispatcher reads this file before worktree teardown and persists it into qa_findings.structured_evidence.investigation_notes.

CLI Tools 0 5mo ago