Inspiration

🚀 What You Can Do

1. Use Guru Docs as Context While You Code

Access your team’s best practices, architecture guides, and API documentation from Guru right inside your IDE.

💡 Example: While implementing a new API endpoint, query Guru for “authentication best practices” or “API versioning standards” to guide your implementation.

2. Generate Guru Cards From Your Code

Turn what you’ve just written into documentation instantly.

💡 Example: After building a new feature, create a Guru card draft summarizing the feature’s purpose, how it works, and any configuration steps.

3. Enrich Code Reviews With Knowledge

Ask Guru questions like:

• “What’s our preferred error-handling pattern?”
• “How do we structure React components?”

Do it directly in your PR review context to align with team standards.

4. Link Code to Verified Knowledge

Attach relevant Guru Cards — like “CI/CD pipeline guide” or “Data model diagram” — to your comments or documentation blocks so teammates can reference the source of truth.

5. Onboard Faster With Instant Context

New developers can search Guru for internal definitions, processes, or design docs without toggling tools.

💡 Example: Typing guru:how do we deploy staging? in your IDE could pull up your deployment runbook from Guru.

6. Document As You Build

As you code new modules, let Guru help you automatically generate draft documentation or technical breakdowns using your file context.

💡 Example: Write a new UserService.ts and generate a Guru Card titled “User Service Feature Breakdown” with summaries of key methods and dependencies.

7. Stay in Sync With Product and Engineering

Search Guru from your IDE to see related feature specs, design docs, or decisions that shaped the code you’re editing.

🧠 Why It Matters

• Stay in flow: No more tab switching — your knowledge lives where you work.
• Ship with confidence: Build using verified information from Guru.
• Keep knowledge fresh: Every code change is a chance to update or create documentation effortlessly.