how
/how
Wyjaśnia, jak działa podsystem, gdzie powinien leżeć kod i kto za niego odpowiada, zanim ktoś coś zmieni.
- Autor
- dabaige53 ↗
- Repozytorium
- dabaige-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 02.11.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 02.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
Wyjaśnia, jak działa podsystem, gdzie powinien leżeć kod i kto za niego odpowiada, zanim ktoś coś zmieni.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Jak działa
- 1. Assess complexity
- 2. Explore (complex only)
- 3. Synthesize (complex only)
- 4. Present
- Output format
Podgląd SKILL.md
--- name: how description: "Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation." disable-model-invocation: false --- # How Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code. Use current Codex tools for a read-only code investigation. Follow applicable local delegation instructions: investigate directly by default, and delegate only when independent parallel exploration clearly justifies its cost. Use only available agent types; inherit the current model unless an authorized override applies. There is no dependency on Cursor model rules or other pstack Skills. ## 1. Assess complexity If the scope is ambiguous, state your interpretation and explore. The user can redirect. - **Simple** (a single module, a small utility, a narrow question such as "how does function X work"): explore and explain directly. Use [explainer-prompt.md](references/explainer-prompt.md) as a checklist without the explorer-findings section. Go to step 4. - **Complex** (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): go to step 2. When in doubt, take the simple path. ## 2. Explore (complex only) Decompose the question into distinct, non-overlapping angles. Investigate directly unless delegation is justified by the rules above. When delegating, use the smallest useful number of explorers within session limits, each with [explorer-prompt.md](references/explorer-prompt.md), its assigned scope and explicit read-only responsibility. Otherwise use the same checklist for focused passes. ## 3. Synthesize (complex only) Synthesize the findings directly using [explainer-prompt.md](references/explainer-prompt.md). If independent synthesis is separately justified, give the reviewer all findings and the original question; do not create an extra agent only to rephrase the answer. ## 4. Present Answer the original question in language suited to the current reader. Cite inspected files and explain necessary terms. Reconcile contradictory findings by checking the code; keep unresolved gaps visible. A diagram is useful only when it clarifies the actual flow. ## Output format The explanation uses the sections defined in `references/explainer-prompt.md`, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas.
Pliki w paczce (5)
- LICENSE 1 KB
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/explainer-prompt.md 3 KB
- references/explorer-prompt.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · dabaige53/dabaige-skills | 85 | MIT |
| sma1lboy/rove | 100 | MIT |
| h2xd/skills | 100 | MIT |
| flora131/atomic | 100 | MIT |
| pantheon-org/tekhne | 100 | MIT |
| jstarfilms/vibecode-protocol-suite | 100 | ISC |
| scino/fstack | 100 | MIT |
| irg1008/cstack | 100 | MIT |
| shrimpwtf/oh-my-pstack | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki c4b322284146 (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
- 80workflow-how
Wyjaśnia, jak działa podsystem, jego przepływ w czasie działania i gdzie powinien leżeć kod, dla nowych w projekcie. - 100comms-how
Wyjaśnia, jak działa podsystem Flowstate: architekturę, przepływ w czasie wykonania i miejsce na nowy kod.