phase 4: fold in allium rules content
- Symlink allium-main/.claude/rules/allium.md into references as allium-rules.md - Add 'Syntax rules' section to elicit, distill, and propagate skills - Instructs model to read rules before writing .allium files
This commit is contained in:
@@ -199,6 +199,10 @@ When generator specs are available, use them to produce valid test data:
|
||||
- For invariants, generate states that exercise boundary conditions
|
||||
- For config parameters, use declared defaults unless testing overrides
|
||||
|
||||
## Syntax rules
|
||||
|
||||
When reading `.allium` specs, be aware of the syntax distinctions documented in `../../allium/references/allium-rules.md`. This covers `with` vs `where`, `transitions_to` vs `becomes`, capitalised vs lowercase pipe values, and other gotchas that affect correct interpretation of the spec.
|
||||
|
||||
## Interaction with other tools
|
||||
|
||||
- /skill:distill produces specs from code. Those specs feed propagate.
|
||||
|
||||
Reference in New Issue
Block a user