LLM Mart Basic

Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications.

Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. Use when working in an EF6 codebase or planning a data layer migration.

Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets. Use when a repo needs a configurable CLI lint gate for frontend correctness, import hygiene, unsafe patterns, or framework-specific rules.

Use the free first-party `dotnet format` CLI for .NET formatting and analyzer fixes. Use when a .NET repo needs formatting commands, `--verify-no-changes` CI checks, or `.editorconfig`-driven code style enforcement.

Build or review gRPC services and clients in .NET with correct contract-first design, streaming behavior, transport assumptions, and backend service integration.

Use HTMLHint in .NET repositories that ship static HTML output or standalone frontend templates. Use when a repo needs a focused CLI lint gate for DOM structure, invalid attributes, and basic HTML correctness checks on static pages.

Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries.

Expert knowledge of the libvlc C API (3.x and 4.x), the multimedia framework behind VLC media player. Use when helping with LibVLC or LibVLCSharp for media playback, streaming, or transcoding.

Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow.

Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows.

Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.

Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for graph-oriented relationships, edge management, and traversal logic on top of Orleans grains. Use when the application models graph structures in a distributed Orleans system.

Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows.

Use ManagedCode.Storage when a .NET application needs a provider-agnostic storage abstraction with explicit configuration, container selection, upload and download flows, and backend-specific integration kept behind one library contract.

Build, review, or migrate .NET MAUI applications across Android, iOS, macOS, and Windows with correct cross-platform UI, platform integration, and native packaging assumptions.

Adopt MCAF governance in a .NET repository with the right AGENTS.md layout, repo-native docs, skill installation, verification rules, and non-trivial task workflow. Use when bootstrapping or updating MCAF alongside the dotnet-skills catalog.

Apply MCAF agile-delivery guidance for backlog quality, roles, ceremonies, and engineering feedback. Use when defining how the team plans, tracks work, and turns feedback into durable improvements.

Apply MCAF developer-experience guidance for onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup. Use when the repo is hard to run, debug, test, or onboard into.

Apply MCAF documentation guidance for docs structure, navigation, source-of-truth placement, and writing quality. Use when a repo’s docs are missing, stale, duplicated, or hard to navigate, or when adding new durable engineering guidance.

Apply MCAF human-review-planning guidance for a large AI-generated code drop by reading the target area, tracing the natural user and system flows, identifying the riskiest boundaries, and prioritizing the files a human should inspect first. Use when the codebase is too large to

An MCP server exposes tools, resources, or prompts through a standard protocol so an AI application can discover and use external capabilities.

Treat an AI agent skill as both an instruction package and a software dependency: inspect what it says, what it runs, what it can access, and how it updates.

Add remote HTTP or local stdio MCP servers to Claude Code, choose the right scope, protect credentials, verify the connection, and test with least privilege.

Skills teach Claude a repeatable method, connectors provide governed access to apps and live data, and plugins package related capabilities for installation and sharing.

Use an agent skill to package reusable know-how and workflow instructions. Use an MCP server when an agent needs live, governed access to external data or actions.

Custom commands and skills can both create a slash-invoked workflow in Claude Code. The important choice is how the workflow is discovered, shared, and permissioned.

A useful Claude skill solves one recurring engineering job, is easy to inspect, and saves more time than it creates in setup and review.

Claude skills can live in your Claude account, your local Claude Code setup, or a repository. Install them where the sessions that need them can load them.

Build a portable AI agent skill from one repeatable job: a precise description, concise instructions, focused resources, and tests that prove it works.

AI agent skills package instructions, scripts, references, and templates into portable folders an agent loads only when the task calls for them.

AI made publishing cheap, which is exactly the problem. What separates a page worth ranking from a competent summary of the first ten results.

A prompt that works once isn't a quality system. Five cases, an observable rubric, and a regression set will tell you whether a change helped.

One character of YAML, four pods that never started, and two safety nets I didn't know were holding. Every restart is an audit. Schedule them before they schedule you.

"Verify your work" isn't an instruction. It's a mood. Here's the version that's an instruction. Verify with a different mechanism than the one that made the claim.

A prompt that works once may still fail in production. A lightweight eval set gives you repeatable cases, a clear rubric, and a way to see whether a prompt change actually improved the workflow.

The best AI tool is not the one with the longest feature list. It is the one that solves a defined job reliably, fits the workflow, handles data appropriately, and remains useful after the novelty wears off.

Use AI to speed research without losing trust. Learn to find primary sources, verify claims, preserve uncertainty, and keep an auditable source trail.

Better prompts aren't magic wording. They're short briefs that hand the model a task, the context it can't infer, the limits, and a quality bar.

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

Guided component creation with proper patterns

Review existing UI for issues and improvements

Initialize a design system with tokens

Generate unit tests for Python, JavaScript/TypeScript, and React code with mocks, edge cases, and coverage gap analysis

Turn a recorded product demo into a prioritized backlog with timestamped evidence.

Turn one screen recording of a bug into an evidence-backed GitHub issue draft (quote, frames, OCR identifiers, wall-clock; silent recordings work too).

Walk a recording's remarks against system logs using wall-clock timestamps.

Turn a recorded meeting (audio is enough) into action items, decisions, and open questions with timestamps.

Turn a recorded workshop or design walkthrough into a structured spec with quoted decisions and open questions.

Turn a narrated screencast into precise, evidence-backed findings JSON (bug / feature / question routing with frame evidence).

Generate and enforce policy gates for AI coding agents (Copilot, Claude Code) — real-time session hooks that deny protected-path edits and dangerous commands, plus a merge-time backstop for anything that bypasses them. Use when asked to "govern AI agents", "block AI from touching secrets", "add an AI policy gate", or "why did the AI agent hook not fire".

Show the active planning-with-files plan (id, mode, attestation, current phase, phase counts)

Start planning-with-files (task_plan.md, findings.md, progress.md); flags --gated, --autonomous, --template analytics, then an optional plan name

Run a paid-ads (ROAS) workflow: audience segments, account structure, ad creative, experiment design, pre-launch signal QA + the account-audit gate, measurement, and attribution. Not sure? Use /aaron-marketing:auto.

Natural-language front door to the marketing pack (narrative/TALE, SEO/GEO/SITE, social/ECHO, email/SEND, Paid Ads/ROAS, influencer/STAR, launch/RAMP). Use when a marketing goal is open-ended or spans disciplines, when it is unclear which skill fits, or for requests like 'help with our marketing', 'grow our traffic', 'plan our launch', 'what should we post', 'is our messaging landing' — it infers the discipline and runs the smallest useful workflow. Add --deep for exhaustive, maximum-rigor, or stress-test runs.

Run an email-marketing (SEND) workflow: deliverability/consent setup, segmentation, email creative, lifecycle flows, newsletter monetization, send-testing, and the email-quality audit gate. Not sure? Use /aaron-marketing:auto.

Run an influencer-marketing (STAR) workflow: audience & creator scouting, campaign targeting, briefs, outreach, amplification, and ROI reporting. Not sure? Use /aaron-marketing:auto.

Run a product-launch (RAMP) workflow: positioning and launch tiering, window/early-access design, message house and asset kits, the launch-readiness gate with a T-1 go/no-go, launch-day execution, and the post-launch prove loop. Not sure? Use /aaron-marketing:auto.

Run a brand-narrative & messaging (TALE) workflow: trace the current message and positioning truth, architect the durable message house/voice/story canon, land it consistently across every surface, and evaluate resonance with tests and drift monitoring. Not sure? Use /aaron-marketing:auto.

SEO/GEO end-to-end along the SITE loop: survey demand and competitors, implement content, tune quality/tech/on-page, and evaluate authority/rankings/reports/memory (--phase survey|implement|tune|evaluate). Not sure? Use /aaron-marketing:auto.

Make any song you can imagine

Leading AI-powered video generation platform that specializes in creating hyper-realistic talking avatars

Hermes Agent is an open-source, self-improving autonomous AI agent developed by Nous Research

Kilo Code is a popular, open-source AI coding agent and "agentic engineering" platform designed to help developers build, refactor, and debug software faster

General-purpose agent in one static Go binary. ReAct loop, ACP server for IDEs, OpenAI-compatible REST API with embedded web UI, Telegram gateway, cron schedule…

Autonomous agent framework with structured memory, safety hooks, and loop management. Built by the agent that runs on it.

TSP自托管、零运维的 A 股「选股 + 监控 + 回测」量化工作台 | 基于 TickFlow 数据源 | LLM能力驱使策略定制+个股分析+复盘 | 自由接入第三方数据源与个性化扩展数据 | 个人开源 ,非TickFlow官方项目

Curated, verified Agent Skills powered by ModelStudio.

Run Claude Code, Codex, Antigravity, Cursor Agent and OpenCode as one runtime — persistent sessions, multi-agent councils, an OpenAI-compatible endpoint, an MCP…

pi had nothing (nothing), so I made something (something) — sorry mariozechner-senpai, I went ahead and lovingly soiled your pure pi for you. opinionated fork o…

A persistent workspace for development work that self-improves and continues beyond one session.

Open-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access.

📚 A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | http…

Deterministic, local-first memory and guardrails for AI coding agents with no LLM in the hot path.

Deterministic spec-orchestration for local LLMs in the pi coding agent — drives prompts through refine→research→grill→compose→critique, with bundled web/docs/fe…

Native Safari browser automation for AI agents. 97 tools via AppleScript — zero overhead, keeps logins, runs silently in background. Drop-in alternative to Chro…

Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.

Git for agent memory. Branches, diffs, PRs, and rollback for what your agents know.

Multi-Provider AI Gateway - No personal logs by design. Model autodiscovery, Failover groups, High availability, Android companion app, and more - "Because we h…

Production-grade MCP server for MikroTik RouterOS with secure AI-native network automation.