The /para-rule command is used to manage the entire AI Agent Rules system within PARA Workspace. These rules explicitly define what an Agent MUST, SHOULD, and MUST NOT do to protect the project’s structural integrity.
Command List
/para-rule [action] [name]| Action | Description |
|---|---|
list | Compare active rules against the Governed Catalog. |
add | Create a new rule draft following PARA standards. |
standardize | Upgrade legacy rules to v1.5.x standards. |
install | Fetch and install rules from the admin library. |
validate | Test for compliance without modifying files. |
Detailed Capabilities
1. Rule Standardization
A PARA-compliant rule must pass five critical checks:
- No absolute paths (use relative paths only).
- Strictly follows PARA boundaries.
- Uses imperative language (Must/Should/Must Not).
- Provides clear, non-ambiguous instructions for the AI.
- Does not conflict with general Workspace discipline.
2. Context Routing & Triggering
PARA Workspace utilizes a Lazy Loading model for rules:
- Rules are NOT loaded all at once.
- Specialized rules are triggered only when the Agent’s context matches specific Trigger Conditions.
- This approach saves tokens and prevents context pollution.
3. Rule Graduation
During development, if a specific lesson or “Bead” repeats more than 3 times, the system suggests “graduating” it into an official Rule via /para-rule add.
Relationships
/para-workflow— Global workflow management./install— Standardized resource installation.