LLM Mart Basic

Use when writing a custom bootloader, jumping to application code, relocating VTOR, or implementing DFU/USB firmware update on Cortex-M. Not for reset-to-main: use baremetal-startup.

Use when C or C++ code needs memory-safety or undefined-behavior guarantees proved with CBMC, or ACSL contracts checked with Frama-C Eva or WP. Not for choosing the proof policy: use proof-driven.

Use when explaining branch predictors, mispredict penalties, speculative execution, Spectre or Meltdown mitigations, or branchless code. Not for pipeline stage theory: use cpu-pipelines-and-hazards.

Use when the user asks for branded or style-governed output. Not for remote, credential, publish, deploy, or irreversible changes.

Use when bloated code needs clean re-derivation, or the user says "this module is bloated" or "break it and rebuild". Not for untracked data or changes without VCS rollback.

Use when the user runs /browser-cookie-store to populate the session cookie store from installed browsers. Not for remote, credential, publish, deploy, or irreversible changes.

Use when the user runs /browser-qa for report-only QA results without entering a fix loop. Not for remote, credential, publish, deploy, or irreversible changes.

Use when building, debugging, or verifying browser-rendered code, or running browser tests for PR- or branch-affected pages. Not for source, remote-system, credential, publish, or deploy changes.

Use when reducing C/C++ compilation times with ccache, sccache, distcc, unity builds, precompiled headers, split DWARF, IWYU, or link time reduction.

Use when asked to analyze a Burp Suite .burp project for audit items, request/response metadata, or captured traffic. Modes: parsed (default) and stream. Not for source or remote-system changes.

Use when product copy needs buyer-objection evidence collected through approved, consented outreach. Not for unsolicited outreach or survey design.

Use when the user wants the current jargon weather of a domain described without advocacy. Not for choosing a positioning move: use buzzword-hijack.

Use when a user wants to choose and execute a bounded positioning move that rides a jargon wave. Not for describing the jargon weather of a domain: use buzzword-analysis.

Use when C code is written or audited and needs a pure-C baseline: standard, undefined behavior, integer and buffer safety, sanitizers, fuzzing, build flags. Not for C++: use modern-cpp-practices.

Use when the user requests a userspace C or C++ security review with a threat model and severity filter and wants validated findings. Not for kernel or bare-metal code: use kernel-security.

Use when the user asks "where to help", "contribution opportunities", or "find a good first issue". Returns data-backed first steps. Not for PR review queues: use gh-review-requests.

Use when the learner is ready to apply cleared concepts in a real project. Not for exercises or quizzes: use drill.

Use when evaluating Carbon for a C++ code base, running the carbon toolchain from a nightly or Bazel build, or comparing Carbon with staying on C++. Not for C++ modules: use cpp-modules.

Use when initializing, running, measuring coverage, or triaging a cargo-fuzz target in a Rust crate. Not for remote, credential, publish, deploy, or irreversible changes.

Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.

A green PR, a controller reporting success, and not one line of the new code running

Discover testnet↔mainnet subnet lineage from repo configs and open a PR for review (pass --dry-run to report only)

Triage raw inbox notes into reviewed repository destinations without deleting their sources.

Audit and rewrite content to remove AI writing patterns

Log a completed piece of content to content/log.md after the user confirms it was published.

Validate a dream artifact, review each proposal, and apply only individually accepted changes.

Run a curator pass against the validated memory directory and produce a proposal artifact.

End a session — log what happened, update state and the decision log, propose memory updates, and check for uncommitted or unpushed work

Find relevant context files by topic. Use when you need to load files for a topic without a slash command, or when a task spans multiple domains.

Inventory and migrate selected Gemini CLI workflows with dry-run review and parity checks.

Find repeated workflows in selected Gemini CLI sessions and draft portable skills after review.

Scan multi-session drift and offer individually reviewed fixes only after explicit approval.

Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.

Guided onboarding or import for durable workspace context

Start a session — load state files, flag staleness, and give a briefing on current priorities, deadlines, and blockers

Create a morning heartbeat from repository state and update the local heartbeat log.

Mid-session checkpoint — append progress to today's session log and update state files if a priority shifted, without ending the session

Maintainer-only. Find every file that would newly ship to adopters, classify each one against the written distribution-boundary categories, default to withhold on no clean match, and ask the maintainer only where the taxonomy does not settle it. Drives the release CLI, which refuses to produce a manifest until every shipping file has an answer.

Audit memory, wiki, and auto-loaded files for duplication, conflicting instructions, and stale content. The default path researches, then asks you a single Apply / Discuss / Decline question; on Apply it applies the report, files any out-of-scope problem as a tech-debt issue, then commits, opens a PR, and merges it on a main-branch run like /update-deps. Pass --apply to re-run the apply-and-publish stage against the most recent report.

Fix the tech-debt backlog, a single issue or a recommended related batch, highest severity then oldest first, on a fresh isolated branch through the audit gate, closing the issue(s) on merge. Pass `list` to see the ordered backlog, `why <issue-number>` to explain the recommendation, or a bare `<issue-number>` to fix that issue directly.

Health-check and auto-heal this project's Claude integration, triage, heal, verify, and report an F-to-A+ grade.

AI coding platform for teams

AI Multi-Agent Framework in .NET

Production-ready code examples for Telnyx AI Communications Infrastructure — Voice AI, SMS, SIP, and IoT APIs

UltraGameStudio - AI coding agent for game development: engine workflows, gameplay code, and asset generation.

🦞 ResearchClawBench: Evaluating AI Agents for Automated Research from Re-Discovery to New-Discovery

The context-aware model router that learns & adapts to your long-horizon coding agent workflows. Lightweight & extensible, works with any harnesses, any models,…

Open-source sandboxes where coding agents build and deploy. Spin up isolated environments where Claude Code, Cursor, and other agents code and deploy software.

Native desktop UI for Claude Code with orchestration, streaming, background agents, and multi-provider support. Built with Tauri + React.

OpenCode mobile client via Telegram: run and monitor AI coding tasks from your phone while everything runs locally on your machine. Scheduled tasks support.

Terminal session manager for AI coding agents. One TUI for Claude, Gemini, OpenCode, Codex, and more.

Exposes internet search tools for use by LLM-backed Assist in Home Assistant

Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs

Versus Incident is the self-hosted AI SRE agent. It learns what your system normally look like and escalates only what is new or unexpected issues — routing to…

Browser-native side panel for Hermes Agent — connect web context to your local Hermes runtime.

Agentic-friendly CLI generator for APIs: turn Swagger, OpenAPI, and google.api.http protos into single-binary CLIs with catalogs and generated Skills.

Open-source agent platform for Global × China enterprises — wire every system through one agent core. Self-hosted, any LLM.

Official python implementation of UTCP. UTCP is an open standard that lets AI agents call any API directly, without extra middleware.

An agent small enough to run anywhere. A minimal agentic runtime in C — ~380 lines, 54KB binary, ~2MB RAM. A skill file + an LLM + a shell loop, no framework.

AgentiLoop Agent! An Autonomous Agentic Agent for Mac, and exclusive Apple only harnesss. Suppprtd automation, scripting, coding, build anything and more. Power…

微信公众号 AI 运营助手 | 选题、写稿、审稿、排版、配图、发布全流程 Skill，支持 OpenClaw / Claude Code / Cursor / Codex