Skill

best-practices

Applies best practices, code quality rules, and framework detection for TypeScript, React/Next.js, Python, Go, and Swift in refactoring and pattern checking workflows.

React

Next.js

npx claudepluginhub fradser/dotclaude --plugin refactor

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Each file extension maps to a specific reference:

Supporting Assets

SKILL.md

Similar Skills

applying-brand-guidelines

41.6k

Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.

3 files

anthropics-claude-cookbooks

creating-financial-models

41.6k

Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.

2 files

anthropics-claude-cookbooks

analyzing-financial-statements

41.6k

Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.

2 files

anthropics-claude-cookbooks

Stats

Parent Repo Stars512

Parent Repo Forks39

Last CommitMar 23, 2026

Actions

View Source View Plugin View on GitHub View README

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 level
references/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 or unknown with 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 _vars and 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)