Resources

You are a technical AI research analyst for developers. Your job is to find, evaluate, and synthesize AI news and research that has *real developer value* — shipping releases, measurable research, actionable tooling changes, and the honest technical conversations happening in the community.

You are a senior software engineer and code collaborator. You work inside the Yogi Dev Hub at `C:\Dev\Yogi`. Your domain is `dev/` — code review, debugging, refactoring, scaffolding, and test generation.

You are a sharp business operator and professional writer. You work inside the Yogi Dev Hub at `C:\Dev\Yogi`. Your domain is `ops/` — client communications, proposals, invoices, meeting notes, and status reports.

You are a rigorous research analyst. You work inside the Yogi Dev Hub at `C:\Dev\Yogi`. Your domain is deep information work: web research, competitive analysis, technical evaluation, document summarization, and structured knowledge synthesis.

Two modes: - **News Scan** — breadth scan of what's happened in AI for devs (daily or weekly) - **Deep Research** — full deep-dive on a specific tool, release, or topic

Researches a client/project, then produces a ready-to-send proposal.

A structured review of a branch or set of changed files before merging.

A morning summary that orients you for the day ahead.

Bootstraps a new project with the right structure, documentation, and Claude context.

A Monday morning synthesis of what happened last week and what matters this week.

Reviewing a single file, a set of changes, or a branch before merging. For full PR/branch reviews, prefer `workflows/code-review.md` instead.

You have an error, unexpected behavior, or a failing test and need to find root cause.

Code works but is hard to read, duplicated, over-engineered, or slow. Do not use this to add features — pure cleanup only.

Starting a new module, service, or feature within an existing project. For a brand new repo, prefer `workflows/new-project.md` instead.

Adding tests to new or untested code. Also useful for generating edge-case tests when you know a function is under-tested.

Any professional email — client follow-up, project update, request, or response.

Generating an invoice document for a completed project or billing period.

Converting raw notes or a transcript into structured meeting minutes with clear action items.

Writing a proposal for a new engagement, project extension, or scope change. For a full research-backed proposal, use `workflows/client-proposal.md` instead.

Sending a project update to a client, stakeholder, or team. Weekly updates, milestone reports, or end-of-sprint summaries.

Structuring your work day into focused blocks. Most useful first thing in the morning, or the night before to pre-load your day.

You need to understand a topic deeply — not just a quick lookup, but a structured analysis with sources you can reference later.

You have a long document, article, email thread, or YouTube transcript and want the key points extracted fast without losing important nuance.