r3ckon-style

A Claude Code skill library. The rules I would otherwise retype at the top of every session.

Six skills, one plugin. Install it as is, or fork it and swap in your own rules.

Install · Skills · The rules · Adding a skill

---

Install

/plugin marketplace add localhostd3veloper/r3ckon-style
/plugin install r3ckon-style@r3ckon-style

Update later with /plugin marketplace update r3ckon-style.

Skills

Skill	Fires when
code-style	Writing or editing code in any language. The universal rules.
frontend-standards	React components, hooks, App Router pages, Tailwind, shadcn.
backend-standards	Route handlers, server actions, MongoDB, API contracts.
style-review	Reviewing a diff or branch against all of the above.
git-conventions	Writing a commit message, naming a branch, opening a PR.
humanize	Writing or editing any prose a person will read.

Each one loads itself from its description, so a normal request activates the right skill. Force one with /code-style, /style-review, and so on.

code-style is the base. Frontend and backend assume it and cover only their own side.

The rules

Every rule ships with its replacement. A ban on its own just gets worked around.

Instead of	Do this
a comment	rename or restructure until the code reads
an em dash	a comma, colon, parentheses, or a full stop
an if/else ladder	a switch
a nested conditional	a guard clause and an early return
letting a file grow	split it: 200 lines frontend, 1000 everywhere else
setState in useEffect	derive during render, reset by key, or an event handler
reading input unparsed	a Zod parse at the boundary
returning a Mongo doc	map it to a response type
committing when done	finish, build, report, then ask

Comments have three exceptions: Zod .describe(), //#region splitting queries from mutations in a hook file, and a named workaround for an external bug.

All twelve rules are on the docs site with the bad version and the replacement side by side, filterable by universal, frontend, backend, and git.

Adding a skill

Copy templates/SKILL.template.md to plugins/r3ckon-style/skills/<name>/SKILL.md.

The description is the only part read when deciding whether to load a skill, so name real triggers: file types, libraries, the words you would use in an actual request. "Best practices for code quality" never fires. "React components, hooks, App Router pages, Tailwind classes" does.

Keep the body short and push detail into a sibling reference/ file, the way humanize does with its word lists.

To iterate without reinstalling after every edit, symlink the skill into your user directory:

ln -s "$PWD/plugins/r3ckon-style/skills/code-style" ~/.claude/skills/code-style

Skills reload on the next session. Remove the symlink once you install the plugin for real, otherwise the same skill registers twice.

Layout

plugins/r3ckon-style/skills/   the six skills
templates/SKILL.template.md    starting point for a new one
docs/                          the site, served from GitHub Pages

License

MIT.