LLM Mart Basic

Use when asked to predict Culture Index traits from an interview transcript before a survey exists, including sparse or contradictory evidence. Not for interpreting completed survey results.

Use when a manager needs profile-specific communication, one-on-one, motivation, and energy guidance for a direct report. Not for general pair or team compatibility analysis.

Use when a signed new hire's Culture Index profile and team profiles need a first-90-days plan. Not for manager coaching: use culture-manager-coaching.

Use when implementing pool/slab/arena allocators, tuning jemalloc/mimalloc/tcmalloc, writing a Rust GlobalAlloc, or benchmarking allocator performance and fragmentation.

Use when customer feedback, NPS, churn, email feedback, call transcripts, or voice-of-the-customer analysis needs a report over a time window.

Use when the user asks to cut, trigger, or start a release candidate for a release branch. Not for full releases, hotfixes, or non-release-candidate workflow dispatches.

Use when the caller supplies a falsifiable out-of-happy-path invariant and a finite budget. Restores via bounded patches or reverts. Not for normal feature delivery or universal retries.

Use when a build, QA pass, demo, user complaint, or abandoned attempt leaves the next pass needing lessons rather than code. Not for changelog extraction. Not for session handoff: use handoff.

Use when a human-curated dbt model index must guide BigQuery SQL for a warehouse question. Not for discovering undocumented models or executing warehouse changes.

Use when a user asks to tighten verbose-but-correct prose without a full rewrite. Cuts in place to load-bearing density, preserving every load-bearing claim.

Use when debugging RelWithDebInfo or -O2 release builds, using -Og for debuggable optimization, split-DWARF, GDB scheduler-locking, reading inlined frames, or understanding "value optimized out".

Use when the user has a fork and wants it resolved and applied, not explored: "decide this", "choose the path", or "decide and fix it".

Use when a user wants to record why one world won over the others, as a decision-diary entry. Not for remote, credential, publish, deploy, or irreversible changes.

Use when a current decision needs pressure-testing until the rationale is clear to a skeptic. Not for tasks requiring source or remote-system changes.

Use when an imperative program needs pre-conditions, post-conditions, and loop invariants proved automatically by SMT in Dafny or Why3, short of a tactic prover.

Use when asked to deduplicate a skill tree, fold overlapping skills, or cut the skill count: analyze, gate per family, then fold. Not for prompt-doctrine cascades: use cascade-dedup.

Use when the user asks to research a topic and produce a thorough sourced report. Not for remote, credential, publish, deploy, or irreversible changes.

Use when the user wants the finished-system contract for a piece of work: behavior, protocols, allowed, forbidden, and impossible states with a state-space proof. Not for runtime verification.

Turns a song (audio file + lyrics) into a hand-painted watercolour music video (MP4) in the style of PDoomVideo, following its pipeline end to end: measure the beat grid and time the lyrics, scaffold the p5.brush engine, design the story, characters and sets from the lyrics, pain

Paints one chapter (src/ch/cNN_name.js) of a paint-mv music video in the PDoomVideo style: watercolour-and-ink frames drawn with p5.brush, the song's own characters (designed from its lyrics) acting on the beat, camera moves and motivated transitions, each frame a pure function o

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.

Create and manage database migrations

Analyze GitHub issue and create technical specification with implementation plan

Scaffold new feature with boilerplate code

Create a Jobs to be Done (JTBD) document for a product feature focusing on user needs

Create developer onboarding guide

Create a new branch, commit changes, and submit a pull request with automatic commit splitting

Create a Product Requirements Document (PRD) for a product feature

Create a comprehensive Product Requirement Prompt (PRP) with research and context gathering

Guide for creating pull requests using GitHub CLI with proper templates and conventions

Manage git worktrees for open PRs and create new branch worktrees

Manage cross-platform reference links

Systematically debug and fix errors

Analyze decision quality with scenario testing, bias detection, and team decision-making process optimization.

Explore decision branches with probability weighting, expected value analysis, and scenario-based optimization.

Audit dependencies for security vulnerabilities

Map and analyze project dependencies

Design optimized database schemas

Design RESTful API architecture

Create systematic digital twins with data quality validation and real-world calibration loops.

Analyze directory structure and purpose

A systematic AI Agent development tutorial covering LLM agents, RAG, tool use, memory systems, multi-agent systems, LangChain, LangGraph, MCP, and agentic RL.｜从…

Convert Files / Folders / GitHub Repos Into AI / LLM-ready Files

Open-source, local-first conversational AI video editor with a professional multi-track timeline, Agent Skills, MCP integration, and Remotion rendering.

Maintainer-governed agent for evidence-backed open-source contribution proposals

A 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…

Local-first AI agent workspace for coding, writing, design, research, and automation — one runtime for desktop GUI and TUI.

Open-source AI Agent platform for teams. Your agents don't just chat — they read files, run code, call APIs, and deliver results.

Give your AI agent eyes for PDFs — structured text, tables, OCR, visual evidence, and page-level citations via MCP. Native Rust, local-first.

Real-world AI penetration testing engineer for authorized assessments — built-in cloud module covering AWS/Azure/GCP + Aliyun/Tencent/Huawei clouds. Built on Cl…

OpenGUI is an Android GUI agent framework for phone-use AI that can see, plan, and operate real mobile apps through the GUI.

Tinybot is a lightweight personal AI Agent that is constantly evolving

Goink 桌面 AI 小说创作助手，对话式写作 + 自动状态追踪 + 本地语义搜索。跨平台开箱即用。AI Agent Novel Generator.

Pluggable DeepSeek-colored TUI for DeepSeek Harness

Entity-level git merge driver. Resolves false conflicts git invents when independent agents edit the same file. ~95% reduction vs. line-based merge.

Percho: 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,…

Run Claude Code, Codex & Gemini in parallel on Windows & macOS — git worktree fan-out with atomic hunk adoption, approval gates, reboot-surviving sessions

A hierarchical memory framework for personalized presentation agents. Try it at memslides.com.

Real-time multimodal desktop agent evolving toward a persistent AI OS interface (0.1 α).

clawdcursor compiles whatever's on screen into one UI map — accessibility tree and OCR fused into stable, addressable elements, with a screenshot only when need…

Repeatable agentic engineering. The workflow layer that turns AI coding agents into a disciplined factory: durable specs, fresh-context workers, adversarial cro…