Removing references to Archon "Alpha"

This commit is contained in:
Cole Medin
2025-09-06 14:51:02 -05:00
parent 01903e5c63
commit 012d2c58ed
21 changed files with 44 additions and 47 deletions

View File

@@ -1,11 +1,11 @@
---
description: Perform comprehensive code review for Archon V2 Alpha, this command will save a report to `code-review.md`.
description: Perform comprehensive code review for Archon V2 Beta, this command will save a report to `code-review.md`.
argument-hint: <PR number, branch name, file path, or leave empty for staged changes>
allowed-tools: Bash(*), Read, Grep, LS, Write
thinking: auto
---
# Code Review for Archon V2 Alpha
# Code Review for Archon V2 Beta
**Review scope**: $ARGUMENTS
@@ -13,7 +13,7 @@ I'll perform a comprehensive code review and generate a report saved to the root
## Context
You're reviewing code for Archon V2 Alpha, which uses:
You're reviewing code for Archon V2 Beta, which uses:
- **Frontend**: React + TypeScript + Vite + TailwindCSS
- **Backend**: Python 3.12+ with FastAPI, PydanticAI, Supabase
@@ -32,7 +32,7 @@ Determine what needs reviewing:
## Review Focus
### CRITICAL: Alpha Error Handling Philosophy
### CRITICAL: Beta Error Handling Philosophy
**Following CLAUDE.md principles - We want DETAILED ERRORS, not graceful failures!**
@@ -59,7 +59,7 @@ Look for:
- **Type hints** on all functions and proper use of Python 3.12+ features
- **Pydantic v2 patterns** (ConfigDict, model_dump, field_validator)
- **Error handling following alpha principles**:
- **Error handling following beta principles**:
```python
# BAD - Silent failure

View File

@@ -7,7 +7,7 @@ description: |
argument-hint: none
---
You are helping a new developer get up and running with the Archon V2 Alpha project! Your goal is to provide them with a personalized onboarding experience.
You are helping a new developer get up and running with the Archon V2 Beta project! Your goal is to provide them with a personalized onboarding experience.
## What is Archon?
@@ -133,7 +133,7 @@ When analyzing the user's chosen area, look for:
After analyzing their chosen area, provide the user with:
1. Key development patterns they should know:
- Alpha mindset (break things to improve them)
- Beta mindset (break things to improve them)
- Error philosophy (fail fast with detailed errors)
- Service boundaries (no cross-service imports)
- Real-time updates via Socket.IO
@@ -150,4 +150,4 @@ After analyzing their chosen area, provide the user with:
- Testing requirements
- Local vs Docker differences
Remember to encourage the user to start small and iterate. This is alpha software designed for rapid experimentation.
Remember to encourage the user to start small and iterate. This is beta software designed for rapid experimentation.

View File

@@ -6,7 +6,7 @@ argument-hint: none
## Prime Context for Archon Development
You need to quickly understand the Archon V2 Alpha codebase. Follow these steps:
You need to quickly understand the Archon V2 Beta codebase. Follow these steps:
### 1. Read Project Documentation
@@ -51,4 +51,4 @@ After reading these files, explain to the user:
3. **Key Patterns**: One sentence about key patterns
4. **Tech Stack**: One sentence about tech stack
Remember: This is alpha software focused on rapid iteration. Prioritize understanding the core functionality
Remember: This is beta software focused on rapid iteration. Prioritize understanding the core functionality

View File

@@ -11,7 +11,7 @@ description: |
argument-hint: <service> <Specific focus>
---
You're about to work on the Archon V2 Alpha codebase. This is a microservices-based knowledge management system with MCP integration. Here's what you need to know:
You're about to work on the Archon V2 Beta codebase. This is a microservices-based knowledge management system with MCP integration. Here's what you need to know:
## Today's Focus area
@@ -171,4 +171,4 @@ Follow the guidelines in CLAUDE.md
- Frontend uses Vite proxy for API calls in development
- Python backend uses `uv` for dependency management
Remember: This is alpha software. Prioritize functionality over production patterns. Make it work, make it right, then make it fast.
Remember: This is beta software. Prioritize functionality over production patterns. Make it work, make it right, then make it fast.

View File

@@ -1,11 +1,11 @@
---
description: Generate Root Cause Analysis report for Archon V2 Alpha issues
description: Generate Root Cause Analysis report for Archon V2 Beta issues
argument-hint: <issue description or error message>
allowed-tools: Bash(*), Read, Grep, LS, Write
thinking: auto
---
# Root Cause Analysis for Archon V2 Alpha
# Root Cause Analysis for Archon V2 Beta
**Issue to investigate**: $ARGUMENTS
@@ -13,7 +13,7 @@ investigate this issue systematically and generate an RCA report saved to `RCA.m
## Context About Archon
You're working with Archon V2 Alpha, a microservices-based AI knowledge management system:
You're working with Archon V2 Beta, a microservices-based AI knowledge management system:
- **Frontend**: React + TypeScript on port 3737
- **Main Server**: FastAPI + Socket.IO on port 8181
@@ -45,7 +45,7 @@ Check if all services are running properly:
### 3. Error Handling Analysis
**Remember: In Alpha, we want DETAILED ERRORS that help us fix issues fast!**
**Remember: In Beta, we want DETAILED ERRORS that help us fix issues fast!**
Look for these error patterns: