code-writing-guide
Skill3 starsChanged 5 months agoApache-2.0View on GitHub
Used when writing or modifying code. Provides coding guidelines for this project.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nowsprinting/unity-coding-skillstheir own version, first seen Oct 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nowsprinting/unity-coding-skills★ 20same name
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.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- implementation-planning-guideSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 10
Do NOT maintain backward compatibility unless explicitly requested.
- Distinctive: line 14
Add a comment whenever a non-obvious implementation choice was made — especially when a natural or standard approach was tried and rejected.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Guide for writing code in this project.
Backward Compatibility
Do NOT maintain backward compatibility unless explicitly requested. Break things boldly.
"Why Not" Comments
Add a comment whenever a non-obvious implementation choice was made — especially when a natural or standard approach was tried and rejected. The goal is to prevent future readers (human or AI) from re-discovering the same dead end.
Triggers that require a "why not" comment:
- A standard API or language feature is avoided because it misbehaves in a specific environment
(e.g.,
withTimeoutdeadlocks on the IntelliJ platform test JVM EDT → usejava.util.Timer) - A less-efficient or more verbose pattern is chosen over a simpler one for correctness reasons
- A seemingly redundant guard, indirection, or workaround exists due to a framework constraint
Format: Explain what was tried, why it failed, and why the chosen approach avoids the problem.
// WHY java.util.Timer instead of withTimeout:
// withTimeout relies on DefaultDelay, whose cancellation is dispatched back to the coroutine's
// event loop. When runBlocking is called from the EDT, the event loop runs ON the EDT — which
// runBlocking blocks — so the callback can never be processed and the timeout never fires.
// java.util.Timer runs on its own daemon thread and calls continuation.resume() directly,
// bypassing the scheduler entirely.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.