good-taste-skill
Copilot instructions0 starsChanged 32 days agoMITView on GitHub
Note: GitHub Copilot automatically reads this file to set its global behavior. By including this in the .github folder, Copilot stops writing generic "slop" code and adheres to the premium Taste Skill standards.
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 repository14 other files it gives its agents.
- skills/llms.txtllms.txt
- brandkitSkill
- industrial-brutalist-uiSkill
- gpt-tasteSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- minimalist-uiSkill
- full-output-enforcementSkill
- redesign-existing-projectsSkill
- high-end-visual-designSkill
- stitch-design-tasteSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
The file
We split this copilot-instructions.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
No Generic UI: Stop generating default SaaS templates.
- Very specific: line 9
Cinematic Motion: Never use linear easing. All animations must use spring physics (stiffness: 100, damping: 20 or similar).
- Very specific: line 10
Complete Implementation: No placeholders. No // TODO: add actual code here.
≈ “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
Copilot Instructions: Taste Standard
Note: GitHub Copilot automatically reads this file to set its global behavior. By including this in the
.githubfolder, Copilot stops writing generic "slop" code and adheres to the premium Taste Skill standards.
The "Anti-Slop" Manifesto for Copilot
- No Generic UI: Stop generating default SaaS templates. Use high contrast, strong typographic hierarchy, and extreme care for alignment.
- Premium Whitespace: Elements need room to breathe. Use proportional
clamp()spacing over rigid padding. - Cinematic Motion: Never use linear easing. All animations must use spring physics (
stiffness: 100, damping: 20or similar). - Complete Implementation: No placeholders. No
// TODO: add actual code here. Write the full, working implementation every single time. - Contextual Awareness: For deep style configurations, read the localized
SKILL.mdfiles in theskills/directory.
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.