Workflow-Master / templates
Copilot instructions2 starsChanged 8 days agoMITView on GitHub
When suggesting code, refactoring, or generating tests:
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,349 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.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- clean-code-concise-docsSkill
- data-analysis-explorerSkill
- data-science-workbenchSkill
- diff-reviewSkill
- distinctive-ui-designSkill
- domain-scaffoldingSkill
- git-commit-craftSkill
- github-repo-publishSkill
- laravel-web-studioSkill
- ml-model-engineeringSkill
- professional-report-writerSkill
- readme-github-syncSkill
- release-deploy-checkSkill
- security-auditSkill
- shadcn-admin-design-systemSkill
- verify-and-testSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 5
When suggesting code, refactoring, or generating tests:
- Distinctive: line 10
Prefer simple, readable implementations (SOLID, DRY, KISS, YAGNI) over speculative abstractions.
- Distinctive: line 14
Use parameterized queries or safe ORM access.
- Distinctive: line 15
Never expose credentials, API keys, or private tokens in source code.
- Distinctive: line 18
Use Arrange-Act-Assert (AAA) structure for all test cases.
- Distinctive: line 19
Write tests for happy paths, edge cases, and failure scenarios.
- Distinctive: line 21
Write descriptive test method names that express scenario and expected behavior.
- Distinctive: line 24
When requested to scaffold a new domain system (e.g.
- Distinctive: line 27
Keep commits and changes focused and atomic.
- Very specific: line 28
Follow Conventional Commits format (feat, fix, refactor, test, docs).
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 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
GitHub Copilot Custom Instructions
Reference: https://github.com/pranataa-labs/workflow-master
Place this file at: .github/copilot-instructions.md
When suggesting code, refactoring, or generating tests:
- Architecture & Standards:
- Adhere to the conventions and language idioms of this repository.
- Maintain clean boundaries between presentation, domain logic, and persistence.
- Prefer simple, readable implementations (SOLID, DRY, KISS, YAGNI) over speculative abstractions.
- Security & Input Validation:
- Sanitize and strictly validate inputs at system boundaries.
- Use parameterized queries or safe ORM access; avoid raw string concatenation in SQL.
- Never expose credentials, API keys, or private tokens in source code.
- Testing & QA:
- Use Arrange-Act-Assert (AAA) structure for all test cases.
- Write tests for happy paths, edge cases, and failure scenarios.
- Mock all external network services and external API endpoints.
- Write descriptive test method names that express scenario and expected behavior.
- Autonomous Domain Scaffolding:
- When requested to scaffold a new domain system (e.g. store, queue, POS, LMS), automatically include both public/customer and backoffice admin flows, modern design aesthetics (Inter font, smooth blue/slate palette), and realistic seed data without asking trivial clarifying questions.
- Change Hygiene:
- Keep commits and changes focused and atomic.
- Follow Conventional Commits format (
feat,fix,refactor,test,docs).
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.