Task Master is a monorepo providing an AI-driven task management system designed for integration with AI coding assistants (Claude Code, Cursor, Windsurf, etc.). It consists of a CLI tool (`task-master`), an MCP server, a VS Code extension, and core library packages. The system manages tasks with statuses, priorities, dependencies, tags, and subtasks, and offers AI-assisted operations like PRD parsing, task expansion, complexity analysis, and TDD workflow automation (autopilot). It supports multiple storage backends (local JSON files, remote Hamster API via Supabase) and 15+ AI providers. The architecture follows a clean layered pattern with domain modules in `@tm/core` consumed by CLI and MCP interfaces, though a legacy `scripts/` directory still contains overlapping logic being gradually migrated. The codebase demonstrates strong engineering practices including factory patterns, abstract base classes, dependency injection, atomic file operations, and extensive test coverage. Some technical drift is present due to the ongoing migration from JavaScript to TypeScript and duplicated MCP server implementations.
This repository is a curated collection of system prompts, tool definitions, and behavioral configurations extracted from dozens of commercial and open-source AI coding assistants and products. It contains over 100 text files organized by vendor (Anthropic, Cursor, VSCode Agent, Manus, Devin, Replit, etc.), each representing a snapshot of how these AI agents are instructed to behave, what tools they can use, and what safety rules they follow. The collection is not an application or a data pipeline; it is a reference archive for researchers, prompt engineers, and developers studying AI agent design patterns, prompt injection risks, and competitive analysis. The repository includes both full system prompts (e.g., Claude Code 2.0, Cursor Agent, Manus) and structured tool JSON schemas that define function-calling APIs. While the content is valuable for understanding AI agent architecture, the repository itself has no executable code, no versioning of individual prompts, and no automated validation, making it a static snapshot rather than a living project.