ivfarias

Use when starting work on any project (technical or non-technical) to understand structure, standards, and best practices before making changes

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Apply the code-quality checklist to audit files or directories and produce a Markdown report with findings and suggested fixes. Use when asked to "audit these files", "run a quality check", "code quality review", or "check against the code-quality checklist".

Generate a structured deep research prompt. USE WHEN the user needs to research a complex topic, market, or bug deeply. Capabilities include objective clarification, tech stack validation, and prompt generation.

Use for go-to-market strategy, user acquisition, channel analysis, and performance marketing.

Generate documentation for an existing project. USE WHEN onboarded to a new codebase OR documenting legacy code. Capabilities include architectural mapping, tech stack inventory, and technical debt documentation.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Transform user requests into detailed, precise prompts for AI models. Use when users say "promptify", "promptify this", or explicitly request prompt engineering or improvement of their request for better AI responses.

Orchestrates deterministic code review feedback loop — simplify → request review → receive and implement feedback → repeat until done. Run this before creating a PR.

Use this before spawning coding agents when you need to turn an idea into an execution-ready prompt file for bootstrap-task.sh or spawn-agent.sh.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Thematic brainstorming entrypoint. Use before implementation to clarify intent and produce an execution-ready prompt/spec.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when you have a spec or requirements for a multi-step task, before touching code