how
/how
Wyjaśnia, jak działa wskazany podsystem, jaki jest przepływ wykonania i kto za co odpowiada, zanim ktoś zmieni kod.
- Autor
- THonour99 ↗
- Repozytorium
- pstack-herdr ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.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 10.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 wskazany podsystem, jaki jest przepływ wykonania i kto za co odpowiada, zanim ktoś zmieni kod.
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: true --- # How In Codex, read [the Codex adapter](../../docs/harness/codex.md) once per session before you follow this skill. It maps the Cursor names in pstack skills to Codex. 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 a Task subagent with `subagent_type: generalPurpose` and `readonly: true`. Explorers use the `how explorer` line in the `pstack-models.mdc` rule (default `grok-4.7-xhigh-fast`), and every explainer uses the `how explainer` line (default `claude-opus-5-5-xhigh`). Set `model` to that line's value, or to the default if the rule or the line is missing. Leave `model` unset when the value is `auto` or `inherit-parent`. If the value is `hc:<program>`, follow the `hc:` rule in the Subagents section of the **poteto-mode** skill instead of spawning a Task. If the Task tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill. ## 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. ## 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 3 KB
- references/explainer-prompt.md 3 KB
- references/explorer-prompt.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · THonour99/pstack-herdr | 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 edb259cbf766 (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. - 95codebase-investigation
Wyjaśnia, jak działa kod i dlaczego jest taki, czytając historię Git, pull requesty, zgłoszenia i dokumentację.