LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when implementing a multi-file change, building a feature from a breakdown, or writing a large amount of code. Not for a single settled ticket: use work.
Use when writing or restructuring code, before adding a helper, wrapper, config key, or dependency, or when the user asks for minimal or DRY code. Not for performance tuning: use optimize.
Use when asked to audit comments in code files and propose structural replacements or deletions with per-candidate approval. Not for deterministic commented-out-code removal: use deslop.
Use when a human says "overhaul", "rebuild this subsystem", or "rewrite it from scratch". Not for thin-slice features: use incremental-implementation. Not for root-cause repair: use strike-the-root.
Use when asked to optimize code, speed up a path, reduce allocations, repair a regression, or profile a target. Not for remote, credential, publish, deploy, or irreversible changes.
Use when a request names a working principle (subtract before you add, idempotent operations, never block on the human) or asks which principle applies. Not for running a repair: use strike-the-root.
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly. Not for additive refactors that must preserve the old path.
Use when a trusted bug or performance report needs reproduction and fix. Not for untrusted reports or scope beyond the named feature.
Use when an implementation has more workarounds than structure and another patch will not pay. Not for in-place re-derivation: use breaking-driven. Not for one-artifact rewrites: use rewrite-clean-v0.
Use when the user says "simplify this diff" or asks for a compression pass over a change-set. Not for dead-code sweeps: use deslop.
Use when an exact symbol, path, entrypoint, or line range can bound a focused code question or patch proposal under a fixed source budget. Not for source changes or broad repository exploration.
Use when writing or verifying framework-specific code, boilerplate, or a documented, correct implementation. Not for remote, credential, publish, deploy, or irreversible changes.
Use when a feature begins or specs are checked in: author or update behavioral specs and keep them current with what ships. Not for producing the initial approved spec and plan: use spec-driven.
Use when a bug, failure, flake, regression, review finding, or ticket needs the core fixed so it cannot recur. Not for greenfield features: use tdd. Not for style-only review or typo-class one-liners.
Use when the user says greenfield this or rescue this codebase, names a field (dark, red, blue, or brown), or diagnoses a subsystem. Not for specs: use to-spec. Not for remote or irreversible changes.
Use when an abstraction leak must be sealed as a module seam, configuration option, or explicit override, or exposed as a named boundary. Not for detecting concealment patterns: use no-hide.
Use when the user says "audit my code", "find all the bugs", "review until clean", or "grill my changes". Not for remote, credential, or irreversible changes.
Use when asked to audit an agent or AI feature for agentic-experience quality (AX review, agent-native critique, trust question). Not for source or remote-system changes.
Use when asked to determine what a change could break before it ships. Not for remote, credential, publish, deploy, or irreversible changes.
Use when a user wants to identify the true sources of complexity qualitatively before counting metrics. Not for source or remote mutation.
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.
/tasks
Tasks
Plural alias for task status, pause, prompts, recovery, and ignore
/test
Test
Verify that the autorun plugin command surface is loaded
/tm
Tm
Tmux session management - create, list, cleanup isolated sessions, short for /ar:tmux
/tmux
Tmux
Tmux session management - create, list, cleanup isolated sessions
/tt
Tt
CLI testing in isolated tmux sessions, short for /ar:ttest
/ttest
Ttest
CLI testing in isolated tmux sessions
/x
X
Graceful stop - finish current task then stop (short for /ar:stop)
/ar-allow
ar-allow
Set AutoFile policy to ALLOW — permit creation of new files without justification
/ar-commit
ar-commit
Refresh git commit guidelines before staging changes
/ar-find
ar-find
Set AutoFile policy to FIND — restrict edits to existing files only
/ar-go
ar-go
Start an autorun task with three-stage verification (initial → critical review → final verification)
/ar-ph
ar-ph
Refresh the universal system design philosophy before designing or reviewing code
/ar-st
ar-st
Show the current AutoFile policy and any active autorun state
/extract
Extract
Extract text from PDF files or directories to markdown
/ship
Ship
Trigger: `/ship` or "ship it" or "deploy to production"
/skip-questions
Skip questions
Suppress 5-question enforcement for rapid sessions
/check-outage
Check outage
Check a Dutch address for KPN outages and report what connectivity is available there
/lost-phone
Lost phone
Find the KPN business-mobile contract for a lost or stolen phone and block its SIM after confirmation
/skillopt-sleep-handoff
Skillopt sleep handoff
Run the SkillOpt-Sleep cycle with the handoff backend — no API subprocess; this session answers the engine's model calls via prompt/answer files, in isolated fresh-context subagents
/skillopt-sleep
Skillopt sleep
Run or manage the SkillOpt-Sleep self-evolution cycle (review past sessions, replay tasks through a selected backend, consolidate validated memory + skills, or schedule nightly runs)
Okou connects to the tools your team already uses and does the work — across marketing, sales, engineering, and operations, under your control.
4 views 0 likesAn open-source Digital Worker platform for reliable execution, continuous co-evolution, and building Enterprise AI assets.
6 views 0 likesA curated list of AI Agent evolution, memory systems, multi-agent architectures, and self-improvement projects. | evomap.ai
4 views 0 likesA governance harness for AI coding.
3 views 0 likesDeepSeek Harness 手机版:可直接安装的 Android APK,AI 免 Root 操作手机(Shizuku/root 可选),文件编辑只需所有文件访问权限,前台保活 + AI 通知
1 views 0 likesLocal-first, governed AI agent runtime for Python — embed it in your app, or run it as a CLI or ACP server. Permissions, MCP, memory and audit replay built in.
2 views 0 likesOrbi — the factory that builds and operates AI software factories. GitHub Issues in, releases and runnable system out
3 views 0 likesOpen-source AI agent harness in native Rust — GUI, CLI, headless, and webapp from one binary. Multi-provider, MCP, skills, plugins, agent teams.
1 views 0 likesThe SDK for browser agents. Interact, search, extract, and fetch any site reliably across the web
4 views 0 likesAgent-native shopping for extreme value: verifiable same-product price evidence, checkout, orders, delivery, and after-sales.
5 views 0 likesThe extensible power-user platform for Google Antigravity. Adds a native In-App Browser, animated Desktop Pets, revamped Gemini UI, and custom BYOK Gemini Pro k…
4 views 0 likesOpen-source, single-binary, self-hosted AI agent — your models and data stay on your machine. A coding agent on par with Claude Code and a personal assistant li…
4 views 0 likesYour pocket agent. Local-first AI agents on iOS and Android — real workspaces, tool execution with approvals, and your choice of model (DSH · Claude Code · Code…
3 views 0 likesBridge between QQ (SnowLuma OneBot v11) and DeepSeek Harness agents: social simulation, safe MCP tools, slang learning and more.
2 views 0 likesA 7×6 framework for agent architecture. 28 patterns, each placed at a coordinate, runnable Python code with verified engineering slices from Claude Code, Aider,…
2 views 0 likes针对 AI 自动化渗透 Agent 的新一代反制蜜罐,通过反向代理将API密饵载入真实业务、反向提示词注入等方式反制自动化渗透 Agent,实现多款主流通用Agent的反制上线控制。
2 views 0 likesOpen-source, local-first AI agent for coding and real work. BYOK models, MCP, skills, plugins, workflows, and private knowledge bases.
4 views 0 likesA free AI-agent toolbox for Android, 一站式安卓AI Agent工具箱
4 views 0 likesGoogle Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. I…
4 views 0 likesIndependent, unofficial CLI to edit CapCut and JianYing (剪映) projects — subtitles, timing, speed, volume, templates, cut long-form to shorts. No API needed, rea…
5 views 0 likes