docs: improve documentation formatting and remove Claude references\n\n- Format AboutMe.md with beautiful tables and improved structure\n- Remove all Claude references from documentation per ethical/legal concerns\n- Create README.md files in all top-level and sub-level directories\n- Update README.md to link to README.md files instead of directories\n- Add beautiful stub README.md files for COO, CTO, and PMO directories\n- Fix directory linking issues in main README.md\n- Ensure all links point to actual files rather than directories\n- Update version tracking in AboutMe.md to v1.0.1 reflecting improvements\n- Maintain consistency with filesystem structure and documentation standards\n- Preserve AI tools: Codex, Qwen, Gemini while removing Claude references
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
@@ -36,8 +36,8 @@
|
||||
- `databank/personal/` - Personal information
|
||||
- `databank/agents/` - Agent guidelines and tools
|
||||
- `databank/operations/` - Operational environment information
|
||||
- `databank/coo/` - Chief Operating Officer domain (for Albert and his AI agents)
|
||||
- `databank/cto/` - Chief Technology and Product Officer domain
|
||||
- `databank/coo/` - Chief Operating Officer domain (shared between Charles and Albert, transitioning to Albert in January 2026)
|
||||
- `databank/cto/` - Chief Technology and Product Officer (CTPO) domain
|
||||
- `databank/cto/vpengineering/` - VP Engineering focus area (AI-based operations)
|
||||
- `databank/cto/vpproduct/` - VP Product focus area (AI-based operations)
|
||||
- `databank/templates/` - Template files for projects
|
||||
@@ -217,7 +217,8 @@ The PMO (Project Management Office) provides centralized project oversight. Proj
|
||||
|
||||
### Authority and Decision Making
|
||||
- Charles N Wyble (@ReachableCEO) is in charge at all times for general operations
|
||||
- Albert will become a major user/contributor for COO functions, transitioning from Charles's role as Chief Operating Officer (focused on Vice President Production Technology Operations) by end of December 2025
|
||||
- Charles N Wyble (@ReachableCEO) serves as Chief Technology and Product Officer (CTPO)
|
||||
- Charles N Wyble (@ReachableCEO) and Albert currently share the Chief Operating Officer (COO) role, with Albert taking over the COO role fully in January 2026
|
||||
- If something is adrift between docs and filesystem/code, stop and ask Charles to resolve the issue
|
||||
- Especially if discrepancy isn't reflected in git or conversation history, ask for clarification
|
||||
- When Charles or Albert modify filesystem manually (vs having AI do it), they will ensure AI integrates the changes into mental model
|
||||
@@ -267,7 +268,6 @@ In this mode, continue to apply the default persona guidelines while focusing on
|
||||
- **Codex** - Primary daily driver (subscription-based), best for code generation and completion
|
||||
- **Qwen** - Heavy system orchestration, excels at shell/Docker operations
|
||||
- **Gemini** - Primarily used for audits and analysis
|
||||
- **Claude** - Used occasionally for specific tasks
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -31,25 +31,17 @@ This document captures the current AI tool preferences and usage patterns for th
|
||||
- **Strengths**: Analytical capabilities, detailed reviews, comparison operations
|
||||
- **Role**: Quality assurance and audit functions
|
||||
|
||||
### 4. Claude (Occasional Use)
|
||||
- **Status**: Used occasionally for specific tasks
|
||||
- **Usage**: Specific reasoning tasks when needed
|
||||
- **Strengths**: Advanced reasoning, document analysis, creative tasks
|
||||
- **Role**: Specialized tasks when other tools aren't optimal
|
||||
|
||||
## Usage Patterns
|
||||
|
||||
### Daily Workflow
|
||||
1. **Morning**: Start with Codex (if quota available) for primary development tasks
|
||||
2. **Throughout Day**: Switch to Qwen when Codex quota is reached or for system operations
|
||||
3. **Review/Audit**: Use Gemini for detailed analysis and code reviews
|
||||
4. **Special Tasks**: Use Claude for specific reasoning requirements
|
||||
|
||||
### Tool Selection Guidelines
|
||||
- **Code Generation/Completion**: Codex (primary), Qwen (when Codex unavailable)
|
||||
- **System Orchestration**: Qwen (primary), Codex (secondary)
|
||||
- **Audits and Reviews**: Gemini (primary), others (as needed)
|
||||
- **Advanced Reasoning**: Claude (primary for complex reasoning), others (as needed)
|
||||
|
||||
### Context for AI Agents
|
||||
When working in this environment, AI agents should be aware that:
|
||||
@@ -65,13 +57,11 @@ When working in this environment, AI agents should be aware that:
|
||||
- **Codex**: Excellent for code generation but limited by subscription quota
|
||||
- **Qwen**: Reliable for system operations, good for heavy tasks, no quota limits
|
||||
- **Gemini**: Best for analytical tasks and detailed reviews
|
||||
- **Claude**: Good for complex reasoning but used selectively
|
||||
|
||||
### Optimizing Tool Usage
|
||||
- Leverage Qwen for operations that require extensive system knowledge
|
||||
- Use Codex for code-related tasks when available
|
||||
- Employ Gemini for validation and quality checks
|
||||
- Reserve Claude for specialized reasoning tasks
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user