LLM Mart Basic

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

Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.

Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.

Review PR, branch, commit or working-tree changes for concrete defects and fidelity to intended behavior. Also use when explicitly asked to independently challenge a prepared plan, diagnosis or verification claim.

Design or review module ownership, public interfaces and abstractions; UI token/component ownership; or domain-driven models, bounded contexts and invariants. Use for structural decisions, not routine edits within an established owner.

Prove real user journeys across browser, mobile, desktop, API and CLI surfaces using the project's existing test tools. Use for end-to-end verification, runtime UI review or requested visual proof.

Apply Hard Eng's planning, project context, verification and gate-adaptation guidance when implementing or reviewing code in an installed project.

Implement and verify a ready, authorized plan through focused fixes and integrated checks, ending with a ready-for-ship handoff. Use for implementation, bug fixes or resuming build work; skip planning-only, review-only and shipping-only requests.

Prevent verified repeated failures and preserve lasting decisions in terse ADRs. Use when failures recur, prevention needs strengthening, or accepted decisions and steering need durable capture; skip ordinary one-off fixes and routine task updates.

Plan a change before implementation, resolve material user decisions and prepare repository-grounded UX references. Use a compact plan for small changes; route large, unclear efforts or explicit Wayfinder requests to Wayfinder. Skip explanation-only requests and execution already

Deliver a verified build through a task branch and PR, check the intended remote result, and clean up the completed task safely. Use for PR creation, shipping, merging or release/deployment requests; skip planning, implementation and review-only work.

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 issues (GitHub/GitLab/Bitbucket) using progressive analyze-specify-plan-implement workflow

Address PR/MR review feedback by reading comments, implementing fixes, and resolving threads. GitHub and GitLab support.

Retrospective analysis and improvement of workflow components with self-evolving patterns

Fix broken functionality from pasted error output, stack traces, or

Summarize recent git history since a baseline with structured analysis of what changed, why, and what to watch for.

Consolidate ephemeral LLM-generated markdown into permanent documentation.

Review pull requests with scope validation, code analysis, and line comments. Supports GitHub PRs and GitLab MRs.

Prepare a PR end-to-end by updating documentation, running tests, dogfooding checks, and validating with code review.

Batch-resolve unresolved PR/MR review threads via GraphQL API (GitHub/GitLab)

Detect and fix drift between plugin.json registrations and capabilities reference documentation

Update pre-commit hooks and CI/CD workflows based on recent project changes

Scan and update dependencies across all ecosystems with conflict detection

Update project documentation with consolidation, debloating, AI slop detection, capabilities sync, and accuracy verification.

Audit and sync plugin.json registrations with actual disk contents. Detects missing or stale skills, commands, agents, hooks.

Review and update test coverage using TDD/BDD methodology with quality validation. Generates tests for changed code.

Generate or update tutorials with VHS and Playwright recordings

Bump project versions using git-workspace-review and version-updates skills.

Generate and self-execute a diff-derived test plan for a PR. Reads

Generate new documentation with human-quality writing.

Clean up AI-generated content and improve documentation quality.

The fastest way to put Volcengine Ark in your terminal and your AI agent — go from prompt to generated media, multimodal answer, or deployed endpoint in a sin…

本地私有、开源的自进化跨平台 AI 内容发现 Agent：先理解你，再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。（支持 deepseek harness 插件） | Local-first open-source cross-platform AI cont…

Persistent memory for AI coding agents — one verified kb_search replaces the grep/find/ls orientation loop. Cross-repo, CPU-only, zero token spend.

AI 时代的伯克希尔：基于 Claude Code / Codex 的价值投资研究框架。巴菲特·芒格·段永平·李录四大师方法论 + 多Agent并行研究。| AI-era Berkshire: a value investing research framework built for Claude Code / Co…

The batteries-included, No-Code FinOps automation platform, with the AI you trust.

Open-source 3D AI agent framework — GLB/glTF avatars with LLM brains, memory, emotions, and autonomous payments. MCP server · x402 · Solana/EVM · Three.js. Embe…

XLSX parser for LLMs, RAG, LangChain, LangGraph, CrewAI, Claude, MCP — turns Excel (.xlsx) into citation-ready JSON with formulas, charts, dependency graphs, an…

Hermes-Relay — Your Hermes AI agent, in your pocket — chat, voice, and control.

A minimalist, terminal-native coding agent written in C.

AI-powered OSINT agent with interactive REPL, MCP server, and CLI. 19 tools. Works with Claude, GPT-4, or local models. For authorized security research only.

AI pair programming in your terminal — one static binary, sub-ms startup, any model

Where data access meets operational intelligence

Build your own security agents. Open-source framework for agents with live, read-only access to your infrastructure, with no path to widen it. Reasons across AW…

Multi-workspace terminal aggregator with Claude Code AI integration

Go implementation of AI coding agent

Harness engineering beginner tutorial, from 0 to 1

Generate images directly in DeepSeek Harness chats

A smarter, self-hosted AI assistant — multi-user, multi-agent.

Turn any research paper into a commercialization report — 6 AI agents, TRL/MRL scoring, patent landscape, market intelligence, verified citations. DeepSeek / Op…

Power BI CLI - semantic models (.NET TOM) and PBIR reports for token-efficient AI agent usage, built for Claude Code