LLM Mart Basic

Merge multiple partial requirements YAML files from different readers into one consolidated req.yaml. Detects field conflicts between sources, identifies critical gaps, and produces a gap report. Run after all readers, before the gap-filling interview in arch-requirements.

Architecture committee review. Evaluates a diagram or design document against enterprise standards with structured scoring per dimension. Produces a gate decision: APPROVED / APPROVED WITH CONDITIONS / REJECTED. Use when: preparing for architecture review board, requesting commit

Deep-dive security audit of a technical architecture diagram. Focused exclusively on authentication, authorization, credential protection, network boundaries, and data classification. Does NOT score overall quality — produces a prioritized security finding list. Use after arch-va

Validate a technical architecture diagram image against enterprise architecture standards. Scores six dimensions (10 pts total), outputs structured JSON + text report. Use when: reviewing a draw.io export, checking a new design before committee review, or running CI validation on

Pipeline gatekeeper that enforces the mandatory ArchHarness stage order (requirements -> design -> draw -> validate -> enforce -> security/review -> optimize -> report). Uses the executable `archharness workflow` state machine — checks recorded manifests and gate decisions before

Use when establishing branching strategies, implementing Conventional Commits, creating or reviewing PRs, resolving PR review comments, merging PRs (including CI verification, auto-merge queues, and post-merge cleanup), managing PR review threads, merging PRs with signed commits,

Set up, evolve, or operate a hraness/wordcell local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design Wordcell conventions or a recurring Wordcell ritual; search or query a Wordcell or Obsidian vault; load or recover repository context, plans,

End-to-end reviewer for a completed multi-phase feature at the end of a phase-orchestrator run. Use after all requested phases are finalized: inspects the whole feature against the plan and PRD/spec, hunting integration bugs across phase boundaries, missing acceptance criteria, s

Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless co

Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and p

Reviews and fixes a just-implemented phase of a multi-phase plan during a phase-orchestrator run. Use after a phase's implementation and initial validation: checks the phase against the plan, PRD/spec, repo conventions, security, tenancy/data ownership, migrations, and test cover

Writes or restructures an implementation plan in the format the phase-orchestrator skill consumes: dependency-ordered phases with explicit scope, acceptance criteria, validation commands, and status/log conventions. Use when the user asks to write a plan for phase orchestration,

Build a complete account sheet before a meeting - company, people, news, tech, pains, and talking angles. Use before any important prospect or client interaction.

Produce complete ad creative sets - concepts, hooks, copy, AI-generated images and videos declined per platform and format. Use for Meta, Google, LinkedIn, TikTok campaigns and product launches.

Choose the right depth of reasoning for the task - shallow for routine edits, deep for architecture, security, or ambiguous bugs. Use when work quality depends on thinking harder (or intentionally less).

Read OpenAPI specs, call APIs, validate responses, and draft connectors. Use for integration work, contract testing, and client generation.

Audit the web/API attack surface - authn/authz on endpoints, CORS, CSRF, SSRF, security headers, rate limiting, mass assignment, and OWASP API Top 10. Use for /perimeter, API reviews, or exposed-surface hardening.

Track job applications - statuses, follow-ups, interviews, and reminders - in a structured pipeline. Use to keep a job search organized.

Default Navin skill for architecture and technical diagrams. Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle diagrams as explorable HTML with inline SVG (PNG/SVG/WebM export). Use for system architecture, infrastructure topology, PPT/deck dia

Score CV-to-job-offer match, identify missing keywords, and check ATS parseability. Use before submitting any application.

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.

Plan and organize sprint workflows

Generate daily standup reports

Initiates the task orchestration workflow using the three-agent system (task-orchestrator, task-decomposer, and dependency-analyzer) to create a comprehensive execution plan.

Check the current status of tasks in the orchestration system with various filtering and reporting options.

Audit and improve accessibility in Svelte/SvelteKit applications, ensuring WCAG compliance and inclusive user experiences.

Create new Svelte components with best practices, proper structure, and optional TypeScript support.

Help debug Svelte and SvelteKit issues by analyzing error messages, stack traces, and common problems.

Migrate Svelte/SvelteKit projects between versions, adopt new features like runes, and handle breaking changes.

Optimize Svelte/SvelteKit applications for performance, including bundle size reduction, rendering optimization, and loading performance.

Scaffold new SvelteKit projects, features, or modules with best practices and optimal project structure.

Migrate Storybook configurations and stories to newer versions, including Svelte CSF v5 and @storybook/sveltekit framework.

Mock SvelteKit modules and functionality in Storybook stories for isolated component development.

Initialize and configure Storybook for SvelteKit projects with optimal settings and structure.

Create comprehensive Storybook stories for Svelte components using modern patterns and best practices.

Diagnose and fix common Storybook issues in SvelteKit projects, including build errors, module problems, and configuration issues.

General-purpose Storybook assistance for SvelteKit projects, including setup guidance, best practices, and common tasks.

Analyze test coverage, identify testing gaps, and provide recommendations for improving test coverage in Svelte/SvelteKit projects.

Troubleshoot and fix failing tests in Svelte/SvelteKit projects, including debugging test issues and resolving common testing problems.

Set up comprehensive testing infrastructure for Svelte/SvelteKit projects, including unit testing, component testing, and E2E testing frameworks.

Create comprehensive tests for Svelte components and SvelteKit routes, including unit tests, component tests, and E2E tests.

Your Personal AI Assistant; easy to install, deploy on your own machine or on the cloud; supports multiple chat apps with easily extensible capabilities.

Agent OS: the agent gets smarter on its own. We just hold the line: the grading command and expected result never make it into the success contract we hand it.…

Curated systems, benchmarks, and papers etc. on memory for LLMs/MLLMs --- long-term context, retrieval, and reasoning.

:memo: Vimlike Modal Text Editor in Rust

CI-native security testing for MCP servers. Attack simulation, schema drift detection, and health scoring before agents depend on them.

Hermes Agent memory plugin/provider for scope-aware recall, SQLite truth, LanceDB semantic search, and hybrid retrieval.

For You Agent——AI 时代的个人随身数字人格。把你的模型、AI 账号、技能、提示词和工作方式，带到每一个 AI 工具里。

A coding agent: give it a prompt and it reads, writes, runs commands, and searches code in a loop until the work is done, using native tool-calling across OpenA…

A secure persistent personal agent server in Rust. One binary, sandboxed execution, multi-provider LLMs, voice, memory, Telegram, WhatsApp, Discord, Teams, and…

Self-evolving agent: grows skill tree from 3.3K-line seed, achieving full system control with 6x less token consumption

DeepSeek Harness Desktop (dsh-desktop). EAC: Embracing All Creation (揽尽万象). Bundled Node.js runtime with full dsh-CLI kernel, one-click startup, 10 built-in UI…

See your agent think. Zero-config observability & governance for 26 AI agent runtimes: Claude Code, Cursor, OpenAI Codex, GitHub Copilot, Gemini CLI, Cline, Ope…

Save 94% on AI coding tokens. Index your codebase, agents search instead of reading files. Works with Claude Code, Codex, Copilot, Cursor, Gemini CLI. Local MCP…

Yet another coding agent harness, lightweight and written in go.

a coding Agent from pi. ∞ providers, sub-agents, hashline edits, and a permission gate

Omnigent is an open-source AI agent framework and meta-harness: orchestrate Claude Code, Codex, Cursor, Pi, and custom agents — swap harnesses without rewriting…

🧠 Leon is your open-source personal assistant.

The Station, an open-world multi-agent environment that models a miniature scientific ecosystem.

The Frontend Stack for Agents & Generative UI. React, Angular, Mobile, Slack, and more. Makers of the AG-UI Protocol

VelaTerm = iTerm2 + Codex, The Best Terminal for AI Coding