rails-toolkit
CLAUDE.md2 starsChanged 8 days agoMITView on GitHub
Make sure to check all of the following and make sure they are up-to-date after making changes; 1. tool-specific documentation for tools you edited 2. skills for tools you edited 3. plugin.json 4. README.md 5. CLAUDE.md Bump the plugin version on every commit. Patch version for small fixes, minor version for more substantial changes (new skill or tool). This repo follows the dev-hooks dev-env standard (shell/Claude Code plugin stack, DEV_ENV_VERSION in mise.toml). Tools are pinned via mise + mise.lock; pre-commit…
In this repository24 other files it gives its agents.
- rails-activestorageSkill
- rails-apiSkill
- rails-auditSkill
- rails-clean-test-outputSkill
- rails-controllersSkill
- rails-coreSkill
- rails-database-performanceSkill
- rails-i18nSkill
- rails-jobsSkill
- rails-loggingSkill
- rails-mailersSkill
- rails-migrationsSkill
- rails-modelsSkill
- rails-multi-tenancySkill
- rails-performanceSkill
- rails-philosophySkill
- rails-project-setupSkill
- rails-securitySkill
- rails-stimulusSkill
- rails-styleSkill
- rails-testingSkill
- rails-turboSkill
- rails-upgradeSkill
- rails-viewcomponentsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 1
Make sure to check all of the following and make sure they are up-to-date after making changes.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Make sure to check all of the following and make sure they are up-to-date after making changes;
- tool-specific documentation for tools you edited
- skills for tools you edited
- plugin.json
- README.md
- CLAUDE.md
Bump the plugin version on every commit. Patch version for small fixes, minor version for more substantial changes (new skill or tool).
Development
This repo follows the dev-hooks dev-env standard (shell/Claude Code plugin stack, DEV_ENV_VERSION in mise.toml). Tools are pinned via mise + mise.lock; pre-commit checks run via hk and are mirrored in CI (.github/workflows/ci.yml).
- Provision tools:
mise trust && mise install(hk, pkl, shellcheck, shfmt, ruff, uv, python, node, gitleaks). - Install the git hook:
hk install. - Lint + audits (shellcheck/shfmt/ruff, vulture dead-code, jscpd duplication, gitleaks, large-file guard):
hk run check. - Tests:
uv run pytest— every bundled script inbin/must have a test that runs it as a subprocess and asserts on real output (seetests/test_scripts.py). - Any new Python script must be self-contained (PEP 723 inline deps,
#!/usr/bin/env -S uv run --script).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.