FrootAI User Guide
> The complete guide to using FrootAI β from first install to production deployment.
1. Getting Started
Step 1: Install the VS Code Extension
code --install-extension frootai.frootai-vscodeOr search βFrootAIβ in the VS Code Extensions Marketplace.
Step 2: Browse the Knowledge Hub
Open the sidebar β FROOT Modules panel to explore 18 knowledge modules across 5 layers:
| Layer | Modules | Focus |
|---|---|---|
| π± Foundations | GenAI, LLM Landscape, AI Glossary, Agentic OS | Core AI concepts |
| πͺ΅ Reasoning | Prompt Engineering, RAG, Deterministic AI | Making AI reliable |
| πΏ Orchestration | Semantic Kernel, AI Agents, MCP & Tools | Building agents |
| π Operations | Azure AI, Infrastructure, Copilot Ecosystem | Platform & infra |
| π Transformation | Fine-Tuning, Responsible AI, Production Patterns | Production readiness |
Step 3: Init DevKit
Open Command Palette (Ctrl+Shift+P / Cmd+Shift+P) β FROOT: Init DevKit
This scaffolds the .github/ Agentic OS into your project:
agent.mdβ Agent behavior rulescopilot-instructions.mdβ Copilot context- Prompt files, CI workflows, and config templates
Step 4: Init TuneKit
Command Palette β FROOT: Init TuneKit
Adds tunable configuration files:
config/agents.jsonβ Agent routing and parametersconfig/model-comparison.jsonβ Model selection criteriaconfig/guardrails.jsonβ Safety and content limitsevaluation/β Golden sets and scoring scripts
Step 5: Deploy
Command Palette β FROOT: Deploy Solution
Packages your configured play for deployment. Output depends on the selected solution play.
2. Using the VS Code Extension
2.1 All Commands
Open Command Palette and type FROOT: to see all available commands:
| Command | Description |
|---|---|
| FROOT: Browse Modules | Open the knowledge hub and browse all knowledge modules |
| FROOT: Search Knowledge | Full-text search across all modules |
| FROOT: Lookup Term | Look up any AI term in the glossary (comprehensive glossary) |
| FROOT: Init DevKit | Scaffold .github Agentic OS files into your project |
| FROOT: Init TuneKit | Add config and evaluation files |
| FROOT: Show Solution Plays | Browse all 20 solution plays with status |
| FROOT: Open Play | Open a specific playβs folder |
| FROOT: Deploy Solution | Package and deploy the current play |
| FROOT: Show MCP Tools | View documentation for all 16 MCP tools |
| FROOT: Read User Guide | Open this guide in the editor |
| FROOT: Show Architecture | Display system architecture diagram |
| FROOT: Show Changelog | View version history |
| FROOT: Check Updates | Check for new versions of all components |
2.2 Sidebar Panels
The FrootAI sidebar (click the π± icon) has these panels:
- FROOT Modules β Expandable tree of all 18 knowledge modules, color-coded by layer
- Solution Plays β All 20 plays with status badges (Ready / In Progress)
- MCP Tools β Documentation for all 16 MCP server tools, grouped by type
- Quick Actions β One-click access to common commands
2.3 Standalone Mode
The extension works offline with bundled knowledge. It caches downloaded content in globalStorage with a 24-hour TTL. No internet required for core functionality.
3. Using the MCP Server
3.1 What is the MCP Server?
The FrootAI MCP Server exposes 23 tools that any MCP-compatible AI agent can call. It adds AI architecture knowledge to your agentβs capabilities.
3.2 Setup
Add to your .vscode/mcp.json:
{
"servers": {
"frootai": {
"command": "npx",
"args": ["frootai-mcp"]
}
}
}3.3 Tool Reference
Static Tools (bundled knowledge)
| Tool | What it does | Example query |
|---|---|---|
get_module | Retrieve a full knowledge module | βGet the RAG Architecture moduleβ |
list_modules | List all knowledge modules with metadata | βWhat modules are available?β |
search_knowledge | Full-text search across all content | βSearch for vector databasesβ |
lookup_term | Look up a term in the AI glossary | βWhat is LoRA?β |
Live Tools (real-time retrieval)
| Tool | What it does | Example query |
|---|---|---|
fetch_azure_docs | Fetch current Azure documentation | βGet Azure AI Search pricingβ |
fetch_external_mcp | Query external MCP registries | βFind MCP servers for databasesβ |
Chain Tools (multi-step workflows)
| Tool | What it does | Example query |
|---|---|---|
agent_build | Generate a new agent scaffold | βBuild an IT ticket resolution agentβ |
agent_review | Review an agentβs configuration | βReview my agent.md for security issuesβ |
agent_tune | Optimize agent parameters | βTune my agent for lower latencyβ |
AI Ecosystem Tools
| Tool | What it does | Example query |
|---|---|---|
get_architecture_pattern | Get architecture patterns for a scenario | βPattern for multi-agent RAGβ |
get_froot_overview | Overview of the FrootAI platform | βWhat is FrootAI?β |
get_github_agentic_os | Explain the .github Agentic OS | βWhat files does DevKit create?β |
list_community_plays | Browse community solution plays | βShow me community playsβ |
get_ai_model_guidance | Model selection guidance | βCompare GPT-4o vs Claude 3.5β |
3.4 Using in Copilot Chat
In VS Code with GitHub Copilot, you can invoke MCP tools naturally:
@workspace Use frootai to search for "semantic kernel orchestration"
@workspace Use frootai to get the RAG Architecture module
@workspace Use frootai agent_build to create an IT ticket agent4. Solution Plays
4.1 What is a Solution Play?
A solution play is a pre-configured scenario accelerator. Each play includes:
- README.md β Overview, architecture, deployment steps
- DevKit (
.github/Agentic OS) β Agent rules, copilot instructions, prompts, CI - TuneKit (
config/+evaluation/) β Tunable parameters and quality benchmarks
4.2 Available Plays (20)
| # | Play | Category |
|---|---|---|
| 01 | IT Ticket Resolution | IT Operations |
| 02 | Customer Support Agent | Customer Service |
| 03 | Code Review Assistant | Development |
| 04 | Security Incident Response | Security |
| 05 | Knowledge Base FAQ | Knowledge Management |
| 06 | Onboarding Assistant | HR / People |
| 07 | Sales Intelligence | Sales |
| 08 | Compliance Checker | Governance |
| 09 | Data Quality Monitor | Data Engineering |
| 10 | Infrastructure Health | Platform / SRE |
| 11 | Cost Optimization Advisor | FinOps |
| 12 | Release Notes Generator | DevOps |
| 13 | API Documentation Writer | Documentation |
| 14 | Meeting Summarizer | Productivity |
| 15 | Competitive Analysis | Strategy |
| 16 | Training Content Creator | Learning |
| 17 | Change Management | ITSM |
| 18 | Document Processor | Document AI |
| 19 | Multi-Agent Orchestrator | Agent Platform |
| 20 | Custom Play Template | Template |
4.3 Choosing a Play
Use the Solution Configurator at /configurator β answer 3 questions and get a recommendation. Or use the AI Assistant at /chatbot.
4.4 Customizing a Play
FROOT: Init DevKitto scaffold the playβs .github files- Edit
agent.mdto adjust behavior rules FROOT: Init TuneKitto add config parameters- Tune
config/agents.jsonfor your scenario - Run evaluation against the golden set
5. DevKit Deep Dive
The DevKit scaffolds .github Agentic OS β a structured set of files that make your project agent-ready.
5.1 File Reference
| File | Purpose |
|---|---|
.github/agent.md | Primary agent behavior rules β scope, constraints, tools, error handling |
.github/copilot-instructions.md | GitHub Copilot context β project structure, conventions, key files |
.github/prompts/init.prompt.md | Initial prompt for bootstrapping the agent |
.github/prompts/review.prompt.md | Code review prompt template |
.github/prompts/deploy.prompt.md | Deployment preparation prompt |
.github/workflows/validate.yml | CI pipeline β structure validation, lint, test |
.github/ISSUE_TEMPLATE/bug.yml | Structured bug report template |
.github/ISSUE_TEMPLATE/feature.yml | Feature request template |
.github/pull_request_template.md | PR description template |
5.2 The 7 Primitives
The Agentic OS uses 7 composable primitives:
- Agent Rules (
agent.md) β Behavioral boundaries - Context (
copilot-instructions.md) β Project knowledge - Prompts (
prompts/*.prompt.md) β Reusable prompt templates - Workflows (
workflows/*.yml) β CI/CD automation - Templates (
ISSUE_TEMPLATE/,pull_request_template.md) β Structured collaboration - Config (
config/) β Tunable parameters - Evaluation (
evaluation/) β Quality benchmarks
6. TuneKit Deep Dive
6.1 Config Files
| File | Parameters |
|---|---|
config/agents.json | Agent routing, model selection, temperature, max_tokens |
config/model-comparison.json | Model capabilities, latency, cost comparison |
config/guardrails.json | Content filters, blocked topics, rate limits |
config/search.json | Search method (vector, hybrid, keyword), top_k |
config/chunking.json | Chunk size, overlap, strategy |
6.2 Tuning Workflow
- Review current config:
FROOT: Show Config - Adjust parameters based on your scenario
- Run evaluation:
python evaluation/evaluate.py - Compare scores against the golden set
- Iterate until quality targets are met
6.3 Evaluation
Each play includes:
evaluation/golden-set.jsonlβ Expected inputs/outputs (5+ examples)evaluation/evaluate.pyβ Scoring script (accuracy, latency, safety)- Results output to
evaluation/results.json
6b. SpecKit Deep Dive
SpecKit provides architecture specifications and WAF (Well-Architected Framework) alignment for every solution play.
Whatβs in SpecKit?
| File | Purpose |
|---|---|
spec/play-spec.json | Architecture pattern, WAF pillar scores, evaluation thresholds |
WAF Alignment (6 Pillars)
Every play is scored across the Azure Well-Architected Framework:
| Pillar | What it checks |
|---|---|
| Reliability | Retry policies, health probes, multi-region readiness |
| Security | Managed identity, private endpoints, RBAC, no API keys |
| Cost Optimization | Right-sized SKUs, autoscaling, reserved capacity |
| Operational Excellence | Diagnostic settings, Log Analytics, CI/CD |
| Performance | Caching, async patterns, connection pooling |
| Responsible AI | Content Safety, guardrails, bias monitoring |
CLI WAF Scorecard
npx frootai validate --wafRuns 17 checks across 6 pillars and shows per-pillar scores + failing items.
6c. Using the CLI
The FrootAI CLI (npx frootai) provides 8 commands for terminal-based workflows.
Commands
| Command | What it does |
|---|---|
npx frootai init | Interactive project scaffolding (auto-detects existing projects) |
npx frootai scaffold <play> | One-command play scaffold (e.g. scaffold play-01) |
npx frootai search <query> | Search across 18 knowledge modules |
npx frootai cost <service> | Estimate Azure AI service costs |
npx frootai validate | Run consistency checks across your project |
npx frootai validate --waf | WAF alignment scorecard (6 pillars, 17 checks) |
npx frootai doctor | Health check: Node.js, npm, VS Code, MCP config |
npx frootai help | Show all available commands |
Scaffold Command
One-command play scaffolding β creates all 5 FROOT kits + froot.json manifest:
npx frootai scaffold 01-enterprise-rag
# or shorthand:
npx frootai scaffold play-01Creates: .github/agents/, config/, spec/, evaluation/, froot.json, WAF instructions.
Auto-detects existing projects and merges files alongside yours.
6d. Using Docker
Run the FrootAI MCP Server as a container β no Node.js required.
Quick Start
docker run -i --rm ghcr.io/frootai/frootai-mcp:latestClient Configuration
Claude Desktop / Cursor:
{
"mcpServers": {
"frootai": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/frootai/frootai-mcp:latest"]
}
}
}VS Code Copilot (.vscode/mcp.json):
{
"servers": {
"frootai": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/frootai/frootai-mcp:latest"],
"type": "stdio"
}
}
}Multi-arch (amd64 + arm64). Same 23 tools, 682KB knowledge. Pinnable versions.
6e. Using the REST API
The FrootAI REST API provides 5 HTTP endpoints β no SDK or MCP client needed.
Base URL
https://frootai-chatbot-api.azurewebsites.net
Endpoints
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/chat | Chat with Agent FAI (AI assistant) |
| GET | /api/search?q=<query> | Search solution plays |
| GET | /api/cost?service=<name> | Estimate Azure AI costs |
| GET | /api/health | Health check |
| GET | /api/openapi.json | OpenAPI 3.1 specification |
Rate Limits
60 requests/minute per IP. Sliding window. Returns HTTP 429 when exceeded.
7. Agent Chain
The build β review β tune chain is a three-step workflow:
Step 1: Build (agent_build)
Generate a new agent scaffold based on your scenario description. Produces agent.md, config files, and evaluation templates.
Step 2: Review (agent_review)
Analyze the generated agent for:
- Security gaps
- Missing error handling
- Unclear scope boundaries
- Config completeness
Step 3: Tune (agent_tune)
Optimize parameters based on review findings and evaluation results. Adjusts temperature, model selection, guardrails, and routing.
Deploying a Solution Play
Deploy any play with one command:
# Deploy play 01 (Enterprise RAG)
./scripts/deploy-play.sh 01 --resource-group rg-frootai-dev
# Deploy play 05 (IT Ticket Resolution) without evaluation
./scripts/deploy-play.sh 05 --resource-group rg-frootai --skip-evalThe script: validates the play structure β deploys Azure infra via Bicep β copies config files β runs evaluation.
Exporting FROOT Knowledge as Copilot Skills
Make any FROOT module available as a GitHub Copilot skill:
# Export a single module
./scripts/export-skills.sh F1
# Export all knowledge modules
./scripts/export-skills.sh --allThis creates .github/skills/<module-id>/SKILL.md + README.md that Copilot reads automatically.
Knowledge Auto-Update
The MCP server can auto-refresh its knowledge:
- Bundled knowledge.json is checked every 7 days
- If stale, fetches latest from GitHub automatically
- Falls back to bundled version if offline
To manually rebuild: ./scripts/rebuild-knowledge.sh
8. FAQ
Q: Does FrootAI require an internet connection?
A: Core functionality works offline. The VS Code extension bundles knowledge locally. Live tools (fetch_azure_docs, fetch_external_mcp) require connectivity.
Q: Which AI models does FrootAI support?
A: FrootAI is model-agnostic. Solution plays can be configured for any model in config/agents.json. The knowledge modules cover GPT-4o, Claude, Gemini, Phi, Llama, and more.
Q: Can I use FrootAI without VS Code? A: Yes. The MCP server works with any MCP-compatible client (Claude Desktop, Cursor, Windsurf, Azure AI Foundry). The website is accessible via browser.
Q: How do I add a custom solution play? A: See the Contributor Guide for step-by-step instructions.
Q: Is FrootAI free? A: Yes. FrootAI is 100% open source under the MIT license.
Q: How do I report a bug? A: Open an issue on GitHubΒ using the bug report template.
Q: How often is the knowledge base updated? A: Knowledge modules are updated with each release. The changelog tracks all content changes.
> Next: Admin Guide Β· Contributor Guide Β· API Reference