LLM Mart Basic
@llm-mart · Joined Jun 2026
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
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval
Create frontend work plan from design document and obtain plan approval
Design Doc compliance and security validation with optional auto-fixes
Execute materialized fullstack task files with layer-aware agent routing
Orchestrate full-cycle implementation across backend and frontend layers
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.
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
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.
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal te
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
Collects compact repository evidence for scope confirmation, technical option selection, complete design, and verification. Use before Design Doc creation when repository facts can change scope, reuse, contracts, cost, or proof.
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.
/python-scaffold
Python scaffold
Scaffold a Python project (FastAPI, Django, library, or CLI) with uv, type hints, testing, and dev tooling
/approve-review
Approve review
Open a review-action approval window by creating the ./.review-approved flag file. Takes an optional reason string that is recorded in the flag file and an unsigned approval log.
/list-pending
List pending
List the review actions that the review-governance policy blocked in this session. protect-mcp 0.7.4 writes no receipt for a denied call, so the list comes from the session, not from ./review-receipts/.
/compliance-check
Compliance check
Review software compliance controls, regulatory requirements, and audit readiness
/security-dependencies
Security dependencies
Scan dependencies for vulnerabilities and generate supply chain security evidence
/security-hardening
Security hardening
Orchestrate comprehensive security hardening with defense-in-depth strategy across all application layers
/security-sast
Security sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks
/setup
Setup
Initialises the ShipMate pipeline in the current project. Creates the stories folder, sets up the pipeline state directory, and runs the initial codebase scan to generate project-doc.md and AGENTS.md.
/ship
Ship
Master pipeline entry point. Routes requirements from a story file through scan → orchestrate → architect → implement → review → QA → playwright stages. Use /ship stories/foo.md to start, /ship status to check progress, /ship resume to continue.
/business-case
Business case
Generate comprehensive investor-ready business case document with market, solution, financials, and strategy
/financial-projections
Financial projections
Create detailed 3-5 year financial model with revenue, costs, cash flow, and scenarios
/market-opportunity
Market opportunity
Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations
/rust-project
Rust project
Scaffold a Rust project (binary, library, workspace, or Axum web API) with Cargo, testing, and dev tooling
/tdd-cycle
Tdd cycle
Execute a comprehensive TDD workflow with strict red-green-refactor discipline
/tdd-green
Tdd green
Implement minimal code to make failing tests pass in TDD green phase
/tdd-red
Tdd red
Write comprehensive failing tests following TDD red phase principles
/tdd-refactor
Tdd refactor
Refactor code while keeping all tests green in TDD refactor phase
/issue
Issue
Resolve a GitHub issue from triage and root cause analysis through test-driven implementation and a pull request
/standup-notes
Standup notes
Generate async standup notes from git commits, Jira tickets, and Obsidian notes
/accessibility-audit
Accessibility audit
Audit UI code for WCAG compliance
Your efficient agentic AI coding CLI assistant
2 views 0 likesAI coding with Aegis governance built into execution: baseline-aware changes, evidence-backed delivery. Free desktop client, your choice of model. 将哲科思维融入 AI 开发…
1 views 0 likesAndroid in docker solution with noVNC supported, video recording, mcp server and AI-agent
2 views 0 likesYour AI assistant, built for the agentic era. Open source and local: talk to it, and it runs your agents, your coding CLIs, your browser and your apps. Windows,…
0 views 0 likesVerifiable program-level self-evolution for AI-for-Science agents: Skills and typed Operators grow from replay-verified executions.
3 views 0 likesLet Claude Code and other coding agents drive and debug Chrome from the shell. DOM, network, console and raw CDP as short commands, no screenshots and no MCP ne…
3 views 0 likesUnofficial, agent-friendly Mercadona shopping CLI (Go) — search products, read prices, build a cart and prepare checkout from the terminal. BYO credentials.
3 views 0 likesLocal-first AI canvas for visual workflows, AI short drama, image/video generation, storyboarding and asset management. ComfyUI, AI agents, MCP & Blender. 本地优先…
3 views 0 likesLet any AI coding tool — Claude Code, Cursor, Codex — drive your real Chrome. One-prompt setup, muscle memory, local-first.
3 views 0 likesruns anywhere. uses anything
3 views 0 likesOpen-source dots for the web: an AI agent with its own browser, one that does not get blocked.
0 views 0 likesFree MIT AI coding agent — no API key needed. Built-in free model, or bring Claude, GPT, Gemini, DeepSeek, Ollama +50 more. Swarm mode, 40+ tools, browser & des…
3 views 0 likesOpen-source AI customer support system. AI-first support, human-ready operations.
3 views 0 likesA durable, multiplayer, mobile-first web app for Pi agents, built on Pi Durable
3 views 0 likesEmbedded Cypher knowledge graph for Python and Rust. Bundled MCP server, describe() schema, and code-graph parser for LLM agents.
3 views 0 likesTurn PDFs, books and papers into interactive learning webpages|将复杂材料转化为可追溯、可测验、可做笔记的学习网页
3 views 0 likesPhysicsOS 是一个面向初高中物理学习的公益可视化智能体,通过 AI 理解题目并结合物理引擎,将抽象物理过程转化为可交互、可观察、可计算、可验证的真实物理场景。
3 views 0 likes