Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
Apply a disciplined engineering workflow to any code change.
Install Code Standards
$ npx skills add tamdogood/builder-essential-skills --skill code-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tamdogood/builder-essential-skills code-standards --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tamdogood/builder-essential-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/code-standards .claude/skills/code-standards && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-standards" agent skill from https://github.com/tamdogood/builder-essential-skills/tree/main/skills/code-standards into .claude/skills/code-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-standards", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tamdogood/builder-essential-skills/tree/main/skills/code-standardsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tamdogood/builder-essential-skills --skill code-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tamdogood/builder-essential-skills code-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tamdogood/builder-essential-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/code-standards .agents/skills/code-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-standards" agent skill from https://github.com/tamdogood/builder-essential-skills/tree/main/skills/code-standards into .agents/skills/code-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-standards", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tamdogood/builder-essential-skills --skill code-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tamdogood/builder-essential-skills code-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tamdogood/builder-essential-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/code-standards .cursor/skills/code-standards && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-standards" agent skill from https://github.com/tamdogood/builder-essential-skills/tree/main/skills/code-standards into .cursor/skills/code-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-standards", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tamdogood/builder-essential-skills.git --path skills/code-standards--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tamdogood/builder-essential-skills --skill code-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tamdogood/builder-essential-skills code-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tamdogood/builder-essential-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/code-standards .gemini/skills/code-standards && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-standards" agent skill from https://github.com/tamdogood/builder-essential-skills/tree/main/skills/code-standards into .gemini/skills/code-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-standards", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tamdogood/builder-essential-skills code-standardsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tamdogood/builder-essential-skills --skill code-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tamdogood/builder-essential-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/code-standards .github/skills/code-standards && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-standards" agent skill from https://github.com/tamdogood/builder-essential-skills/tree/main/skills/code-standards into .github/skills/code-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-standards", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tamdogood/builder-essential-skills --skill code-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tamdogood/builder-essential-skills code-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tamdogood/builder-essential-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/code-standards .opencode/skills/code-standards && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-standards" agent skill from https://github.com/tamdogood/builder-essential-skills/tree/main/skills/code-standards into .opencode/skills/code-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-standards", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
code-standards- GitHub stars
- 219
- Token cost
- ~738 tokens
- SKILL.md length
- 363 words
- Files
- 2
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply a disciplined engineering workflow to any code change.
- Works in 8 steps: Orient. Read any project lessons/gotchas… → Plan if non-trivial (3+ steps or an… → Baseline: get the project's build + test… → …
- Implementing a feature
- SKILL.md covers Steps, Tripwires — stop and re-check… and No-progress guard
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Code Standards is an agent skill from tamdogood/builder-essential-skills. Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).
Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`). Compatibility notes: claude-code
It sits in Development, covering Linting and formatting and Refactoring. The repository describes itself as: A repository for skills that are essential to my daily work. The licence is MIT.
When your agent uses it
- Implementing a feature
- Refactoring — before writing code
Example prompts
- “/code-standards”
Requirements
- Compatibility (from SKILL.md): claude-code
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Orient. Read any project lessons/gotchas file (e.g. tasks/lessons.md) and obey it.
- Plan if non-trivial (3+ steps or an architectural choice): short plan in tasks/todo.md —
- Baseline: get the project's build + test command green before touching anything. A
- Implement the smallest root-cause change. Hand-match the surrounding style.
- Test: new behavior gets a test that fails without the change; security gates get
- Verify: run the full check suite (build + lint + type-check + tests) until green
- Self-review your own diff as if it were someone else's PR (or invoke a review
- Close out: update docs in the same change; append to a lessons file if you were
What it can do on your machine
Read from SKILL.md and the folder at commit 1be9984. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
claude-code
From compatibility in the SKILL.md frontmatter.
Context cost
Code Standards loads about 738 tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 363 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tamdogood/builder-essential-skills at commit 1be9984, republished under its MIT licence (© tamdogood). 363 words, ~738 tokens.
Download SKILL.mdSave it as
.claude/skills/code-standards/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- code-standards
- description
- Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).
- compatibility
- claude-code
Code standards — the change workflow
You are making a code change. This skill is the execution order; it is
stack-agnostic. Adapt every command to the project's actual toolchain: read the
project's own docs (README, CONTRIBUTING, AGENTS.md/CLAUDE.md, a Makefile or
package scripts) once to learn its build, test, lint, and format commands before
you start.
Steps
- Orient. Read any project lessons/gotchas file (e.g.
tasks/lessons.md) and obey it. Find and read the one doc for the subsystem you're changing, not the whole tree. - Plan if non-trivial (3+ steps or an architectural choice): short plan in
tasks/todo.md— files touched, tests to add, risks. Going sideways → stop and re-plan. - Baseline: get the project's build + test command green before touching anything. A pre-existing red is the first task; never build on top of a broken baseline.
- Implement the smallest root-cause change. Hand-match the surrounding style. Don't run a mass auto-formatter on files you touch; it buries your real diff in noise.
- Test: new behavior gets a test that fails without the change; security gates get negative-assertion tests (wrong token → denied, state unchanged, no data leak).
- Verify: run the full check suite (build + lint + type-check + tests) until green before you call it "done".
- Self-review your own diff as if it were someone else's PR (or invoke a review skill). Fix findings before presenting.
- Close out: update docs in the same change; append to a lessons file if you were
corrected or surprised; write a conventional commit message (
feat|fix|docs(scope): …).
Show full SKILL.md (113 more words)Show less
Tripwires — stop and re-check the project's guidelines when you're about to…
- change a public or shared interface (API, wire format, schema) → check every caller; prefer additive changes
- add a dependency → weigh transitive weight and licenses, and whether the stdlib already covers it
- touch auth, tokens, or permissions → audit every writer and reader path, add negative tests
- write a secret to disk → use the platform's atomic create-private API, never write-then-chmod
- hold a lock across an
await/blocking call, or read env inside logic → extract a pure decision function
No-progress guard
The same failure surviving two fix attempts means stop: write the finding to your lessons
file, mark the item [BLOCKED], and surface it. Don't thrash.
© tamdogood, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/code-standards of tamdogood/builder-essential-skills.
- SKILL.md
- README.md
Open the folder on GitHubat commit 1be9984
Compare with similar skills
Code Standards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code Standards this skilltamdogood/builder-essential-skills | 219 | — | ~738 | Automated safety check: Pass | MIT | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| File Good First BugBrowserWorks/waterfox-android | 379 | 2 repos | ~2k | Automated safety check: Pass | Custom licence | |
| Unslop CodeJCarterJohnson/vibecoded-design-tells | 511 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Code Quality Gatefengshao1227/ccg-workflow | 5.9k | — | ~593 | Automated safety check: Notes | MIT | |
| Rust Hygiene Audittsz-org/tsz | 577 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
File Good First Bug
BrowserWorks/waterfox-android
A skill your agent uses when the user wants to file good-first-bugs in Bugzilla for Firefox.
Unslop Code
JCarterJohnson/vibecoded-design-tells
Strips the tells that make source code read as AI-generated and forces code that fits the project instead of the model's default average.
Code Quality Gate
fengshao1227/ccg-workflow
Scans code for complexity, long functions, duplicated blocks, naming problems and code smells with a Node script, then reports and suggests refactors.
Rust Hygiene Audit
tsz-org/tsz
Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.
Dep Validate
blokadaorg/blokada
A skill your agent uses to validate risky dependency bumps end to end as a local or cloud-launched agent.
More from tamdogood/builder-essential-skills
All 18 skills in this repoCreate Marketing Kit
tamdogood/builder-essential-skills
Create truthful, human-centered marketing campaigns for an app or product, including positioning, channel copy, original artwork, editable layouts, README banners, and selective website integration.
Name Your Business
tamdogood/builder-essential-skills
Generate, refine, compare, and when needed validate distinctive names for startups, AI products, developer tools, protocols, open-source projects, apps, product families, local businesses, services…
Session Profiler
tamdogood/builder-essential-skills
Profile and debug Hermes sessions from their JSONL transcripts.
Build Scenario Tests
tamdogood/builder-essential-skills
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code.
Create Skill
tamdogood/builder-essential-skills
Create or update a complete repository skill from a user's idea, including the workflow instructions, references, scripts or assets, agent metadata, skill-card artwork, cinematic banner artwork…
Paper Opportunity Radar
tamdogood/builder-essential-skills
Run a cumulative daily or retrospective sweep of research papers on a chosen topic, audit their claims, methods, integrity signals, and independent support, then identify overlooked but feasible…
Related
Categories
Questions about Code Standards
What does Code Standards do?
Apply a disciplined engineering workflow to any code change. Code Standards is an agent skill from tamdogood/builder-essential-skills. Apply a disciplined engineering workflow to any code change.
When should I use Code Standards?
Code Standards fits situations like: implementing a feature; refactoring — before writing code.
How do I install Code Standards in Claude Code?
Run `npx skills add tamdogood/builder-essential-skills --skill code-standards -a claude-code`. Or copy the skill folder (skills/code-standards in tamdogood/builder-essential-skills) into .claude/skills/code-standards in your project. Claude Code loads it when a task matches its description.
How do I install Code Standards in Codex?
Run `npx skills add tamdogood/builder-essential-skills --skill code-standards -a codex`. Or copy the skill folder (skills/code-standards in tamdogood/builder-essential-skills) into .agents/skills/code-standards in your project. Codex loads it when a task matches its description.
Can I use Code Standards in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tamdogood/builder-essential-skills --skill code-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-standards, .gemini/skills/code-standards, .github/skills/code-standards and .opencode/skills/code-standards in your project.
What does Code Standards need to run?
SKILL.md names no scripts, command-line tools or credentials: Code Standards is instructions for the agent only. Compatibility (from SKILL.md): claude-code.
Does Code Standards access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Code Standards safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Code Standards use?
Code Standards is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Code Standards use?
About 738 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Code Standards?
Skills that share tags, products or a category with Code Standards: Rust Best Practices (farm-fe/farm, 5.6k stars), File Good First Bug (BrowserWorks/waterfox-android, 379 stars), Unslop Code (JCarterJohnson/vibecoded-design-tells, 511 stars) and Code Quality Gate (fengshao1227/ccg-workflow, 5.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Standards?
tamdogood (a GitHub user) maintains it in tamdogood/builder-essential-skills, which has 219 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on August 16, 2026.
Source: tamdogood/builder-essential-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.