This repository is a curated collection of tips, scripts, and a Claude Code plugin (dx) that enhances developer workflows with Claude Code. It is primarily a knowledge base and tooling repository, not a standalone application. The core deliverable is the dx plugin, which bundles skills for GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, Reddit/HN research, private GitHub search, and version checks. The repository also includes a custom status line script (context-bar.sh), a setup script for recommended configurations, and extensive markdown content documenting 49 tips for using Claude Code effectively. The architecture is a mix of bash scripts, skill definitions (markdown with YAML frontmatter), and a plugin manifest. The standout component is the half-clone-conversation.sh script, a 400+ line bash utility that clones Claude Code conversations with careful edge-case handling, cross-platform support (macOS, Linux, Windows Git Bash), and a comprehensive 19-test suite. The repository demonstrates high craftsmanship in its bash scripting, thorough testing, and detailed documentation of workarounds for platform limitations (e.g., Reddit's blocking, GitHub's private repo search).
This monorepo (Nx) implements a complete ecosystem for managing and distributing 'skills'—curated, structured instructions for AI coding agents. The codebase reveals a production CLI (`agent-skills`) built with Ink/React for interactive terminal UI, an MCP server (`agent-skills-mcp`) for agent-in-context skill lookup via FastMCP, a Next.js marketplace website for browsing, and a skills catalog with over 150 skill definitions across architecture, cloud, development, quality, security, and other domains. The core library (`@tech-leads-club/core`) uses a clean hexagonal architecture with port/adapter separation for file system, HTTP, environment, logging, and shell operations, enabling testability and future portability. The CLI supports interactive and non-interactive install/remove/update workflows with atomic lockfile writes, append-only audit logging, and content-hash integrity verification. The MCP server implements a progressive disclosure pattern (search → read → fetch/prepare) to minimize token usage, with registry caching and ETag revalidation. The marketplace is highly SEO-optimized with JSON-LD structured data, breadcrumbs, and static generation. Property-based tests (fast-check) for UI components and cache boundaries demonstrate strong engineering discipline. The skills catalog itself is the core product—each skill is a markdown file with YAML frontmatter, optional scripts/references, and trigger phrases, all validated by a custom validation tool and security-scanned in CI. While the architecture is solid and the codebase is actively maintained with frequent releases, some areas show drift risk: duplicate validation scripts across skills, hardcoded benchmark data in the marketplace, and tight coupling to external CDN availability for registry downloads. The cloud-deploy skill references an enormous set of Cloudflare product docs that will inevitably become outdated. Overall, this is a well-crafted, modern TypeScript monorepo that effectively solves the problem of giving AI agents reusable, safe, and discoverable instructions.
This repository provides `mmx-cli`, a TypeScript-based command-line interface for the MiniMax AI platform. It allows users to authenticate, generate text, images, video, speech, perform web search, and manage configuration entirely from the terminal. The codebase is modular with a command registry pattern, supports both OAuth and API key authentication, handles streaming responses (SSE), and includes a programmatic SDK for Node.js/TypeScript consumers. Key architectural patterns include a hierarchical command resolution system, a generic HTTP client with retry and timeout logic, file download utilities with atomic writes, and a polling utility for async task monitoring. The CLI also automates setup for third-party AI coding agents (Claude Code, Codex, Grok, etc.) by writing configuration files. Testing is extensive with a mock server pattern. The tool is dual-region (global and China) with automatic endpoint detection. While early in development (version 0.0.0-dev), the engineering quality is solid with clear separation of concerns, typed error handling, and thoughtful output formatting (text, JSON). Some components like the agent configurator and video generation validation are tightly coupled to MiniMax-specific APIs, but many utility and client modules exhibit patterns reusable in other CLI tools or API wrappers.
This is a full-stack cultivation world simulator game (xianxia RPG) with a Python backend (FastAPI + asyncio) and a Vue 3 + TypeScript + PixiJS frontend, supported by an optional Electron desktop shell for Epic Games Store distribution. The simulation engine runs a month-by-month tick system orchestrating ~29 phases (lifecycle, actions, social, war, world events, etc.) producing emergent narratives driven by LLM calls (OpenAI/Anthropic compatible) for character decisions, story generation, world lore rewriting, and roleplay interactions. The codebase is heavily data-driven with static game configurations (sects, techniques, items, regions) loaded from CSV files and multi-language localization via gettext PO files. It exposes a public REST API (query/command) and WebSocket for real-time state updates, supports save/load with JSON snapshots and SQLite event storage, and includes comprehensive test coverage (pytest, vitest, Playwright) and CI/CD workflows. While the architecture shows strong engineering patterns (effect system, action registry, single-choice decision framework, phased simulation pipeline), it carries risks from tight coupling of global singleton registries, LLM dependency, and use of `eval` in effect conditions.
Optio is a self-hosted, Kubernetes-native orchestration platform for AI coding agents (Claude Code, OpenAI Codex, GitHub Copilot, Gemini, Cursor, OpenCode). In production it runs three task tiers — repo tasks (issue/request → agent pod → PR), standalone jobs (parameterized agent runs without repo checkout), and persistent agents (long-lived, message-driven agents with turn-based execution) — plus an autonomous PR review loop. The core loop is driven by ~15 BullMQ workers (task, PR watcher, review, webhook, ticket sync, reconcile, workflow trigger) against a Postgres database, with Redis pub/sub powering a real-time event bus and WebSocket log/terminal/chat streaming to the Next.js dashboard and CLI. Agents execute in ephemeral pods built from per-language Docker images; a K8s-style reconciliation control plane (world snapshot + pure decision functions + CAS-gated executor) converges four run kinds and catches drift. The architecture is a pnpm/turbo monorepo: a Fastify 5 API with Drizzle ORM and Zod-validated OpenAPI schemas; a Next.js 15 admin dashboard (tasks, jobs, reviews, sessions, agents, cluster, analytics); a Commander-based CLI (login, task/repo/session/secret commands over REST + WebSocket); and a static docs site. Shared packages provide a clean AgentAdapter interface (`validateSecrets` → `buildContainerConfig` → `parseResult`), a Docker/Kubernetes container runtime abstraction, ticket provider adapters (GitHub, GitLab, Jira, Linear, Notion), and shared types/utilities (task state machines, repo URL parsing, SSRF guards, cost arithmetic). Workspace-scoped multi-tenancy with admin/member/viewer RBAC, AES-256-GCM secret encryption with AAD binding, WebSocket upgrade tokens, HMAC-signed internal calls, and a security-focused audit trail (optio_actions) are enforced throughout. Engineering strengths: the test suite is unusually thorough for a project this size — nearly every route, service, worker, and shared utility has a unit test, with per-file Postgres/Redis isolation for integration tests, real-server E2E tests using a deterministic fake container runtime (with mock directives like [[mock:pr]]), and Playwright smoke tests. The reconcile pattern, generic state machine utilities, and pure decision functions in `packages/shared/src/reconcile/` are the highest-craftsmanship code. Known debt: five near-duplicate NDJSON event parsers (one per agent, with drift risk), hardcoded model pricing tables in the Codex/Gemini adapters, scattered duplicated workspace-scoping checks, a 60+ file migration history with historical prefix collisions (now script-enforced), and raw SQL in the analytics service. The project moves fast (v0.1 → v0.4.1 within months, last commit 2026-08) and some surface area (OpenCode/OpenClaw adapters, skills marketplace) is explicitly experimental, but the core architecture is coherent and production-oriented.
DeepZero is an automated vulnerability research pipeline engine, primarily targeting Windows kernel driver (BYOVD) analysis. It provides a highly concurrent, resumable orchestration framework where pipelines are defined declaratively in YAML. The engine supports stages: ingest, map (parallel analysis), reduce (aggregation), and bulk_map, with built-in fault tolerance, atomic state persistence, and live progress dashboards. It integrates external tools like Ghidra (headless decompilation), Semgrep (static analysis), LIEF (PE parsing), and LLM backends (LiteLLM, Claude Code) for exploitability assessment. The repository includes a full reference pipeline (loldrivers) and multiple language documentation sites. While primarily an application framework, it has strong data research characteristics due to its focus on binary corpus analysis and heuristic/AI assessment.
Fonnx is a Flutter plugin that enables cross-platform, on-device machine learning inference by wrapping the ONNX Runtime engine. It provides a unified Dart API that abstracts away the complexities of native FFI (for iOS, Android, macOS, Windows, Linux) and WebAssembly (for web), allowing developers to run models like OpenAI Whisper, Silero VAD, Magika, and various text embedding models without cloud dependencies. The codebase exhibits high software craftsmanship. Its architecture uses conditional Dart imports to cleanly separate native and web backends, employs Dart isolates for offloading heavy inference tasks, and implements a custom RPC protocol for web workers. A standout feature is its robust native memory management, including a C finalizer tested with sanitizers to prevent leaks during Flutter hot-restarts. While primarily a software library, it bridges the gap between ML research and production by bundling specific, optimized ONNX models and providing a deterministic test corpus with golden outputs. It is an excellent resource for Flutter developers building privacy-focused, offline-first AI applications, though its reliance on pinned native assets and specific build tooling introduces a moderate technical drift risk.
GEO Optimizer is a Go library for Generative Engine Optimization that improves content visibility in AI search engines. It features a layered architecture with LLM abstraction, rule-based content scoring, and pluggable optimization strategies. The system optimizes content through a pipeline that applies strategies like structure enhancement, schema generation, and FAQ creation, using LLMs to generate optimized content while tracking improvements through scoring mechanisms. Key design patterns include the strategy interface for interchangeable optimizations and modular separation of concerns in the scoring system.
PhotoPrism is a self-hosted photo management server that indexes, organizes, and serves personal photo and video collections. In production, it extracts EXIF/XMP/IPTC metadata, generates thumbnails and previews, transcodes videos, performs AI-powered object/face recognition and NSFW detection, and provides a web UI for browsing, searching, sharing, and editing media. It also supports WebDAV access, OAuth2/OIDC authentication, and multi-instance clustering. The architecture is a monolithic Go application with a REST API (Gin framework) and a Vue.js frontend. It uses a relational database (MariaDB/MySQL or SQLite) via GORM. Background workers handle indexing, face recognition, place detection, and cleanup. It integrates with external tools: FFmpeg for video transcoding, libvips for image processing, TensorFlow/ONNX for AI models, and exiftool for metadata extraction. The frontend communicates via REST and WebSocket. Key entry points include the CLI (cmd/photoprism/photoprism.go) with subcommands for import, index, search, and user management, and the API layer (internal/api) exposing endpoints for photos, albums, labels, faces, places, and vision. The indexing pipeline scans configured directories, extracts metadata, generates thumbnails, runs AI models, and stores results in the database. The system also supports background sync with remote WebDAV services and backup/restore. External dependencies include FFmpeg, exiftool, libvips, TensorFlow, ONNX Runtime, Darktable, RawTherapee, yt-dlp, and various Go libraries. It can optionally integrate with OpenAI/Ollama for vision captioning. The codebase is large and mature, with extensive utility packages and a well-organized module structure.
PageIndex is a production-ready RAG framework that replaces vector databases with a reasoning-based, hierarchical tree index over documents. Its core innovation is the 'flash' pipeline: a sophisticated, LLM-free PDF structure extractor that uses character-level layout analysis, trie-based keyword matching, and heuristic classification to build a table of contents tree from PDFs in seconds. The system then enables agentic retrieval by feeding this tree to an LLM, which reasons over the hierarchy to find relevant pages without embedding or chunking. The repository provides a full Python SDK (PageIndexClient) with local and cloud modes, CLI tool, integrations with OpenAI Agents SDK, Anthropic SDK, and Claude Agent SDK, plus an MCP bridge for remote tool execution. While primarily an application, it contains a deep research-grade data processing pipeline (flash) with extensive multilingual dictionaries and layout analysis heuristics, giving it a hybrid character. The codebase is well-structured with clear module boundaries, extensive test coverage, and reusable patterns like the tool contract system and trie-based matching. However, it carries medium technical drift risk due to hardcoded thresholds, dependency on private APIs of LLM frameworks, and pdfium version sensitivity.
CopilotKit is a comprehensive SDK and framework designed to integrate AI agents into user interfaces across web, mobile, and chat platforms. It functions as a middleware layer connecting frontend UI components (React, Vue, Angular) with backend agent frameworks (LangGraph, CrewAI, PydanticAI, etc.). The core value proposition lies in its ability to synchronize state between the agent and the UI, support generative UI (A2UI) for dynamic component rendering, and facilitate human-in-the-loop workflows. The repository is structured as a monorepo containing core runtime packages, framework-specific adapters, and an extensive suite of integration showcases. The architecture relies on a centralized runtime (`@copilotkit/runtime`) that handles agent connections via SSE and manages tool execution. Frontend interactions are managed through hooks (`useCopilotKit`, `useAgent`) that subscribe to the runtime. The codebase demonstrates a polyglot approach, supporting Python, TypeScript, Java, and C# backends alongside multiple frontend frameworks. While the core SDK is well-structured, the repository exhibits significant code duplication across its 20+ integration showcases, which serve as both documentation and regression tests.
Onyx is a comprehensive enterprise AI platform that provides knowledge retrieval, chat, and document indexing across 50+ third-party sources. The codebase reveals a FastAPI backend with Celery workers, PostgreSQL with Alembic migrations, OpenSearch vector search, Redis caching, and a separate model server. The frontend is a Next.js application with a custom design system (opal), alongside React Native mobile app, Go CLI, Chrome extension, and an embeddable widget. The platform supports deep research, custom agents, MCP servers, sandboxed code execution (Craft), and enterprise features like SSO, SCIM, billing, and multi-tenancy. Architecture is well-structured with clean separation of concerns, but the large codebase shows some drift: platform duplication across web/mobile/CLI, extensive Alembic migration history, and lint debt. The connector framework and design system are high-quality reusable components.
Cognee is an open-source AI memory platform that enables agents and applications to build, store, and query persistent knowledge graphs from documents, code, and conversations. The system provides a Python SDK, a FastAPI REST API, a CLI, a Next.js frontend, and an MCP server for agent integration. Core operations include ingesting data (remember), extracting entities and relationships via LLMs or GLiNER (cognify), retrieving context (recall), and self-improvement loops (improve). The architecture is modular with adapter/registry patterns for graph databases (Ladybug, Neo4j, Turso), vector stores (LanceDB, PGVector), LLM providers (LiteLLM, OpenAI, Anthropic, Ollama), and integrations (Slack, GitHub, Google Drive). The frontend provides a dashboard for dataset management, knowledge graph visualization, and business analytics. The project also includes an evaluation framework for benchmarking retrieval strategies against standard datasets like HotpotQA and BEAM. While production-grade in many areas, some components are marked as demo-quality or have cloud-only stubs.
Serena is a production-grade MCP (Model Context Protocol) server that provides AI coding agents with deep code intelligence across 40+ programming languages. It acts as an 'IDE for your agent', offering symbol-level retrieval, editing, refactoring, and debugging capabilities by orchestrating Language Server Protocol (LSP) backends. The system is designed to integrate with AI clients like Claude Code, Codex, Copilot, and Grok, exposing a rich set of tools for file manipulation, symbol navigation, memory persistence, and project configuration. Architecturally, Serena is a Python application with a CLI entry point that starts an MCP server, a Flask-based web dashboard for monitoring and configuration, and a hooks system for client-side pre-tool-use events. Its core is the `solidlsp` package, a custom synchronous LSP abstraction layer that manages the lifecycle of 40+ language servers (Python, TypeScript, Rust, Go, Java, etc.), handling initialization, capability negotiation, and request/response framing. The `interprompt` library provides a sandboxed Jinja templating engine for prompt generation, and the memory manager persists project-specific context across sessions. Key features include: multi-language symbol search, references, definitions, hover, rename, and diagnostics; a code editor abstraction supporting both LSP and JetBrains backends; a configurable tool registry with automatic discovery; and a comprehensive test suite with per-language integration tests. The project emphasizes reproducibility through pinned dependency versions and SHA256 verification for downloaded language server binaries, though this creates a maintenance burden as versions must be manually updated.
Databend is an open-source, cloud-native distributed SQL query engine and data warehouse, built in Rust. It provides a full SQL interface for analytical workloads, supporting operations such as SELECT, INSERT, COPY INTO/OUT, MERGE INTO, and complex aggregations with window functions, subqueries, and joins. The architecture follows a storage-compute separation model: a metadata service (Meta) manages schemas, users, and catalogs via a Raft-based consensus layer, while query nodes handle SQL parsing, planning, optimization (Cascades optimizer with rule-based and cost-based passes), and distributed execution over a pipelined framework. Multiple storage engines are supported, including a native columnar Fuse engine optimized for cloud object stores (S3, MinIO, Azure Blob), as well as external formats like Iceberg, Delta Lake, Hive, Paimon, Parquet, and ORC. The system exposes access via MySQL wire protocol, HTTP API, Flight SQL, and gRPC, and includes enterprise features such as data masking, row access policies, materialized views, streams, network policies, and role-based access control.
mcp-agent is a Python framework for building, deploying, and serving AI agents that interact with the Model Context Protocol (MCP). In production, it provides a library and CLI toolkit that allows developers to compose agents using configurable LLM providers (OpenAI, Anthropic, Azure, Bedrock, Ollama, Google), connect to any MCP server (stdio, SSE, Websocket, Streamable HTTP), and orchestrate multi-step workflows with patterns like parallel fan-out/fan-in, router, orchestrator-worker, evaluator-optimizer, and swarm. The framework is architecture-agnostic, supporting both asyncio in-process execution and durable execution via Temporal for long-running, fault-tolerant agent loops. The system ships with a feature-rich CLI (mcp-agent) for local scaffolding, configuration, and cloud deployment to MCP Agent Cloud, including secret management, log tailing, and OAuth integration. Key entry points include the main application bootstrap (MCPApp), the Agent class (managing MCP server connections and LLM), workflow implementations in src/mcp_agent/workflows/, and the server module that exposes agents as MCP servers via FastMCP. The codebase is well-structured with clean abstractioons (ContextDependent, AugmentedLLM base), extensive testing (over 100 test files), and comprehensive observability through OpenTelemetry tracing, token counting, and structured logging. Use cases range from simple chat agents to complex research assistants, real estate analyts, and customer service desks with swarm routing. The framework is actively maintained with frequent commits, a large community, and is built to production standards.
MCP-UI is a monorepo SDK implementing the MCP Apps standard for rendering interactive UIs over the Model Context Protocol. It provides server-side tools (in TypeScript, Python, and Ruby) to create UI resources, and a client-side React SDK to render them in sandboxed iframes. The architecture centers on a secure double-iframe proxy pattern that isolates third-party HTML and external URLs, with JSON-RPC communication via AppBridge. The codebase is well-structured with comprehensive tests, semantic release automation, and cloudflare workers example, demonstrating strong engineering practices across multiple languages.
Text Embeddings Inference (TEI) is a production-grade inference server for open-source text embedding models, built in Rust with multiple backend implementations (Candle, Python, ONNX). The system exposes both HTTP (REST) and gRPC APIs supporting dense and sparse embeddings, reranking, sequence classification, and OpenAI-compatible endpoints. It features dynamic batching with cumulative sequence length management, flash attention optimization across CUDA compute capabilities, and comprehensive observability with Prometheus metrics and OpenTelemetry tracing. The architecture cleanly separates the router layer (HTTP/gRPC handling) from the core inference pipeline (tokenization, batching, backend dispatch) via the `Backend` trait, allowing seamless integration of different model backends and hardware targets including CPU, CUDA, ROCm, Intel, and ARM64. The codebase demonstrates strong engineering practices: modular neural network layer implementations (Linear, LayerNorm, RMSNorm, Rotary) reused across model architectures, snapshot-based regression testing for all supported models, and feature-gated builds for precise dependency control. The router provides production features such as CORS, API key authentication, request size limits, health checks, and graceful shutdown. The batching system (`Queue` struct) efficiently accumulates requests and dispatches them to the backend in configurable token-bucket sizes. While the engineering quality is high, the repository exhibits some maintenance risks: significant model duplication across `flash_` and non-flash variants for each architecture, patched upstream dependencies (candle, cudarc) that may diverge from official releases, and commented-out integration tests. The Python backend, wrapping a subprocess, introduces platform-dependent fragility, and the large number of hardware-specific Dockerfiles increases build complexity. Overall, TEI is a well-architected, actively maintained inference server suitable for production deployments, with reusable patterns in its backend abstraction, batch processing, and layer implementations.
This repository provides client-side integrations, tooling, and examples for Zep, a long-term memory platform for AI agents built on temporal knowledge graphs. It is not the Zep service itself but the ecosystem to use it. The codebase includes SDK packages for over a dozen AI agent frameworks (Google ADK, AutoGen, CrewAI, LangGraph, Pydantic AI, LiveKit, Mastra, Vercel AI SDK, Microsoft Agent Framework, Strands, AG2) in Python, TypeScript, and Go. Each integration follows a consistent pattern: out-of-band provisioning of users and threads (server-generated UUIDs), automatic context injection before each LLM call, and on-demand graph search tools. The repository also contains a standalone ingestion pipeline (zep-ingest) for bulk-loading historical data (Slack exports, emails, documents, transcripts) into Zep graphs, a Model Context Protocol (MCP) server exposing Zep graph tools, benchmarks (LoCoMo, LongMemEval) for evaluating long-term memory retrieval, and an evaluation harness for testing retrieval and question-answering accuracy. While primarily an application-focused repository, it includes data pipeline components and evaluation frameworks that give it a hybrid character.
This repository is a production-grade Model Context Protocol (MCP) server that bridges AI assistants to Figma. It exposes 100+ MCP tools for reading and manipulating Figma files, variables, components, styles, FigJam boards, Slides, version history, tokens, and accessibility audits. The architecture is dual-mode: a local Node.js server (`src/local.ts`) communicates over stdio to AI clients and via WebSocket to a bundled Figma Desktop Bridge plugin, while a Cloudflare Workers variant (`src/index.ts`) supports cloud sessions with OAuth and a Durable Object WebSocket relay. The Desktop Bridge is the primary data channel, with Figma REST API fallbacks for scenarios where the plugin is unavailable or limited to certain plans. Beyond basic Figma CRUD, the codebase contains substantial engineering investment in design-token synchronization: canonical DTCG-aligned token documents round-trip through parsers and formatters for CSS variables, Tailwind v3/v4, SCSS, TypeScript modules, Style Dictionary, and Tokens Studio. A separate extraction engine (`src/core/extraction/`) mines production codebases for styling conventions and scaffolds design-system packages, while a scoring engine produces weighted design-system health dashboards. These components give the repo a hybrid quality: it is fundamentally an application, but its token pipeline and codebase-analysis subsystems are data-engineering-like assets that could be reused independently. The codebase demonstrates strong engineering practices: strict Zod schemas, consistent tool registration factories, connector abstraction, extensive Jest test coverage, atomic file writes, adaptive response compression, and careful caching/invalidation. However, it also carries meaningful debt: some token parsers are unimplemented stubs, a few files are monolithic (`figma-tools.ts`, `src/local.ts`), local/cloud connector implementations must be kept in sync manually, and some documentation references outdated internal paths. Overall, this is a mature, feature-rich MCP server with several genuinely reusable components for anyone building design-tool pipelines, token bridges, or local process-lifecycle infrastructure.