LLM Mart Basic
@llm-mart · Joined Jun 2026
Expert in Firecrawl API for web scraping, crawling, and structured data extraction. Handles dynamic content, anti-bot systems, and AI-powered data extraction.
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session.
Analyzes and reorganizes project directory structures following industry best practices. Cleans up old files, logs, and redundant code. Handles Python, JavaScript, and general software projects with git integration.
Break a design brief into executable time-boxed tasks, each with a done-when line. Use immediately before a build session.
Turn an interrogated brief into the single source of truth for a design project. Use after /grill-me, before any IA or UI work.
Critique a design on layout, accessibility, responsiveness, dark mode and edge cases, with Pass, Needs work or Fail verdicts. Use on a built screen.
Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.
Build an interface from the brief and the tokens rather than from a guess. Use only after grill-me, design-brief, information-architecture and design-tokens have run.
One move you can run on anything: point grill-me at a target and it makes you defend your thinking from first principles until the true matter is clear. Point it at your working contract and it rewrites the weak lines in place. Point it at a brief and it produces a Requirements H
Audit a design against Nielsen's ten usability heuristics, tying every finding to a specific element with a specific fix. Use on a built screen or a detailed mockup.
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or U
Stress-test a design through three lenses, confused user, skeptical engineer and impatient PM, before it goes to a stakeholder. Requires an actual design, an HTML file, Figma link or screenshot.
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when th
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/sk
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/<client>/log.md or career-vault/log.md, one entry per project touc
Host-side setup, configuration, customization, builds, migration, and troubleshooting for the Aerovato Container CLI. Use when working with Aerovato Container, settings.json, Dockerfile.User, build stages, V2-to-V3 migration, mounts, harnesses, tools, permissions, Docker, or Podm
Imported from gal-a/qikly/docs.
Write tests that can actually fail, by withholding the acceptance criteria from the agent that writes the code. Use when someone does not trust a suite that passes. Use when they want tests written from a specification rather than from the code. Use when they ask whether a specif
Drive a software or general-work outcome through Forge's composable Spec, Plan, Build, Acceptance, and Ship lifecycle. Use when the user explicitly asks to use Forge, asks Forge to explore, spec, plan, build, review, accept, verify, simplify, finish, ship, reconcile a Spec change
Independently review an exact code candidate, including UI markup and styles, for reachable defects, regressions, security, engineering standards, and test quality. Use when the user asks for a standalone code review, PR review, branch review, commit review, diff inspection, or c
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.
/icon-lookup
Icon lookup
Search for icons by name, or identify a PUA character
/add-skill
Add skill
Install a pinned skill extension on demand (/add-skill <id>), or list core packs and extensions
/build
Build
Implement an approved plan or issue in its own worktree, run the gate, open the pull request.
/close-out
Close out
Close a finished session: sweep for unfinished work, ask once, land, file the follow-ups, hand off, tell the sessions that depend on this one, then archive.
/handoff
Handoff
Write the repository handoff file for the next session, and record any durable learning.
/land
Land
Merge an approved pull request, clean up its worktree and branch, then check whether a release is due.
/plan
Plan
Turn a topic or issue into a plan the reviewer approves in the native plan pane.
/research
Research
Answer a research question with parallel read-only gatherers and one synthesized digest.
/review
Review
Review the branch's diff in two fresh contexts — scope against the spec, then quality — and report findings only.
/psql-query
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database
/techdebt
techdebt
Find and report technical debt in the codebase
/pull
Pull
Refreshes local project state from a linked Supabase project or branch in one step, instead of running `config pull`, `db pull`, `migration fetch`, and `functions download` individually. It runs four steps, always in this order: pull config into `supabase/config.toml`, optionally
/minutes-x1-send-meeting
Minutes x1 send meeting
Send one of the user's own Minutes meetings to their X1 household for review. Use when the user wants a meeting's summary, decisions, action items, and open questions to reach X1 so they can confirm what belongs in their household record. X1 asks the user to approve the send, and nothing reaches the household record until they confirm each item. Never use it for a restricted meeting, a transcript, or someone else's meeting.
/minutes-x1-send-meeting
Minutes x1 send meeting
Send one of the user's own Minutes meetings to their X1 household for review. Use when the user wants a meeting's summary, decisions, action items, and open questions to reach X1 so they can confirm what belongs in their household record. X1 asks the user to approve the send, and nothing reaches the household record until they confirm each item. Never use it for a restricted meeting, a transcript, or someone else's meeting.
/init-skill
Init skill
> **Usage:** Create a new skill from the template.
/quality-gate
Quality gate
> **Usage:** Run before every commit to ensure code quality.
/validate-skill
Validate skill
> **Usage:** Validate skill files for correctness, completeness, and quality.
/optimize
Optimize
credo - Run the optimisation audit for this repo (opt-in, read-only scan, findings offered one by one)
/peer-lan
Peer lan
credo - Start, stop, or check the LAN peer relay (cross-machine peer messaging, no cloud)
/film-review
film-review
Measure a launch film (a reference to match, or your own render) at its native frame rate and review it against its register. Returns the launch-video-review rubric table plus a per-film JSON.
Offline-first Python AI agent that runs a tiny research business: quotes each job against its own costs, collects via Stripe, fulfils with NVIDIA Nemotron, pays…
0 views 0 likesDSH 插件 · 注入式优化器 0.8(主线):你照常说话,它在你发送后,AI接收前把"这一轮到底要什么"理清楚,再把这份理解交给工作 AI(上下文注入) —— 原话不改写,条条带逐字依据。含控制界面(档位/权限/模型/上下文/只读工具)、拦截浮层(思维层+产出层)与真实 token 用量。可明显提升大多数模型的发挥稳…
0 views 0 likesReliable AI Skill + MCP toolkit for agent-driven desktop CAD automation.
0 views 0 likesCurated real-world use cases for Hermes Agent — the self-improving AI agent from Nous Research. Backed by primary sources.
0 views 0 likesAI Agent 教学仓库 | 系统化 LangChain、RAG、LangGraph、MCP 全栈实战代码 | 万字博客详解 | 开源可运行示例 | 从零构建智能体
0 views 0 likes从 0 复刻 WorkBuddy-style 桌面 AI 助手 Harness:24 章 Python 教程,覆盖 Agent Loop、工具调用、记忆系统、Sidecar、沙盒审计、DeepSeek/OpenAI 评测轨迹
1 views 0 likesMCP server and CLI tools for web search and crawling, built on SearXNG and Crawl4AI
2 views 0 likesDelta MCP is a free app that sits between your AI apps and their MCP servers: one program per task instead of one tool call per step, up to 24.1× fewer tokens i…
2 views 0 likesAva turns any Android 5+ device into a voice-first Home Assistant kiosk. Native C++ under the hood, so a 10-year-old tablet still listens, talks, and runs the h…
0 views 0 likesRoblox Studio macOS Window Capture Fix 2026: Real Screenshot Tool Instead of Magenta Playtest Glitch
2 views 0 likesLabTether
2 views 0 likes