LLM Mart Basic
@llm-mart · Joined Jun 2026
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
Investigate problem, verify findings, and derive solutions
Orchestrate the complete implementation lifecycle from requirements to deployment
Create work plan from design document and obtain plan approval
Design Doc compliance and security validation with optional auto-fixes
Update existing design documents (Design Doc / PRD / ADR) with review
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.
Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions design source, design sys
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
Investigate problem, verify findings, and derive solutions
Adjust an already-implemented UI in-session with verification against the design source
Execute materialized frontend task files in autonomous execution mode
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.
/implement-graphql-api
Implement graphql api
Implement GraphQL API endpoints
/init-project
Init project
Initialize new project with essential structure
/initref
Initref
Build reference documentation by creating markdown files and updating CLAUDE.md
/issue-to-linear-task
Issue to linear task
Convert GitHub issues to Linear tasks
/issue-triage
Issue triage
Triage and prioritize issues effectively
/linear-task-to-issue
Linear task to issue
Convert Linear tasks to GitHub issues
/load-llms-txt
Load llms txt
READ the llms.txt file from https://raw.githubusercontent.com/ethpandaops/xatu-data/refs/heads/master/llms.txt via `curl`. Do nothing else and await further instructions.
/log
Log
Log work from orchestrated tasks to external project management tools like Linear, Obsidian, Jira, or GitHub Issues.
/market-response-modeler
Market response modeler
Model customer and market responses with segment analysis, behavioral prediction, and response optimization.
/memory-spring-cleaning
Memory spring cleaning
Clean and organize project memory
/mermaid
Mermaid
Create entity relationship diagrams using Mermaid from SQL/database files
/migrate-to-typescript
Migrate to typescript
Migrate JavaScript project to TypeScript
/migration-assistant
Migration assistant
Assist with system migration planning
/migration-guide
Migration guide
Create migration guides for updates
/milestone-tracker
Milestone tracker
Track and monitor project milestone progress
/modernize-deps
Modernize deps
Update and modernize project dependencies
/move
Move
Move tasks between status folders following the task management protocol.
/optimize-build
Optimize build
Optimize build processes and speed
/optimize-bundle-size
Optimize bundle size
Reduce and optimize bundle sizes
/optimize-database-performance
Optimize database performance
Optimize database queries and performance
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…
13 views 0 likesYet another coding agent harness, lightweight and written in go.
13 views 0 likesa coding Agent from pi. ∞ providers, sub-agents, hashline edits, and a permission gate
13 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.
14 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