Hardcore scrape, recursively research, and obsessively loop to grab all knowledge about any topic, then compress it into 100% loss-less semantic developer guides.
1. π― Quick Start Dashboard
flowchart LR A[<b>INPUT SPEC/TOPIC</b><br/>β’ Tool / Stack<br/>β’ FOSS Library<br/>β’ Raw Content] --> B[<b>HARDCORE GRAB</b><br/>β’ Web search<br/>β’ Repo read<br/>β’ Issue/PR] B --> C[<b>OBSESSIVE LOOP</b><br/>β’ Cross-ref<br/>β’ Verify<br/>β’ Deepen] C --> D[<b>KURBY DIGEST</b><br/>β’ Strip bloat<br/>β’ Keep core<br/>β’ Density 100%]
2. π Hardcore Grabbing
- Recursive Search: Use
web_searchandreadtools to grab docs, spec sheets, and FOSS repositories. - Local Discovery: Map workspace dependencies (
package.json,Cargo.toml) and environment configs (.env*). - Diverse Sources: Target developer wikis, RFCs, GitHub issues, and discussion threads.
3. π Research Loop
- Perpetual Looping: Avoid stopping at the first search page. Retrieve deep pages and cross-reference contradictory sources.
- Fact Verification: Verify command parameters, API changes, and environment limits against live codebase files.
- Traversing Deprecations: Identify legacy paths, active forks, and pending breaking changes in issue lists.
4. βοΈ Kurby Compression
- Bloat Elimination: Delete conversational pleasantries, introductory guides, meta-dialogues, and verbose explanations.
- Semantic Preservation: Condense text while retaining all parameters, configurations, types, and traps.
- Environment Scope: Isolate and keep only what applies directly to the target operating system, tooling, and constraints.
5. π¨ Formatting
| Emoji | Category | Role in Digest |
|---|---|---|
| π | Quick Start | Scraped installation and bootstrapping steps. |
| π§ | Configuration | Raw configuration flags, properties, and environment variables. |
| π¦ | Dependencies | Target package declarations, modules, and library imports. |
| π‘ | Best Practices | Architectures, design patterns, and optimization tricks. |
| π¨ | Gotchas / Alerts | Deprecations, traps, API incompatibilities, and compiler quirks. |
| π | Verification | Test commands, validation scripts, and sanity assertions. |
6. π Self-Verification Checklist
Before finalizing any digested content, verify against these rules:
- No paragraph exceeds 2 sentences.
- 100% of core information is retained in condensed format.
- No fluff words (e.g. βactuallyβ, βbasicallyβ, βsimplyβ, βobviouslyβ).
- Visual landmarks are applied consistently.