rules
Apply Arc's coding rules to the current project. Copies rules to .ruler/ directory. Use when asked to "set up coding rules", "apply standards", "configure rules", or when starting a project that should follow Arc's conventions.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: rules description: | Apply Arc's coding rules to the current project. Copies rules to .ruler/ directory. Use when asked to "set up coding rules", "apply standards", "configure rules", or when starting a project that should follow Arc's conventions. license: MIT metadata: author: howells
───────────────────────────────────────────────────────────
Apply Arc's coding standards to the current project.
<process>Step 1: Check for existing rules
Use Glob tool: .ruler/*.md
If .ruler/ does not exist: Go to Step 2 (Fresh Install)
If .ruler/ exists: Go to Step 3 (Update Flow)
Step 2: Fresh Install
Copy all rules from Arc to the project:
cp -r ${CLAUDE_PLUGIN_ROOT}/rules/ .ruler/
Tell the user:
Rules copied to .ruler/
Files added:
- code-style.md, env.md, git.md, integrations.md
- nextjs.md, react.md, tailwind.md, testing.md
- turborepo.md, typescript.md, versions.md
- interface/ (animation, design, forms, interactions, layout, performance, typography)
Go to Step 4 (Offer Ruler)
Step 3: Update Flow
Existing .ruler/ found. Ask the user:
Found existing .ruler/ in this project.
Update with Arc's latest rules? This will:
1. Backup current rules to .ruler.backup-TIMESTAMP/
2. Overwrite with Arc's rules
You can review changes with `git diff .ruler/` after.
Update rules? (y/n)
If yes:
# Create backup
cp -r .ruler/ ".ruler.backup-$(date +%Y%m%d-%H%M%S)/"
# Copy fresh rules
rm -rf .ruler/
cp -r ${CLAUDE_PLUGIN_ROOT}/rules/ .ruler/
Tell the user:
Rules updated. Backup saved to .ruler.backup-YYYYMMDD-HHMMSS/
Review changes with: git diff .ruler/
Go to Step 4 (Offer Ruler)
If no:
Keeping existing rules. You can manually compare with Arc's rules at:
${CLAUDE_PLUGIN_ROOT}/rules/
Done.
Step 4: Offer Ruler
Ask the user:
Want me to run `npx ruler apply` to distribute rules to other AI agents (Copilot, Cursor, etc.)?
If yes:
npx ruler apply
If ruler is not installed (command fails):
Ruler not found. Rules are in .ruler/ and ready for use.
To distribute to other AI agents, install ruler:
npm install -g ruler
Then run:
npx ruler apply
If no:
Rules are ready in .ruler/. Run `npx ruler apply` later if you want to distribute to other agents.
Done.
</process> <notes> - Rules are copied, not symlinked, so projects can customize - Backup ensures user customizations are never lost - Ruler is optional — Arc works without it - After copying, rules are immediately available to Arc skills that read from `.ruler/` </notes>More by howells
View allPersistent task backlog that survives across sessions. Git-committed, always available. Use when asked to "add a task", "show my tasks", "update the backlog", "prioritize", or when managing what needs to be done across sessions.
Remove LLM-generated artifacts from code. Cleans unnecessary comments and defensive checks. Use when asked to "clean up the code", "remove AI slop", "deslop this", or after AI-assisted coding sessions to remove artifacts that don't match codebase style.
Create or review a high-level vision document capturing project goals and purpose. Use when asked to "define the vision", "what is this project", "set goals", or when starting a new project that needs clarity on purpose and direction.
Execute an implementation plan task-by-task with TDD and continuous quality checks. Use when asked to "implement the plan", "execute the tasks", "start building from the plan", or after /arc:detail has created an implementation plan ready for execution.