Plugin · Claude Code · Development Tools

Cameronsjo Rules

cameronsjo-rules is a Claude Code plugin for the Ship phase that enforces language, security, quality, git, CI/CD, Docker, MCP, and documentation standards while you work.

by cameronsjo · github.com/cameronsjo/rules

Load persistent Claude Code rules for language standards, security, quality, git, CI/CD, Docker, MCP, and documentation across projects.

0
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install cameronsjo-rules@cameronsjo/rules
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:cameronsjo/rules") and the paste-ready config with skillselion.get_install_config("plugin:cameronsjo/rules").

About

What it does

cameronsjo-rules is a Claude Code plugin that injects how-to-work-with-code guidance: language standards, security expectations, quality bars, git hygiene, CI/CD, Docker practices, MCP usage, and documentation norms. Indie builders install it to stop re-explaining conventions every session and to keep Claude’s edits aligned with shipping discipline, not just feature velocity. The rules act as a lightweight governance layer you can lean on during implementation, pre-merge review, and launch prep—canonical on Ship → review because that is when inconsistent style and missing security checks hurt most. It complements task-specific skills and MCP servers by defining baseline behavior for any repo. One plugin in the marketplace entry keeps setup simple: register cameronsjo/rules and let Claude apply the standards whenever you code, refactor, or prepare releases.

Highlights

  • Single-plugin rules pack (plugin count: 1) covering language standards and documentation
  • Security and quality guardrails aligned with solo-ship workflows
  • Git, CI/CD, and Docker conventions for repeatable delivery
  • MCP usage guidance bundled with general engineering standards
  • Keyword themes: docker, documentation, language, quality, rules, security, standards

Why builders use it

Without shared rules, Claude drifts on style, security, and delivery practices across git, Docker, and CI/CD tasks.

After install, Claude follows a consistent rules plugin for standards, review-minded quality, and documented workflows on every change.

At a glance

  • Type - Plugin in Development Tools.
  • Adoption - 0 installs, 0 stars, 0 votes.

FAQ

Who is cameronsjo-rules for?

It is for Claude Code users who want default language, security, quality, git, CI/CD, Docker, MCP, and documentation standards applied during development and review.

When should I use cameronsjo-rules?

Use it when starting or refactoring a project and whenever you want Claude to respect shipping discipline—not only when writing features.

How do I add cameronsjo-rules to my agent?

Install the cameronsjo/rules Claude Code plugin from the marketplace or repo and enable it so rules load with your Claude Code sessions per plugin documentation.

Discussion

Comments

Share how you use cameronsjo-rules, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.