LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when writing, reviewing, modernizing, building, or debugging C++ - RAII and resource lifetime, smart-pointer ownership, move semantics and the Rule of Zero/Five, target-based CMake with FetchContent, and killing undefined behavior with ASan/UBSan/TSan plus clang-tidy. NOT bor
Professional logo and brand-mark design, from brief to production files. Guides discovery and the design brief, concept generation, choosing a mark type (wordmark, monogram, letterform, pictorial, abstract, emblem, mascot, combination), building clean geometric SVG logos, optical
OpenTelemetry plugins for every coding agent, in the Agent Plugins format — a marketplace that runs itself: open an issue, the repository validates, reviews, li…
Automatically turn successful DeepSeek Harness sessions into reusable, reviewable Agent Skills.
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
Inspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporary_assigns.
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate.
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/phx:investigate).
Record a vetted Hex package version in hex_vet.exs after a security review — manages the audit ledger, not the scanner. Use to approve a dep after /phx:deps-audit findings or to initialize hex_vet.exs.
Use when asked to document Elixir code: add or fill in @moduledoc and @doc for modules and functions. Documents tested code only; may add a README section or ADR. Not for docs lookup or audits.
Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing unique_constraint, foreign_key_constraint, or check_constraint errors.
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.
/log-provenance
log-provenance
Log derived files and trace provenance back to ENCODE source data
/manage-credentials
manage-credentials
Store, check, or clear ENCODE API credentials for restricted data
/quality-check
quality-check
Assess ENCODE experiment quality using audit counts and replicate counts
/search-encode
search-encode
Search ENCODE experiments by assay, organ, biosample, or target
/track-experiments
track-experiments
Track ENCODE experiments locally with publications and provenance
/browse-files
browse-files
List, search, and inspect ENCODE files by format, type, and assembly
/cite-encode
cite-encode
Generate ENCODE citations for publications, grants, and presentations
/compare-experiments
compare-experiments
Check if two ENCODE experiments are compatible for combined analysis
/cross-reference
cross-reference
Cross-reference ENCODE data with PubMed, GEO, ClinicalTrials, and bioRxiv
/download-encode
download-encode
Download ENCODE files (BED, FASTQ, BAM, bigWig) with MD5 verification
/log-provenance
log-provenance
Log derived files and trace provenance back to ENCODE source data
/manage-credentials
manage-credentials
Store, check, or clear ENCODE API credentials for restricted data
/quality-check
quality-check
Assess ENCODE experiment quality using audit counts and replicate counts
/search-encode
search-encode
Search ENCODE experiments by assay, organ, biosample, or target
/track-experiments
track-experiments
Track ENCODE experiments locally with publications and provenance
/document
Document
Record the present state by mode — decision (ADR, RFC, rule), code (spec, doc, guide, scenario), or research (a ready report or one external material); a gate picks the document type.
/init
Init
First-time Archcore setup — wire host configs, measure the authored context, compose the full first-day seed in one preview, and create it on one confirm; import converts CLAUDE.md, AGENTS.md, rule files, ADRs, and docs into native documents; refresh adds new facts or drills into one domain.
/plan
Plan
Plan a feature or initiative through a computed route — a small fix exits with no documents, one capability gets a spec and a plan, a large initiative gets an umbrella PRD with one spec per capability; start with sdd, sources (market research), iso (regulated work), or research (technical investigation) to run that path directly.
/review
Review
Review branch changes against Archcore docs, or report project health; drift runs staleness detection, deep a full documentation audit, closeout closes a finished feature, experience captures a repeated pattern.
/cite-check
cite-check
Verify that citations actually exist and that the claims they support are faithful to the cited source. Runs deterministic existence checks (Crossref / OpenAlex / Semantic Scholar / arXiv) plus a claim-faithfulness pass via the alterlab-citation-verifier skill.
A systematic AI Agent development tutorial covering LLM agents, RAG, tool use, memory systems, multi-agent systems, LangChain, LangGraph, MCP, and agentic RL.|从…
11 views 0 likesConvert Files / Folders / GitHub Repos Into AI / LLM-ready Files
15 views 0 likesOpen-source, local-first conversational AI video editor with a professional multi-track timeline, Agent Skills, MCP integration, and Remotion rendering.
23 views 0 likesMaintainer-governed agent for evidence-backed open-source contribution proposals
12 views 0 likesA Claude Code skill by Hao (駱君昊) that learns your Facebook voice and auto-posts to FB / IG / Threads / X with a 14-day content calendar. Mega-viral validated: 8…
24 views 0 likesLocal-first AI agent workspace for coding, writing, design, research, and automation — one runtime for desktop GUI and TUI.
11 views 0 likesOpen-source AI Agent platform for teams. Your agents don't just chat — they read files, run code, call APIs, and deliver results.
12 views 0 likesGive your AI agent eyes for PDFs — structured text, tables, OCR, visual evidence, and page-level citations via MCP. Native Rust, local-first.
11 views 0 likesReal-world AI penetration testing engineer for authorized assessments — built-in cloud module covering AWS/Azure/GCP + Aliyun/Tencent/Huawei clouds. Built on Cl…
12 views 0 likesOpenGUI is an Android GUI agent framework for phone-use AI that can see, plan, and operate real mobile apps through the GUI.
11 views 0 likesTinybot is a lightweight personal AI Agent that is constantly evolving
15 views 0 likesGoink 桌面 AI 小说创作助手,对话式写作 + 自动状态追踪 + 本地语义搜索。跨平台开箱即用。AI Agent Novel Generator.
14 views 0 likesPluggable DeepSeek-colored TUI for DeepSeek Harness
7 views 0 likesEntity-level git merge driver. Resolves false conflicts git invents when independent agents edit the same file. ~95% reduction vs. line-based merge.
16 views 0 likesPercho: Minimalist desktop GUI for the Pi coding agent — the same engine as the Pi CLI, in a clean visual interface. Multi-session chat, visual tool approvals,…
12 views 0 likesRun Claude Code, Codex & Gemini in parallel on Windows & macOS — git worktree fan-out with atomic hunk adoption, approval gates, reboot-surviving sessions
23 views 0 likesA hierarchical memory framework for personalized presentation agents. Try it at memslides.com.
17 views 0 likesReal-time multimodal desktop agent evolving toward a persistent AI OS interface (0.1 α).
16 views 0 likesclawdcursor compiles whatever's on screen into one UI map — accessibility tree and OCR fused into stable, addressable elements, with a screenshot only when need…
18 views 0 likesRepeatable agentic engineering. The workflow layer that turns AI coding agents into a disciplined factory: durable specs, fresh-context workers, adversarial cro…
23 views 0 likes