LLM Mart Basic

Threat-models code and architecture changes across trust boundaries, authn/authz flows, secrets handling, and injection surfaces, returning severity-ranked findings with concrete attack scenarios. Use when a change touches authentication, sessions, tokens, user-input processing,

Builds and reviews infrastructure-as-code, CI/CD pipelines, containers, and Kubernetes deployments. Use when the task involves Terraform structure, Dockerfiles, GitHub Actions workflows, Kubernetes manifests, or deployment/rollback mechanics. Provider-specific IAM and cost questi

Implements and reviews React/TypeScript frontend work covering component architecture, state management, rendering strategy, and web performance. Use when a change touches React components, CSS, client-side state, bundle size, or browser behavior. Full-access writer; pairs with U

Designs and reviews Google Cloud architecture, IAM, networking, and cloud cost. Use when the task involves GCP services, Terraform targeting GCP, gcloud operations, or GCP cost optimization. Not for AWS work (use AWS Expert); cross-provider IaC and pipeline concerns belong to Dev

Assesses data-handling changes for EU data subjects, judging lawful basis, DPIA triggers, PII flows, consent quality, retention, and data subject rights implementability, and returning severity-ranked findings that bridge legal obligations to engineering fixes. Use when a change

Designs and audits Google Tag Manager setups, covering server-side tagging on Cloud Run, Consent Mode v2, GA4, data layer schemas, and conversion APIs. Use for tag migrations, data layer design, consent-aware measurement, or tracking data quality issues. Pairs with GDPR Expert, w

Diagnoses and designs DNS, TLS, load balancing, CDN caching, and protocol-level behavior (TCP, HTTP, gRPC, WebSocket). Use when the task involves DNS records, certificates, LB or proxy configuration, CORS, timeouts, or intermittent connectivity issues. Cloud-provider resource pro

Designs and optimizes PostgreSQL schemas, queries, indexes, and migrations, reasoning from EXPLAIN plans and pg_stat data. Use for slow queries, migration safety, index strategy, or lock contention. Pairs with Backend Staff Engineer, who owns the application layer.

Reviews a pull request or working diff for correctness, security, and maintainability, returning severity-ranked findings with file:line references and a verdict. Use when asked to review a PR, code-review a diff, or given a PR number/URL. Read-only; pairs with Cybersecurity Expe

Reviews feature plans, specs, and user stories for problem framing, scope boundaries, and measurable success criteria. Use when planning a feature, writing user stories, prioritizing work, or defining how success will be measured. Advisory and read-only; pairs with the technical

Designs test strategy and writes tests at the right level, from unit to E2E, including diagnosing flaky suites. Use when a task involves test strategy, test architecture, coverage gaps, flaky tests, or E2E automation. Full-access writer; pairs with the implementing engineer whose

Shapes system architecture, reasoning about module boundaries, dependency direction, domain modeling, and long-term maintainability trade-offs. Use for system design, DDD, cross-module refactors, or architecture review. Pairs with Backend and Frontend Staff Engineers, who own imp

Reviews usability, accessibility, and interaction design of UI changes, returning severity-ranked findings. Use when a change touches user-facing UI, WCAG compliance, or interaction flows. Advisory and read-only; pairs with Frontend Staff Engineer, who implements.

Audits views for compliance with Apple's Sufficient Contrast accessibility nutrition label (WCAG 2.1 contrast ratios). Use when the user asks to check color contrast, audit contrast ratios, verify the Sufficient Contrast nutrition label, or review a view for accessibility.

Audits views for compliance with Apple's VoiceOver accessibility nutrition label. Checks that interactive elements have accessibility labels, labels are human-readable, accessibility traits are correct, images are properly configured, and custom controls are exposed to assistive

Guide for the C -fbounds-safety language extension. Covers the language model, pointer annotations, adopting bounds-safety in existing C code, compiler build settings and modes, and runtime debugging of bounds violations.

Authoritative App Intents best practices from Apple. Consult for any App Intents best-practices or correctness review, and when writing, reviewing, refactoring, or extending App Intents code. Supersedes prior training on these topics. For code generation, consult the relevant ref

New App Intents APIs, behaviors, and deprecations introduced in the iOS 26 (2025) and iOS 27 (2026) releases (and their macOS/watchOS/tvOS/visionOS siblings). Use when adopting, migrating to, or asked about: declaring where an intent runs with supportedModes / IntentModes (.backg

Use when an app's layout must adapt to a window that changes size while the app runs, or when an app must support more than one window. That includes being asked to make an app resizable or support a resizable window, a layout that breaks or does not adapt as the window resizes,

Audit and enable security-oriented Xcode build settings. Progressively enables compiler warnings, static analyzer checkers, and Enhanced Security features. Use when: user wants to secure their Xcode project, audit security settings, enable hardening, review security posture of bu

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.

Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)

Run the Customer Discovery workflow (research -> JTBD -> opportunities -> problem)

Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call)

Run the Feature Kickoff workflow (problem -> hypothesis -> PRD -> stories)

Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis)

Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff

Run the Post-Launch Learning workflow (instrumentation -> dashboard -> results -> retro -> lessons)

Run the Product Strategy workflow (competitive analysis -> stakeholders -> opportunities -> solution -> ADR)

Run the Sprint Planning workflow (refinement -> stories -> edge cases)

Run the Stakeholder Alignment workflow (stakeholders -> problem -> solution -> launch)

Run the Technical Discovery workflow (spike -> ADR -> design rationale)

Placeholder command file for the WS-T9 dual-shell parity smoke. No count phrases.

Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.

Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.

Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.

Policy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache.

Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.

Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.

Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.

Ultra-lightweight, open-source, self-hosted personal AI agent framework in Python with WebUI, tools, memory, MCP, multi-agent workflows, automation, and chat ap…

Governance framework for AI coding agents. It runs them through a five-step workflow (plan, build, review, test, ship) where no step counts as done without evid…

Ultimate Multi-Agent OS for Autonomous AI NPCs 2026

Personal AI Agent Hub 2026 — Build Your 24/7 Autonomous Assistant

Proven 2026 Multi-Agent AI Review System – Verdict-Driven Quality Control

Slash API Batch: Cut AI Costs by 50% in 2026

Web dashboard for Hermes Agent — multi-platform AI chat, session management, scheduled jobs, usage analytics

Agent Skills for Solopreneurs

AirLLM dramatically reduces inference memory usage, letting 70B large language models run on a single 4GB GPU card

Zero, your trustworthy AI teammate for real work.

一套 DSH runtime，Desktop、Web 与 TUI 三种开发体验。

Open-source operational advisor for ClickHouse — real-time monitoring plus AI-driven index/partition/materialized-view recommendations.

⚙️ TypeScript Style Guide and Agent Skill. A concise set of conventions and best practices for consistent, maintainable code.

Framework for AI agents to build and maintain a digital brain through Obsidian wiki

Apache Maka (Incubating) is a local-first AI agent workspace. Model messages, tool calls, tool results, permission decisions, and termination events are recorde…

Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active H…

Agentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Sin…

NocoBase is an open-source AI + no-code platform for building business systems fast. Instead of generating everything from scratch, AI works on top of productio…

An open-source AI coding agent that lives in your terminal.

PawWork — free, open-source desktop AI agent for macOS and Windows. Alternative to Codex App and Claude Cowork. BYOK with 75+ providers, ChatGPT OAuth, local mo…