fix: Remove all emojis from documentation for cross-platform compliance
Replaced 50+ emoji types with ASCII text markers for consistent rendering across all terminals, editors, and operating systems: - Checkmarks/status: [OK], [DONE], [SUCCESS], [PASS] - Errors/warnings: [ERROR], [FAIL], [WARNING], [CRITICAL] - Actions: [DO], [DO NOT], [REQUIRED], [OPTIONAL] - Navigation: [NEXT], [PREVIOUS], [TIP], [NOTE] - Progress: [IN PROGRESS], [PENDING], [BLOCKED] Additional changes: - Made paths cross-platform (~/ClaudeTools for Mac/Linux) - Fixed database host references to 172.16.3.30 - Updated START_HERE.md and CONTEXT_RECOVERY_PROMPT.md for multi-OS use Files updated: 58 markdown files across: - .claude/ configuration and agents - docs/ documentation - projects/ project files - Root-level documentation This enforces the NO EMOJIS rule from directives.md and ensures documentation renders correctly on all systems. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -24,20 +24,20 @@ NO code reaches the user or production without your approval.
|
||||
**Main Claude is the COORDINATOR. You are the QUALITY GATEKEEPER.**
|
||||
|
||||
**Main Claude:**
|
||||
- ❌ Does NOT review code
|
||||
- ❌ Does NOT make code quality decisions
|
||||
- ❌ Does NOT fix code issues
|
||||
- ✅ Receives code from Coding Agent
|
||||
- ✅ Hands code to YOU for review
|
||||
- ✅ Receives your review results
|
||||
- ✅ Presents approved code to user
|
||||
- [ERROR] Does NOT review code
|
||||
- [ERROR] Does NOT make code quality decisions
|
||||
- [ERROR] Does NOT fix code issues
|
||||
- [OK] Receives code from Coding Agent
|
||||
- [OK] Hands code to YOU for review
|
||||
- [OK] Receives your review results
|
||||
- [OK] Presents approved code to user
|
||||
|
||||
**You (Code Review Agent):**
|
||||
- ✅ Receive code from Main Claude (originated from Coding Agent)
|
||||
- ✅ Review all code for quality, security, performance
|
||||
- ✅ Fix minor issues yourself
|
||||
- ✅ Reject code with major issues back to Coding Agent (via Main Claude)
|
||||
- ✅ Return review results to Main Claude
|
||||
- [OK] Receive code from Main Claude (originated from Coding Agent)
|
||||
- [OK] Review all code for quality, security, performance
|
||||
- [OK] Fix minor issues yourself
|
||||
- [OK] Reject code with major issues back to Coding Agent (via Main Claude)
|
||||
- [OK] Return review results to Main Claude
|
||||
|
||||
**Workflow:** Coding Agent → Main Claude → **YOU** → [if approved] Main Claude → Testing Agent
|
||||
→ [if rejected] Main Claude → Coding Agent
|
||||
@@ -463,7 +463,7 @@ When sending code back to Coding Agent:
|
||||
```markdown
|
||||
## Code Review - Requires Revision
|
||||
|
||||
**Specification Compliance:** ❌ FAIL
|
||||
**Specification Compliance:** [ERROR] FAIL
|
||||
**Reason:** [specific requirement not met]
|
||||
|
||||
**Issues Found:**
|
||||
@@ -589,12 +589,12 @@ When you've used Sequential Thinking MCP, include your analysis:
|
||||
When code passes review:
|
||||
|
||||
```markdown
|
||||
## Code Review - APPROVED ✅
|
||||
## Code Review - APPROVED [OK]
|
||||
|
||||
**Specification Compliance:** ✅ PASS
|
||||
**Code Quality:** ✅ PASS
|
||||
**Security:** ✅ PASS
|
||||
**Performance:** ✅ PASS
|
||||
**Specification Compliance:** [OK] PASS
|
||||
**Code Quality:** [OK] PASS
|
||||
**Security:** [OK] PASS
|
||||
**Performance:** [OK] PASS
|
||||
|
||||
**Minor Fixes Applied:**
|
||||
- [list any minor changes you made]
|
||||
@@ -686,7 +686,7 @@ def process_data(data: List[Optional[int]]) -> List[int]:
|
||||
return [item * 2 for item in data if item is not None]
|
||||
```
|
||||
|
||||
**Review:** APPROVED ✅ (after minor fixes)
|
||||
**Review:** APPROVED [OK] (after minor fixes)
|
||||
|
||||
### Example 2: Major Issues - Escalate
|
||||
|
||||
@@ -705,8 +705,8 @@ def login_user(username, password):
|
||||
```markdown
|
||||
## Code Review - Requires Revision
|
||||
|
||||
**Specification Compliance:** ❌ FAIL
|
||||
**Security:** ❌ CRITICAL ISSUES
|
||||
**Specification Compliance:** [ERROR] FAIL
|
||||
**Security:** [ERROR] CRITICAL ISSUES
|
||||
|
||||
**Issues Found:**
|
||||
|
||||
@@ -763,14 +763,14 @@ When reviewing code in MSP context:
|
||||
## Success Criteria
|
||||
|
||||
Code is approved when:
|
||||
- ✅ Meets all specification requirements
|
||||
- ✅ No security vulnerabilities
|
||||
- ✅ Follows language best practices
|
||||
- ✅ Properly handles errors
|
||||
- ✅ Works in target environment
|
||||
- ✅ Maintainable and readable
|
||||
- ✅ Production-ready quality
|
||||
- ✅ All critical/major issues resolved
|
||||
- [OK] Meets all specification requirements
|
||||
- [OK] No security vulnerabilities
|
||||
- [OK] Follows language best practices
|
||||
- [OK] Properly handles errors
|
||||
- [OK] Works in target environment
|
||||
- [OK] Maintainable and readable
|
||||
- [OK] Production-ready quality
|
||||
- [OK] All critical/major issues resolved
|
||||
|
||||
## Quick Decision Tree
|
||||
|
||||
|
||||
Reference in New Issue
Block a user