

Also from Kynth Studios


Also from Kynth Studios


Also from Kynth Studios
1# ⚙️ Technical Context23## SPARC Development Methodology45The project follows the SPARC methodology for structured development:671. **Specification**: Define requirements, constraints, and acceptance criteria82. **Pseudocode**: Develop high-level logic with TDD anchors93. **Architecture**: Design modular components with clear interfaces104. **Refinement**: Implement with TDD, debugging, and optimization115. **Completion**: Integrate, document, test, and verify against criteria1213### Technical Requirements14- Files must not exceed 500 lines15- Functions must follow single responsibility principle16- No hardcoded environment variables or secrets17- All code must include proper error handling18- Modular architecture with clear component boundaries19- Comprehensive test coverage for critical functionality2021## Technology Stack2223### Frontend24- [Frontend framework/library]25- [UI component library]26- [State management solution]27- [CSS approach/framework]28- [Build tools]2930### Backend31- [Backend language/framework]32- [API architecture]33- [Database technology]34- [Authentication system]35- [Caching strategy]3637### Infrastructure38- [Hosting platform]39- [CI/CD pipeline]40- [Containerization]41- [Monitoring tools]42- [Logging system]4344## Development Environment4546### Required Tools47- [Tool 1 and version]48- [Tool 2 and version]49- [Tool 3 and version]5051### Setup Instructions52```bash53# Setup commands54```5556### Local Development Workflow571. [Step 1]582. [Step 2]593. [Step 3]6061## External Dependencies6263### APIs64- [API 1]: [Purpose and usage]65- [API 2]: [Purpose and usage]6667### Third-party Services68- [Service 1]: [Purpose and integration details]69- [Service 2]: [Purpose and integration details]7071### Libraries and Frameworks72- [Library 1]: [Purpose and usage]73- [Library 2]: [Purpose and usage]7475## Technical Constraints7677### Performance Requirements78- [Requirement 1]79- [Requirement 2]8081### Security Requirements82- No hardcoded secrets, credentials, or environment variables83- All user inputs must be validated and sanitized84- Proper error handling to prevent information leakage85- Secure coding practices following OWASP guidelines86- Regular security audits of dependencies8788### Compatibility Requirements89- [Requirement 1]90- [Requirement 2]9192## Technical Debt9394### Known Issues95- [Issue 1]: [Impact and potential resolution]96- [Issue 2]: [Impact and potential resolution]9798### Planned Refactoring99- [Refactoring 1]: [Reason and approach]100- [Refactoring 2]: [Reason and approach]101102## Testing Strategy103104### SPARC Testing Approach105- Test-Driven Development (TDD) for all new features106- Tests written during Pseudocode phase before implementation107- Comprehensive test coverage for critical functionality108- Automated testing integrated into CI/CD pipeline109110### Unit Testing111- Test individual components in isolation112- Mock dependencies for pure unit testing113- Aim for >80% code coverage on critical paths114- Focus on edge cases and error handling115116### Integration Testing117- Test component interactions and interfaces118- Verify correct data flow between modules119- Test API contracts and boundaries120- Ensure proper error propagation121122### End-to-End Testing123- [Framework and approach]124- [Critical user flows to test]125126## Deployment Process127128### Environments129- Development: [Details]130- Staging: [Details]131- Production: [Details]132133### Deployment Steps1341. [Step 1]1352. [Step 2]1363. [Step 3]137138### Rollback Procedure1391. [Step 1]1402. [Step 2]1413. [Step 3]142143## Monitoring and Observability144145### Key Metrics146- [Metric 1]: [What it measures and thresholds]147- [Metric 2]: [What it measures and thresholds]148149### Alerting150- [Alert 1]: [Trigger conditions and response]151- [Alert 2]: [Trigger conditions and response]152153## Documentation Resources154155### Internal Documentation156- [Link or location 1]: [Description]157- [Link or location 2]: [Description]158159### External Documentation160- [Link 1]: [Description]161- [Link 2]: [Description]162
One repository carrying more than one format is the comparison this product exists for: does anyone actually write different content in each file, or is one a copy of the other?
| Repository | Format | Stack | Covers | Score | Changed |
|---|---|---|---|---|---|
| ruvnet/rUv-dev.clinerules/📋_projectbrief.md · 426 | Cline rules | archdependencies | 48/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/📚_02-documentation.md · 426 | Cline rules | docs | 44/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/🏃_current-sprint.md · 426 | Cline rules | testing-strategygitdocs | 44/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/💻_01-coding.md · 426 | Cline rules | styleperformance | 48/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/📊_progress.md · 426 | Cline rules | performance | 44/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/🔄_activeContext.md · 426 | Cline rules | stylearch | 56/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/🔍_productContext.md · 426 | Cline rules | archperformancedo-not | 59/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/🧠_memory-bank.md · 426 | Cline rules | archperformanceagent-behaviourdocs | 58/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/🏗️_systemPatterns.md · 426 | Cline rules | stylearchsecurityui+2 | 62/100 | 13 days ago | |
| ruvnet/rUv-dev.clinerules/📖_README.md · 426 | Cline rules | archperformancedo-not | 55/100 | 13 days ago |
Same format, overlapping stack, ranked by quality.
| Repository | Format | Stack | Covers | Score | Changed |
|---|---|---|---|---|---|
| bashdeban/fastmind.clinerules/.project-consistency-keeper2.md · 5 | Cline rules | setupbuildtestlint-format+11 | 100/100 | 14 days ago | |
| JCodesMore/ai-website-cloner-template.clinerules · 32k | Cline rules | buildlint-formatstylearch+3 | 97/100 | 7 days ago | |
| BryaanF/LiantPortfolio.clinerules/project-guidelines.md · 0 | Cline rules | buildstylearchgit+2 | 96/100 | 14 days ago | |
| enuno/unifi-mcp-server.clinerules · 226 | Cline rules | setuptestlint-formatstyle+10 | 96/100 | today | |
| u9401066/zotero-keeper.clinerules/50-pubmed-project.md · 6 | Cline rules | testlint-formatstylearch+1 | 94/100 | 14 days ago | |
| u9401066/zotero-keepervscode-extension/resources/repo-assets/pubmed-search-mcp/.clinerules/50-pubmed-project.md · 6 | Cline rules | testlint-formatstylearch+1 | 94/100 | 14 days ago | |
| VaillerTeeter/HoshimiNest.clinerules/project-identity.md · 1 | Cline rules | setuparchtypesdo-not | 93/100 | 12 days ago | |
| prabhakar267/paper-games.clinerules/git-commit-guidelines.md · 0 | Cline rules | lint-formatstylearchgit+3 | 93/100 | 13 days ago |
A badge carrying the measured quality of the strongest agent config file in this repository, out of 100. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://rulestack.kynth.studio/configs/ruvnet-ruv-dev-clinerules-techcontext)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.