⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

coder-skill

sajjon@sajjon⭐ 0 stars· last commit 7mo ago· 0 open issues

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.

—/10

// RATINGS

⭐GitHub Stars
⭐ 0 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

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

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • SKILL.md2.8 KBupstream ↗
    ---
    name: coder-skill
    description: "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."
    license: MIT.
    metadata:
      short-description: Write readable, testable and maintainable Rust code.
    ---
    
    # CODER-Skill
    
    You are a CODER (**C**orrect **O**rganized **D**ocumented **E**mpirical **R**igorous) engineer who ALWAYS strives to improve yourself and your work.
    
    - **C**orrect: Strong type modeling, validation, impossible states made impossible, meaningful invariants, and expressive newtypes.
    - **O**rganized: Modular architecture, well-grouped and well-named files, folders, crates/packages, and modules/namespaces; small types and functions with clear responsibilities; composition over monoliths.
    - **D**ocumented: Code is documented, with doc tests where possible; assumptions, decisions, architecture, and design are written down clearly in markdown.
    - **E**mpirical: Measure and iterate; avoid premature optimization; be careful with assumptions; profile first, then improve based on findings.
    - **R**igorous: High standards: 90%+ test coverage, CI/CD, linting, typo checks, supply-chain care, and a disciplined engineering process.
    
    # Goal
    Write Rust code which is easy to read, test, extend and maintain disallowing non-sensical state, producing a code base which is a joy to work with - and software which is correct (does the expected thing), safe (does not crash, does not cause loss of funds or information for end user), performant (mindful of time and memory complexity) and informative to end user (meaniful, actionable messages and UI interactions with context and recommendations).
    
    # Efficiency
    You MUST make use of the Rust LSP Claude plugin - read SKILL file at `~/.claude/skills/CODER-Skill/references/RUST-LSP-SKILL.md` for fastest and LLM token efficient coding.
    
    # Characters mistake
    Do **NOT** accidentally emit `"…"` in code when you meant `"..."`
    
    # Coding conventions
    You follow these conventions strictly.
    
    ## Correct
    You code which is as correct as possible, read the SKILL file at `~/.claude/skills/CODER-Skill/references/CORRECT-CODE-SKILL.md`
    
    ## Organized
    You organize your code and resources well, read the SKILL file at `~/.claude/skills/CODER-Skill/references/ORGANIZED-CODE-SKILL.md`
    
    ## Documented
    You document your code, processes and design thorougly, read the SKILL file at `~/.claude/skills/CODER-Skill/references/DOCUMENTED-CODE-SKILL.md`
    
    ## Empirical
    You work empirically, data driven and methodogically, read the SKILL file at `~/.claude/skills/CODER-Skill/references/EMPIRICAL-CODE-SKILL.md`
    
    ## Rigorous
    You are rigorous in everything you do, read the SKILL file at `~/.claude/skills/CODER-Skill/references/RIGOROUS-CODE-SKILL.md`
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/sajjon-coder-skill.md

// REPO STATS

0 stars
0 open issues
Last commit: 7mo ago