TypeScript, React, and JavaScript best practices enforced by Ultracite/Biome.
67
51%
Does it follow best practices?
Impact
92%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./frontend/.claude/skills/code-standards/SKILL.mdAsync/await patterns and console logging
async/await not .then()
100%
100%
Promise.all for concurrency
100%
100%
No floating promises
100%
100%
No async in Promise executor
100%
100%
try/catch error handling
100%
100%
No console.log/debug/info
100%
100%
console.error/warn only for errors
100%
100%
No biome-ignore suppressions
100%
100%
No explicit `any` type
100%
100%
Vitest not Jest
0%
100%
No .then() in tests
100%
100%
React functional components, hooks rules, modern imports
Functional component only
100%
100%
No nested component definitions
100%
100%
Hooks at top level
100%
100%
Named export
87%
100%
useState for open/close
100%
100%
Sonner toast not useToast
0%
0%
No Chakra or Redpanda UI imports
100%
100%
Zod not Yup
0%
100%
No explicit `any` type
100%
100%
Vitest not Jest
100%
100%
No biome-ignore suppressions
100%
100%
Zustand global state, no legacy patterns, Vitest tests
Zustand not MobX
100%
100%
Not in src/state/
0%
0%
No MobX decorators
100%
100%
Functional component
100%
100%
Named export
100%
100%
No Chakra or Redpanda UI imports
100%
100%
No explicit `any` type
100%
100%
Vitest not Jest
100%
100%
Zustand create() pattern
100%
100%
No console.log/debug/info
100%
100%
02210fa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.