smithery/itsmealee

applying-clean-code

General syntax and naming rules to keep the codebase maintainable. Use for all code generation.

Installation

$ npx skills add smithery/itsmealee --skill applying-clean-code

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/itsmealee.

npx skills add smithery/itsmealee

Browse all from smithery/itsmealee

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,047 B
  • docs SUMMARY.md 122 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Clean Code Principles

When to use this skill

  • Naming variables, functions, and files.
  • Deciding on function size and complexity.

Principles

  • Self-Documenting Names: isBookingPending > status === 1.
  • DRY (Don't Repeat Yourself): If logic is duplicated, move it to a utility or hook.
  • KISS (Keep It Simple, Stupid): Avoid over-engineering complex solutions for simple tasks.
  • Constants: Use const over let. Use uppercase constants for magic numbers/IDs: const MAX_GUESTS = 20;.

Naming Conventions

  • Components: PascalCase (TourCard.tsx).
  • Functions/Variables: camelCase (handleSubmit).
  • Interfaces: PascalCase (TourInfo).
  • Files: kebab-case or PascalCase (stay consistent with project structure).

Instructions

  • Avoid Comments: Write code so clear that comments are mostly unnecessary. Only comment the "why," not the "what."