feat: Update CLAUDE.md files, add coolify skill
Some checks failed
CI/CD Pipeline / backend (push) Failing after 2m19s
CI/CD Pipeline / frontend (push) Successful in 5m29s
CI/CD Pipeline / deploy (push) Has been skipped

This commit is contained in:
2026-03-16 08:35:53 +01:00
parent 37a907e087
commit ea41b1edec
6 changed files with 77 additions and 5 deletions

View File

@@ -158,6 +158,13 @@ When adding a new section file:
2. Add the `!include` directive to the corresponding `_main.yaml`
3. Maintain logical section ordering
### Rule 9: Change process must start with template, then sync demo
Any change request that affects form structure, visibility conditions, or section spawn triggers must follow this process:
1. **Modify the template**: Make all necessary changes to the template files first, ensuring structural integrity and logical consistency
2. **Sync the demo form**: After the template is updated, modify the demo form to mirror the structural changes and add contextually appropriate test data
3. **Verify both**: Ensure that the template remains the source of truth and that the demo form accurately reflects the template's structure and visibility logic
## Checklist for Template Changes
When you modify files in the **template/ directory**, verify each item:
@@ -179,4 +186,4 @@ When you modify files in the **demo/ directory**, verify:
- [ ] **Value consistency**: New values are consistent with the SAP S/4HANA "Einfuehrung" context
- [ ] **Table data alignment**: Table JSON arrays all have the same length within a single table element
- [ ] **Cross-reference integrity**: Table values that reference other tables use valid IDs from those tables
- [ ] **_main.yaml update**: If you added/removed a section file, update `demo/_main.yaml`
- [ ] **_main.yaml update**: If you added/removed a section file, update `demo/_main.yaml`