LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when the user wants a cybernetic flow design document for an interactive system. Not for implementing or deploying the system.
Use when a user wants a looser conceptual graph for exploratory work. Not for remote, credential, publish, deploy, or irreversible changes.
Use when a human has an approved delivery plan and wants the full chain run under phase gates. Not for planning, open-ended debugging, or single-step execution: use work directly.
Use when the user runs /autoplan on a plan or idea. Reviews, amends, and derives task IDs with a final human approval gate. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user says release this, publish this package, or cut a release for a changesets-based npm package. Not for non-npm packages or releases without a changesets workflow.
Use when the user requests axiom, axiom-mode, axiom-compact, formal-logic, or compact form. Not for changing code or remote state.
Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.
Use when writing reset-to-main startup code, vector tables, VTOR, .data/.bss init, stack setup, startup.s, or crt0 for Cortex-M/RISC-V. Not for the bootloader jump: use bootloaders-embedded.
Use when writing Bazel BUILD files with cc_library or cc_binary rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox debugging, or bazel query and cquery graphs.
Use when asked to validate a web app, CLI, API, or generated artifact against a source-blind behavior contract. Not for source or remote-system changes.
Use when building static archives with ar, stripping or converting binaries, mapping crash addresses with addr2line, or demangling C++ symbols. Not for ELF analysis: use elf-inspection.
Use when asked to determine what a change could break before it ships. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user names one book, course, paper, or source document and asks to distill it into a reusable skill. Not for a folder of sources: use map-corpus.
Use when writing a custom bootloader, jumping to application code, relocating VTOR, or implementing DFU/USB firmware update on Cortex-M. Not for reset-to-main: use baremetal-startup.
Use when C or C++ code needs memory-safety or undefined-behavior guarantees proved with CBMC, or ACSL contracts checked with Frama-C Eva or WP. Not for choosing the proof policy: use proof-driven.
Use when explaining branch predictors, mispredict penalties, speculative execution, Spectre or Meltdown mitigations, or branchless code. Not for pipeline stage theory: use cpu-pipelines-and-hazards.
Use when the user asks for branded or style-governed output. Not for remote, credential, publish, deploy, or irreversible changes.
Use when bloated code needs clean re-derivation, or the user says "this module is bloated" or "break it and rebuild". Not for untracked data or changes without VCS rollback.
Use when the user runs /browser-cookie-store to populate the session cookie store from installed browsers. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user runs /browser-qa for report-only QA results without entering a fix loop. Not for remote, credential, publish, deploy, or irreversible changes.
Fourteen posts of being wrong in production, compressed to checkboxes
Healthy nodes, a quiet network, 300 restarts in three days, and a latency budget measured in milliseconds
Discovery worked. Ping worked. Every TCP connection timed out, and later the tunnel only worked when someone had a terminal open.
Every VM came back. The cluster did not. Declarative systems converge on config, and the datapath isn't config.
A surprising share of AI-in-the-terminal failures aren't the AI. They're zsh, and a version of bash from 2006.
A Claude Code plugin turns standalone project configuration into a namespaced, installable extension that teams and communities can update as one unit.
None of the safety came from the model. It came from six boring habits.
Skills package instructions and references. Subagents run work in a separate context and return results. They solve different problems and can be composed deliberately.
Six hours in, one step left, everything green, and the incident that didn't happen
CLAUDE.md carries persistent project context. Skills load reusable procedures when relevant. Separating stable facts from task-specific workflows keeps both easier to maintain.
Twenty minutes recovering secrets that never existed, and the one sentence from a human that ended it
An API request routing a model's tool call through an approval gate to a remote MCP server
31 config keys, two audits, and why the first one was wrong in both directions
The official MCP Registry stores standardized server metadata rather than package code. Publishers verify a namespace, describe installation or remote access, and submit immutable versions.
Everyone looks at the Dockerfile. The file that actually leaked the key was the project file.
Remote MCP authorization uses established OAuth standards, but secure integration still requires issuer validation, least-privilege scopes, protected token handling, and server-side enforcement.
"Copy it over and switch the reference" is two steps, and the outage lives in the one nobody checks
stdio fits local processes and prototypes. Streamable HTTP fits hosted services and shared integrations. The right choice follows where the capability runs and who must reach it.
The most important rule wasn't about what I could change. It was about what I was allowed to display.
Tools perform operations, resources expose readable context, and prompts provide reusable templates. Choosing the correct primitive makes an MCP server easier to understand and govern.
/social
Social
Run an organic-social (ECHO) workflow: channel portfolio and voice dossiers, platform-native content and calendars, the social-quality gate with a pre-publish go/no-go, community/inbox/crisis operations, and the listening/SOV/dark-social measurement loop. Not sure? Use /aaron-marketing:auto.
/minutes-mcp-recall
Minutes mcp recall
Route meeting-recall questions to the right Minutes MCP tool.
/minutes-x1-closeout
Minutes x1 closeout
Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.
/minutes-mcp-recall
Minutes mcp recall
Route meeting-recall questions to the right Minutes MCP tool.
/minutes-x1-closeout
Minutes x1 closeout
Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.
/capacity
Capacity
`crabbox capacity [--json]` reports the authenticated owner's current admission
/code-review
Code review
Code review the current proposed code change
/merge-conflict
Merge conflict
Resolve a merge conflict
/pr-review
Pr review
Code review for pull request $1
/6hats
6hats
Six Thinking Hats Analysis
/README
README
Slash commands shipped by the plugin. Portable framework commands work in any Claude Code session; the workflow commands embed one author's personal setup and are opt-in - see [Adapting for your workflow](../README.md#adapting-for-your-workflow) before relying on them. Back to th
/fix-develop
fix-develop
Autonomous fix loop for failing CI on the repo's default branch
/fix-pr
fix-pr
Autonomous PR fixing loop - iterates on CI failures and review comments until green
/issues
issues
GitHub-issue marathon - triage open issues, then run agent-ready ones to merge with Agent Teams
/tm-marathon-config-example
tm-marathon-config-example
Example Marathon Configuration for CLAUDE.md - copy the section below into your project's CLAUDE.md
/tm
tm
Task Master - plan, start, review, and close
/understand
understand
Deep understanding mode (nemawashi) - exhaustive context-gathering before action
/burp-search
Burp search
Searches Burp Suite project files for security analysis
/ct-check
Ct check
Detects timing side-channels in cryptographic code
/diff-review
Diff review
Performs security-focused differential review of code changes
AI coding platform for teams
20 views 0 likesAI Multi-Agent Framework in .NET
14 views 0 likesProduction-ready code examples for Telnyx AI Communications Infrastructure — Voice AI, SMS, SIP, and IoT APIs
12 views 0 likesUltraGameStudio - AI coding agent for game development: engine workflows, gameplay code, and asset generation.
12 views 0 likes🦞 ResearchClawBench: Evaluating AI Agents for Automated Research from Re-Discovery to New-Discovery
12 views 0 likesThe context-aware model router that learns & adapts to your long-horizon coding agent workflows. Lightweight & extensible, works with any harnesses, any models,…
20 views 0 likesOpen-source sandboxes where coding agents build and deploy. Spin up isolated environments where Claude Code, Cursor, and other agents code and deploy software.
24 views 0 likesNative desktop UI for Claude Code with orchestration, streaming, background agents, and multi-provider support. Built with Tauri + React.
22 views 0 likesOpenCode mobile client via Telegram: run and monitor AI coding tasks from your phone while everything runs locally on your machine. Scheduled tasks support.
17 views 0 likesTerminal session manager for AI coding agents. One TUI for Claude, Gemini, OpenCode, Codex, and more.
23 views 0 likesExposes internet search tools for use by LLM-backed Assist in Home Assistant
15 views 0 likesTemplates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
8 views 0 likesVersus Incident is the self-hosted AI SRE agent. It learns what your system normally look like and escalates only what is new or unexpected issues — routing to…
14 views 0 likesBrowser-native side panel for Hermes Agent — connect web context to your local Hermes runtime.
6 views 0 likesAgentic-friendly CLI generator for APIs: turn Swagger, OpenAPI, and google.api.http protos into single-binary CLIs with catalogs and generated Skills.
10 views 0 likesOpen-source agent platform for Global × China enterprises — wire every system through one agent core. Self-hosted, any LLM.
7 views 0 likesOfficial python implementation of UTCP. UTCP is an open standard that lets AI agents call any API directly, without extra middleware.
11 views 0 likesAn agent small enough to run anywhere. A minimal agentic runtime in C — ~380 lines, 54KB binary, ~2MB RAM. A skill file + an LLM + a shell loop, no framework.
10 views 0 likesAgentiLoop Agent! An Autonomous Agentic Agent for Mac, and exclusive Apple only harnesss. Suppprtd automation, scripting, coding, build anything and more. Power…
10 views 0 likes微信公众号 AI 运营助手 | 选题、写稿、审稿、排版、配图、发布全流程 Skill,支持 OpenClaw / Claude Code / Cursor / Codex
17 views 0 likes