CookHero
Copilot instructions629 starsChanged 10 months agoApache-2.0View on GitHub
We split this copilot-instructions.md into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Never automatically execute git commit: after making code changes.
- Distinctive: line 25
Always activate the virtual environment in the project root before running or testing code.
- Very specific: line 31
After modifying frontend code, always run the following command to compile and check for errors: npm run build.
- Distinctive: line 32
Ensure the build succeeds before proceeding with other operations to maintain code consistency and stability.
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Global Instructions
0. General Code Quality Requirements
- Clarity and Simplicity: Write clean, self-documenting code with meaningful names and consistent formatting. Prefer straightforward solutions; avoid unnecessary abstraction or complexity.
- Reliability and Correctness: Ensure code is robust and predictable. Handle errors gracefully, validate inputs, and include tests where appropriate.
- Maintainability and Modularity: Structure code to be easy to understand, modify, and extend. Minimize coupling between modules and keep related functionality cohesive.
- Consistency and Standards: Follow established project conventions and language best practices consistently. Avoid introducing special cases without strong justification.
1. Task Decomposition & Planning
- For complex or multi-step tasks, carefully analyze and plan before proceeding.
- Break down tasks into a prioritized to-do list of executable steps.
- Process each subtask sequentially by priority, ensuring logical progression and clarity.
2. Version Compatibility Policy
- No backward compatibility guarantee — Feel free to break old formats to prioritize new features and improvements.
- Allow destructive updates, prioritize code quality and architectural soundness over maintaining legacy support.
3. Git Operations
- Never automatically execute git commit after making code changes.
- Perform git operations (e.g., commit, push) only when explicitly instructed by the user.
Python Project Instructions
1. Python Environment Management
- Always activate the virtual environment in the project root before running or testing code.
- Activation command:
source .venv/bin/activate
Frontend Project Instructions
1. Frontend Build Process
- After modifying frontend code, always run the following command to compile and check for errors:
npm run build. - Ensure the build succeeds before proceeding with other operations to maintain code consistency and stability.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

