/creating-claude-rules-skill
Use when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApply
$ npx -y skills add AgentWorkforce/relay --skill creating-claude-rules-skill --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/creating-claude-rules-skill
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApply
SKILL.md
creating-claude-rules-skill.SKILL.mdname: creating-claude-rules
description: Use when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApply
Creating Claude Rules
Overview
Rules in `.claude/rules/` are modular instructions scoped to specific files via glob patterns. They load automatically with same priority as `CLAUDE.md`.
When to Use
- Creating new rules in `.claude/rules/`
- Fixing rules that use wrong frontmatter (`globs` instead of `paths`)
- Migrating Cursor rules to Claude format
- Organizing project-specific conventions
Quick Reference
| Field | Claude | Cursor | | ------------- | -------------- | ------------------- | | Path patterns | `paths` | `globs` | | Always apply | Omit `paths` | `alwaysApply: true` | | Description | Not documented | `description` |
Frontmatter
Path-Scoped Rules
---
paths:
- 'src/api/**/*.ts'
- 'tests/**/*.test.ts'
---
Or single pattern:
---
paths: src/**/*.{ts,tsx}
---Global Rules
Omit frontmatter entirely - applies to all files:
# TypeScript Conventions
Use .js extensions in imports.
Common Mistakes
# ❌ WRONG - globs is Cursor format
---
globs:
- '**/*.ts'
---
# ✅ CORRECT - Claude uses paths
---
paths:
- '**/*.ts'
---
# ❌ WRONG - alwaysApply is Cursor-only
---
alwaysApply: true
---
# ✅ CORRECT - just omit paths for global rules
# (no frontmatter needed)
# ❌ WRONG - unquoted patterns
---
paths:
- **/*.ts
---
# ✅ CORRECT - quote glob patterns
---
paths:
- "**/*.ts"
---
Directory Structure
.claude/rules/
├── testing.md # Path-scoped or global
├── typescript.md
└── frontend/ # Subdirectories supported
└── react.mdFiles discovered recursively. Use subdirectories to organize.
Glob Patterns
| 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/ |
Reference
https://code.claude.com/docs/en/memory#modular-rules-with-claude/rules/
Read more
name: creating-claude-rules description: Use when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApply
Creating Claude Rules
Overview
Rules in `.claude/rules/` are modular instructions scoped to specific files via glob patterns. They load automatically with same priority as `CLAUDE.md`.
When to Use
- Creating new rules in `.claude/rules/`
- Fixing rules that use wrong frontmatter (`globs` instead of `paths`)
- Migrating Cursor rules to Claude format
- Organizing project-specific conventions
Quick Reference
| Field | Claude | Cursor | | ------------- | -------------- | ------------------- | | Path patterns | `paths` | `globs` | | Always apply | Omit `paths` | `alwaysApply: true` | | Description | Not documented | `description` |
Frontmatter
Path-Scoped Rules
--- paths: - 'src/api/**/*.ts' - 'tests/**/*.test.ts' ---
Or single pattern:
---
paths: src/**/*.{ts,tsx}
---Global Rules
Omit frontmatter entirely - applies to all files:
# TypeScript Conventions Use .js extensions in imports.
Common Mistakes
# ❌ WRONG - globs is Cursor format --- globs: - '**/*.ts' --- # ✅ CORRECT - Claude uses paths --- paths: - '**/*.ts' ---
# ❌ WRONG - alwaysApply is Cursor-only --- alwaysApply: true --- # ✅ CORRECT - just omit paths for global rules # (no frontmatter needed)
# ❌ WRONG - unquoted patterns --- paths: - **/*.ts --- # ✅ CORRECT - quote glob patterns --- paths: - "**/*.ts" ---
Directory Structure
.claude/rules/
├── testing.md # Path-scoped or global
├── typescript.md
└── frontend/ # Subdirectories supported
└── react.mdFiles discovered recursively. Use subdirectories to organize.
Glob Patterns
| 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/ |
Reference
https://code.claude.com/docs/en/memory#modular-rules-with-claude/rules/
Let Claude Code message Codex. Let your Hyperagent talk to your Hermes agent. Give your custom agents a way to message each other.
Repo: AgentWorkforce/relay
Other skills on relay.
- /browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality
Open skill - /choosing-swarm-patterns
Use when coordinating multiple AI agents with Agent Relay's workflow engine and need to pick the right orchestration pattern - covers the 10 core patterns (fan-out, pipeline, hub-spoke, consensus, mesh, handoff, cascade, dag, debate, hierarchical) plus 14 specialized ones, with
Open skill - /creating-claude-agents-skill
Use when creating or improving Claude Code agents. Expert guidance on agent file structure, frontmatter, persona definition, tool access, model selection, and validation against schema.
Open skill - /creating-claude-hooks-skill
Use when creating or publishing Claude Code hooks - covers executable format, event types, JSON I/O, exit codes, security requirements, and PRPM package structure
Open skill - /creating-skills-skill
Use when creating new Claude Code skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, CSO optimization, and real examples
Open skill - /debugging-websocket-issues
Use when seeing WebSocket errors like "Invalid frame header", "RSV1 must be clear", or "WS_ERR_UNEXPECTED_RSV_1" - covers multiple WebSocketServer conflicts, compression issues, and raw frame debugging techniques
Open skill

