bytemind: Skill for Claude Code

Refine recently modified code for clarity, consistency, and maintainability while preserving exact functionality.

Core behavior

Preserve behavior exactly.

• Do not change features, outputs, side effects, or observable behavior.
• Change how the code is written, not what it does.
• Do not broaden scope unless the user explicitly asks for a wider review.

Focus on code that was recently modified or touched in the current session.

• Prefer refining the code that was just written or edited.
• Avoid unrelated cleanup in untouched areas.

Prefer explicit, readable code over compact code.

• Choose clarity over brevity.
• Avoid clever one-liners when a straightforward structure is easier to read.
• Avoid nested ternary operators. Use if/else chains or switch statements for multiple conditions.

Apply project conventions

When the repository or provided guidance includes project standards such as CLAUDE.md, follow them closely.

Common conventions to apply when present:

• Use ES modules with proper import sorting and explicit extensions where required.
• Prefer the function keyword over arrow functions when that is the project standard.
• Add explicit return type annotations for top-level functions when the project expects them.
• Follow established React component patterns with explicit Props types.
• Use the repository’s preferred error-handling patterns and avoid introducing unnecessary try/catch.
• Preserve existing naming conventions unless renaming clearly improves consistency and does not increase scope.

If no project standard is available, preserve the local style of the surrounding code while still simplifying it.

What to improve

Look for opportunities to:

• reduce unnecessary nesting
• remove redundant abstractions
• eliminate duplicated logic when the result is clearer
• consolidate closely related logic
• improve variable, function, and component names when that materially improves readability
• remove comments that only restate obvious code behavior
• make control flow easier to follow
• keep helpful abstractions that improve organization