/code-standards

TypeScript, React, and JavaScript best practices enforced by Ultracite/Biome.

BOOST

redpanda-data@redpanda-data

GitHub

From plugin

console

4.3k11 skills4 agents2 commands2 MCP

Install

$ npx -y skills add redpanda-data/console --skill code-standards --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/code-standards

Context preview

The summary Claude sees to decide when to auto-load this skill.

TypeScript, React, and JavaScript best practices enforced by Ultracite/Biome.

SKILL.md

code-standards.SKILL.md

name: code-standards
description: TypeScript, React, and JavaScript best practices enforced by Ultracite/Biome.

Code 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`, or `console.info` in production code
Only use `console.error` and `console.warn` for actionable errors
For debug logging, wrap in `if (IsDev) { ... }`
Don't use `biome-ignore` to suppress console warnings - remove the logs instead