create-architecture
/create-architecture
Tworzy projekty architektury rozwiązania i decyzje, by agenci AI działali spójnie.
- Autor
- danielchukuma-dev ↗
- Repozytorium
- cougr ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 21.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 14
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 21.10.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
Tworzy projekty architektury rozwiązania i decyzje, by agenci AI działali spójnie.
Wyzwalacze z opisu
Oryginalny opis (EN)
Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design
Jak działa
- Conventions
- WORKFLOW ARCHITECTURE
- On Activation
- Execution
Podgląd SKILL.md
---
name: create-architecture
description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
---
# Architecture Workflow
**Goal:** Create comprehensive architecture decisions through collaborative step-by-step discovery that ensures AI agents implement consistently.
**Your Role:** You are an architectural facilitator collaborating with a peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and architectural knowledge, while the user brings domain expertise and product vision. Work together as equals to make decisions that prevent implementation conflicts.
## Conventions
- Bare paths (e.g. `steps/step-01-init.md`) resolve from the skill root.
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
- `{project-root}`-prefixed paths resolve from the project working directory.
- `{skill-name}` resolves to the skill directory's basename.
## WORKFLOW ARCHITECTURE
This uses **micro-file architecture** for disciplined execution:
- Each step is a self-contained file with embedded rules
- Sequential progression with user control at each step
- Document state tracked in frontmatter
- Append-only document building through conversation
- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.
## On Activation
### Step 1: Resolve the Workflow Block
Run: `python3 {project-root}/.stellar-build/scripts/resolve_customization.py --skill {skill-root} --key workflow`
**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
1. `{skill-root}/customize.toml` - defaults
2. `{project-root}/.stellar-build/custom/{skill-name}.toml` - team overrides
3. `{project-root}/.stellar-build/custom/{skill-name}.user.toml` - personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
### Step 2: Execute Prepend Steps
Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
### Step 3: Load Persistent Facts
Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` - load the referenced contents as facts. All other entries are facts verbatim.
### Step 4: Load Config
Load config from `{project-root}/.stellar-build/bmm/config.yaml` and resolve:
- Use `{user_name}` for greeting
- Use `{communication_language}` for all communications
- Use `{document_output_language}` for output documents
- Use `{planning_artifacts}` for output location and artifact scanning
- Use `{project_knowledge}` for additional context scanning
### Step 5: Greet the User
Greet `{user_name}`, speaking in `{communication_language}`.
### Step 6: Execute Append Steps
Execute each entry in `{workflow.activation_steps_append}` in order.
Activation is complete. Begin the workflow below.
## Execution
Read fully and follow: `./steps/step-01-init.md` to begin the workflow.
**Note:** Input document discovery and all initialization protocols are handled in step-01-init.md.
Pliki w paczce (14)
- SKILL.md 3 KB
- architecture-decision-template.md 1 KB
- customize.toml 2 KB
- data/domain-complexity.csv 2 KB
- data/project-types.csv 1 KB
- steps/step-01-init.md 6 KB
- steps/step-01b-continue.md 6 KB
- steps/step-02-context.md 8 KB
- steps/step-03-starter.md 12 KB
- steps/step-04-decisions.md 10 KB
- steps/step-05-patterns.md 11 KB
- steps/step-06-structure.md 11 KB
- steps/step-07-validation.md 12 KB
- steps/step-08-complete.md 3 KB
Wersje
W bazie nie ma innych skilli o nazwie create-architecture.
Migawka bazy z 13.11.2026 · wersja paczki 53a43bf35a34 (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
- 100specify-solution
Tworzy i waliduje dokumenty projektu rozwiązania (SDD): architektura, interfejsy, decyzje techniczne, analiza komponentów i pliki solution.md w .start/specs/. - 100bmad-architecture
Ustala i zapisuje decyzje architektoniczne zapewniające spójność osobno budowanych części systemu w krótkim dokumencie architektury, który tworzy, aktualizuje lub waliduje na podstawie pliku zgłoszenia. - 90bmad-architecture
Ustala i zapisuje decyzje architektoniczne, które utrzymują spójność osobno budowanych części systemu w krótkim dokumencie. - 100solution-architecture
Projektuje architekturę rozwiązania na podstawie PRD i ograniczeń: wskazuje komponenty, wzorce integracji, opcje technologiczne i kompromisy między atrybutami jakości. - 100architecture
Wspiera projektowanie systemu, tworzenie ADR i przegląd architektury przy decyzjach architektonicznych. - 95wicked-garden-engineering-architecture
Projektuje architekturę rozwiązania: wzorce, decyzje technologiczne, kompromisy i diagramy systemu.