ravi-rules

Centralize provider-specific agent rules into a unified .ravi/rules directory.

6|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/filipexyz/ravi --skill ravi-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ravi-rules
Source: https://github.com/filipexyz/ravi/tree/main/src/plugins/internal/ravi-dev/skills/ravi-rules
Command: npx skills add https://github.com/filipexyz/ravi --skill ravi-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation of agent instructions by centralizing, validating, and injecting workspace-specific runtime rules into AI system prompts.

Core Features & Use Cases

  • Unified Rule Management: Consolidates rules from various provider-specific folders into a single source of truth within the .ravi/rules directory.
  • Deterministic Injection: Ensures that workspace instructions are consistently applied across all sessions, preventing rule duplication or omission.
  • Use Case: When migrating from individual Claude or agent-specific rule files to a unified Ravi-managed environment, use this skill to import and verify that all operational behaviors are correctly structured for the runtime.

Quick Start

Use the ravi-rules skill to import all existing provider-specific rules into the centralized Ravi runtime configuration.

Frequently Asked Questions about ravi-rules

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

FAQPage Schema
How do I centralize workspace-specific runtime rules for AI agent system prompts?

You can centralize workspace-specific runtime rules by consolidating them into a unified .ravi/rules directory, which serves as a single source of truth for AI agent system prompts. This prevents rule fragmentation across provider-specific folders.

How do I migrate provider-specific agent rules into a unified configuration?

To migrate provider-specific agent rules, import existing rule files from disparate provider folders into the centralized Ravi runtime configuration. This verifies that all operational behaviors are correctly structured for the runtime.

Why does my AI agent ignore workspace instructions during different sessions?

Workspace instructions are ignored when rules are fragmented across provider-specific folders. Centralizing them into a .ravi/rules directory ensures deterministic rule injection and validation across all agent sessions and task executions.

What is deterministic rule injection for AI agents?

Deterministic rule injection is the process of consistently applying workspace instructions across all AI agent sessions. It ensures rules are injected into system prompts without duplication or omission during task executions.

Can I validate agent rules across multiple task executions?

Yes, you can validate agent rules across multiple task executions by migrating them into a unified .ravi/rules directory structure. This ensures deterministic rule injection and validation across all agent sessions.

Do I need specific dependencies to manage runtime agent rules?

No specific dependencies are required to manage runtime agent rules. The skill operates independently to centralize, validate, and inject workspace-specific rules into AI system prompts without external components.