About code-standards
A coding standards skill for developers addressing lint, formatting, review feedback, and style questions. It provides concise guidance and Ultracite commands for checking and fixing issues.
Key features
- 01Lint and formatting guidance
- 02React component and async rules
- 03Biome-enforced type and regex rules
- 04Ultracite fix, check, and doctor commands
- 05Production console logging guidance
Use cases
- 01Fixing lint errors in a codebase
- 02Applying consistent formatting
- 03Responding to code review style feedback
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ redpanda-data/ console --skill code-standardsAfter installing, type/code-standardsin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
rules/async-await-promises.mdno-legacy.mdreact-functional-only.mdDetails
From the project READMECode Standards
Write code that is accessible, performant, type-safe, and maintainable.
Activation Conditions
- Linting errors need fixing
- Code formatting issues
- Code review feedback
- Questions about style guidelines
Quick Reference
| Action | Rule |
|---|---|
| Write components | react-functional-only.md |
| Async code | async-await-promises.md |
| Avoid legacy libs | no-legacy.md |
any types and top-level regex are enforced by Biome (noExplicitAny, useTopLevelRegex).
Commands
bun x ultracite fix # Format and fix
bun x ultracite check # Check for issues
bun x ultracite doctor # Diagnose setup
Quick Fix
Most issues are auto-fixed:
bun x ultracite fix
Console Logging
- Never use
console.log,console.debug, orconsole.infoin production code - Only use
console.errorandconsole.warnfor actionable errors - For debug logging, wrap in
if (IsDev) { ... } - Don't use
biome-ignoreto suppress console warnings - remove the logs instead
Rules
See rules/ directory for detailed guidance.
Comments
Markdown supported