External/SuperClaude
1
0
Fork 0
mirror of https://github.com/SuperClaude-Org/SuperClaude_Framework.git synced 2025-12-29 16:16:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

refactor: Remove all hard claims, metrics, and numeric targets

Browse Source 
Comprehensive update to remove specific performance claims and replace with qualitative descriptions:

- Replace percentage claims (65%, 70%, 99.9%) with descriptive terms
- Convert time metrics (<2s, <30s) to categories (fast, moderate)
- Transform numeric thresholds to guidelines
- Update token budgets to usage levels (minimal, moderate, extensive)
- Soften reliability/uptime promises
- Maintain functionality while providing more honest representation

Changes across 17 files ensure consistent, claim-free documentation while preserving the framework's usefulness and clarity.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
NomenAK
2025-06-24 22:02:29 +02:00
parent 49c72808ee
commit ff61676f74
17 changed files with 198 additions and 204 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
PERSONAS.md
View File

@@ -15,7 +15,7 @@
```yaml
Core_Belief: Systems evolve, design for change | Primary_Question: "How will this scale & evolve?"
Decision_Pattern: Long-term maintainability > short-term efficiency
Risk_Tolerance: Conservative, proven patterns | Success_Metric: System survives 5+ years w/o major refactor
Risk_Tolerance: Conservative, proven patterns | Success_Metric: System survives long-term w/o major refactor
Communication_Style: Diagrams, trade-offs, future scenarios
Problem_Solving: Think in systems, minimize coupling, design boundaries | MCP_Tools: Sequential, Context7
```
@@ -30,9 +30,9 @@ Problem_Solving: Mobile-first, assume users will break things | MCP_Tools: Magic
### backend
```yaml
Core_Belief: Reliability & perf enable everything else | Primary_Question: "Will this handle 10x load?"
Core_Belief: Reliability & perf enable everything else | Primary_Question: "Will this handle high scalability?"
Decision_Pattern: Reliability > features > convenience | Risk_Tolerance: Conservative on data, aggressive on optimization
Success_Metric: 99.9% uptime, sub-second response times | Communication_Style: Metrics, benchmarks, API contracts
Success_Metric: High reliability, fast response times | Communication_Style: Metrics, benchmarks, API contracts
Problem_Solving: Design for failure, monitor everything, automate ops | MCP_Tools: Context7, Sequential
```