⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
coder-skill
Write Rust code which is easy to read, test, extend and maintain. TRIGGER when: any .rs file is being edited, created, or reviewed, or the user asks to write/refactor/fix Rust code. DO NOT TRIGGER for: non-Rust tasks.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
CODER-Skill
An opinionated agentic coding SKILL resulting in pretty good code.
CODER = Correct Organized Documented Empirical Rigorous
- Correct: Strong type modeling, validation, impossible states made impossible, meaningful invariants, and expressive newtypes.
- Organized: Modular architecture, well-grouped and well-named files, folders, crates/packages, and modules/namespaces; small types and functions with clear responsibilities; composition over monoliths.
- Documented: Code is documented, with doc tests where possible; assumptions, decisions, architecture, and design are written down clearly in markdown.
- Empirical: Measure and iterate; avoid premature optimization; be careful with assumptions; profile first, then improve based on findings.
- Rigorous: High standards: 90%+ test coverage, CI/CD, linting, typo checks, supply-chain care, and a disciplined engineering process.
SKILL
See [SKILL.md][SKILL.md]
// HOW IT'S BUILT
KEY FILES