Scoping skills with `paths`
Open 💬 0 comments Opened May 28, 2026 by sieu-n
What variant of Codex are you using?
App
What feature would you like to see?
https://code.claude.com/docs/en/memory#organize-rules-with-claude/rules/
I want some skills to be more explicitly loaded in some context, and I find claude code's paths in rules system quite handy.
I do recognize the skills standard is a mess, and maybe it parts slightly, but I hope to see some kind of variant, as it seems super clean and reasonable in many use cases where I 1) want some skill to be more deteriminstically loaded (e.g. I want my Python standards to be loaded when editing Python files), 2) want it to be scoped (2 sub-projects might have different coding standards, workflows, mental models).
example 1 - scoping to some subfolder in a monorepo/big project
---
paths:
- 'apps/crawler-v2/**'
---
# crawler-v2 — Scraping System
...
example 2 - scoping to specific types of files
---
paths:
- '**/*.svelte'
- '**/*.svelte.ts'
---
# Svelte 5 + SvelteKit Conventions
...
Additional information
_No response_