Guide
The Anatomy of a Rule
AI Rules Hub extracts actionable intelligence from your documentation. Learn how to structure your rules for maximum impact.
Smart Extraction Engine
Our analyzer doesn't just read text; it understands engineering constraints. By following standard Markdown patterns, you ensure your rules are correctly detected by AI assistants like Cursor, Windsurf, and Copilot.
Core Concepts
Three pillars of effective rule definition.
Headings for Context
Use H2 (##) or H3 (###) to group rules by domain.
## Components
Bullet Lists
Clear, indented lists are the most reliable markers.
- Use hooks...
Actionable Verbs
Priority keywords like Always, Never, Avoid.
Always validate...
Preferred Structure
The most reliable way to format your .md files.
standards.md
# Rules Hub Standard
## API Interaction
- Always use React Query for data fetching.
- Prefer Zod for runtime schema validation.
- Never use native fetch directly.
## UI Components
- Prefer Tailwind for all styling.
- Avoid inline CSS styles.
Quality Standards
Good Rule
"Always use functional components and hooks. Avoid classes."
ActionableSpecificDirect
Avoid Vague Rules
"Make the code look clean and ensure it's easy to read."
SubjectiveHard to Enforce
CLI-First Workflow
Don't manually copy rules. Use our CLI to instantly sync your team's standards directly into your project root.
$ npx @airuleshub/cli@latest add react-rules
Auto-detects
Cursor, Windsurf, Copilot configs
Safe Updates
Prompts before overwriting files
Ready to standardize?
Start writing rules that your AI actually understands.