fa-engineering-architecture
/fa-engineering-architecture
Pilnuje dokumentacji architektury Gaia w docs/architecture/ (komponenty, przypadki użycia, diagramy klas, UI), aby była zgodna z kodem przed planowaniem i implementacją zmian struktury.
- Autor
- frostaura ↗
- Repozytorium
- ai.toolkit.gaia ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 16.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 16.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pilnuje dokumentacji architektury Gaia w docs/architecture/ (komponenty, przypadki użycia, diagramy klas, UI), aby była zgodna z kodem przed planowaniem i implementacją zmian struktury.
Oryginalny opis (EN)
Provides Gaia architecture documentation guidance that keeps docs, README messaging, and design decisions aligned to the current operating model. Use it by updating the relevant files under the consuming repository's docs/architecture/ tree (system components, use cases, class diagrams, UI) before any planning or implementation that changes structure, then resolving doc↔code drift before resuming feature work. Use it when system structure, trust boundaries, interfaces, workflows, ownership, or architectural assumptions change, or when architecture drift blocks planning or delivery, or when one
Jak działa
- Scope and when to use
- Required inputs
- Owned outputs
- Decision tree
- Core workflow
- Artifact selection order
- Failure recovery
- Anti-patterns
- Handoff and downstream impact
- Examples
Podgląd SKILL.md
--- name: fa-engineering-architecture description: Provides Gaia architecture documentation guidance that keeps docs, README messaging, and design decisions aligned to the current operating model. Use it by updating the relevant files under the consuming repository's docs/architecture/ tree (system components, use cases, class diagrams, UI) before any planning or implementation that changes structure, then resolving doc↔code drift before resuming feature work. Use it when system structure, trust boundaries, interfaces, workflows, ownership, or architectural assumptions change, or when architecture drift blocks planning or delivery, or when one repository has no architecture baseline at all and the implemented system must be documented from source. It owns one repository's architecture docs; putting a context layer and the design documentation its projects never had across a whole tree belongs to `fa-foundation-optimize-directory-tree`. license: MIT --- # Gaia Architecture ## Scope and when to use Use this skill to keep the consuming repository's `docs/architecture/` tree — the architecture docs of the project Gaia is operating on — current and concrete enough that the rest of Gaia can plan and deliver against a stable target solution. Use this skill when: - the operating model, system structure, or trust boundaries change - the repository's `docs/architecture/` is missing or stale - README messaging must be aligned to architecture changes - planning or testing expose a design ambiguity that blocks progress Do not use this skill when: - the issue is only execution order or branch sequencing - the problem is purely local implementation work - the only remaining question is final release readiness ## Required inputs - the current request and approved constraints - the repository's existing `docs/architecture/` content or evidence that it is absent - relevant contract, README, agent, and skill definitions - architecture templates and shared ownership rules ## Owned outputs - current architecture docs under the consuming repository's `docs/architecture/` - explicit assumptions, invariants, and out-of-scope statements - README alignment when the high-level system story changed - clear downstream impact notes for planners and maintainers ## Decision tree - If no baseline exists, document the current implemented system first — from ranked evidence (build files, entrypoints, routes, schema over README and roadmap), and from `fa-foundation-optimize-directory-tree`'s analysis where that skill produced one. - If only the story changed but not the design, update README and architecture summaries without inventing a new delta. - If planning cannot proceed because architecture is vague, make the missing decision explicit before handoff. - If implementation or validation defects do not imply a design change, route them back to the true owner instead of redesigning the system. ## Core workflow 1. Assess the repo, docs, README, and operating definitions for drift. 2. Decide whether the change is a real architecture delta or a justified no-op. 3. Update the relevant architecture artifacts using the provided templates. 4. Keep the architecture docs specific enough for planning and QA to act on. 5. Align README language when the user-facing Gaia story changed materially. 6. Hand off any agent or skill maintenance implied by the new design. ## Artifact selection order - start with system components when the runtime or ownership model changes - add or update use cases when workflow behavior or actor responsibilities change - update class or data views only when structural detail improves the design basis - align README after the architecture set is internally consistent ## Failure recovery | Failure mode | Recovery | Owner | Escalation | | ------------------------------------------ | ---------------------------------------------- | --------- | ---------------------------------- | | missing baseline | create the baseline from current repo behavior | architect | block planning until complete | | unclear request | obtain clearer scope or constraints | intake | stay upstream | | downstream role requests design workaround | restate the design or reject the workaround | architect | escalate unresolved contradictions | | README drift after design change | update README after architecture stabilizes | architect | block release messaging claims | ## Anti-patterns - do not treat architecture as optional background material - do not solve code defects by silently changing the design - do not leave README claims inconsistent with the target solution - do not push planning forward on implied architecture ## Handoff and downstream impact - tell planning which artifacts are now authoritative - tell engineering which invariants or boundaries must not be violated - tell testing which behaviors, actors, or flows changed materially - tell maintainers which agent or skill definitions must align with the new design ## Examples - **Good fit:** create the initial `docs/architecture/` baseline in a repository before rewriting its operating definitions. - **Good fit:** update system boundaries after the contract adds explicit delegation and failure routing. - **Not a fit:** publish a branch plan or implement the definition changes directly. ## Completion checklist - affected architecture artifacts are current or explicitly no-op - assumptions, invariants, and out-of-scope items are named - README drift is resolved when the system story changed - downstream roles know what changed and what artifact to read first ## References - [Gaia ownership and conventions](../../references/ownership-and-conventions.md) - [System Components Template](references/system-components-template.md) - [Use Cases Template](references/use-cases-template.md) - [Class Diagrams Template](references/class-diagrams-template.md) - [User Interface Template](references/user-interface-template.md)
Pliki w paczce (5)
- SKILL.md 6 KB
- references/class-diagrams-template.md 6 KB
- references/system-components-template.md 7 KB
- references/use-cases-template.md 5 KB
- references/user-interface-template.md 11 KB
Wersje
W bazie nie ma innych skilli o nazwie fa-engineering-architecture.
Migawka bazy z 13.11.2026 · wersja paczki 425f4a4866a3 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100architecture-diagram
Tworzy lub aktualizuje diagramy architektury i przepływów na stronę dokumentacji agent-desktop w katalogu apps/docs. - 100write-architecture-docs
Pisze i przegląda dokumenty architektury podsystemów oraz ADR-y dla zespołu inżynierskiego w katalogu docs. - 100isodraw
Odczytuje i zmienia diagramy architektury IsoDraw oraz ich dokumentację przez CLI, także przy pytaniach o komponenty systemu. - 100documentation-structure
Opisuje architekturę dokumentacji repozytorium: README.md, CONTRIBUTING.md i katalog docs/, z podziałem odpowiedzialności, standardami dokumentacji dostawców, odsyłaczami i walidacją. - 100generating-project-docs
Tworzy i odświeża dokumentację projektu: README.md, ARCHITECTURE.md, STRUCTURE.md oraz aktualizacje wybranych sekcji. - 90arc42 Architecture Templates
Dostarcza szablony arc42 do opisu architektury: sekcje, widoki building blocks i diagramy kontekstu.