Namespaces: Organizing Your AI Context

As your skills and preferences grow, organization becomes critical. You don’t want your Python preferences bleeding into your Go projects. You don’t want work context mixing with personal projects.

Namespaces solve this.

Segmentation

Namespaces let you segment your skills and preferences into logical groups:

• work/backend - Skills for your job’s backend services
• work/frontend - Different conventions for the frontend
• personal/projects - Your side projects with different tooling
• learning/rust - Experimental preferences while learning

Categorization

Beyond segmentation, namespaces provide categorization. You can:

• Group related skills together
• Apply preferences to entire categories at once
• Inherit from parent namespaces

Practical Example

Imagine you work at a company that uses a specific code style, but your personal projects follow different conventions. With namespaces:

/work        -> 2-space indentation, semicolons
/personal    -> tabs, no semicolons

When you switch contexts, your AI assistant switches too.

Why This Matters

Without organization, personalization becomes chaos. The more you customize your AI assistant, the more important it becomes to keep those customizations structured.

Namespaces give you that structure without adding friction to your workflow. Context switches cleanly. Preferences stay where they belong.