rbin-task-flow 1.3.0 → 1.4.0

package/.cursor/rules/git_control.mdc

@@ -5,11 +5,12 @@ alwaysApply: true
 ---
 
 - **General Command Permission:**
-  - **✅ CAN execute** any system command without asking
-  - **✅ CAN execute** npm, yarn, pnpm, docker, etc without confirmation
-  - **✅ CAN execute** scripts, tests, linters, formatters without asking
+  - **✅ CAN execute** any system command without asking (Claude may run commands without asking for approval)
+  - **✅ CAN execute** npm, yarn, pnpm, docker, scripts, tests, linters, formatters without confirmation
   - **✅ DON'T need to ask** before executing simple or common commands
-  - **❌ ONLY EXCEPTION**: `git` commands that modify the repository
+  - **❌ EXCEPTIONS** (do not execute without user approval):
+    - **Git**: `git` commands that modify the repository (add, commit, push, pull, merge, checkout, etc.)
+    - **Cloud/remote resources**: Commands that run or connect to cloud/remote resources (e.g. database connections, cloud CLI that provisions resources, migrations against remote DB, deploying to production)
 
 - **Read Commands - Automatic Execution:**
   - **✅ ALWAYS execute without asking** commands that only read information:
@@ -85,4 +86,4 @@ alwaysApply: true
   - RBIN Task Flow workflow should not include automatic git execution
 
 - **Fundamental Principle:**
-  > **User has complete control over the Git repository. AI can execute any system command without asking, EXCEPT git commands. For git, only suggests, analyzes, and informs. Never modifies git state.**
+  > **Claude may execute commands without asking, except: (1) git commands that modify the repository, and (2) commands that run cloud/remote resources (e.g. database, cloud provisioning). For those, only suggest or ask for approval.**

package/.cursor/rules/task_execution.mdc

@@ -6,6 +6,7 @@ alwaysApply: true
 
 - **RBIN Task Flow - AI-Powered Task Management:**
   - This project uses **RBIN Task Flow** for task tracking and management
+  - **Models**: Claude and Cursor use the **default model** of each environment. Do not specify or require a particular model.
   - **IMPORTANT**: When user mentions "task flow", they always refer to **RBIN Task Flow**
   - Tasks are defined in plain text: `.task-flow/tasks.input.txt`
   - Task data is stored in: `.task-flow/.internal/` (do not edit directly - internal system files)

package/.cursor/rules/task_generation.mdc

@@ -7,31 +7,32 @@ alwaysApply: true
 - **Task Generation - Direct and Efficient:**
   - When user asks to "Read tasks.input.txt and generate detailed subtasks updating task status":
     - **READ**: `.task-flow/tasks.input.txt` (only process lines starting with `- `)
-    - **READ**: `.task-flow/screens/` directory to list available screenshots (ALWAYS check this directory)
+    - **READ**: `.task-flow/contexts/` directory to list available context files (ALWAYS check this directory)
     - **GENERATE**: Two JSON files and one markdown file with the exact structure below
     - **SAVE**: All files to `.task-flow/`
     - **DON'T**: Check existing JSONs, explore codebase, or ask questions
 
-- **Screenshot Reference System:**
-  - **AUTOMATIC**: Always check `.task-flow/screens/` directory for available screenshots (PNG, JPG files)
-  - **NO LISTING NEEDED**: Don't require screenshots to be listed in tasks.input.txt - always scan the directory
-  - **AUTOMATIC MATCHING**: Automatically match screenshots to tasks based on keywords (e.g., "login" → `login_recover_signup.png`, "dashboard" → `dashboard.png`, "paciente" → `patient.png`)
-  - **SPECIFIC REFERENCE**: If task contains `task-flow-screen nome_do_arquivo.png`, reference that specific screenshot from `.task-flow/screens/`
-  - **PATH ALWAYS**: `task-flow-screen` always references files in `.task-flow/screens/` directory
-  - **INCLUDE**: Add screenshot reference in instructions: "Visual reference: `.task-flow/screens/filename.png`"
+- **Context Reference System:**
+  - **PURPOSE**: `.task-flow/contexts/` is for AIs to consult reference material (any type: .md, .txt, .png, .jpg, .json, etc.) when generating and working on tasks
+  - **AUTOMATIC**: Always check `.task-flow/contexts/` directory for available context files (all file types)
+  - **NO LISTING NEEDED**: Don't require context files to be listed in tasks.input.txt - always scan the directory
+  - **AUTOMATIC MATCHING**: Match context files to tasks by keywords (e.g., "login" → `login-mockup.png` or `api-login.md`, "dashboard" → `dashboard.png`)
+  - **SPECIFIC REFERENCE**: If task contains `task-flow-screen nome_arquivo.ext`, reference that file from `.task-flow/contexts/`
+  - **PATH ALWAYS**: `task-flow-screen` always references files in `.task-flow/contexts/`
+  - **INCLUDE**: In subtask instructions, add the reference: "Context/reference: `.task-flow/contexts/filename.ext`" (or "Visual reference" for images)
 
 - **Required Actions:**
   1. Read `tasks.input.txt`:
      - Process task lines (only process lines starting with `- `)
      - Check for `task-flow-screen nome_do_arquivo.png` markers in task descriptions
-  2. **ALWAYS** list available screenshots from `.task-flow/screens/` directory (PNG, JPG files)
+  2. **ALWAYS** list available context files from `.task-flow/contexts/` directory (all file types: .md, .txt, .png, .jpg, .json, etc.)
   3. For each task line, create a task with sequential ID starting at 1
   4. Generate 3-8 subtasks per task with:
      - Clear title
      - Brief description
      - Step-by-step instructions (3-5 steps)
-     - **AUTOMATIC**: Include relevant screenshot references when applicable (match by keywords)
-     - **SPECIFIC**: If task has `task-flow-screen nome_do_arquivo.png`, reference that specific screenshot from `.task-flow/screens/`
+     - **AUTOMATIC**: Include relevant context references when applicable (match by keywords)
+     - **SPECIFIC**: If task has `task-flow-screen nome_arquivo.ext`, reference that file from `.task-flow/contexts/`
   5. Create `.task-flow/.internal/tasks.json` with structure below
   6. Create `.task-flow/.internal/status.json` with all tasks/subtasks as "pending"
   7. Create `.task-flow/tasks.status.md` with all tasks and subtasks marked as `- [ ]` (pending)
@@ -117,26 +118,27 @@ alwaysApply: true
 
 - **Example:**
   - Input (`tasks.input.txt`): `- Create authentication system`
-  - Screenshots available: `login_recover_signup.png`
-  - Output: Task with ID 1, 5 subtasks with screenshot references:
-    - Subtask 1: "Setup database schema" (no screenshot)
-    - Subtask 2: "Create login form" → Instructions include: "Visual reference: `.task-flow/screens/login_recover_signup.png`"
-    - Subtask 3: "Implement registration" → Instructions include screenshot reference
-    - Subtask 4: "Add JWT authentication" (no screenshot)
-    - Subtask 5: "Test authentication flow" → Instructions include screenshot reference
+  - Context files available: `login_recover_signup.png`
+  - Output: Task with ID 1, 5 subtasks with context references:
+    - Subtask 1: "Setup database schema" (no context)
+    - Subtask 2: "Create login form" → Instructions include: "Visual reference: `.task-flow/contexts/login_recover_signup.png`"
+    - Subtask 3: "Implement registration" → Instructions include context reference
+    - Subtask 4: "Add JWT authentication" (no context)
+    - Subtask 5: "Test authentication flow" → Instructions include context reference
   
-- **Screenshot Reference Examples:**
-  - Task: `- Dentist authentication system` → Automatically matches and references `login_recover_signup.png` from `.task-flow/screens/`
-  - Task: `- Basic dashboard with structure task-flow-screen dashboard.png` → References specific `.task-flow/screens/dashboard.png`
-  - Task: `- Complete patient CRUD` → Automatically matches and references `patient.png` and `patient_profile.png` from `.task-flow/screens/` if available
-  - **IMPORTANT**: `task-flow-screen` always references files in `.task-flow/screens/` - no need to specify full path
+- **Context Reference Examples:**
+  - Task: `- Dentist authentication system` → Automatically matches and references `login_recover_signup.png` from `.task-flow/contexts/`
+  - Task: `- Basic dashboard with structure task-flow-screen dashboard.png` → References specific `.task-flow/contexts/dashboard.png`
+  - Task: `- Complete patient CRUD` → Automatically matches and references `patient.png` and `patient_profile.png` from `.task-flow/contexts/` if available
+  - **IMPORTANT**: `task-flow-screen` always references files in `.task-flow/contexts/` - no need to specify full path
+  - **FILE TYPES**: Contexts can be any type (images, markdown, text, JSON, etc.) for the AI to read and use when working on tasks
 
 - **Critical Rules:**
   - ✅ Be direct: Read → Generate → Save
-  - ✅ **ALWAYS** check `.task-flow/screens/` directory for available screenshots (automatic, no need to list in tasks.input.txt)
-  - ✅ Automatically match and reference relevant screenshots in subtask instructions based on keywords
-  - ✅ Support `task-flow-screen nome_do_arquivo.png` format - always references `.task-flow/screens/nome_do_arquivo.png`
-  - ✅ No exploration of codebase beyond screenshots directory
+  - ✅ **ALWAYS** check `.task-flow/contexts/` directory for available context files (automatic, no need to list in tasks.input.txt)
+  - ✅ Automatically match and reference relevant context files in subtask instructions based on keywords
+  - ✅ Support `task-flow-screen nome_do_arquivo.png` format - always references `.task-flow/contexts/nome_do_arquivo.png`
+  - ✅ No exploration of codebase beyond `.task-flow/contexts/` directory
   - ✅ No questions - just generate
   - ✅ Use current timestamp for `createdAt`
   - ✅ All statuses start as "pending"

package/.cursor/rules/task_work.mdc

@@ -62,8 +62,8 @@ alwaysApply: true
      - Skip "done" and "in_progress" subtasks
   3. **For each subtask**:
      - Read full instructions from `tasks.json`
-     - **CHECK**: If instructions mention screenshot references (`.task-flow/screens/...`), verify screenshot exists
-     - **REFERENCE**: Use screenshots as visual reference when implementing UI-related subtasks
+     - **CHECK**: If instructions mention context references (`.task-flow/contexts/...`), verify the context file exists
+     - **CONSULT**: Read and use context files from `.task-flow/contexts/` when implementing (images, .md, .txt, .json, etc. – any type that helps the task)
      - Implement following step-by-step instructions
      - Test/verify implementation
      - Update `status.json` to mark as "done"
@@ -91,8 +91,8 @@ alwaysApply: true
      - Skip "done" and "in_progress" subtasks
   4. **For each subtask** (only if dependency check passed):
      - Read full instructions from `tasks.json`
-     - **CHECK**: If instructions mention screenshot references (`.task-flow/screens/...`), verify screenshot exists
-     - **REFERENCE**: Use screenshots as visual reference when implementing UI-related subtasks
+     - **CHECK**: If instructions mention context references (`.task-flow/contexts/...`), verify the context file exists
+     - **CONSULT**: Read and use context files from `.task-flow/contexts/` when implementing (images, .md, .txt, .json, etc. – any type that helps the task)
      - Implement following step-by-step instructions
      - Test/verify implementation
      - Update `status.json` to mark as "done"
@@ -206,15 +206,16 @@ alwaysApply: true
   - If file doesn't exist → create it
   - If instructions unclear → ask for clarification (but try to infer first)
 
-- **Screenshot Support:**
-  - **AUTOMATIC**: When implementing subtasks, check if instructions reference screenshots
-  - **REFERENCE**: Use screenshots from `.task-flow/screens/` as visual reference for UI implementation
-  - **MATCHING**: Match screenshot references mentioned in subtask instructions
-  - **NO NEED**: User doesn't need to explicitly mention screenshots - they're automatically considered
+- **Context Support:**
+  - **PURPOSE**: `.task-flow/contexts/` holds reference material (any file type) for the AI to consult when working on tasks
+  - **AUTOMATIC**: When implementing subtasks, check if instructions reference context files
+  - **CONSULT**: Read and use files from `.task-flow/contexts/` as needed (specs, mockups, examples, .md, .txt, .png, .json, etc.)
+  - **MATCHING**: Use the context files mentioned in subtask instructions; support any extension, not only images
+  - **NO NEED**: User doesn't need to explicitly mention context files - they're automatically considered
 
 - **Integration:**
   - Works with [task_execution.mdc](mdc:.cursor/rules/task_execution.mdc) - same workflow
-  - Follows [task_generation.mdc](mdc:.cursor/rules/task_generation.mdc) - screenshots are automatically referenced in generated subtasks
+  - Follows [task_generation.mdc](mdc:.cursor/rules/task_generation.mdc) - context files are automatically referenced in generated subtasks
   - Follows [commit_practices.mdc](mdc:.cursor/rules/commit_practices.mdc) - suggest commit after completion
   - Respects [git_control.mdc](mdc:.cursor/rules/git_control.mdc) - never commit automatically
 

package/.cursor/settings.json

@@ -1,3 +1 @@
-{
-  "model": "claude-sonnet-4-5-20250929"
-}
+{}

package/.model-versions.json

@@ -1,17 +1 @@
-{
-  "claude": {
-    "current": "claude-sonnet-4-5-20250929",
-    "latest": "claude-sonnet-4-5-20250929",
-    "checkUrl": "https://docs.anthropic.com/claude/docs/models-overview"
-  },
-  "cursor": {
-    "current": "claude-sonnet-4-5-20250929",
-    "latest": "claude-sonnet-4-5-20250929",
-    "checkUrl": "https://docs.cursor.com/models"
-  },
-  "gemini": {
-    "current": "gemini-3-flash",
-    "latest": "gemini-3-flash",
-    "checkUrl": "https://ai.google.dev/models/gemini"
-  }
-}
+{"claude":{"current":"claude-sonnet-4-5-20250929","latest":"claude-sonnet-4-5-20250929","checkUrl":"https://docs.anthropic.com/claude/docs/models-overview"},"cursor":{"current":"claude-sonnet-4-5-20250929","latest":"claude-sonnet-4-5-20250929","checkUrl":"https://docs.cursor.com/models"}}

package/.task-flow/contexts/example.png.txt

@@ -0,0 +1,29 @@
+# Example Context
+
+This folder (`.task-flow/contexts/`) is for AIs to consult reference material when working on tasks.
+
+## Purpose
+
+- **Contexts** = any files that help the AI understand what to build or how to do it
+- The AI reads and uses these files when generating subtasks and when implementing them
+- Different file types are supported: images, docs, specs, examples, etc.
+
+## Supported file types (examples)
+
+- **Images:** `.png`, `.jpg` – mockups, screenshots, diagrams
+- **Text / docs:** `.md`, `.txt` – specs, requirements, notes
+- **Data / config:** `.json`, `.yaml` – examples, schema, sample data
+- **Other:** any file that is useful as context for the task
+
+## How to use
+
+1. Add your context files to this folder with descriptive names (e.g. kebab-case)
+2. RBIN Task Flow lists and references them when generating subtasks
+3. To reference a specific file in a task, use: `task-flow-screen filename.ext`
+
+## Example names
+
+- `login-mockup.png`
+- `api-contract.json`
+- `requirements.md`
+- `dashboard-spec.txt`

package/.task-flow/tasks.input.txt

@@ -7,12 +7,13 @@
 3. Use `task-flow: sync` to generate subtasks from your tasks
 4. Use `task-flow: status` to view task progress
 
-## Screenshots:
+## Contexts:
 
-- Add your screenshots to the `.task-flow/screens/` folder (PNG or JPG)
-- RBIN Task Flow automatically detects and references available screenshots when generating subtasks
-- To reference a specific screenshot in a task, use: `task-flow-screen filename.png`
-- Example: `- Create login screen task-flow-screen login.png`
+- The `.task-flow/contexts/` folder is for AIs to consult when working on tasks (different file types: .md, .txt, .png, .jpg, .json, etc.)
+- Add specs, mockups, requirements, examples, or any reference file to this folder
+- RBIN Task Flow detects and references them when generating and implementing subtasks
+- To reference a specific context in a task: `task-flow-screen filename.ext`
+- Example: `- Create login screen task-flow-screen login-mockup.png`
 
 ## Tasks:
 

package/CLAUDE.md

@@ -1,5 +1,9 @@
 # Claude Code Instructions
 
+## Models
+
+Claude and Cursor use the **default model** of each environment. No specific model is set in this project; do not specify or require a particular model.
+
 ## Development Rules
 
 All development rules are automatically loaded from `.cursor/rules/` directory. These rules include:

package/README.md

@@ -3,13 +3,12 @@
 <div align="center">
 
 ![Claude](https://img.shields.io/badge/Claude-Sonnet%204.5-8A2BE2?style=for-the-badge&logo=anthropic&logoColor=white)
-![Gemini](https://img.shields.io/badge/Gemini-3%20Flash-4285F4?style=for-the-badge&logo=google&logoColor=white)
 ![Cursor](https://img.shields.io/badge/Cursor-IDE-blue?style=for-the-badge&logo=visual-studio-code&logoColor=white)
 ![Task Flow](https://img.shields.io/badge/Task%20Flow-AI%20Powered-green?style=for-the-badge)
 ![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=for-the-badge)
 ![npm](https://img.shields.io/npm/v/rbin-task-flow?style=for-the-badge)
 
-**Configuração com um comando para Claude Code, Gemini, Cursor e RBIN Task Flow em qualquer projeto**
+**Configuração com um comando para Claude Code, Cursor e RBIN Task Flow em qualquer projeto**
 
 <div style="margin-top: 20px; margin-bottom: 20px;">
   <a href="#português">🇧🇷 Português</a> | <a href="#english">🇬🇧 English</a>
@@ -36,13 +35,13 @@
 
 ## O Que É Este Projeto?
 
-RBIN Task Flow é um sistema de gerenciamento de tarefas alimentado por IA que configura automaticamente Claude Code, Gemini e Cursor IDE em qualquer projeto. Você define tarefas em texto simples e a IA gera subtarefas detalhadas e acionáveis automaticamente.
+RBIN Task Flow é um sistema de gerenciamento de tarefas alimentado por IA que configura automaticamente Claude Code e Cursor IDE em qualquer projeto. Você define tarefas em texto simples e a IA gera subtarefas detalhadas e acionáveis automaticamente.
 
 **Principais benefícios:**
 - ✅ Instalação global NPM - instale uma vez, use em qualquer projeto
 - ✅ Zero configuração - pronto para usar imediatamente
 - ✅ Gerenciamento simples - escreva tarefas em texto, a IA faz o resto
-- ✅ Múltiplos modelos de IA - Claude, Gemini e Cursor configurados
+- ✅ Múltiplos modelos de IA - Claude e Cursor configurados
 
 ## Instalação
 
@@ -80,7 +79,7 @@ rbin-task-flow report <ids>  # Gera relatório (ex: "1" ou "1,2" ou "all")
 
 ### Comandos da IA - Por Que Usar?
 
-Após inicializar, use estes comandos na IA (Cursor/Claude/Gemini) para gerenciar tarefas automaticamente:
+Após inicializar, use estes comandos na IA (Cursor/Claude) para gerenciar tarefas automaticamente:
 
 | Comando | Por Que Usar | Feature Principal |
 |---------|--------------|-------------------|
@@ -116,13 +115,13 @@ cd meu-projeto && rbin-task-flow init
 
 ## Visão Geral
 
-Repositório centralizado de configurações e regras de desenvolvimento que podem ser instaladas instantaneamente em qualquer projeto. Fornece configuração completa para Claude Code, Gemini, Cursor IDE e RBIN Task Flow - um sistema simples de gerenciamento de tarefas alimentado por IA.
+Repositório centralizado de configurações e regras de desenvolvimento que podem ser instaladas instantaneamente em qualquer projeto. Fornece configuração completa para Claude Code, Cursor IDE e RBIN Task Flow - um sistema simples de gerenciamento de tarefas alimentado por IA.
 
 ### Principais Recursos
 
 - **Instalação Global NPM** - Instale uma vez, use em qualquer lugar com `npm install -g rbin-task-flow`
 - **Gerenciamento Simples de Tarefas** - Defina tarefas em texto simples, a IA gera subtarefas detalhadas
-- **Múltiplos Modelos de IA** - Claude Code Sonnet e Gemini 3 Flash configurados e prontos para uso
+- **Múltiplos Modelos de IA** - Claude Code Sonnet configurado e pronto para uso
 - **.gitignore Discreto** - Configurações de IA ocultas com comentários genéricos
 - **Zero Configuração** - Pronto para usar imediatamente
 - **RBIN Task Flow** - Gerenciamento de tarefas alimentado por IA com interface de texto simples
@@ -131,7 +130,7 @@ Repositório centralizado de configurações e regras de desenvolvimento que pod
 
 - **Sistema Operacional:** macOS, Linux ou Windows (WSL)
 - **Ferramentas:** Git, Bash, Node.js
-- **Necessário:** Claude Code CLI, acesso à API Gemini ou Cursor IDE (com assinatura Pro)
+- **Necessário:** Claude Code CLI ou Cursor IDE (com assinatura Pro)
 
 ### Alternativa: Instalação Legacy (Sem NPM)
 
@@ -165,9 +164,6 @@ seu-projeto/
 ├── .claude/
 │   └── settings.json             # Configurações do Claude Code
 │
-├── .gemini/
-│   └── settings.json             # Configurações do Gemini
-│
 ├── .task-flow/                   # RBIN Task Flow
 │   ├── tasks.input.txt           # Definições de tarefas em texto simples (edite isso!)
 │   ├── tasks.status.md           # ⚠️ Status das tarefas (atualizado automaticamente, NÃO EDITE)
@@ -182,7 +178,6 @@ seu-projeto/
 
 Nenhuma configuração adicional necessária! Apenas certifique-se de ter:
 - Claude Code CLI instalado, OU
-- Acesso à API Gemini configurado, OU
 - Cursor IDE com assinatura Pro ativa
 
 **Você está pronto!**
@@ -207,13 +202,6 @@ O Claude Code vem pré-configurado com:
 - Integração com RBIN Task Flow
 - Melhores práticas de desenvolvimento
 
-### Integração com Gemini
-
-O Gemini vem pré-configurado com:
-- Configurações personalizadas
-- Integração com RBIN Task Flow
-- Melhores práticas de desenvolvimento
-
 ## O Que Está Configurado
 
 ### Regras de Desenvolvimento
@@ -241,11 +229,9 @@ O instalador adiciona estas entradas ao `.gitignore`:
 
 ```gitignore
 .claude/
-.gemini/
 .cursor/
 .task-flow/
 CLAUDE.md
-GEMINI.md
 ```
 
 **Por que discreto?**
@@ -290,9 +276,6 @@ rbin-task-flow/
 ├── .claude/
 │   └── settings.json             # Configurações do Claude Code
 │
-├── .gemini/
-│   └── settings.json             # Configurações do Gemini
-│
 ├── .task-flow/
 │   ├── README.md                 # Referência rápida de comandos
 │   ├── tasks.input.txt           # Template de definições de tarefas
@@ -304,7 +287,6 @@ rbin-task-flow/
 ├── .gitignore                    # Template gitignore
 ├── .model-versions.json          # Referência de versão do modelo (atualize quando novos modelos forem lançados)
 ├── CLAUDE.md                     # Instruções principais do Claude
-├── GEMINI.md                     # Instruções principais do Gemini
 ├── install.sh                    # Script de instalação
 └── README.md                     # Este arquivo
 ```
@@ -315,11 +297,11 @@ rbin-task-flow/
 - ✅ Use RBIN Task Flow em **projetos que recebem** as configurações via instalação
 - 🔄 O instalador **sempre sobrescreve** configurações existentes
 - 🤫 As entradas do .gitignore são **discretas** (sem menções a IA)
-- 🎯 Funciona com **Claude Code CLI**, **API Gemini** ou **Cursor Pro**
+- 🎯 Funciona com **Claude Code CLI** ou **Cursor Pro**
 - 📦 O diretório Task Flow (`.task-flow/`) é **automaticamente gitignored**
 - 📝 Defina tarefas em `.task-flow/tasks.input.txt` usando formato simples: `- Descrição da tarefa`
 - 🚀 **Instalação Global NPM**: `npm install -g rbin-task-flow`, depois use `rbin-task-flow init` em qualquer projeto
-- 🔒 **Chaves de API podem ser necessárias** - depende do seu provedor de IA (Claude Code, API Gemini ou Cursor Pro)
+- 🔒 **Chaves de API podem ser necessárias** - depende do seu provedor de IA (Claude Code ou Cursor Pro)
 - 🔔 **Verificação de versão do modelo** - Use `rbin-task-flow version-check` para verificar versões mais recentes dos modelos (verificação rápida e local)
 
 ## Atualizando Versões dos Modelos
@@ -337,16 +319,11 @@ Quando novas versões de modelos forem lançadas, atualize `.model-versions.json
     "current": "claude-sonnet-4-5-20250929",
     "latest": "NOVA_VERSÃO_AQUI",
     "checkUrl": "https://docs.cursor.com/models"
-  },
-  "gemini": {
-    "current": "gemini-3-flash",
-    "latest": "NOVA_VERSÃO_AQUI",
-    "checkUrl": "https://ai.google.dev/models/gemini"
   }
 }
 ```
 
-O instalador verificará automaticamente versões mais recentes dos modelos e **perguntará individualmente** se você deseja atualizar cada um (Claude, Cursor, Gemini). Esta verificação é **rápida e local** - sem chamadas de API, sem solicitações de rede, apenas uma simples comparação de strings.
+O instalador verificará automaticamente versões mais recentes dos modelos e **perguntará individualmente** se você deseja atualizar cada um (Claude, Cursor). Esta verificação é **rápida e local** - sem chamadas de API, sem solicitações de rede, apenas uma simples comparação de strings.
 
 **Atualizações Interativas:** Quando uma versão mais recente estiver disponível, o instalador irá:
 - Mostrar versões atuais e mais recentes
@@ -401,13 +378,13 @@ Para problemas ou perguntas:
 
 ## What Is This Project?
 
-RBIN Task Flow is an AI-powered task management system that automatically configures Claude Code, Gemini, and Cursor IDE in any project. You define tasks in plain text and the AI automatically generates detailed, actionable subtasks.
+RBIN Task Flow is an AI-powered task management system that automatically configures Claude Code and Cursor IDE in any project. You define tasks in plain text and the AI automatically generates detailed, actionable subtasks.
 
 **Key benefits:**
 - ✅ Global NPM installation - install once, use in any project
 - ✅ Zero configuration - ready to use immediately
 - ✅ Simple management - write tasks in text, AI does the rest
-- ✅ Multiple AI models - Claude, Gemini, and Cursor configured
+- ✅ Multiple AI models - Claude and Cursor configured
 
 ## Installation
 
@@ -445,7 +422,7 @@ rbin-task-flow report <ids>   # Generate report (e.g., "1" or "1,2" or "all")
 
 ### AI Commands - Why Use Them?
 
-After initializing, use these commands in your AI (Cursor/Claude/Gemini) to automatically manage tasks:
+After initializing, use these commands in your AI (Cursor/Claude) to automatically manage tasks:
 
 | Command | Why Use It | Key Feature |
 |---------|------------|-------------|
@@ -481,13 +458,13 @@ cd my-project && rbin-task-flow init
 
 ## Overview
 
-A centralized repository of development configurations and rules that can be instantly installed in any project. Provides complete setup for Claude Code, Gemini, Cursor IDE, and RBIN Task Flow - a simple AI-powered task management system.
+A centralized repository of development configurations and rules that can be instantly installed in any project. Provides complete setup for Claude Code, Cursor IDE, and RBIN Task Flow - a simple AI-powered task management system.
 
 ### Key Features
 
 - **NPM Global Installation** - Install once, use everywhere with `npm install -g rbin-task-flow`
 - **Simple Task Management** - Define tasks in plain text, AI generates detailed subtasks
-- **Multiple AI Models** - Claude Code Sonnet and Gemini 3 Flash configured and ready to use
+- **Multiple AI Models** - Claude Code Sonnet configured and ready to use
 - **Discrete .gitignore** - AI configs hidden with generic comments
 - **Zero Configuration** - Ready to use immediately
 - **RBIN Task Flow** - AI-powered task management with simple text interface
@@ -496,7 +473,7 @@ A centralized repository of development configurations and rules that can be ins
 
 - **Operating System:** macOS, Linux, or Windows (WSL)
 - **Tools:** Git, Bash, Node.js
-- **Required:** Claude Code CLI, Gemini API access, or Cursor IDE (with Pro subscription)
+- **Required:** Claude Code CLI or Cursor IDE (with Pro subscription)
 
 ### Alternative: Legacy Installation (Without NPM)
 
@@ -530,9 +507,6 @@ your-project/
 ├── .claude/
 │   └── settings.json             # Claude Code settings
 │
-├── .gemini/
-│   └── settings.json             # Gemini settings
-│
 ├── .task-flow/                   # RBIN Task Flow
 │   ├── tasks.input.txt           # Plain text task definitions (edit this!)
 │   ├── tasks.status.md           # ⚠️ Task status (auto-updated, DO NOT EDIT)
@@ -547,7 +521,6 @@ your-project/
 
 No additional configuration required! Just make sure you have:
 - Claude Code CLI installed, OR
-- Gemini API access configured, OR
 - Cursor IDE with an active Pro subscription
 
 **You're ready!**
@@ -572,13 +545,6 @@ Claude Code is pre-configured with:
 - RBIN Task Flow integration
 - Development best practices
 
-### Gemini Integration
-
-Gemini is pre-configured with:
-- Custom settings
-- RBIN Task Flow integration
-- Development best practices
-
 ## What's Configured
 
 ### Development Rules
@@ -606,11 +572,9 @@ The installer adds these entries to `.gitignore`:
 
 ```gitignore
 .claude/
-.gemini/
 .cursor/
 .task-flow/
 CLAUDE.md
-GEMINI.md
 ```
 
 **Why discrete?**
@@ -655,9 +619,6 @@ rbin-task-flow/
 ├── .claude/
 │   └── settings.json             # Claude Code settings
 │
-├── .gemini/
-│   └── settings.json             # Gemini settings
-│
 ├── .task-flow/
 │   ├── README.md                 # Quick commands reference
 │   ├── tasks.input.txt           # Task definitions template
@@ -669,7 +630,6 @@ rbin-task-flow/
 ├── .gitignore                    # Template gitignore
 ├── .model-versions.json          # Model version reference (update when new models are released)
 ├── CLAUDE.md                     # Main Claude instructions
-├── GEMINI.md                     # Main Gemini instructions
 ├── install.sh                    # Installation script
 └── README.md                     # This file
 ```
@@ -680,11 +640,11 @@ rbin-task-flow/
 - ✅ Use RBIN Task Flow in **projects that receive** the configs via installation
 - 🔄 Installer **always overwrites** existing configs
 - 🤫 .gitignore entries are **discrete** (no AI mentions)
-- 🎯 Works with **Claude Code CLI**, **Gemini API**, or **Cursor Pro**
+- 🎯 Works with **Claude Code CLI** or **Cursor Pro**
 - 📦 Task Flow directory (`.task-flow/`) is **automatically gitignored**
 - 📝 Define tasks in `.task-flow/tasks.input.txt` using simple format: `- Task description`
 - 🚀 **NPM Global Install**: `npm install -g rbin-task-flow`, then use `rbin-task-flow init` in any project
-- 🔒 **API keys may be required** - depends on your AI provider (Claude Code, Gemini API, or Cursor Pro)
+- 🔒 **API keys may be required** - depends on your AI provider (Claude Code or Cursor Pro)
 - 🔔 **Model version checking** - Use `rbin-task-flow version-check` to check for newer model versions (fast, local check)
 
 ## Updating Model Versions
@@ -702,16 +662,11 @@ When new model versions are released, update `.model-versions.json` in this repo
     "current": "claude-sonnet-4-5-20250929",
     "latest": "NEW_VERSION_HERE",
     "checkUrl": "https://docs.cursor.com/models"
-  },
-  "gemini": {
-    "current": "gemini-3-flash",
-    "latest": "NEW_VERSION_HERE",
-    "checkUrl": "https://ai.google.dev/models/gemini"
   }
 }
 ```
 
-The installer will automatically check for newer model versions and **ask you individually** if you want to update each one (Claude, Cursor, Gemini). This check is **fast and local** - no API calls, no network requests, just a simple string comparison.
+The installer will automatically check for newer model versions and **ask you individually** if you want to update each one (Claude, Cursor). This check is **fast and local** - no API calls, no network requests, just a simple string comparison.
 
 **Interactive Updates:** When a newer version is available, the installer will:
 - Show current and latest versions

package/bin/cli.js

@@ -10,7 +10,7 @@ const chalk = require('chalk');
 
 program
   .name('rbin-task-flow')
-  .description('AI-powered task management for Claude, Cursor, and Gemini')
+  .description('AI-powered task management for Claude and Cursor')
   .version(require('../package.json').version);
 
 program
@@ -65,7 +65,7 @@ program
     console.log('\n' + chalk.cyan('╔════════════════════════════════════════════════════════════════╗'));
     console.log(chalk.cyan('║') + '        ' + chalk.magenta('✨ RBIN Task Flow ✨') + '                           ' + chalk.cyan('║'));
     console.log(chalk.cyan('╚════════════════════════════════════════════════════════════════╝') + '\n');
-    console.log(chalk.blue('AI-powered task management for Claude, Cursor, and Gemini'));
+    console.log(chalk.blue('AI-powered task management for Claude and Cursor'));
     console.log(chalk.yellow('\nVersion:'), require('../package.json').version);
     console.log(chalk.yellow('Repository:'), 'https://github.com/rbinoliveira/rbin-task-flow');
     console.log(chalk.yellow('\nCommands:'));

package/lib/install.js

@@ -39,7 +39,6 @@ async function installInProject(targetPath, options = {}) {
     const dirs = [
       '.cursor/rules',
       '.claude',
-      '.gemini',
       '.task-flow'
     ];
 
@@ -111,26 +110,6 @@ async function copyConfigs(targetPath) {
     showSuccess('Claude instructions');
   }
 
-  const geminiSettingsPath = path.join(TEMPLATE_DIR, '.gemini/settings.json');
-  if (fs.existsSync(geminiSettingsPath)) {
-    await fs.copy(
-      geminiSettingsPath,
-      path.join(targetPath, '.gemini/settings.json'),
-      { overwrite: true }
-    );
-    showSuccess('Gemini settings');
-  }
-
-  const geminiInstructionsPath = path.join(TEMPLATE_DIR, 'GEMINI.md');
-  if (fs.existsSync(geminiInstructionsPath)) {
-    await fs.copy(
-      geminiInstructionsPath,
-      path.join(targetPath, 'GEMINI.md'),
-      { overwrite: true }
-    );
-    showSuccess('Gemini instructions');
-  }
-
   await copyTaskFlow(targetPath);
 }
 
@@ -143,16 +122,16 @@ async function copyTaskFlow(targetPath) {
   showSuccess('Task Flow directory');
   showInfo('Note: .internal/tasks.json and .internal/status.json are NOT overwritten (your data is safe)');
 
-  const screensDest = path.join(taskFlowDest, 'screens');
-  await fs.ensureDir(screensDest);
-  showSuccess('Screenshots directory (.task-flow/screens/)');
+  const contextsDest = path.join(taskFlowDest, 'contexts');
+  await fs.ensureDir(contextsDest);
+  showSuccess('Contexts directory (.task-flow/contexts/)');
 
   const docsDest = path.join(taskFlowDest, 'docs');
   await fs.ensureDir(docsDest);
   showSuccess('Documentation directory (.task-flow/docs/)');
 
-  const exampleSrc = path.join(taskFlowSrc, 'screens/example.png.txt');
-  const exampleDest = path.join(screensDest, 'example.png.txt');
+  const exampleSrc = path.join(taskFlowSrc, 'contexts/example.png.txt');
+  const exampleDest = path.join(contextsDest, 'example.png.txt');
   if (fs.existsSync(exampleSrc) && !fs.existsSync(exampleDest)) {
     await fs.copy(exampleSrc, exampleDest);
   }
@@ -186,11 +165,9 @@ async function updateGitignore(targetPath) {
 
   const entries = [
     '.claude/',
-    '.gemini/',
     '.cursor/',
     '.task-flow/',
-    'CLAUDE.md',
-    'GEMINI.md'
+    'CLAUDE.md'
   ];
 
   for (const entry of entries) {
@@ -246,24 +223,6 @@ async function showModelVersions(targetPath) {
     }
   }
 
-  const geminiSettingsPath = path.join(targetPath, '.gemini/settings.json');
-  if (fs.existsSync(geminiSettingsPath)) {
-    try {
-      const settings = await fs.readJSON(geminiSettingsPath);
-      if (settings.model) {
-        const modelName = typeof settings.model === 'string' 
-          ? settings.model 
-          : settings.model.name || 'Default (recommended)';
-        console.log(chalk.blue('Gemini:'), chalk.yellow(modelName));
-        hasModels = true;
-      } else {
-        console.log(chalk.blue('Gemini:'), chalk.yellow('Default (recommended)'));
-        hasModels = true;
-      }
-    } catch (error) {
-    }
-  }
-
   if (!hasModels) {
     console.log(chalk.yellow('No model versions configured yet'));
   }

package/lib/version.js

@@ -43,10 +43,6 @@ async function checkVersionUpdates() {
       await checkModelVersion('Cursor', versions.cursor, '.cursor/settings.json', rl);
     }
 
-    if (versions.gemini) {
-      await checkModelVersion('Gemini', versions.gemini, '.gemini/settings.json', rl);
-    }
-
     rl.close();
 
     console.log(chalk.green('\n✅ Version check completed!\n'));

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "rbin-task-flow",
-  "version": "1.3.0",
-  "description": "AI-powered task management for Claude, Cursor, and Gemini",
+  "version": "1.4.0",
+  "description": "AI-powered task management for Claude and Cursor",
   "main": "index.js",
   "bin": {
-    "rbin-task-flow": "./bin/cli.js",
-    "task-flow": "./bin/cli.js"
+    "rbin-task-flow": "bin/cli.js",
+    "task-flow": "bin/cli.js"
   },
   "scripts": {
     "test": "echo \"No tests yet\"",
@@ -16,7 +16,6 @@
     "ai",
     "claude",
     "cursor",
-    "gemini",
     "cli",
     "task-management",
     "ai-powered"
@@ -25,17 +24,15 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/rbinoliveira/rbin-task-flow.git"
+    "url": "git+https://github.com/rbinoliveira/rbin-task-flow.git"
   },
   "files": [
     "bin/",
     ".cursor/",
     ".claude/",
-    ".gemini/",
     ".task-flow/",
     ".model-versions.json",
     "CLAUDE.md",
-    "GEMINI.md",
     "lib/"
   ],
   "preferGlobal": true,

package/.gemini/settings.json

@@ -1,5 +0,0 @@
-{
-  "model": {
-    "name": "gemini-3-flash"
-  }
-}

package/.task-flow/screens/example.png.txt

@@ -1,23 +0,0 @@
-# Example Screenshot
-
-This is a placeholder file. Replace this file with a real screenshot (PNG or JPG).
-
-## How to add screenshots:
-
-1. Add your image files (.png or .jpg) to this folder
-2. Use descriptive names in kebab-case
-3. RBIN Task Flow will automatically detect and reference the screenshots
-
-## Example names:
-
-- `login_recover_signup.png`
-- `dashboard.png`
-- `patient.png`
-- `patient_profile.png`
-- `prescriptions.png`
-- `medicine.png`
-
-## Reference in tasks:
-
-To reference a specific screenshot in a task, use:
-`task-flow-screen filename.png`

package/GEMINI.md

@@ -1,38 +0,0 @@
-# Gemini Instructions
-
-## Development Rules
-
-All development rules are automatically loaded from `.cursor/rules/` directory. These rules include:
-- Cursor rules formatting guidelines
-- Self-improvement processes
-- Code commenting standards
-- Commit practices
-- Git command control
-- Task execution management with RBIN Task Flow
-
-## RBIN Task Flow
-
-This project uses RBIN Task Flow for task management:
-- **Task Definition**: Edit `.task-flow/tasks.input.txt` using simple format: `- Task description`
-- **AI Commands**: Use AI-powered commands for task management:
-  - `task-flow: sync` - Synchronize tasks from tasks.input.txt
-  - `task-flow: think` - Analyze code and suggest new tasks
-  - `task-flow: status` - View current task status
-  - `task-flow: run next X` - Work on next X subtasks
-  - `task-flow: run X` - Execute all pending subtasks of task X (simplified - no "task" needed)
-  - `task-flow: run X,Y` - Execute multiple tasks (comma-separated)
-  - `task-flow: run all` - Execute all tasks
-  - `task-flow: review X` - Review specific task(s) (comma-separated or "all")
-  - `task-flow: refactor X` - Refactor specific task(s) (comma-separated or "all")
-  - `task-flow: estimate X` - Estimate time for task X (simplified - no "task" needed)
-  - `task-flow: estimate X,Y` - Estimate multiple tasks (comma-separated)
-  - `task-flow: estimate all` - Estimate all tasks
-  - `task-flow: report X` - Generate implementation report for task X (simplified - no "task" needed)
-  - `task-flow: report X,Y` - Generate reports for multiple tasks (comma-separated)
-  - `task-flow: report all` - Generate reports for all tasks
-- **Files**:
-  - `.task-flow/tasks.input.txt` - Define your tasks here
-  - `.task-flow/tasks.status.md` - Auto-generated status (DO NOT EDIT manually)
-  - `.task-flow/.internal/` - Internal system files (ignore)
-
-Follow all rules defined in `.cursor/rules/` for consistent development practices.