rule

Create and update instruction files with YAML frontmatter across user, workspace, and path scopes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jeff-hamm/ai-tools --skill rule-jeff-hamm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule
Source: https://github.com/jeff-hamm/ai-tools/tree/main/src/skills/rule
Command: npx skills add https://github.com/jeff-hamm/ai-tools --skill rule-jeff-hamm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured method to create, edit, and refactor instruction/rules files across user, workspace, and path scopes, enabling consistent governance of prompts and automation rules.

Core Features & Use Cases

  • Create or update instruction/rules files in the correct scope directories (e.g., ~/.agents/rules/ for user rules, workspace rules in .github/instructions or project-specific paths) following the YAML frontmatter conventions.
  • Use YAML frontmatter with name and description, plus applyTo for path-scoped rules, to ensure precise auto-attachment and discovery.
  • Follow the documented workflow including safety checks, backups, and change-control steps to safeguard edits.

Quick Start

Create a new rule file in the appropriate scope directory, include the required YAML frontmatter with description, and implement the rule content in the body.

Frequently Asked Questions about rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create workspace rules with correct YAML frontmatter and scope placement?

Workspace rules require YAML frontmatter with name and description fields, placed in scope-specific directories like .github/instructions. This Skill automates creation and updates of instruction files while enforcing correct path placement and frontmatter conventions for consistent governance.

What's the best way to manage path-specific instruction files across different project scopes?

Managing path-specific instruction files involves using the applyTo field in YAML frontmatter to target specific paths. This Skill automates placement across user, workspace, and project scopes, ensuring precise auto-attachment and discovery of rules where they apply.

How does the safe-change workflow handle backups and safety checks when editing rules files?

The safe-change workflow safeguards rule edits through documented safety checks, backups, and change-control steps. This Skill integrates with that workflow to ensure modifications to instruction files across scopes are performed safely and with proper governance.

Can I use this to set up personal rules in addition to workspace-wide policies?

Yes, personal rules are supported through placement in ~/.agents/rules/ directories. This Skill handles user-level rules, workspace-wide policies, and path-specific rules, enabling consistent governance across all scope levels.

Do I need any dependencies or components to create and refine instruction files?

No dependencies or components are required to create and refine instruction files. This Skill operates independently to automate creation and updates of rules files with correct scope placement and YAML frontmatter enforcement.

When should I use applyTo in frontmatter versus creating a workspace-wide instruction file?

Use applyTo in YAML frontmatter when rules need to target specific file paths within a project. Workspace-wide instruction files apply broadly, while path-scoped rules with applyTo ensure precise auto-attachment only where relevant.