.agents/skills/creating-claude-rules-skill/SKILL.md
Use when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApply
npx skillsauth add AgentWorkforce/relayfile creating-claude-rulesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Rules in .claude/rules/ are modular instructions scoped to specific files via glob patterns. They load automatically with same priority as CLAUDE.md.
.claude/rules/globs instead of paths)| Field | Claude | Cursor |
|-------|--------|--------|
| Path patterns | paths | globs |
| Always apply | Omit paths | alwaysApply: true |
| Description | Not documented | description |
---
paths:
- "src/api/**/*.ts"
- "tests/**/*.test.ts"
---
# TypeScript Conventions
Use .js extensions in imports.
# ❌ WRONG - globs is Cursor format
---
globs:
- "**/*.ts"
---
# ✅ CORRECT - Claude uses paths
---
paths:
- "**/*.ts"
---
.claude/rules/
├── testing.md # Path-scoped or global
├── typescript.md
└── frontend/ # Subdirectories supported
└── react.md
| Pattern | Matches |
|---------|---------|
| **/*.ts | All .ts files anywhere |
| src/**/* | Everything under src/ |
| *.md | Markdown in root only |
| **/*.{ts,tsx} | .ts and .tsx files |
| {src,lib}/**/*.ts | .ts in src/ or lib/ |
https://code.claude.com/docs/en/memory#modular-rules-with-claude/rules/
devops
Use when an agent needs to self-bootstrap agent-relay and autonomously manage a team of workers - covers infrastructure startup, agent spawning, lifecycle monitoring, and team coordination without human intervention
development
Use when building multi-agent workflows with the relay broker-sdk - covers the WorkflowBuilder API, DAG step dependencies, agent definitions, step output chaining via {{steps.X.output}}, verification gates, evidence-based completion, owner decisions, dedicated channels, dynamic channel management (subscribe/unsubscribe/mute/unmute), swarm patterns, error handling, event listeners, step sizing rules, authoring best practices, and the lead+workers team pattern for complex steps
devops
Use when an agent needs to self-bootstrap agent-relay and autonomously manage a team of workers - covers infrastructure startup, agent spawning, lifecycle monitoring, and team coordination without human intervention
data-ai
Use when working in a shared relayfile virtual filesystem with other agents - covers reading/writing files with metadata, discovering other agents' work, conflict handling, ACL permissions, and real-time collaboration patterns