mithraeums

@mithraeums source repo

9 skills
0 followers
9 hours ago last updated

▌
Sync · mithraeums
Propagate one change to every place that references it — code, docs, version strings, config, sibling repos, JSON/YAML data. Use after a rename, a version bump, an API or contract change, or any edit where "did I update everywhere?" is a real question. Turns the error-prone manual sweep into a deliberate pass. Host-agnostic. Trigger: /sync, "update everywhere", "did I get all of them", "rename X to Y", "keep in sync".

0
installs
▌
Brief · mithraeums
Token-lean output mode. Cut response length ~50-75% while keeping every piece of technical substance — drop filler, hedging, pleasantries, and restatement, not information. Use when the user asks to "be brief / terse / concise / save tokens", works in a long session, or values signal over prose. Host-agnostic. Trigger: /brief, "be brief", "less tokens", "terse", "tl;dr mode".

0
installs
▌
Scope · mithraeums
Turn a vague request into a scoped plan before building — explicit goal, explicit non-goals, the smallest viable first step. Use at the start of any non-trivial task, when a request is ambiguous or could balloon, or when you catch yourself about to over-build. Stops scope creep and wasted work. Host-agnostic. Trigger: /scope, "plan this", "before we build", "what's the smallest version", "is this in scope".

0
installs
▌
Memory · mithraeums
Persistent file-based memory for any agent. Keep durable facts across sessions in a MEMORY.md index + one-fact-per-file, with rules for what to save, how to recall, and how to avoid stale/duplicate memories. Use when the user shares a durable preference, a project constraint, or says "remember this" / "from now on" — or at session start to recall. Host-agnostic; no database, just markdown. Trigger: /memory, "remember", "don't forget", "save this", "what do you know about".

0
installs
▌
Handoff · mithraeums
Write a START-HERE state doc so the next session (you, later, or a teammate) resumes in seconds instead of re-deriving everything. Use at session end, before a long pause, when context is about to compact, or when the user says "wrap up / save state / where were we". Captures done / next / gotchas — not a transcript. Host-agnostic. Trigger: /handoff, "wrap up", "save state", "where were we", "hand off", "session notes".

0
installs
▌
Release · mithraeums
Cut a clean release: bump the version consistently everywhere, write the changelog entry, and generate a push-order checklist — including multi-repo suites where order matters. Use when the user says "ship it / cut a release / bump the version / push everything", or is juggling several repos. Host-agnostic. Trigger: /release, "cut a release", "bump version", "push order", "ship it", "tag".

0
installs
▌
Corp · mithraeums
A company in a folder — a referential multi-agent org for any AI coding assistant. Loads CEO, DEV, DESIGN, QA, and ARCH agents from markdown on demand. Use when a task spans multiple domains, before building anything non-trivial, or to decide which agent handles a given task. Host-agnostic (Claude / Codex / Cursor / Gemini / hako / any). Trigger: /corp, "which agent", "load corp", "who handles X".

0
installs
▌
Corp Init · mithraeums
Interactive setup wizard for corp. Fills in the [PROJECT] block in .claude/CLAUDE.md and the entity/contract section in .claude/agents/ARCH.md by asking the user questions. Run once when dropping corp into a new repo. Trigger: /corp:init, "set up corp", "configure corp", "corp setup".

0
installs
▌
Corp Add Agent · mithraeums
Scaffolds a new corp agent file and wires it into the org. Use when a domain grows large enough to deserve its own agent (auth, infra, ML, data pipeline, payments, etc.). Trigger: /corp:add-agent, "add agent", "new agent", "create agent for X".

0
installs

9 published skills