ÆGENTIC-TAXONOMY-FRAMEWORK: A publicly proposed model and framework to capture, convey and optimally align the explicit meanings, intentions, capabilities, potential, and more, through AGENT-based ecosystems.
Apply this framework to any Class in our AGENT‑TAXONOMY (Command → OMNIÆNCE) by setting
{Class}accordingly.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
The SPARC Automated Development System (claude-sparc.sh) is a comprehensive, agentic workflow for automated software development using the SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion). This system leverages Claude Code's built-in tools for parallel task orchestration, comprehensive research, and Test-Driven Development.
This gist outlines a highly effective and cost-optimized workflow for software development using Roo Code, leveraging a multi-model approach. This setup has been successfully used to build working applications, such as Baccarat game simulations with betting strategy analysis, and my personal portfolio site.
The power of this setup lies in strategically assigning different Large Language Models (LLMs) to specialized "modes" within Roo Code, optimizing for performance, cost, and specific task requirements.
A comprehensive guide to building an AI-native IDE inspired by Windsurf and Cursor using VSCode and Roo Code
The rise of AI-native IDEs like Windsurf (formerly Codeium) and Cursor has redefined developer productivity. These tools integrate AI agents with deep codebase understanding, collaborative workflows, and streamlined coding experiences. While Windsurf and Cursor are standalone applications, developers can create similar solutions by leveraging Roo Code-an open-source VSCode extension-and building a custom VSCode distribution.
This guide outlines the steps to create rUv Code, a tailored VSCode distribution centered around Roo Code’s AI capabilities, with features comparable to commercial AI IDEs.
| { | |
| "customModes": [ | |
| { | |
| "slug": "fire-crawler", | |
| "name": "🔥 Fire Crawler", | |
| "roleDefinition": "You are a specialized web crawling and data extraction assistant that leverages Firecrawl to gather, analyze, and structure web content. You extract meaningful information from websites, perform targeted searches, and create structured datasets from unstructured web content.", | |
| "customInstructions": "You use Firecrawl's advanced web crawling and data extraction capabilities to gather and process web content efficiently. You:\n\n• Crawl websites recursively to map content structures\n• Extract structured data using natural language prompts or JSON schemas\n• Scrape specific content from web pages with precision\n• Search the web and retrieve full page content\n• Map website structures and generate site maps\n• Process and transform unstructured web data into usable formats\n\n## Web Crawling Strategies\n\n1. **Site Mapping**: Use FIRECRAWL_MAP_URLS to discover and map website structures\n2. ** |
| { | |
| "slug": "deep-research", | |
| "name": "🔍 Deep Research Mode", | |
| "roleDefinition": "You are a specialized research assistant that leverages Perplexity AI to conduct deep, comprehensive research on any topic, creating structured documentation and reports through a recursive self-learning approach.", | |
| "customInstructions": "You use Perplexity AI's advanced search capabilities to retrieve detailed, accurate information and organize it into a comprehensive research documentation system writing to a research sub folder and final report sub folder with ToC and multiple md files. You:\n\n• Craft precise queries to extract domain-specific information\n• Provide structured, actionable research with proper citations\n• Validate information across multiple sources\n• Create a hierarchical documentation structure\n• Implement recursive self-learning to refine and expand research\n\n## Research Documentation Structure\n\nFor each research project, create the following folder structure:\n\n```\nresearch/\n |
Powered by composio this MCP.json provides detailed information on Model Context Protocol (MCP) integration capabilities and enables seamless agent workflows by connecting to more than 80 servers.
It covers development, AI, data management, productivity, cloud storage, e-commerce, finance, communication, and design. Each server offers specialized tools, allowing agents to securely access, automate, and manage external services through a unified and modular system. This approach supports building dynamic, scalable, and intelligent workflows with minimal setup and maximum flexibility.
The UOR Model provides a meta-mathematical framework for defining and manipulating ontologies using the principles of prime decomposition, observer invariance, and coherence. This document details the model's architecture, implementation, and usage patterns.
The UOR Model embodies the essential principles of the UOR Framework:
| # SPARC Agentic Development Rules | |
| Core Philosophy | |
| 1. Simplicity | |
| - Prioritize clear, maintainable solutions; minimize unnecessary complexity. | |
| 2. Iterate | |
| - Enhance existing code unless fundamental changes are clearly justified. |
| { | |
| "customModes": [ | |
| { | |
| "slug": "sparc", | |
| "name": "⚡️ SPARC Orchestrator", | |
| "roleDefinition": "You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.", | |
| "customInstructions": "Follow SPARC:\n\n1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.\n2. Pseudocode: Request high-level logic with TDD anchors.\n3. Architecture: Ensure extensible system diagrams and service boundaries.\n4. Refinement: Use TDD, debugging, security, and optimization flows.\n5. Completion: Integrate, document, and monitor for continuous improvement.\n\nUse `new_task` to assign:\n- spec-pseudocode\n- architect\n- code\n- tdd\n- debug\n- security-review\n- docs-writer\n- integration\n- post-deployment-monitoring-mode\n- refinement-optimization-mode\n\nValidate:\n✅ Files < 500 lines\n✅ No hard-coded |