rules-create-global
Installation
SKILL.md
Create Rules: Set Up Your Project's Global Rules
Inputs: wire the arguments first
This skill takes up to two optional paths and uses them to pick your lane. Read whatever was passed and classify each by its content:
$path1: the first path, if any.$path2: the second path, if any.
| A passed path that is... | Lane | Use it as |
|---|---|---|
a PRD (intent, what/why, from plan-create-prd) |
greenfield | product context (the "what this is"), NOT the source of technical rules |
an architecture / spec doc (the how, from plan-architecture) |
greenfield | the technical decisions your rules derive from (may be the same file as the PRD, if the architecture was folded in as an ## Architecture section) |
a codebase-analysis doc (a large-repo /prime-codebase + subagent fan-out) |
brownfield | the source of "what is" |
Pick the lane from what you were given:
- Greenfield if a PRD and/or architecture path was passed, or the workspace is a bare scaffold: derive what should be from the architecture decisions (
$path2, or$path1if that is where they live). - Brownfield if no path was passed, or a codebase-analysis path was: derive what is from the analysis doc if one was passed, otherwise from the primed codebase in this conversation.
Brownfield, not primed yet? If no path was passed and this conversation has not been primed on the code, run
/prime-codebasefirst (or offer to) so you derive from real files, then continue. Never invent rules from nothing.