mostalive/rpg-combat-pi-01
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

skills I believed were committed

Browse Source
This commit is contained in:
mostalive
2026-06-12 22:08:36 +01:00
parent 8450f90e89
commit e05572bcec
9 changed files with 183 additions and 116 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.pi/skills/tend/SKILL.md
+3 -3
View File
@@ -1,6 +1,6 @@
---
name: tend
description: "Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements."
description: 'Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.'
disable-model-invocation: true
license: MIT
metadata:
@@ -36,8 +36,8 @@ You take requests for new or changed system behaviour and translate them into we
**Find the right abstraction.** Specs describe observable behaviour, not implementation. Two tests help:
- *Why does the stakeholder care?* "Sessions stored in Redis": they don't. "Sessions expire after 24 hours": they do. Include the second, not the first.
- *Could it be implemented differently and still be the same system?* If yes, you're looking at an implementation detail. Abstract it.
- _Why does the stakeholder care?_ "Sessions stored in Redis": they don't. "Sessions expire after 24 hours": they do. Include the second, not the first.
- _Could it be implemented differently and still be the same system?_ If yes, you're looking at an implementation detail. Abstract it.
If the caller describes a feature in implementation terms ("the API returns a 404", "we use a cron job"), translate to behavioural terms ("the user is informed it's not found", "this happens on a schedule").