@plinng/ai-code-assistant-tools

Versioned, modular AI coding standards for the Plinng platform. Provides behavioral and architectural rules for Claude Code and Cursor that encode what linters and formatters cannot: architectural intent, error philosophy, and design discipline.

What this is

These are not linter rules. ESLint, Prettier, Ruff, and Biome handle formatting and style deterministically at zero LLM token cost. These rules encode the decisions that static analysis has no reach into:

• Which layer is responsible for what.
• When and how to handle errors.
• Which design patterns to prefer and why.
• SOLID principles and how to apply them in this codebase.

Rules included

| Rule file | Tool | Activated when | Enforces | |---|---|---|---| | CLAUDE.md / universal.mdc | Both | Always | How to work, commits, task runner, error + architecture summary | | error-handling.md/mdc | Both | **/*.ts, **/*.py | No silent catches; structured boundary logging; propagation discipline | | architecture.md/mdc | Both | **/handlers/**, **/resolvers/**, **/routes/**, **/app/** | Layer ordering; no DB client in handlers; factory injection | | solid-principles.md/mdc | Both | **/*.ts, **/*.tsx | SRP, OCP, LSP, ISP, DIP; don't refactor violations unless asked | | clean-architecture.md/mdc | Both | **/*.ts, **/*.py | Four-layer model; domain types from repositories; coupling detector | | design-patterns.md/mdc | Both | Always (Claude) / Agent Requested (Cursor) | Propose pattern + rationale before implementing |

Install

Interactive CLI

npx @plinng/ai-code-assistant-tools

The installer will ask which AI assistant you use (Claude Code / Cursor / Both) and, for Cursor, whether to install at project scope or user scope. Existing files are backed up automatically as <file>.backup-<timestamp>

Manual install — Claude Code

cp claude-code/CLAUDE.md ~/.claude/CLAUDE.md
cp claude-code/rules/*.md ~/.claude/rules/

Manual install — Cursor (project scope)

cp -r cursor/rules/ .cursor/rules/

Cursor scope note

Project scope (.cursor/rules/) is the reliably enforced path for teams. Rules installed there are version-controlled and apply to every developer who opens the project in Cursor.

User scope (~/.cursor/rules/) is a filesystem convention. Cursor reads user rules from its Settings UI (plain text), not from a filesystem path directly. To apply user rules from this install, paste the content of each .mdc file into Cursor Settings → General → Rules for AI, or use Cursor Team Rules (requires Cursor Team/Enterprise plan) for enforced team standards.

Updating

Re-run the installer to get the latest rules. Existing files will be backed up before overwriting:

npx @plinng/ai-code-assistant-tools

Contributing

Before adding or modifying a rule, verify it meets this checklist:

1. Cannot be enforced by a linter — if ESLint/Ruff can catch it, it belongs in tool config, not here
2. Imperative with motivation — "Use X because Y", not "Consider using X"
3. Both .md and .mdc updated — keep Claude Code and Cursor rule content in sync
4. Line count passes — run moon run ai-code-assistant-tools:lint-rules
5. PR to platform team — rules affect all engineers; review is required

moon run ai-code-assistant-tools:lint-rules