AgentSkillsCN

rules

将Arc的编码规则应用于当前项目。将规则复制到.ruler/目录。 当被要求“设置编码规则”、“应用标准”、“配置规则”，或当开始一个应遵循Arc惯例的项目时使用。

SKILL.md
--- frontmatter
name: rules
disable-model-invocation: true
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
website:
  order: 20
  desc: Apply standards
  summary: Apply Arc's coding standards to your project. TypeScript, React, Next.js, testing patterns, UI conventions—all in .ruler/ where every AI tool can read them.
  what: |
    Rules copies Arc's coding standards to your project's .ruler/ directory: TypeScript patterns, React conventions, Next.js best practices, Tailwind usage, testing strategies, and UI design guidelines. Every Arc skill reads from .ruler/ when generating or reviewing code—so the AI follows your project's standards, not generic ones.
  why: |
    Without shared standards, every AI-generated file is inconsistent. Rules puts the playbook in one place that all AI tools can read. Combined with Ruler (optional), these standards propagate to Copilot, Cursor, and other agents—so your whole toolchain follows the same conventions.
  decisions:
    - Copy, not symlink. Projects can customize rules for their needs.
    - Backup on update. Your customizations are never lost.
    - Optional Ruler integration. Distributes rules to Copilot, Cursor, and other agents.
code

───────────────────────────────────────────────────────────

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:

bash
cp -r ${CLAUDE_PLUGIN_ROOT}/rules/ .ruler/

Tell the user:

code
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:

code
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:

bash
# 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:

code
Rules updated. Backup saved to .ruler.backup-YYYYMMDD-HHMMSS/

Review changes with: git diff .ruler/

Go to Step 4 (Offer Ruler)

If no:

code
Keeping existing rules. You can manually compare with Arc's rules at:
${CLAUDE_PLUGIN_ROOT}/rules/

Done.

Step 4: Offer Ruler

Ask the user:

code
Want me to run `npx ruler apply` to distribute rules to other AI agents (Copilot, Cursor, etc.)?

If yes:

bash
npx ruler apply

If ruler is not installed (command fails):

code
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:

code
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>