Coding standards for AI coding assistants. Auto-detect tech stack, generate project rules. Works with Claude Code, Cu...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health 42/100. no security policy. 1 open issues make this testable, but not something to trust blind.
AI Agent
Multiple
Model
Multiple
Fastest way to find out if claude-rules belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
# Visit: https://github.com/lifedever/claude-rulesRun this first. You will know quickly if the workflow earns a permanent slot.
# No automated removal — visit https://github.com/lifedever/claude-rulesNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ claude-rules/ ← installs here └─ settings.json
Coding standards for AI coding assistants. Auto-detect tech stack, generate project rules. Works with Claude Code, Cursor, Antigravity, GitHub Copilot.. An open-source skill for the AI coding ecosystem.
Source: GitHub repository
Source check: July 28, 2026
Upstream commit: March 19, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.