LLM Mart Basic
@llm-mart · Joined Jun 2026
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
Apply when you write, change, or keep a test. Identify a relevant defect and check that the test detects it. Assert the required result or observable effect, including absence when the contract requires it.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritat
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leav
/lineage-discovery
Lineage discovery
Discover testnet↔mainnet subnet lineage from repo configs and open a PR for review (pass --dry-run to report only)
/capture
capture
Triage raw inbox notes into reviewed repository destinations without deleting their sources.
/clean-ai-writing
clean-ai-writing
Audit and rewrite content to remove AI writing patterns
/content-shipped
content-shipped
Log a completed piece of content to content/log.md after the user confirms it was published.
/dream-apply
dream-apply
Validate a dream artifact, review each proposal, and apply only individually accepted changes.
/dream
dream
Run a curator pass against the validated memory directory and produce a proposal artifact.
/end
end
End a session — log what happened, update state and the decision log, propose memory updates, and check for uncommitted or unpushed work
/find-context
find-context
Find relevant context files by topic. Use when you need to load files for a topic without a slash command, or when a task spans multiple domains.
/migrate-gemini
migrate-gemini
Inventory and migrate selected Gemini CLI workflows with dry-run review and parity checks.
/mine-gemini-workflows
mine-gemini-workflows
Find repeated workflows in selected Gemini CLI sessions and draft portable skills after review.
/reconcile
reconcile
Scan multi-session drift and offer individually reviewed fixes only after explicit approval.
/recover
recover
Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.
/setup
setup
Guided onboarding or import for durable workspace context
/start
start
Start a session — load state files, flag staleness, and give a briefing on current priorities, deadlines, and blockers
/today
today
Create a morning heartbeat from repository state and update the local heartbeat log.
/update
update
Mid-session checkpoint — append progress to today's session log and update state files if a priority shifted, without ending the session
/distribution-audit
distribution-audit
Maintainer-only. Find every file that would newly ship to adopters, classify each one against the written distribution-boundary categories, default to withhold on no clean match, and ask the maintainer only where the taxonomy does not settle it. Drives the release CLI, which refuses to produce a manifest until every shipping file has an answer.
/gaia-audit
gaia-audit
Audit memory, wiki, and auto-loaded files for duplication, conflicting instructions, and stale content. The default path researches, then asks you a single Apply / Discuss / Decline question; on Apply it applies the report, files any out-of-scope problem as a tech-debt issue, then commits, opens a PR, and merges it on a main-branch run like /update-deps. Pass --apply to re-run the apply-and-publish stage against the most recent report.
/gaia-debt
gaia-debt
Fix the tech-debt backlog, a single issue or a recommended related batch, highest severity then oldest first, on a fresh isolated branch through the audit gate, closing the issue(s) on merge. Pass `list` to see the ordered backlog, `why <issue-number>` to explain the recommendation, or a bare `<issue-number>` to fix that issue directly.
/gaia-fitness
gaia-fitness
Health-check and auto-heal this project's Claude integration, triage, heal, verify, and report an F-to-A+ grade.
Your Personal AI Assistant; easy to install, deploy on your own machine or on the cloud; supports multiple chat apps with easily extensible capabilities.
16 views 0 likesAgent OS: the agent gets smarter on its own. We just hold the line: the grading command and expected result never make it into the success contract we hand it.…
17 views 0 likesCurated systems, benchmarks, and papers etc. on memory for LLMs/MLLMs --- long-term context, retrieval, and reasoning.
14 views 0 likes:memo: Vimlike Modal Text Editor in Rust
27 views 0 likesCI-native security testing for MCP servers. Attack simulation, schema drift detection, and health scoring before agents depend on them.
16 views 0 likesHermes Agent memory plugin/provider for scope-aware recall, SQLite truth, LanceDB semantic search, and hybrid retrieval.
15 views 0 likesFor You Agent——AI 时代的个人随身数字人格。把你的模型、AI 账号、技能、提示词和工作方式,带到每一个 AI 工具里。
12 views 0 likesA coding agent: give it a prompt and it reads, writes, runs commands, and searches code in a loop until the work is done, using native tool-calling across OpenA…
14 views 0 likesA secure persistent personal agent server in Rust. One binary, sandboxed execution, multi-provider LLMs, voice, memory, Telegram, WhatsApp, Discord, Teams, and…
14 views 0 likesSelf-evolving agent: grows skill tree from 3.3K-line seed, achieving full system control with 6x less token consumption
14 views 0 likesDeepSeek Harness Desktop (dsh-desktop). EAC: Embracing All Creation (揽尽万象). Bundled Node.js runtime with full dsh-CLI kernel, one-click startup, 10 built-in UI…
14 views 0 likesSee your agent think. Zero-config observability & governance for 26 AI agent runtimes: Claude Code, Cursor, OpenAI Codex, GitHub Copilot, Gemini CLI, Cline, Ope…
13 views 0 likesSave 94% on AI coding tokens. Index your codebase, agents search instead of reading files. Works with Claude Code, Codex, Copilot, Cursor, Gemini CLI. Local MCP…
12 views 0 likesYet another coding agent harness, lightweight and written in go.
12 views 0 likesa coding Agent from pi. ∞ providers, sub-agents, hashline edits, and a permission gate
12 views 0 likesOmnigent is an open-source AI agent framework and meta-harness: orchestrate Claude Code, Codex, Cursor, Pi, and custom agents — swap harnesses without rewriting…
25 views 0 likes🧠 Leon is your open-source personal assistant.
12 views 0 likesThe Station, an open-world multi-agent environment that models a miniature scientific ecosystem.
14 views 0 likesThe Frontend Stack for Agents & Generative UI. React, Angular, Mobile, Slack, and more. Makers of the AG-UI Protocol
23 views 0 likesVelaTerm = iTerm2 + Codex, The Best Terminal for AI Coding
21 views 0 likes