Rohit Ghumare

Use when deciding what project context should be remembered, retrieved, updated, or deliberately forgotten.

The English summary is being prepared. Showing the original description.

Use when a command, adapter, or runtime smoke depends on proving an agent runtime's capabilities before trusting command routing, writes, shell access, or validation claims.

The English summary is being prepared. Showing the original description.

Use when an agent runtime must choose or verify a /brain-* command route from a user request, handoff, adapter transcript, or stale command catalog.

The English summary is being prepared. Showing the original description.

Use when a design needs pressure-testing for UX, information architecture, states, and accessibility.

The English summary is being prepared. Showing the original description.

Use when broad work needs to be broken into small verifiable slices.

The English summary is being prepared. Showing the original description.

Use when behavior needs concrete proof before review, merge, or shipment.

The English summary is being prepared. Showing the original description.

Use when uncertainty remains and the minimum useful sequence of questions should be asked.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-brief: after intake, research, and grill have enough signal.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-build: an implementation plan has a selected task and validation method.

The English summary is being prepared. Showing the original description.

Use when an output artifact, template, schema, example, or handoff field must stay aligned across commands, skills, docs, and validators.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-start: a user starts from a vague request, idea, task, or product ambition.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-wiki: ingesting sources or updating durable project knowledge.

The English summary is being prepared. Showing the original description.

Use when creating Product Hunt launch carousel images for developer tools, AI tools, open-source projects, GitHub launches, or technical products. Research comparable launches, inspect the project, extract verified proof points, then generate 4-5 launch-ready images with consistent branding, product surfaces, readable copy, and source-grounded claims.

The English summary is being prepared. Showing the original description.

Use when generating a single dense technical architecture, reference poster, or system diagram image for a software project. Produces a source-grounded bitmap diagram with topology, primitives, ingest/process flow, core logic, state scopes, tiers/modules, surfaces, runtime cards, and strict semantic color rules.

The English summary is being prepared. Showing the original description.

Use when creating or editing raster images, visual concepts, product graphics, launch assets, diagrams, posters, thumbnails, reference sheets, UI mock images, or image prompts that need source-grounded claims, readable text, brand direction, and post-generation verification.

The English summary is being prepared. Showing the original description.

Deep, iterative internet research for current facts, source triangulation, contradiction checks, due diligence, competitive analysis, claim verification, "latest" lookups, and cited reports. Use when the user asks to browse, search, research the web, verify claims, compare sources, gather primary sources, investigate companies, people, products, technical topics, news, events, markets, or create AKBP-ready durable research evidence.

The English summary is being prepared. Showing the original description.

Self-verification loop. After completing a task, re-read the original request, list each requirement, verify whether it was met, and fix gaps before stopping.

The English summary is being prepared. Showing the original description.