

Also from Kynth Studios


Also from Kynth Studios


Also from Kynth Studios
1# Development Guidelines23## Basic Rules45- Follow Instructions6 - Execute tasks as per defined requirements7 - Report progress or issues proactively89- Autonomous Problem Solving10 - Analyze and propose solutions when errors or problems occur11 - Clearly state recommended options if multiple approaches exist12 - Report issues that might be outside of the code1314- Respect Existing Code15 - Follow existing code style and patterns16 - Explain if major changes are necessary1718- Handling Repeated Failures19 - If a test fails twice in a row, summarize the situation with reproduction steps, logs, and error messages, and report it20 - Do not repeat the same action — always propose a solution2122## Security2324### Confidential Files2526Do not read or modify the following under any circumstances2728- .env file29- Any file containing API keys, tokens, or credentials3031If changes to confidential files are necessary, contact the project owner.3233Also follow these security practices:3435- Never commit confidential files36- Use environment variables for secrets37- Avoid logging sensitive data (auth/user info)3839## Workflow4041Follow these four steps during development:42431. Requirements (PM Mode)44 - Clarify and refine requirements45 - Ask questions or make suggestions if needed46472. Design (Architect Mode)48 - Choose appropriate architecture or design patterns49 - Design components, data flows, and use case diagrams50513. Implementation (Code Mode)52 - Write code based on the design53 - Create unit tests54 - Must be executable via Vitest55 - 100% test coverage required for:56 - statements57 - branches58 - functions59 - lines60 - Each function/component should be tested with mocked external dependencies61624. Quality Check (PMO Mode)63 - Code Review64 - Lint/format checks (ESLint / Prettier)65 - Validate user input properly66 - Consider performance and security67 - Requirement Verification6869AI should make autonomous decisions to progress through these steps and deliver complete results in a single request whenever possible.70
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 |
|---|---|---|---|---|---|
| sakatai11/todoApp-next.clinerules/introduction.md · 0 | Cline rules | no sections | 16/100 | 13 days ago | |
| sakatai11/todoApp-next.claude/CLAUDE.md · 0 | CLAUDE.md | buildtestlint-formattesting-strategy+1 | 82/100 | 13 days ago | |
| sakatai11/todoApp-next.clinerules/best-practices.md · 0 | Cline rules | style | 8/100 | 13 days ago | |
| sakatai11/todoApp-next.clinerules/coding-guidelines.md · 0 | Cline rules | test | 29/100 | 13 days ago | |
| sakatai11/todoApp-next.clinerules/project-structure.md · 0 | Cline rules | testarchtypestesting-strategy+2 | 62/100 | 13 days ago | |
| sakatai11/todoApp-next.clinerules/security-guidelines.md · 0 | Cline rules | security | 4/100 | 13 days ago | |
| sakatai11/todoApp-next.clinerules/tech-stack.md · 0 | Cline rules | testlint-formattesting-strategy | 33/100 | 13 days ago | |
| sakatai11/todoApp-nextAGENTS.md · 0 | AGENTS.md | buildtestlint-formattesting-strategy+1 | 82/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 | |
| 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 | |
| u9401066/zotero-keeper.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 | |
| blendsdk/codeops-mcp.clinerules/project.md · 0 | Cline rules | buildteststylearch+7 | 91/100 | 14 days ago | |
| tsongglod123/excel-formula-visualizer.clinerules/development.md · 0 | Cline rules | setupbuildtestarch+2 | 86/100 | today |
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/sakatai11-todoapp-next-clinerules-development-guidelines)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.