explore
/explore
Mapuje teren przed projektowaniem zmiany: co już istnieje, jakie są twarde ograniczenia i pułapki, zanim powstanie plan.
- Autor
- pandysp ↗
- Repozytorium
- claude-plugins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 20.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 20.10.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
Mapuje teren przed projektowaniem zmiany: co już istnieje, jakie są twarde ograniczenia i pułapki, zanim powstanie plan.
Wyzwalacze z opisu
Oryginalny opis (EN)
Map the terrain before designing. Use before any substantive design or planning step. Codebase changes, doc drafting, strategy decisions, anything with non-trivial structure. Trigger when the user invokes the explore skill, says "explore first", "what's already there", "map the codebase", or "survey the landscape". The output is mostly for my own grounding. Only surprises, hard constraints, and gotchas surface to the user. If exploration was uneventful, that itself is the report.
Jak działa
- Tooling
- The four phases
- What to surface
- After exploration
- Common pitfalls
Podgląd SKILL.md
--- name: explore description: Map the terrain before designing. Use before any substantive design or planning step. Codebase changes, doc drafting, strategy decisions, anything with non-trivial structure. Trigger when the user invokes the explore skill, says "explore first", "what's already there", "map the codebase", or "survey the landscape". The output is mostly for my own grounding. Only surprises, hard constraints, and gotchas surface to the user. If exploration was uneventful, that itself is the report. --- # Explore: map the terrain before designing Designing without exploring produces options grounded in general priors rather than the actual terrain. They look reasonable in the abstract but don't fit how this codebase / client / domain actually works. This skill enforces a discipline: **before any design step, systematically map what's already there.** Existing patterns, hard constraints, hooks, and things that would surprise you if you weren't looking. ## Tooling Match the tool to the operation, not the domain: - **Autonomous broad exploration.** When the host offers fresh, read-only exploration workers, spawn one when scope is known and several in parallel when scope is uncertain or spans subsystems. Give each worker a *distinct* search focus. If no worker channel exists, perform the same focused passes with the host's search and file-reading capabilities. - **Targeted lookups.** Use the host's search and file-reading capabilities directly when you need raw content in your own context. - **Non-codebase sources.** File reads against notes/docs, web search, MCP queries. ## The four phases The phases apply across domains. Adapt depth and tooling. The *questions* generalize even when the artifacts don't. ### 1. Locate: find what's relevant What artifacts, sources, prior work, or context are in play? Don't accept the user's framing as the boundary. Adjacent material often turns out to be critical. ### 2. Trace: follow how things connect Where does data/argument flow? What depends on what? Which derivations are critical? A trace is complete when you followed the primary artifact end to end: ingress, persistence, consumption. ### 3. Pattern: identify conventions What recurring shapes and established ways of doing things exist? Fighting them creates friction; fitting them removes it. ### 4. Constrain: name the hard limits What would create problems if violated? Knowing these upfront prevents proposing options that get killed in review. ## What to surface Most findings stay in your context. Surface only **surprises**, **hard constraints**, **gotchas**, and **genuine ambiguities** that need user input before design can proceed. If exploration was uneventful, say that plainly. The detailed terrain map stays in your context for the next phase. ## After exploration Findings are grounding for the next step, typically design. If you're proceeding in a way that ignores something from exploration, surface it: *"I'm doing X despite Y. The reason is..."* ## Common pitfalls - **Performative exploration.** Reading material to look thorough, without tying findings to design implications. - **Dumping the reading list.** "I read these 12 files". They want surprises and constraints, not the catalog. - **Confusing locate with trace.** Listing artifacts isn't tracing how things connect. The phases build on each other. - **Skipping because the terrain feels familiar.** Map it anyway when the work is non-trivial. The finding you'd skip past is often the one that reshapes the design. - **Treating exploration as a deliverable.** It's grounding, not a research project. Time-box it. - **Fanning out the same prompt to multiple exploration workers.** Each worker should have a distinct search focus, otherwise you're paying 3× for the same answer.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · pandysp/claude-plugins | 90 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| rapiddweller/archkeel | 100 | MIT |
| zimoliao/scholaraio | 100 | MIT |
| artk0de/tearags-mcp | 100 | MIT |
| artk0de/tearags-mcp | 100 | MIT |
| artk0de/tearags-mcp | 100 | MIT |
| artk0de/tearags-mcp | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki b581db8bc778 (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
- 90explore-codebase
Zbiera kontekst z kodu przed planowaniem: pliki, wzorce, projekty Nx, kod do ponownego użycia, ograniczenia i otwarte pytania. - 95codebase-explore
Analizuje bazę kodu wyłącznie do odczytu: sprawdza architekturę, szuka powiązanych plików i poznaje projekt przed zmianami. - 100design-exploration
Bada kodebazę i podejścia projektowe przed implementacją: jak pasuje nowa funkcja, jakie wzorce już istnieją i jak zaimplementowano dany element. - 100design-exploration
Bada kodebazę i podejścia projektowe przed implementacją: jak pasuje nowa funkcja, jakie wzorce już istnieją i jak zaimplementowano dany element. - 100codebase-onboarding
Przeprowadza rozpoznanie nieznanego projektu przed zmianami: eksploruje repozytorium, mapuje architekturę i stos, i tworzy zweryfikowany raport z rozpoznania przed projektowaniem lub edycją. - 100plan
Bada bazę kodu i projektuje plany wdrożenia bez zmian w plikach, mapując zależności i strategie refaktoryzacji.