best-practices
Language-specific best practices, code quality standards, and framework detection rules. Use when executing refactoring workflows, applying code quality rules, detecting frameworks, or checking language-specific patterns for TypeScript, Python, Go, Swift, or React.
- Installs
- 114
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/fradser/dotclaude --skill best-practices- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads best-practices automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Best Practices
Language References
Each file extension maps to a specific reference:
.ts,.js—references/typescript.md.tsx,.jsx—references/typescript.md+references/react/react.md.py—references/python.md+references/python/INDEX.md.go—references/go.md.swift—references/swift.md
Universal principles are in references/universal.md.
Next.js/React References
For Next.js projects, the references/react/ directory provides:
references/react/rules/INDEX.md— pattern index by impact levelreferences/react/rules/_sections.md— priorities and categories- Specific rule files matching observed patterns
Rule Application
- Framework-specific rules (e.g., Next.js) apply only when that framework is detected
- CRITICAL rules have highest priority: waterfalls, bundle size, hydration
- All refactoring MUST preserve behavior and public interfaces
Code Quality Standards
- Comments: Only for complex business logic; code-restating comments are unnecessary
- Error Handling: Try-catch only where recoverable; no defensive checks in trusted paths
- Type Safety: No
any; proper types orunknownwith guards are required - Style: Existing code style and CLAUDE.md conventions take precedence
- Cleanup: Unused imports, variables, functions, and types are removed
- No compat hacks: Unused
_varsand re-exports of deleted code are deleted - Renaming: Descriptive names are preferred over marking as unused
- Dead code: Dead code is deleted, never commented out
- File Organization: Single Responsibility applies at file level; files with multiple concerns are candidates for splitting (see
references/universal.md)
FAQ
What does the best-practices skill do?
Language-specific best practices, code quality standards, and framework detection rules. Use when executing refactoring workflows, applying code quality rules, detecting frameworks, or checking language-specific patterns for TypeScript, Python, Go, Swift, or React.
How do I install best-practices?
Run npx skills add https://github.com/fradser/dotclaude --skill best-practices in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/best-practices/ (personal) or .claude/skills/best-practices/ (project).
Which AI agents can use best-practices?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is best-practices safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains best-practices?
It is published by fradser in fradser/dotclaude. It has 114 recorded installs.
More from fradser/dotclaude
patent-architect
fradser/dotclaude
Automatically searches prior art via SerpAPI and generates Chinese patent application forms. This skill should be used when the user wants to generate Chinese patent application forms, or mentions "patents", "inventions", or wants to protect technical innovations.
agent-browser
fradser/dotclaude
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
behavior-driven-development
fradser/dotclaude
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
executing-plans
fradser/dotclaude
Executes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches.
commit-and-push
fradser/dotclaude
Creates clean conventional git commits using standard git and pushes changes to the remote repository. Use when the user asks to "commit and push", "push changes", or complete a commit followed by git push.
brainstorming
fradser/dotclaude
Designs new software features and multi-component changes for the current repo into implementation-ready BDD specs via autonomous codebase research, then commits the design for review (runs to completion without mid-design questions). Scope covers new features, greenfield design, and multi-component changes. Not for hardware/physical-system design, out-of-repo questions, single-file refactors, or known-root-cause bugs (those go to direct edits or systematic-debugging).
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.