Oh-My-ClaudeCode (OMC) is a multi-agent orchestration layer for Claude Code, Anthropic's AI coding assistant. It extends Claude Code with a plugin system, custom MCP tools, a team collaboration engine, a real-time HUD, and a rich hook system. The system is implemented in TypeScript and runs as a CLI tool (`omc`), an npm package (`oh-my-claude-sisyphus`), and a Claude Code plugin. It manages autonomous coding pipelines (autopilot, ralph), multi-worker team sessions via tmux, skill learning and injection, and provides extensive tooling including LSP integration, AST analysis, Python REPL, and git-based checkpoints. Architecturally, OMC is a modular monolith with clear separation: a CLI entry point (Commander-based), a hook registry with ~20+ lifecycle hooks (session-end, pre-tool-use, persistent-mode, etc.), a team subsystem with state machines and tmux-based worker management, a HUD rendering engine, and a standalone MCP server exposing 33+ tools. The system integrates with multiple AI providers (Claude, Codex, Gemini, Grok, Cursor) and git hosting providers (GitHub, GitLab, Azure DevOps, Bitbucket, Gitea). External dependencies include `@anthropic-ai/claude-agent-sdk`, `@modelcontextprotocol/sdk`, `better-sqlite3`, `zod`, and `commander`. Key data flows include: user input → CLI or Claude Code hook → hook dispatcher → feature modules (autopilot, team, skills) → tool execution → state persistence (filesystem, SQLite). The system maintains extensive state on disk (`.omc/state/`, session transcripts, team events, skill files) and uses file-based locking for concurrency safety. The JEV shadow judgment system provides non-blocking evaluation of heuristic decisions against an external API for quality monitoring. The codebase demonstrates strong engineering practices: extensive test coverage (~3000+ tests), modular architecture with clear interfaces, atomic file operations, and security-conscious utilities (SSRF guard, token redaction, path traversal prevention). It is actively maintained with frequent releases and responsive issue triage.
Claude HUD is a real-time statusline plugin for Claude Code, the AI coding assistant. It runs as a subprocess and renders a multi-line or compact HUD below the input field, displaying context usage, rate limits, active tools, running agents, todo progress, git/jj status, memory usage, and cost tracking. The system reads session data from stdin (JSON payload) and optionally parses the Claude Code transcript JSONL file for detailed tool/agent activity. It is highly configurable with ~60+ options for layout, colors, visibility, and i18n (English, Simplified/Traditional Chinese). The architecture is modular: a CLI orchestrator (src/index.ts) loads config, runs git/jj/memory/extra-cmd in parallel, then renders via a pure render layer. It uses no external npm dependencies, relying on Node.js built-ins and child processes. The codebase demonstrates strong engineering practices: extensive test coverage (unit, integration, golden snapshot tests), dependency injection for testability, atomic file writes for persistent state, and thorough sanitization of untrusted inputs to prevent terminal injection. It is actively maintained with frequent releases and CI/CD pipelines.
This repository is a Claude Code marketplace providing Language Server Protocol (LSP) plugins for enhanced code intelligence. It contains self-contained plugin directories for over 30 programming languages, each with plugin.json metadata and .lsp.json LSP configuration files. The repository includes validation and synchronization scripts that ensure consistency between plugin definitions and the marketplace manifest (.claude-plugin/marketplace.json). When installed through Claude Code's plugin system, these plugins enable features like go-to-definition, find-references, hover info, and symbol search for respective languages.
Ponytail is a skill ecosystem for AI coding agents that enforces a 'lazy senior developer' mindset through a priority ladder: YAGNI, reuse existing code, prefer stdlib/native features, avoid unrequested abstractions, and write minimal working code. It delivers this via platform-specific adapters (hooks, command files, plugin manifests) for agents like Claude Code, Codex, GitHub Copilot, OpenCode, Gemini CLI, and others. The core skill definition lives in skills/ponytail/SKILL.md, with companion skills for review, audit, debt tracking, gain scoring, and help. The system includes automated validation scripts to maintain consistency across platform-specific rule copies and version manifests, benchmark suites to measure code/token/cost reductions, and test coverage for hook behavior and plugin integrity.
claude-mem is a persistent memory system for AI coding assistants, primarily targeting Claude Code but also supporting Codex, Cursor, Windsurf, OpenClaw, and other platforms. It captures observations, summaries, and user prompts from coding sessions via lifecycle hooks (SessionStart, PostToolUse, etc.), stores them in SQLite (local) or Postgres (server), and injects relevant context into future sessions to maintain continuity across agent interactions. The system operates as a background worker daemon (Bun) or a multi-user server (Express + BullMQ + Valkey) with API key authentication, team/project scoping, and rate limiting. Architecturally, claude-mem is a hybrid of a CLI plugin and a standalone server. The CLI component integrates into IDEs via hook scripts and MCP servers, while the server component provides REST APIs for memory management, search, and cloud sync. It features a dual-storage backend (SQLite for local, Postgres for server) with vector search via ChromaDB and full-text search via SQLite FTS5. The system includes a React-based viewer for browsing memory feeds, telemetry (opt-out PostHog), and a Cloudflare Workers-based sync hub for cross-device synchronization. The codebase demonstrates strong engineering practices with well-abstracted components (search strategies, provider abstraction, atomic file operations, telemetry scrubbing) but carries some technical debt from its dual-runtime evolution (legacy worker vs. server-beta) and extensive Windows-specific workarounds. It is actively maintained with frequent releases and comprehensive test coverage.
The Agentic Startup repository is a spec-driven development (SDD) framework for Claude Code that enables multi-agent AI collaboration for software development. It provides a structured workflow: specify → validate → implement → test → review → document, with optional skills for analysis, refactoring, debugging, and constitution enforcement. The framework uses three implementation tiers (Direct, Incremental, Factory) selected by an automatic complexity classifier, and enforces quality gates through validation checks, drift detection, and constitution-based governance rules (L1/L2/L3 levels). Key features include progressive disclosure for context efficiency, information barriers to prevent bias, and automatic documentation generation. The system is designed as a plugin-based architecture with 'start' (core workflow) and 'team' (specialized agents) components, storing specifications in .start/specs/ and generating documentation in docs/.
This repository is a meta-skill/plugin for Claude Code that serves as a 'team-architecture factory'. It is not a traditional software application but a collection of highly structured Markdown files (SKILL.md and references) that act as instructions for the Claude Code AI to design and evolve multi-agent teams. The system takes a domain description from a user and generates agent definitions, skills, and orchestrators to automate complex workflows. It demonstrates deep expertise in multi-agent orchestration: three execution modes (workflow orchestration, persistent agent collaboration, sub-agent delegation), six team architecture patterns, and workflow-native quality patterns (adversarial verification, judge panels, loop-until-dry). The project underwent a ground-up rebuild from v1 to v2 to align with the current Claude Code runtime, removing reliance on deprecated APIs like TeamCreate. The codebase is exceptionally well-documented for its domain, with clear principles, phased workflows, testing methodologies, and migration guides. The primary artifact is documentation, not executable code, which limits traditional software engineering evaluation but the craftsmanship in structuring meta-instructions for an AI is high. It is actively maintained with recent commits, thorough changelog, and professional issue templates.
Total Recall is a memory system for Claude Code that provides persistent, curated memory across sessions. It implements a tiered architecture with daily logs for raw capture, registers for structured domain knowledge, working memory for essential context (auto-loaded every session), and archive for historical data. The core innovation is its write gate mechanism that evaluates whether information should be saved based on whether it changes future behavior, preventing memory bloat. The system includes automatic hooks for session context loading and pre-compaction flushing, a sophisticated ID-based metadata system for tracking memory entries, and maintenance routines for pressure-based cleanup. It's designed as both a plugin and standalone installation with comprehensive slash commands for all memory operations.
A Claude Code and Cursor plugin that delivers behavioral guidelines for AI coding assistants, derived from Andrej Karpathy's observations about LLM coding pitfalls. The core artifact is a single CLAUDE.md file (and its Cursor rules equivalent) encoding four principles: Think Before Coding, Simplicity First, Surgical Changes, and Goal-Driven Execution. The repository packages this file as a Claude Code plugin with marketplace metadata, a Cursor project rule with alwaysApply, and a reusable skill definition. The EXAMPLES.md file provides detailed before/after code examples demonstrating each principle. The entire functional surface is documentation-as-configuration — there is no application logic, data processing, or runtime code. The plugin packaging is clean with proper marketplace.json and plugin.json manifests. The Cursor rule is correctly structured with frontmatter. The examples are concrete and well-annotated, showing realistic LLM mistakes and corrections. The Chinese README translation is a nice touch for accessibility. This is essentially a configuration and documentation project that delivers genuine value through carefully crafted AI assistant instructions.
This repository is a comprehensive plugin and skill set for Claude Code (and compatible CLI assistants like Codex CLI and OpenCode), designed to transform the AI into a semi-automated research assistant for academic and software development workflows. It is not a standalone application but a configuration package that installs skills, commands, agents, hooks, and rules into the user's Claude environment. The architecture follows a skill-based pattern: each skill is a directory with a SKILL.md entry point, references, examples, and optional scripts, all consumed by the AI at runtime. The repository covers the full research lifecycle—ideation, literature review (via Zotero MCP and arXiv APIs), experiment analysis, ML paper writing with conference-specific LaTeX templates (NeurIPS, ICLR, ICML, ACL, AAAI), reviewer response drafting, publication chart creation, and post-acceptance promotion. It also integrates deeply with Obsidian for project knowledge management and includes a meta-toolchain for developing and QA-ing skills themselves. While primarily an application configuration, it contains substantial research-oriented content (Kaggle competition analyses, citation verification workflows, writing pattern references), making it a hybrid tool that bridges software engineering and data science research. The codebase is actively maintained, well-documented, and demonstrates strong craftsmanship in its script utilities and hook infrastructure.
This repository is a Python library and Claude Code plugin for generating McKinsey-style PowerPoint (PPTX) presentations. It provides ~40 slide templates (executive summaries, charts, matrices, org charts, roadmaps, etc.) with a consistent deep-navy/bright-blue design system. The core architecture is a builder pattern: `PresentationBuilder` accepts slide specs (as dicts or keyword arguments) and delegates to slide-specific drawing functions in the `slides/` subpackage. A CLI (`mckinsey_pptx.cli`) reads JSON specs and produces `.pptx` files. The Claude Code integration includes an agent definition (`mckinsey-slide-agent.md`) that reads a template catalog, plans a deck story arc, generates a Python build script, executes it, and optionally renders PNG previews via LibreOffice/Poppler. The code is well-structured with a clean separation of concerns: theme dataclasses, base primitives, slide templates, and a builder. The adaptive slide type inference (`infer_slide_type`) is a clever design pattern that allows the same API to accept loosely-typed payloads. The library is production-ready, with provenance from a real consulting tool (AX Labs).
tsumiki is a Claude Code plugin and skill library that operationalizes AI Test-Driven Development (AITDD). It exposes slash commands (`/dev-impl`, `/dev-debug`, `/ipa-security-check`, `/orchestrate`) and Markdown-based skills that guide an AI coding agent through a Red-Green-Refactor-Validation cycle. The repository is not a standalone runtime; it is a development methodology toolkit whose primary artifacts are command definitions, skill instructions, and workflow orchestration logic consumed by Claude Code.
This repository is a plugin for Claude Code, providing a set of 10 structured 'skills' based on the book 'The Minimalist Entrepreneur' by Sahil Lavingia. Each skill is a Markdown file with YAML frontmatter that defines a command name, description, and a detailed system prompt. When installed, Claude Code can invoke these skills via slash commands (e.g., `/find-community`, `/mvp`) to guide users through business advice frameworks. The repo contains no executable code, tests, or CI/CD pipelines—it is purely a collection of well-organized prompt templates. The architecture is trivial: a plugin manifest and a directory of skill files. While the content is thoughtfully crafted and follows a consistent structure, there is no software craftsmanship to evaluate; the repo's value lies in its instructional design rather than code quality. It is actively maintained by the book's author and serves its niche purpose effectively, but it offers no reusable software components for other projects.