Adding skills & isac talent updates
This commit is contained in:
@@ -119,6 +119,18 @@ project owner declares a production-stable format. During the prototype phase:
|
||||
5. Add compatibility support only when the project owner requires it for a
|
||||
production-stable format.
|
||||
|
||||
## Talent mechanic conventions
|
||||
|
||||
Before importing a Talent or changing its mechanic program, read
|
||||
`docs/TALENT_MECHANIC_RULES.md`. Treat the confirmed lifecycle, trigger,
|
||||
cooldown, and targeting rules in that document as authoritative game behavior.
|
||||
Do not mark a mechanic `requires_assumptions` for behavior that the document
|
||||
resolves. Do not extend a rule to Talents outside its stated scope.
|
||||
|
||||
When the project owner clarifies another Talent mechanic, record the answer in
|
||||
`docs/TALENT_MECHANIC_RULES.md`. Keep unresolved questions separate from
|
||||
confirmed behavior.
|
||||
|
||||
## ISAC editor lifecycle
|
||||
|
||||
All ISAC data-management editors must follow the same successful-save behavior:
|
||||
|
||||
Reference in New Issue
Block a user