Cline rules
.clinerules/project_rules.mdCline rules
Quality
30/100
Scores the file, not the repository.Length
332 words
0 headings · 0 code blocksRepository
1
— · pushed 0 days agoLast changed
3 days ago
First indexed 3 days ago.11. Refer to readme.md and detail_docs.md files for information about the scripts.2 - The readme.md file should provide a high-level overview of the project, including its purpose, how to set it up, and how to use it.3 - The detail_docs.md file should provide more in-depth information about each script, including its functionality, input/output formats, and any dependencies or prerequisites.4 - The .clinerules/cheatsheet.md file contains a summary of key project directory locations and default database configuration details.5 - Ensure that these files are kept up to date with any changes made to the scripts or the project as a whole.6 - Load the readme.md, detail_docs.md, cheatsheet.md files into context for a new task.7 - Remember that you listing functions sometimes have truncated outputs!82. After writing/updating a script, add documentation in the readme.md file about the script9 - Include the purpose of the script, how to run it, and any dependencies or prerequisites.10 - Provide examples of input and output if applicable.11 - Ensure that the documentation is clear and concise, making it easy for others to understand the script's functionality.12 - In the Input section, include the input format and any specific requirements for the input data. Also - if the input is generated by another script, mention that script's name and location.133. After writing/updating a script, add documentation in the detail_docs.md file about the script14 - Here, you can provide more in-depth information about the script's functionality, including:15 - The logic behind the script, including any algorithms or methods used.16 - Any specific considerations or edge cases that the script handles.17 - Any known limitations or issues with the script.184. After removing a script, move the script to the archive folder.19 - Ensure that the script is no longer referenced in any active documentation readme.md and detail_docs.md or code.20 - Update any relevant documentation to reflect the removal of the script.21 - Maintain a record of removed scripts in a changelog or similar document for future reference - changelog.md
Also in Leah1314/gut-balance-buddy-24
Diff this repo’s formatsOne 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 |
|---|---|---|---|---|---|
| Leah1314/gut-balance-buddy-24.clinerules/cheatsheet.md · 1 | Cline rules | testlint-formatarchdatabase | 71/100 | 3 days ago |
Similar configs
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 | 3 days ago | |
| JCodesMore/ai-website-cloner-template.clinerules · 31k | Cline rules | buildlint-formatstylearch+3 | 97/100 | 2 days ago | |
| BryaanF/LiantPortfolio.clinerules/project-guidelines.md · 0 | Cline rules | buildstylearchgit+2 | 96/100 | 3 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 | 3 days ago | |
| u9401066/zotero-keeper.clinerules/50-pubmed-project.md · 6 | Cline rules | testlint-formatstylearch+1 | 94/100 | 3 days ago | |
| VaillerTeeter/HoshimiNest.clinerules/project-identity.md · 1 | Cline rules | setuparchtypesdo-not | 93/100 | yesterday | |
| blendsdk/codeops-mcp.clinerules/project.md · 0 | Cline rules | buildteststylearch+7 | 91/100 | 3 days ago | |
| cline/cline.clinerules/general.md · 66k | Cline rules | setupbuildstylearch+2 | 86/100 | 3 days ago |
