coding-guidelines
Skill2 starsChanged 4 months agoMITView on GitHub
Behavioral guidelines that reduce common LLM coding mistakes — surgical changes, no overcomplication, surface assumptions, define verifiable success, no silent scope creep. Use while writing, reviewing, or refactoring code, or when the user says "코딩 가이드", "수술적으로", "과설계 하지마", "keep it simple".
16 other projects use a version of this.
Adopted by
Most recently taken up by
- StephanMeijer/skillstheir own version, first seen Nov 8, 2026
- TeddyAlbina/skillstheir own version, first seen Nov 1, 2026
- Apprentice-Geo/skillstheir own version, first seen Nov 1, 2026
- basaltbytes/skillstheir own version, first seen Nov 1, 2026
- kaynetik/skillstheir own version, first seen Oct 20, 2026
- okaneconnor/agent-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use grill-me.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- ZhangHanDong/rust-skills★ 1.5ksame name
- actionbook/rust-skills★ 1.5ksame name
- fjrevoredo/mini-diarium★ 318same name
- aromanarguello/roman-skills★ 18same name
- Keming-Shen/MotionSurf★ 16same name
- Lucky1192405754/MotionSurf★ 6same name
- Apprentice-Geo/skills★ 3same name
- basaltbytes/skills★ 2same name
- okaneconnor/agent-skills★ 2same name
- TeddyAlbina/skills★ 2same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Don't overcomplicate: Prefer the simplest thing that works — no speculative abstraction, no config for a case that doesn't exist yet.
- Distinctive: line 21
Surface assumptions: If the task hinges on an unstated assumption (a field exists, an API behaves a certain way), state it and verify it …
- Distinctive: line 24
Verifiable success: Before starting, name how you'll KNOW it works (a test, a command, an observable output).
- Distinctive: line 26
No silent scope creep: Do what was asked; if you spot adjacent work, surface it — don't fold it in unannounced.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Coding guidelines
Apply while writing or changing code — these counter the usual LLM failure modes.
- Surgical changes. Change the minimum to achieve the goal. Don't rewrite working code you were only asked to extend; don't reformat unrelated lines.
- Don't overcomplicate. Prefer the simplest thing that works — no speculative abstraction, no config for a case that doesn't exist yet. Delete before you add.
- Match the surroundings. New code reads like the code around it — naming, idioms, comment density, error handling. Don't import a foreign style.
- Surface assumptions. If the task hinges on an unstated assumption (a field exists, an API behaves a certain way), state it and verify it (grep / run) before building on it.
- Verifiable success. Before starting, name how you'll KNOW it works (a test, a command, an observable output). "Done" means that check actually ran and passed.
- No silent scope creep. Do what was asked; if you spot adjacent work, surface it — don't fold it in unannounced.
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.