Dan Capri MFD3000

Multi-Agent System Requirements Document

You are an expert AI systems architect. Create a comprehensive, detailed implementation plan for the following multi-agent system:

Project Overview

[Provide a concise description of your multi-agent system concept - what it does and the primary value it delivers]

Target Agents & Use Cases

Who will interact with this system? [Types of agents]

Cursor AI Prompting Framework Usage Guide

This guide explains how to use the structured prompting files (core.md, refresh.md, request.md) to optimize your interactions with Cursor AI, leading to more reliable, safe, and effective coding assistance.

Core Components

core.md (Foundational Rules)
- Purpose: Establishes the fundamental operating principles, safety protocols, tool usage guidelines, and validation requirements for Cursor AI. It ensures consistent and cautious behavior across all interactions.
- Usage: This file's content should be persistently active during your Cursor sessions.

Expertise: React, TypeScript, MUI, @dnd-kit, framer-motion, Vite. Follow Airbnb React style guide, Screaming Architecture, and project-specific standards.

Code Style & Structure:

Use functional components and hooks; avoid classes. Prefer modularization over duplication.
Descriptive variable names (e.g., isLoading, hasError). Component names in PascalCase; variables and functions in camelCase.
File structure: Feature-first. Use _shared/ for reusable components, theme, and types.
Absolute Imports: Configure and use absolute paths for imports to avoid deep relative paths.

	{
	"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

	#!/bin/bash

	# Check if a GitHub URL is provided as an argument
	if [ -z "$1" ]; then
	echo "Usage: $0 <github_url>"
	exit 1
	fi

	# Store the GitHub URL
	GIT_URL="$1"