rbin-task-flow 1.0.1 → 1.1.2

package/.cursor/rules/task_generation.mdc

@@ -6,22 +6,36 @@ alwaysApply: true
 
 - **Task Generation - Direct and Efficient:**
   - When user asks to "Read tasks.input.txt and generate detailed subtasks updating task status":
-    - **READ ONLY**: `.task-flow/tasks.input.txt`
+    - **READ**: `.task-flow/tasks.input.txt` (only process lines starting with `- `)
+    - **READ**: `.task-flow/screens/` directory to list available screenshots (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**: Read other files, check existing JSONs, explore codebase, or ask questions
+    - **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: "Referência visual: `.task-flow/screens/nome_do_arquivo.png`"
 
 - **Required Actions:**
-  1. Read `tasks.input.txt` (ignore comments, only process lines starting with `- `)
-  2. For each task line, create a task with sequential ID starting at 1
-  3. Generate 3-8 subtasks per task with:
+  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)
+  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)
-  4. Create `.task-flow/.internal/tasks.json` with structure below
-  5. Create `.task-flow/.internal/status.json` with all tasks/subtasks as "pending"
-  6. Create `.task-flow/tasks.status.md` with all tasks and subtasks marked as `- [ ]` (pending)
-  7. Write all three files immediately
+     - **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/`
+  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)
+  8. Write all three files immediately
 
 - **tasks.json Structure:**
   ```json
@@ -103,12 +117,26 @@ alwaysApply: true
 
 - **Example:**
   - Input (`tasks.input.txt`): `- Create authentication system`
-  - Output: Task with ID 1, 5 subtasks (setup database, create models, implement login, add JWT, test)
+  - 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: "Referência visual: `.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
+  
+- **Screenshot Reference Examples:**
+  - Task: `- Sistema de autenticação do dentista` → Automatically matches and references `login_recover_signup.png` from `.task-flow/screens/`
+  - Task: `- Dashboard básico com estrutura task-flow-screen dashboard.png` → References specific `.task-flow/screens/dashboard.png`
+  - Task: `- CRUD completo de pacientes` → 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
 
 - **Critical Rules:**
   - ✅ Be direct: Read → Generate → Save
-  - ✅ No unnecessary file reads
-  - ✅ No exploration of codebase
+  - ✅ **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
   - ✅ No questions - just generate
   - ✅ Use current timestamp for `createdAt`
   - ✅ All statuses start as "pending"

package/.cursor/rules/task_work.mdc

@@ -56,6 +56,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
      - Implement following step-by-step instructions
      - Test/verify implementation
      - Update `status.json` to mark as "done"
@@ -83,6 +85,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
      - Implement following step-by-step instructions
      - Test/verify implementation
      - Update `status.json` to mark as "done"
@@ -196,8 +200,15 @@ 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
+
 - **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 [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/.task-flow/screens/example.png.txt

@@ -0,0 +1,24 @@
+# Screenshot de Exemplo
+
+Este é um arquivo placeholder. Substitua este arquivo por um screenshot real (PNG ou JPG).
+
+## Como adicionar screenshots:
+
+1. Adicione seus arquivos de imagem (.png ou .jpg) nesta pasta
+2. Use nomes descritivos em kebab-case
+3. O RBIN Task Flow automaticamente detectará e referenciará os screenshots
+
+## Exemplos de nomes:
+
+- `login_recover_signup.png`
+- `dashboard.png`
+- `patient.png`
+- `patient_profile.png`
+- `prescriptions.png`
+- `medicine.png`
+
+## Referenciar em tasks:
+
+Para referenciar um screenshot específico em uma task, use:
+`task-flow-screen nome_do_arquivo.png`
+

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

@@ -7,8 +7,14 @@
 3. Use `task-flow: sync` to generate subtasks from your tasks
 4. Use `task-flow: status` to view task progress
 
+## Screenshots:
+
+- Adicione seus screenshots na pasta `.task-flow/screens/` (PNG ou JPG)
+- O RBIN Task Flow automaticamente detecta e referencia os screenshots disponíveis ao gerar subtasks
+- Para referenciar um screenshot específico em uma task, use: `task-flow-screen nome_do_arquivo.png`
+- Exemplo: `- Criar tela de login task-flow-screen login.png`
+
 ## Tasks:
 
 - First task
 - Second task
-

package/lib/install.js

@@ -157,6 +157,18 @@ async function copyTaskFlow(targetPath) {
   showSuccess('Task Flow directory');
   showInfo('Note: .internal/tasks.json and .internal/status.json are NOT overwritten (your data is safe)');
 
+  // Criar pasta screens
+  const screensDest = path.join(taskFlowDest, 'screens');
+  await fs.ensureDir(screensDest);
+  showSuccess('Screenshots directory (.task-flow/screens/)');
+
+  // Copiar arquivo de exemplo para screens se não existir
+  const exampleSrc = path.join(taskFlowSrc, 'screens/example.png.txt');
+  const exampleDest = path.join(screensDest, 'example.png.txt');
+  if (fs.existsSync(exampleSrc) && !fs.existsSync(exampleDest)) {
+    await fs.copy(exampleSrc, exampleDest);
+  }
+
   // Copiar apenas templates, não sobrescrever dados do usuário
   const files = [
     { name: 'README.md', overwrite: true },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rbin-task-flow",
-  "version": "1.0.1",
+  "version": "1.1.2",
   "description": "AI-powered task management for Claude, Cursor, and Gemini",
   "main": "index.js",
   "bin": {

package/.claude/settings.local.json

@@ -1,8 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(chmod:*)",
-      "Bash(npm install)"
-    ]
-  }
-}