LLM Mart Basic
@llm-mart · Joined Jun 2026
Diagnose and repair Operator memory load failures.
Initialize and configure the Operator User Partition.
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested `.editorconfig` files are allowed when they serve a clear subtree-specific pu
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.
Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide.
Build, upgrade, and operate .NET Aspire application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps.
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.
Use the open-source free `Asynkron.Profiler` dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.
Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. Use when a repo prefers a modern all-in-one CLI over a larger ESLint plus Prettier style stack.
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices.
Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate. Use when the problem is frontend architecture drift in the file tree rather than semantic code issues insid
Use the open-source free `cloc` tool for line-count, language-mix, and diff statistics in .NET repositories. Use when a repo needs C# and solution footprint metrics, branch-to-branch LOC comparison, or repeatable code-size reporting in local workflows and CI.
Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. Use when a .NET repo needs first-party code analysis, `EnableNETAnalyzers`, `AnalysisLevel`, or warning-as-error policy wired into build and CI.
Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.
Use the open-source CodeQL ecosystem for .NET security analysis. Use when a repo needs CodeQL query packs, CLI-based analysis on open source codebases, or GitHub Action setup with explicit licensing caveats for private repositories.
Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Use when a repo needs cyclomatic complexity checks, maintainability thresholds, or complexity-driven refactoring gates.
Use the open-source free `coverlet` toolchain for .NET code coverage. Use when a repo needs line and branch coverage, collector versus MSBuild driver selection, or CI-safe coverage commands.
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.
Use MCP Inspector to connect to local or remote servers, inspect capabilities, call tools, read resources, test prompts, and diagnose failures before release.
Build an MCP server in TypeScript with focused tools, validated schemas, local and remote transports, Inspector tests, and production security controls.
An MCP server exposes tools, resources, or prompts through a standard protocol so an AI application can discover and use external capabilities.
/setup
Setup
credo - Set up Claude Code with recommended workflows and plugins
/cleanup
Cleanup
dogma - Find and fix AI-typical patterns in code (reactive cleanup)
/docs-update
Docs update
dogma - Sync documentation across README files and wiki articles
/force
Force
dogma - Interactively collect and apply CLAUDE rules to the project
/ignore
Ignore
dogma - Add ignore patterns to multiple locations at once
/lint
Lint
dogma - Run project-specific linting and formatting on staged files (non-interactive)
/permissions
Permissions
dogma - Create or update DOGMA-PERMISSIONS.md interactively (Git, File, and Workflow permissions)
/sanitize-git
Sanitize git
dogma - Sanitize git history from Claude/AI traces and fix tracking issues
/sync
Sync
dogma - Intelligently sync Claude instructions from a source to the current project with interactive review
/versioning
Versioning
dogma - Check and fix version mismatches across all version files
/setup
gsd:setup
Install GSD resources into the active Claude config dir (${CLAUDE_CONFIG_DIR:-$HOME/.claude}/get-shit-done/) (required before using other GSD commands)
/uninstall
gsd:uninstall
Remove GSD resources from the active Claude config dir (${CLAUDE_CONFIG_DIR:-$HOME/.claude})
/cleanup
Cleanup
hydra - Remove already merged worktrees and their branches
/create
Create
hydra - Create a new Git worktree for isolated work
/delete
Delete
hydra - Safely remove a Git worktree
/help
Help
hydra - Show available commands and explain the concept
/list
List
hydra - List all Git worktrees of the repository
/merge
Merge
hydra - Merge a worktree branch back into current branch
/parallel
Parallel
hydra - Start multiple agents in parallel across worktrees
/spawn
Spawn
hydra - Start an agent in an existing worktree
Make any song you can imagine
38 views 0 likesLeading AI-powered video generation platform that specializes in creating hyper-realistic talking avatars
37 views 0 likesHermes Agent is an open-source, self-improving autonomous AI agent developed by Nous Research
36 views 0 likesKilo Code is a popular, open-source AI coding agent and "agentic engineering" platform designed to help developers build, refactor, and debug software faster
33 views 0 likesGeneral-purpose agent in one static Go binary. ReAct loop, ACP server for IDEs, OpenAI-compatible REST API with embedded web UI, Telegram gateway, cron schedule…
18 views 0 likesAutonomous agent framework with structured memory, safety hooks, and loop management. Built by the agent that runs on it.
19 views 0 likesTSP自托管、零运维的 A 股「选股 + 监控 + 回测」量化工作台 | 基于 TickFlow 数据源 | LLM能力驱使策略定制+个股分析+复盘 | 自由接入第三方数据源与个性化扩展数据 | 个人开源 ,非TickFlow官方项目
14 views 0 likesCurated, verified Agent Skills powered by ModelStudio.
17 views 0 likesRun Claude Code, Codex, Antigravity, Cursor Agent and OpenCode as one runtime — persistent sessions, multi-agent councils, an OpenAI-compatible endpoint, an MCP…
16 views 0 likespi had nothing (nothing), so I made something (something) — sorry mariozechner-senpai, I went ahead and lovingly soiled your pure pi for you. opinionated fork o…
13 views 0 likesA persistent workspace for development work that self-improves and continues beyond one session.
32 views 0 likesOpen-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access.
19 views 0 likes📚 A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | http…
28 views 0 likesDeterministic, local-first memory and guardrails for AI coding agents with no LLM in the hot path.
30 views 0 likesDeterministic spec-orchestration for local LLMs in the pi coding agent — drives prompts through refine→research→grill→compose→critique, with bundled web/docs/fe…
19 views 0 likesNative Safari browser automation for AI agents. 97 tools via AppleScript — zero overhead, keeps logins, runs silently in background. Drop-in alternative to Chro…
31 views 0 likesAgent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
14 views 0 likesGit for agent memory. Branches, diffs, PRs, and rollback for what your agents know.
31 views 0 likesMulti-Provider AI Gateway - No personal logs by design. Model autodiscovery, Failover groups, High availability, Android companion app, and more - "Because we h…
15 views 0 likesProduction-grade MCP server for MikroTik RouterOS with secure AI-native network automation.
27 views 0 likes