Reorganize repo structure and standards references
This commit is contained in:
1 parent
3cb93a81be
commit
be2054274d
5885 files changed
+2588
-195
No files matched your search
@@ -18,8 +18,11 @@ Dieser Vault ist der Arbeitsbereich fuer Screens, Wireframes und Handoffs.
|
||||
| `01 Regeln` | dauerhafte Regeln und Arbeitsweisen |
|
||||
| `02 Wireframes` | alle Wireframe-Pakete, Screen-Dateien und Canvas-Dateien |
|
||||
| `02 Wireframes/_Templates` | Vorlagen fuer neue Pakete und Screens |
|
||||
| `03 Quellen und Repo` | Hinweise zum Gitea-Repo und lokalen Planning-Dateien |
|
||||
| `hivegrid-cloud` | technisches Repo mit Planning-Quellen |
|
||||
| `03 Quellen und Referenzen` | Quellen, Referenz-Repos und Repo-Hinweise |
|
||||
| `03 Quellen und Referenzen/hivegrid-cloud` | mitgepushte HiveGrid-Cloud-Referenz mit Planning-Quellen |
|
||||
| `04 Standards/Subframe UI Standards` | eigenes Standards-Projekt fuer dauerhafte Subframe-, Komponenten- und Layout-Standards |
|
||||
| `Tickets` | Ticket-Handoff-Index |
|
||||
| `Tickets/Fertige Tickets` | fertige oder handofffaehige Ticket-Zusammenfassungen |
|
||||
|
||||
---
|
||||
|
||||
@@ -152,6 +155,13 @@ Sync-Regel:
|
||||
|
||||
Subframe wird nicht automatisch aus dem Tracker heraus bearbeitet.
|
||||
|
||||
Die Subframe UI Standards unter `04 Standards/Subframe UI Standards/` sind ebenfalls geschuetzt:
|
||||
|
||||
- Sie sind ein eigenes Standards-Projekt innerhalb dieses Repos.
|
||||
- Sie werden als Referenz fuer Layout-, Komponenten- und Subframe-Konventionen genutzt.
|
||||
- Sie duerfen nicht durch normale Screen-/Flow-Arbeit automatisch umgeschrieben werden.
|
||||
- Aenderungen brauchen eine explizite Aufgabe oder eine vorher validierte systemweite Entscheidung.
|
||||
|
||||
Regel:
|
||||
|
||||
- Bestehende Subframe-Screens bleiben unberuehrt, auch wenn sie gleich heissen.
|
||||
|
||||
@@ -22,6 +22,7 @@ This file is the operative checklist. `Screen Agent Workflow - Brainstorming.md`
|
||||
- MUST check for similar existing flows, screens, reusable patterns and naming conflicts before creating a new flow or screen.
|
||||
- MUST use internal Planning as the default source of truth.
|
||||
- MUST use external research only as decision support, and validate relevant research-derived ideas with David before they enter planning.
|
||||
- MUST use `04 Standards/Subframe UI Standards/` as reference for already validated Subframe, component and layout standards when relevant.
|
||||
- MUST give an assumption and recommendation before asking David a decision question.
|
||||
- MUST have David validate every product, UX, screen, state, backlog, scope and research-derived decision.
|
||||
- MUST keep one small flow or screen package in focus at a time.
|
||||
@@ -40,6 +41,7 @@ This file is the operative checklist. `Screen Agent Workflow - Brainstorming.md`
|
||||
- NEVER finalize unvalidated decisions.
|
||||
- NEVER silently create, delete, rename or split screens.
|
||||
- NEVER build or edit Subframe without explicit OK for the concrete screen or flow.
|
||||
- NEVER edit `04 Standards/Subframe UI Standards/` during normal screen work unless David explicitly asks for standards work or validates a systemwide rule that belongs there.
|
||||
- NEVER overwrite or revert David's manual changes in Obsidian or Subframe.
|
||||
- NEVER let external examples override internal Planning without making the conflict visible and asking David.
|
||||
- NEVER create Canvas nodes for normal Toasts, Banners, Inline States, field validation or pure documentation states.
|
||||
@@ -155,9 +157,9 @@ Then check:
|
||||
|
||||
When a ticket is finished, ready for external ticket-system handoff, or David asks for a ticket summary:
|
||||
|
||||
- Create or update one Markdown file in `Tickets/`.
|
||||
- Use the same structure as `Tickets/D-P2 Auth Wireframes.md`.
|
||||
- Name it clearly after the ticket and area, for example `Tickets/D-P2 Auth Wireframes.md`.
|
||||
- Create or update one Markdown file in `Tickets/Fertige Tickets/`.
|
||||
- Use the same structure as `Tickets/Fertige Tickets/D-P2 Auth Wireframes.md`.
|
||||
- Name it clearly after the ticket and area, for example `Tickets/Fertige Tickets/D-P2 Auth Wireframes.md`.
|
||||
- Include ticket id, area, status, repo link, central tracker link and working area.
|
||||
- Summarize what was done, what David validated and what remains Backlog/Open.
|
||||
- Link every relevant flow package MD, Canvas and Subframe flow.
|
||||
|
||||
Reference in new issue
Block a user