arch
/arch
Przegląda plan architektury w pliku .reins i proponuje zmiany z dowodami, bez stosowania ich przed zatwierdzeniem.
- Autor
- fredarcito ↗
- Repozytorium
- reins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 12.11.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
Przegląda plan architektury w pliku .reins i proponuje zmiany z dowodami, bez stosowania ich przed zatwierdzeniem.
Oryginalny opis (EN)
Review the architecture plan in .reins/architecture.yml against the code and propose changes with evidence, applying nothing until the person approves. Use it after reins init, when asked to review or adjust the architecture, or every few months to check that the plan still fits.
Jak działa
SKILL.md bez nagłówków drugiego poziomu · 25 linii, 526 słów
Podgląd SKILL.md
--- name: arch description: Review the architecture plan in .reins/architecture.yml against the code and propose changes with evidence, applying nothing until the person approves. Use it after reins init, when asked to review or adjust the architecture, or every few months to check that the plan still fits. --- # Review the architecture plan `reins check` enforces whatever `.reins/architecture.yml` says, even a bad plan, and a person decides it. Your job is to show where the plan doesn't fit the code and propose changes with evidence. **Don't edit `.reins/architecture.yml` or `.reins/baseline.json` until the person approves each change.** 1. Gather the facts (don't read the whole repo): - `npx reins check --coverage`: files per layer and domain, folders outside every layer, imports between layers, exceptions, baseline (`--json` if easier). - `.reins/init-report.md` if it exists: mixed directions, doubtful dependencies, orphans. - `npx reins check --verbose`: the violations frozen in the baseline. 2. Look for these, and confirm each one by opening the files involved: - **Layer order:** a pair with many imports going "up". Is the order wrong, or the code? - **Folders outside every layer:** `layer-direction` doesn't check them. Which layer do they belong to? - **Layers that match no file**, and globs that overlap (the first match wins). - **Domains:** features without a domain, a public API that doesn't exist or exposes internals, domains reaching into each other's internals. - **Route folders left out** (listed in `init-report.md`): `init` drops one-file routes that own no folder, but several of them can be one flow (`signIn`, `resetPassword`, `acceptInvite`… → `auth`). Group the ones that share what they import (the same API module, forms or components) into one domain with several paths; leave app shell (guards, layouts, maintenance pages) outside every domain. - **Generated code, fixtures, stories:** candidates for `ignore:`. - **`allow:` entries** whose reason no longer holds, and a baseline that isn't shrinking. 3. What the file accepts: `version`, `adapter`, `preset`, `ignore` (globs left out of the analysis), `layers`, `domains`, `rules`, `allow` (with a `reason`). Unknown keys are errors. Full reference: https://github.com/fredarcito/reins/blob/main/docs/architecture-yml.md 4. Rules for proposals: - An existing violation stays in the **baseline** by default: it is debt to fix later. Propose `allow:` only when the person says it is a decision, with their reason, never one you make up. - Never reorder layers, widen globs or add exceptions just to make `reins check` pass. - When you can't tell whether something is a mistake or a decision, ask. 5. Present the proposal as a numbered list. For each item: the change (as a YAML snippet), the evidence (files and imports), why, and its effect on the check (violations that appear or disappear). Then stop and wait for the person. 6. After approval: apply only the approved items. Run `npx reins check --update-baseline` only if the person agreed to freeze the violations the change reveals; then `npx reins check`. For every domain you added that has no note in `.reins/notes/`, draft one with `npx reins notes new <domain>` (one per call), then fill in its TODO lines following the `notes` skill, or tell the person they are drafts; `reins doctor` flags any domain left without a note. Tell them the pull request will show an `integrity` warning for the changed `architecture.yml`: that is expected, and the PR description should explain the change. 7. Reasons that last go where people will see them: `allow:` reasons in the file, and decisions about a module in its note (`.reins/notes/`).
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · fredarcito/reins | 86 | MIT |
| justinedevs/meta-architect | 100 | MIT |
| srujan375/bird | 95 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 6a5c5981557b (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
- 86reins-arch
Przegląda plan architektury w pliku reins.yml względem kodu i proponuje zmiany z dowodami, bez ich stosowania przed zgodą. - 90reins-notes
Uzupełnia, poprawia i sprawdza notatki modułów w .reins/notes: cel, mapę, działanie, decyzje i pułapki. - 100reins
Steruje prawdziwą, zalogowaną przeglądarką z shella przez CLI reins: pobiera dane zza logowań, czyta ciasteczka, podsłuchuje ruch API, klika, wpisuje tekst i robi zrzuty ekranu. - 85arch-check
Sprawdza kod funkcji pod kątem reguł architektury z karty projektu: warstwy zależności, cykle, zakazane wzorce i rozmiar plików. - 100arch-review
Przegląda istniejącą architekturę metodą ATAM-lite względem scenariuszy atrybutów jakości, wyszukując ryzyka, kompromisy i antywzorce, i przygotowuje raport. - 100rtl-p2-arch-team
Prowadzi fazę architektury projektu RTL równoległym zespołem: dwa strumienie, architekturę i rozwój modelu referencyjnego.