giuice

Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, when a task complete, or combined bug/security and code-quality branch audits.

Executes CodeWiki phase plans one task at a time with focused implementation, plan updates, verification, and pending wiki follow-up. Use when the user asks to implement or continue tasks, process a task file, finish the next unchecked item, run verified development work, or handle pending absorb state during the build loop.

Searches the local CodeWiki and synthesizes grounded answers with citations to wiki pages. Use when the user asks how the project works, why a decision was made, where knowledge lives, what is known about an entity/issue/lesson/source, or whether a substantial answer should be filed back into the wiki.

Extracts durable CodeWiki knowledge from recent code changes, git diffs, changed files, and phase outcomes. Use when a phase is complete, pending absorb state exists, substantial coding work has landed, or lessons/entities/issues/decisions from implementation should be proposed for human-approved wiki updates.

Routes the current request to the right CodeWiki skill based on user intent and repository state. Use when the user asks what to do next, wants the recommended workflow, resumes a session, starts a feature, reacts to pending absorb state, or needs help choosing between CodeWiki skills.

Fluxo de trabalho com IA em 3 fases — Explorar (brainstorm guiado), Planejar (plano com tarefas atômicas) e Executar (passo a passo). Ative esta skill sempre que o usuário digitar `/explorar`, `/planejar` ou `/executar`, ou quando tiver qualquer objetivo que envolva planejamento, criação ou dúvida aberta. Serve tanto para tarefas de código quanto para tarefas do mundo real (escrever, pesquisar, contatar, montar). Idioma pt-BR.

Converts a CodeWiki PRD into implementation phases, actionable tasks, and relevant files. Use when codewiki-prd has produced a PRD, a PRD exists but no phase plan exists, the user asks to break down work, or codewiki-process needs an execution-ready plan.

Finds important but undocumented CodeWiki entities, concepts, decisions, lessons, or issues by scanning wikilinks, backlinks, repeated mentions, and code-backed references. Use when the wiki has thin pages, missing high-signal pages, repeated unresolved links, or the user asks to expand the knowledge graph.

A brief description of what this skill does

Mandatory safety guide for every Virtual Office change involving presence, sessions, realtime, space placement, movement, occupancy, private-space access, Knock, presence database contracts, migrations, rollout, or production incidents. Use before editing or diagnosing any of these areas.

Mandatory safety guide for every Virtual Office change involving presence, sessions, realtime, space placement, movement, occupancy, private-space access, Knock, presence database contracts, migrations, rollout, or production incidents. Use before editing or diagnosing any of these areas.

Mandatory safety guide for Virtual Office presence, Realtime, placement, membership lifecycle, capacity, private-space access, and Knock changes. Consult it before changing any Presence client, server route, database function, policy, migration, cache key, storage hint, or space UI that can affect connection, occupancy, movement, logout, reconnection, or access.

Scaffold a new Supabase SQL migration in supabase/migrations/ with the correct UTC-timestamp filename and an RLS-aware template that bakes in the project's users.id-vs-supabase_uid rule. Use when creating a database migration, schema change, new table, column, index, or RLS / storage-bucket policy.

Scaffold a new Supabase SQL migration in supabase/migrations/ with the correct UTC-timestamp filename and an RLS-aware template that bakes in the project's users.id-vs-supabase_uid rule. Use when creating a database migration, schema change, new table, column, index, or RLS / storage-bucket policy.

Executes CodeWiki phase plans one task at a time with focused implementation, plan updates, verification, and pending wiki follow-up. Use when the user asks to implement or continue tasks, process a task file, finish the next unchecked item, run verified development work, or handle pending absorb state during the build loop.

Searches the local CodeWiki and synthesizes grounded answers with citations to wiki pages. Use when the user asks how the project works, why a decision was made, where knowledge lives, what is known about an entity/issue/lesson/source, or whether a substantial answer should be filed back into the wiki.

Fluxo de trabalho com IA em 3 fases — Explorar (brainstorm guiado), Planejar (plano com tarefas atômicas) e Executar (passo a passo). Ative esta skill sempre que o usuário digitar `/explorar`, `/planejar` ou `/executar`, ou quando tiver qualquer objetivo que envolva planejamento, criação ou dúvida aberta. Serve tanto para tarefas de código quanto para tarefas do mundo real (escrever, pesquisar, contatar, montar). Idioma pt-BR.

Create a complete SPEC from scratch through an exhaustive requirements interview before any planning or implementation. Use this skill whenever the user asks to create, define, clarify, scope, or write a spec/SPEC/PRD/requirements document from an idea, especially when they want to avoid assumptions, start at "step zero," or prepare input for later planning workflows. This skill must question goals, requirements, constraints, edge cases, business rules, and acceptance criteria before drafting the final spec.

Use when working through DreamShaper forms for the new workshop project "Desenvolver Software com IA e SDD" from temp.md, pasted HTML prompt snippets, or docs/dreamshaper-status.md. Helps extract the current question, draft concise Brazilian Portuguese responses grounded in the user's own project evidence, and update progress/status. Do not use for evading AI detection, fabricating experience, or submitting work without user-provided facts.