feature-arch-gate
/feature-arch-gate
Surowo ocenia zgodność kodu React z regułami architektury funkcji, zwraca werdykt zaliczone lub niezaliczone dla każdej zasady z dowodami.
- Autor
- pproenca ↗
- Repozytorium
- dot-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 15.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 40
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 15.08.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
Surowo ocenia zgodność kodu React z regułami architektury funkcji, zwraca werdykt zaliczone lub niezaliczone dla każdej zasady z dowodami.
Oryginalny opis (EN)
Adversarial pass/fail review gate that enforces the feature-arch skill's React feature-based architecture rules. Use when a diff, branch, PR, or src/ tree must be judged for architecture conformance before merge — feature folder structure, import boundaries, cross-feature isolation, data-fetching, state, testing, and naming rules. A single blind reviewer renders per-rule PASS/FAIL verdicts with cited evidence, and the reviewer's structured output is the verdict fail-closed. Use the feature-arch skill itself to design or migrate an architecture; use this gate to judge whether work conforms to i
Jak działa
- When to Apply
- Review Protocol
- Verdict Format
- Rule Categories
- Reference Files
- Related Skills
Podgląd SKILL.md
---
name: feature-arch-gate
description: Adversarial pass/fail review gate that enforces the feature-arch skill's React feature-based architecture rules. Use when a diff, branch, PR, or src/ tree must be judged for architecture conformance before merge — feature folder structure, import boundaries, cross-feature isolation, data-fetching, state, testing, and naming rules. A single blind reviewer renders per-rule PASS/FAIL verdicts with cited evidence, and the reviewer's structured output is the verdict fail-closed. Use the feature-arch skill itself to design or migrate an architecture; use this gate to judge whether work conforms to it.
---
# Feature-Arch Gate
Enforce React feature-based architecture conformance — a pass/fail gate: a single blind reviewer subagent judges the work against the rules of feature-arch v1.1.0 with an adversarial mandate, and the work passes only when every rule is PASS or N/A. This skill renders verdicts; it never fixes the work.
The gate is **self-sufficient**: the 33 decidable rules it enforces (of the source's 43) are vendored into this skill's `references/` directory as a snapshot of feature-arch v1.1.0, so a review needs nothing outside this folder. [references/_rule-evidence.md](references/_rule-evidence.md) records the provenance, the evidence that decides each rule, and the 10 source rules excluded as non-decidable.
## When to Apply
- A PR or branch touching a feature-organized React codebase needs an architecture conformance verdict before merge.
- A migration step from a `FEATURE-ARCH-TARGET.md` blueprint is claimed complete and needs independent verification.
- A full `src/` tree audit is requested ("does this codebase conform to feature-arch?").
- Agent-generated feature work needs a gate that is blind to the conversation that produced it.
Do NOT apply this gate to design or migrate an architecture — that is the `feature-arch` skill's job (it produces the blueprint; this skill judges conformance to the rules).
## Review Protocol
Follow these steps exactly — the gate's value is that every review runs the same way.
1. **Identify the target.** Pin down exactly what is under review (a diff, a set of files, or a full `src/` tree) and note the ref/paths so the review runs against an unambiguous, fixed target. Record two context facts the reviewer needs: does the codebase use React Server Components, and is a query library (TanStack Query etc.) present — two rules are N/A without them.
2. **Load the rules.** Read [references/_rule-evidence.md](references/_rule-evidence.md) and resolve the 33 vendored rule files it lists against this skill's own `references/` directory. If any listed rule file is missing or unreadable, **STOP and report the error** — never proceed with partial rules or silently pass.
3. **Compose the reviewer prompt.** Fill [references/reviewer-prompt.md](references/reviewer-prompt.md) with the rule file paths, the target, and (if the target repo has one) its `docs/architecture/FEATURE-ARCH-TARGET.md` blueprint. The composed prompt must be fully self-contained — a reviewer sees no conversation history, so nothing may refer to context outside the prompt.
4. **Dispatch one blind reviewer.** Launch a single Task subagent whose entire input is the composed prompt — no conversation context, no commentary alongside it.
5. **Render fail-closed.** The reviewer's structured output is the verdict — there is no merge step. Overall verdict is PASS only when every rule is PASS or N/A; any single FAIL fails the gate. Never average, weigh severity, or waive a rule — a "minor" FAIL is a FAIL.
6. **Render the verdict.** Fill [assets/templates/verdict.md](assets/templates/verdict.md). On FAIL, aggregate the reviewer's "missing for PASS" suggestions into the fix list, each with its location, ordered by the source skill's category priority (struct → import → bound → fquery → fcomp → fstate → test → name). Every rule whose final result is FAIL must appear in the fix list with a change concrete enough to apply as written — if the reviewer's suggestion only restates the violation, derive the fix from the rule's Correct example before rendering.
If the same rule flips verdicts across re-reviews of an unchanged target, or a human reads the evidence and overrides the verdict, that is a decidability bug in the rule — record it in [gotchas.md](gotchas.md) and sharpen the rule; do not override the gate.
## Verdict Format
The reviewer returns, per rule: `PASS | FAIL | N/A`, evidence (`file:line` or a quote — required for PASS as well as FAIL), and for every FAIL, the fix that flips the rule to PASS once applied — the named change plus its location, never a restatement of the violation. The final report follows [assets/templates/verdict.md](assets/templates/verdict.md).
## Rule Categories
The eight categories and their priority order are defined in [references/_sections.md](references/_sections.md); the 33 vendored rule files live alongside it in `references/`, and [references/_rule-evidence.md](references/_rule-evidence.md) lists them with the evidence that decides each, plus the 10 excluded source rules (with reasons).
## Reference Files
| File | Description |
|------|-------------|
| [references/reviewer-prompt.md](references/reviewer-prompt.md) | Self-contained prompt template for the blind reviewer |
| [assets/templates/verdict.md](assets/templates/verdict.md) | Verdict report template |
| [references/_rule-evidence.md](references/_rule-evidence.md) | Vendoring provenance + per-rule deciding evidence + exclusions |
| [references/_sections.md](references/_sections.md) | Category definitions and fix-list priority order |
| `references/<category>-*.md` | The 33 vendored rule files (struct/import/bound/fquery/fcomp/fstate/test/name) |
| [metadata.json](metadata.json) | Version and source references |
## Related Skills
- `feature-arch` — the source distillation skill this gate's rules were vendored from; use it (if available) to design or migrate the target architecture, and to read the 10 judgment-call rules the gate excludes. The gate itself never needs it at review time.
Pliki w paczce (40)
- SKILL.md 6 KB
- gotchas.md 3 KB
- metadata.json 1 KB
- assets/templates/verdict.md 1 KB
- references/_rule-evidence.md 9 KB
- references/_sections.md 2 KB
- references/bound-feature-scoped-routing.md 2 KB
- references/bound-interface-contracts.md 2 KB
- references/bound-minimize-shared-state.md 2 KB
- references/fcomp-colocate-styles.md 2 KB
- references/fcomp-composition-over-props.md 2 KB
- references/fcomp-error-boundaries.md 2 KB
- references/fquery-avoid-n-plus-one.md 2 KB
- references/fquery-colocate-with-feature.md 2 KB
- references/fquery-feature-scoped-keys.md 2 KB
- references/fquery-parallel-fetching.md 2 KB
- references/fquery-server-component-fetching.md 2 KB
- references/fquery-single-responsibility.md 2 KB
- references/fstate-feature-scoped-stores.md 2 KB
- references/fstate-server-state-separation.md 3 KB
- references/import-avoid-barrel-files.md 2 KB
- references/import-no-cross-feature.md 4 KB
- references/import-path-aliases.md 2 KB
- references/import-public-api.md 2 KB
- references/import-type-only.md 2 KB
- references/import-unidirectional-flow.md 2 KB
- references/name-descriptive-exports.md 2 KB
- references/name-feature-naming.md 3 KB
- references/name-file-conventions.md 3 KB
- references/reviewer-prompt.md 5 KB
- references/struct-app-layer.md 2 KB
- references/struct-feature-folders.md 2 KB
- references/struct-feature-self-contained.md 2 KB
- references/struct-flat-hierarchy.md 2 KB
- references/struct-optional-segments.md 2 KB
- references/struct-shared-layer.md 2 KB
- references/test-colocate-with-feature.md 2 KB
- references/test-feature-isolation.md 2 KB
- references/test-integration-at-app-layer.md 3 KB
- references/test-shared-utilities.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie feature-arch-gate.
Migawka bazy z 13.11.2026 · wersja paczki 7abfd9ae41b4 (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
- 100feature-arch
Tworzy docelowy plan architektury Reacta opartej na funkcjach w docs/architecture/FEATURE-ARCH-TARGET.md: drzewo katalogów, publiczne API funkcji, macierz granic importów i plan migracji. - 100feature-arch
Podaje wytyczne architektury Reacta opartej na funkcjach dla skalowalnych aplikacji: organizacja funkcji, granice modułów, importy między funkcjami, pobieranie danych i kompozycja komponentów. - 90react-architecture
Porządkuje strukturę aplikacji React: foldery według funkcji, podział na komponenty, hooki i granice błędów. - 100adversarial-tanstack
Ocenia zmiany w aplikacjach TanStack Start i TypeScript w werdykcie zalicz lub odrzuć: granice klient-serwer, uwierzytelnianie i typy. - 85arch-check
Sprawdza kod funkcji pod kątem reguł architektury z karty projektu: warstwy zależności, cykle, zakazane wzorce i rozmiar plików. - 100setup-arch-unit
Konfiguruje testy architektury dla Next.js, proponuje reguły granic modułów i dodaje hook Husky uruchamiany przed każdym commitem.