skills/code-standards/SKILL.md
Enforces project-specific coding conventions by loading language standards before writing code. Use when about to write, edit, modify, or generate Go, Rust, Python, or Tailwind CSS files. Loads once per language per session and overrides default style with project conventions. DO NOT TRIGGER for languages other than Go, Rust, Python, or Tailwind CSS.
npx skillsauth add shousper/claude-kit code-standardsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Load language-specific coding standards before editing code files. Invoke this skill when you are about to write or modify files in a supported language.
Determine which languages to load based on the file you are about to edit:
| File Pattern | Language | Standards File |
|-------------|----------|----------------|
| *.go, go.mod, go.sum | Go | ../../code-standards/go/CLAUDE.md |
| *.rs, Cargo.toml, Cargo.lock | Rust | ../../code-standards/rust/CLAUDE.md |
| *.py, pyproject.toml, requirements.txt, setup.py | Python | ../../code-standards/python/CLAUDE.md |
| *.css, *.tsx, *.jsx, *.vue, *.svelte, *.astro, *.html with Tailwind | Tailwind CSS | ../../code-standards/tailwindcss/CLAUDE.md |
All paths are relative to this skill's base directory.
Use the Read tool to load the standards file for the language you are about to edit. Only load once per language per session — if you have already loaded Go standards, do not re-read the file.
Follow these standards for ALL code you write in that language during this session. These are project conventions that override your defaults.
development
Creates, edits, and tests Claude skill files (SKILL.md) using TDD methodology with baseline pressure testing and rationalization defense. Use when writing a new skill, modifying an existing skill, optimizing a skill description for discovery (CSO), testing whether a skill triggers correctly, or structuring skill documentation. Enforces RED-GREEN-REFACTOR for process documentation.
development
Creates detailed, bite-sized implementation plans with TDD structure, exact file paths, complete code, and test commands. Use when you have a spec, requirements, design doc, or feature request and need to plan before coding — especially for multi-step tasks, large features, or when handing off to another session. DO NOT TRIGGER when asked to write code directly or fix a simple bug.
testing
Removes git worktrees safely, cleans up associated branches, and pulls latest mainline after removal. Use when finished with a worktree, done with a branch, cleaning up after a merge or PR, abandoning work in a worktree, or when "git worktree list" shows stale entries. Checks for uncommitted changes, verifies no open PRs before branch deletion, and handles force-removal of locked worktrees.
development
Enforces fresh verification evidence before any completion or success claims. Use when about to say "done", "fixed", "tests pass", "build succeeds", or any synonym; before committing, creating PRs, or moving to the next task; before expressing satisfaction or positive statements about work state; and after agent delegation to independently verify results. Prevents unverified claims by requiring command execution, output inspection, and exit code confirmation.