mostalive/pi-allium-port
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

phase 4: fold in allium rules content

Browse Source 
- 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:
Willem
2026-04-23 14:09:44 +01:00
committed by mostalive
parent 4bd4f16633
commit 761f0fb68d
5 changed files with 40 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.pi/skills/distill/SKILL.md
+5
View File
@@ -870,7 +870,12 @@ If any remain, ask: "Would a stakeholder include this in a requirements doc?"
The extracted spec is a starting point. For targeted changes as requirements evolve, use /skill:tend. For checking ongoing alignment between the spec and implementation, use /skill:weed.
## Syntax rules
Before writing any `.allium` file, read `../../allium/references/allium-rules.md` for syntax gotchas, naming conventions and anti-patterns. This covers common model mistakes (e.g. `with` vs `where`, `transitions_to` vs `becomes`, capitalised vs lowercase pipe values) that the language reference does not emphasise.
## References
- [Language reference](references/language-reference.md), full Allium syntax
- [Worked examples](references/worked-examples.md), complete code-to-spec examples in Python, TypeScript and Java
- [Allium rules](../../allium/references/allium-rules.md), syntax gotchas and anti-patterns