daily-coding
Skill35 starsChanged 2 months agoMITView on GitHub
Use for everyday coding tasks that involve writing or modifying source code.
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- Vepricov/claude-brainlabword for word, first seen Nov 1, 2026
- Galaxy-Dawn/claude-scholaredited, first seen Apr 15, 2026
- Clay-HHK/claude-skillsedited, first seen Mar 5, 2026
Other versions3 projects use a version of this.
Word for word · 1
- Vepricov/claude-brainlab★ 35100% same
Edited · 2
- Galaxy-Dawn/claude-scholar★ 5.9k98% same
- Clay-HHK/claude-skills★ 173% same
Wrote their own version · 0
None found.
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 repository68 other files it gives its agents.
- rules/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- academic-plottingSkill
- agent-identifierSkill
- architecture-designSkill
- astar-paper-reviewSkill
- bug-detectiveSkill
- call-notesSkill
- cavemanSkill
- citation-verificationSkill
- code-ingestSkill
- code-librarySkill
- code-review-excellenceSkill
- command-developmentSkill
- create-projectSkill
- defuddleSkill
- diagnoseSkill
- doc-coauthoringSkill
- experiment-runsSkill
- frontend-designSkill
- git-guardrails-claude-codeSkill
- git-workflowSkill
- google-workspace-mcpSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- handoff-to-jarvisSkill
- hook-developmentSkill
- improve-codebase-architectureSkill
- json-canvasSkill
- kaggle-learnerSkill
- lab-knowledgeSkill
- latex-conference-template-organizerSkill
- mcp-integrationSkill
- ml-paper-writingSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-experiment-logSkill
- obsidian-markdownSkill
- operon-obsidian-setupSkill
- paper-ingestSkill
- paper-searchSkill
- paper-to-socialSkill
- paper-venue-formattingSkill
- pdf-readerSkill
- planning-with-filesSkill
- plugin-structureSkill
- presentationSkill
- presenter-modeSkill
- prototypeSkill
- research-cycleSkill
- research-ideationSkill
- restore-sessionSkill
- results-analysisSkill
- results-reportSkill
- reverse-outline-flow-checkSkill
- review-responseSkill
- setup-pre-commitSkill
- skill-developmentSkill
- tddSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 14
Use this skill for:
- Distinctive: line 22
Do not use this skill for:
- Distinctive: line 75
Use pathlib for file paths, avoid path traversal
- Distinctive: line 76
Never hardcode sensitive info (API keys, passwords)
≈ “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
Daily Coding Checklist
A minimal coding quality assurance checklist ensuring every code modification follows best practices.
When to Use
Use this skill for:
- Implementing new features
- Adding code or modifying existing code
- User requests like "write a...", "implement...", "add...", or "modify..."
- Any coding task that involves Edit or Write tools
When Not to Use
Do not use this skill for:
- Pure reading or understanding tasks with no modification intent
- Work already covered by specialized skills such as
bug-detective,architecture-design, ortdd-guide - Configuration-only changes
- Documentation-only writing
Core Checklist
Before Starting
- Read before modify - Must read target file with Read tool before making changes
- Understand context - Confirm understanding of existing code logic and design intent
During Coding
- Minimal changes - Only change what's necessary, no over-engineering, no unrelated features
- Type safety - Add type hints for Python, avoid
anyin TypeScript - Security check - Avoid command injection, XSS, SQL injection vulnerabilities
After Completion
- Verify execution - Ensure code runs correctly with no syntax errors
- Clean up - Remove print/console.log debug statements and temporary files
- Brief summary - Inform user what was changed and the scope of impact
Quick Reference
Common Mistakes to Avoid
# ❌ Don't
def process(data=[]): # Mutable default argument
pass
# ✅ Should
def process(data: list | None = None):
data = data or []# ❌ Don't
except: # Bare except
pass
# ✅ Should
except ValueError as e:
logger.error(f"Processing failed: {e}")
raiseSecurity Check Points
- User input must be validated/escaped
- Use pathlib for file paths, avoid path traversal
- Never hardcode sensitive info (API keys, passwords)
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.

