how
/how
Wyjaśnia, jak działa podsystem, gdzie powinien leżeć kod i kto za niego odpowiada, zanim ktoś coś zmieni.
- Autor
- guangshinhaha ↗
- Repozytorium
- shinstack ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.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." --- # 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. Every spawn is an `Agent` call with `subagent_type: general-purpose`, read-only in intent (explorers, light weight, and the explainer, standard weight, never edit files). Use the parent model unless the user says otherwise. ## 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"): no explorers. Spawn one explainer that explores and explains in one pass, built from `references/explainer-prompt.md` 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. **Other harnesses.** If your harness has no subagent tool, run each role yourself, one after another. ## 2. Explore (complex only) Decompose the question into 2 to 4 angles, each a distinct slice of the subsystem. Spawn all explorers in a single message, each with `references/explorer-prompt.md` and its angle filled in. ## 3. Synthesize (complex only) Once all explorers have returned, spawn one explainer with `references/explainer-prompt.md` and every explorer's findings filled in. ## 4. Present Present the explainer's output. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it. ## 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 (3)
- SKILL.md 2 KB
- references/explainer-prompt.md 3 KB
- references/explorer-prompt.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · guangshinhaha/shinstack | 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 73c4e3f3e760 (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.