codeloop 0.1.1 → 0.1.3

package/dist/templates/claude-agents.d.ts

@@ -1,5 +1,5 @@
 export declare const CODELOOP_LOOP_MD = "You are a QA loop runner. Use CodeLoop MCP tools to verify code quality.\n\nProcess:\n1. Call codeloop_verify to run all checks\n2. Call codeloop_diagnose to classify failures\n3. Fix only confirmed issues\n4. Repeat verification\n5. Call codeloop_gate_check to evaluate completion\n6. Stop when all gates pass or escalation is needed\n\nNever mark a task complete without evidence from CodeLoop.\n\nWhen codeloop_gate_check returns \"ready_for_review\" with confidence >= 85%:\n- Generate or update the project README.md with: project description, features,\n  setup instructions, how to run, how to test, architecture overview, deployment\n  instructions, and a CodeLoop verification summary including confidence score,\n  gates passed, and test results.\n- Include a \"Verified by CodeLoop\" section in the README.\n";
 export declare const CODELOOP_QA_MD = "You are a QA verification specialist. Run CodeLoop visual review\nand design comparison. Report structured issues with severity,\nevidence, and fix hints.\n";
 export declare const CODELOOP_ADVISOR_MD = "You are an infrastructure and tooling advisor. Use CodeLoop\nrecommendation tools to suggest the best tools based on the\nproject stack, budget, and constraints. Always explain your\nreasoning and include tradeoffs.\n";
-export declare const CLAUDE_MD = "# CodeLoop Integration\n\nCodeLoop provides automated verification for AI-generated code via MCP tools. Follow these rules to ensure code quality.\n\n## After implementing or modifying any feature:\n1. Call codeloop_verify to run all checks on the current project\n2. Read the structured output carefully \u2014 trust deterministic results first, visual diffs second, model opinions third\n3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks\n4. Fix ONLY the confirmed issues listed in the repair tasks \u2014 do not guess or fix unrelated code\n5. After fixing, call codeloop_verify again to confirm the fixes worked\n6. Repeat until all failures are resolved or a blocker is identified\n\n## Before marking any task or feature as complete:\n1. Call codeloop_gate_check with the run_id, spec path, and acceptance path\n2. If the result says \"continue_fixing\", keep fixing and re-verifying\n3. If the result says \"escalate\", stop and report the blockers to the developer\n4. Only declare the task complete when gate_check returns \"ready_for_review\" with confidence >= 85%\n\n## When you have attempted to fix an issue 2 or more times and tests still fail:\n- You MUST call codeloop_diagnose before making another fix attempt\n- Read the repair tasks carefully \u2014 the structured analysis is more reliable than guessing from raw output\n\n## For multi-section projects:\n- Call codeloop_section_status to see current progress and which section to work on next\n- If integration_due is true, run codeloop_verify with scope \"full\" first and fix any regressions\n- After ALL sections pass, run codeloop_release_readiness for a final quality assessment\n\n## When choosing tools or infrastructure:\n- Call codeloop_recommend_tool with the relevant category and detected stack\n- Present results with reasoning, tradeoffs, and pricing\n- Always prefer CLI-based setup over web dashboard (e.g., `vercel login`, `heroku login`, `firebase login`)\n- Guide the user through CLI installation and authentication when needed\n- Verify CLI auth with a status command after login (e.g., `vercel whoami`, `heroku auth:whoami`)\n\n## After codeloop_gate_check returns \"ready_for_review\" with confidence >= 85%:\n- Generate or update the project README.md with:\n  - Project description and key features\n  - Prerequisites and setup instructions\n  - How to run locally\n  - How to run tests\n  - Architecture overview (key directories and files)\n  - CodeLoop verification: \"Verified by CodeLoop (run_id: {id}). Confidence: {score}%. Gates passed: {list}. Tests: {passed}/{total} passed.\"\n  - Deployment instructions (if applicable)\n  - Known issues (if any remain from codeloop_diagnose)\n\n## Terminal authorization:\n- Common development commands (flutter, npm, git, brew, etc.) are pre-authorized\n- If a command is blocked, check the allow-list in .claude/settings.local.json\n- For service provider CLIs: install via the recommended package manager, then authenticate\n\n## Never:\n- Mark a task complete without evidence from codeloop_gate_check\n- Ignore codeloop_verify results\n- Modify files outside the allowed_file_scope from repair tasks\n- Continue fixing after 8 failed repair attempts \u2014 escalate instead\n";
+export declare const CLAUDE_MD = "# CodeLoop Integration\n\nCodeLoop provides automated verification for AI-generated code via MCP tools. Follow these rules to ensure code quality.\n\n## After implementing or modifying any feature:\n1. Call codeloop_verify to run all checks on the current project\n2. Read the structured output carefully \u2014 trust deterministic results first, visual diffs second, model opinions third\n3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks\n4. Fix ONLY the confirmed issues listed in the repair tasks \u2014 do not guess or fix unrelated code\n5. After fixing, call codeloop_verify again to confirm the fixes worked\n6. Repeat until all failures are resolved or a blocker is identified\n\n## Before marking any task or feature as complete:\n1. Call codeloop_gate_check with the run_id, spec path, and acceptance path\n2. If the result says \"continue_fixing\", keep fixing and re-verifying\n3. If the result says \"escalate\", stop and report the blockers to the developer\n4. Only declare the task complete when gate_check returns \"ready_for_review\" with confidence >= 85%\n\n## When you have attempted to fix an issue 2 or more times and tests still fail:\n- You MUST call codeloop_diagnose before making another fix attempt\n- Read the repair tasks carefully \u2014 the structured analysis is more reliable than guessing from raw output\n\n## For multi-section projects:\n- Call codeloop_section_status to see current progress and which section to work on next\n- If integration_due is true, run codeloop_verify with scope \"full\" first and fix any regressions\n- After ALL sections pass, run codeloop_release_readiness for a final quality assessment\n\n## When choosing tools or infrastructure:\n- Call codeloop_recommend_tool with the relevant category and detected stack\n- Present results with reasoning, tradeoffs, and pricing\n- Always prefer CLI-based setup over web dashboard (e.g., `vercel login`, `heroku login`, `firebase login`)\n- Guide the user through CLI installation and authentication when needed\n- Verify CLI auth with a status command after login (e.g., `vercel whoami`, `heroku auth:whoami`)\n\n## After codeloop_gate_check returns \"ready_for_review\" with confidence >= 85%:\n- Generate or update the project README.md with:\n  - Project description and key features\n  - Prerequisites and setup instructions\n  - How to run locally\n  - How to run tests\n  - Architecture overview (key directories and files)\n  - CodeLoop verification: \"Verified by CodeLoop (run_id: {id}). Confidence: {score}%. Gates passed: {list}. Tests: {passed}/{total} passed.\"\n  - Deployment instructions (if applicable)\n  - Known issues (if any remain from codeloop_diagnose)\n\n## Multi-page visual review:\nApps have multiple pages \u2014 a single screenshot is never sufficient.\n1. Call codeloop_discover_screens to find all routes/pages from source code\n2. Build and run the app\n3. For EACH page: navigate to it, call codeloop_capture_screenshot(screen_name: \"<name>\")\n4. Explore navigation elements (buttons, tabs, menus, links) to discover sub-pages\n5. Capture modals, dialogs, error states, and empty states\n6. After all pages captured, call codeloop_visual_review to analyze everything\n7. Cross-reference against discover_screens results for coverage\n\n## Terminal authorization:\n- Common development commands (flutter, npm, git, brew, etc.) are pre-authorized\n- If a command is blocked, check the allow-list in .claude/settings.local.json\n- For service provider CLIs: install via the recommended package manager, then authenticate\n\n## Never:\n- Mark a task complete without evidence from codeloop_gate_check\n- Ignore codeloop_verify results\n- Modify files outside the allowed_file_scope from repair tasks\n- Continue fixing after 8 failed repair attempts \u2014 escalate instead\n";
 //# sourceMappingURL=claude-agents.d.ts.map

package/dist/templates/claude-agents.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"claude-agents.d.ts","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,wzBAkB5B,CAAC;AAEF,eAAO,MAAM,cAAc,iKAG1B,CAAC;AAEF,eAAO,MAAM,mBAAmB,8NAI/B,CAAC;AAEF,eAAO,MAAM,SAAS,uuGAuDrB,CAAC"}
+{"version":3,"file":"claude-agents.d.ts","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,wzBAkB5B,CAAC;AAEF,eAAO,MAAM,cAAc,iKAG1B,CAAC;AAEF,eAAO,MAAM,mBAAmB,8NAI/B,CAAC;AAEF,eAAO,MAAM,SAAS,uzHAiErB,CAAC"}

package/dist/templates/claude-agents.js

@@ -71,6 +71,16 @@ CodeLoop provides automated verification for AI-generated code via MCP tools. Fo
   - Deployment instructions (if applicable)
   - Known issues (if any remain from codeloop_diagnose)
 
+## Multi-page visual review:
+Apps have multiple pages — a single screenshot is never sufficient.
+1. Call codeloop_discover_screens to find all routes/pages from source code
+2. Build and run the app
+3. For EACH page: navigate to it, call codeloop_capture_screenshot(screen_name: "<name>")
+4. Explore navigation elements (buttons, tabs, menus, links) to discover sub-pages
+5. Capture modals, dialogs, error states, and empty states
+6. After all pages captured, call codeloop_visual_review to analyze everything
+7. Cross-reference against discover_screens results for coverage
+
 ## Terminal authorization:
 - Common development commands (flutter, npm, git, brew, etc.) are pre-authorized
 - If a command is blocked, check the allow-list in .claude/settings.local.json

package/dist/templates/claude-agents.js.map

@@ -1 +1 @@
-{"version":3,"file":"claude-agents.js","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkB/B,CAAC;AAEF,MAAM,CAAC,MAAM,cAAc,GAAG;;;CAG7B,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;CAIlC,CAAC;AAEF,MAAM,CAAC,MAAM,SAAS,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuDxB,CAAC"}
+{"version":3,"file":"claude-agents.js","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkB/B,CAAC;AAEF,MAAM,CAAC,MAAM,cAAc,GAAG;;;CAG7B,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;CAIlC,CAAC;AAEF,MAAM,CAAC,MAAM,SAAS,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiExB,CAAC"}

package/dist/templates/cursor-rules.d.ts

@@ -1,6 +1,6 @@
 export declare const CORE_MDC = "---\ndescription: CodeLoop core verification rules for all projects\nglobs: [\"**/*\"]\n---\n\n# CodeLoop Verification Rules\n\n## After implementing or modifying any feature:\n1. Call codeloop_verify to run all checks on the current project\n2. Read the structured output carefully \u2014 trust deterministic results first, visual diffs second, model opinions third\n3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks\n4. Fix ONLY the confirmed issues listed in the repair tasks \u2014 do not guess or fix unrelated code\n5. After fixing, call codeloop_verify again to confirm the fixes worked\n6. Repeat until all failures are resolved or a blocker is identified\n\n## Before marking any task or feature as complete:\n1. Call codeloop_gate_check with the run_id, spec path, and acceptance path\n2. If the result says \"continue_fixing\", keep fixing and re-verifying\n3. If the result says \"escalate\", stop and report the blockers to the developer\n4. Only declare the task complete when gate_check returns \"ready_for_review\" with confidence >= 85%\n\n## When you have attempted to fix an issue 2 or more times and tests still fail:\n- You MUST call codeloop_diagnose before making another fix attempt\n- Read the repair tasks carefully \u2014 the structured analysis is more reliable than guessing from raw output\n\n## Never:\n- Mark a task complete without evidence from codeloop_gate_check\n- Ignore codeloop_verify results\n- Modify files outside the allowed_file_scope from repair tasks\n- Continue fixing after 8 failed repair attempts \u2014 escalate instead\n";
 export declare const LOOP_MDC = "---\ndescription: CodeLoop multi-section development loop\nglobs: [\"docs/specs/_master.md\"]\n---\n\n# Multi-Section Development Loop\n\nWhen a master spec exists at docs/specs/_master.md:\n\n1. Call codeloop_section_status to see current progress and which section to work on next\n2. If integration_due is true, run codeloop_verify with scope \"full\" first and fix any regressions\n3. Read the spec file for the current section (the path is in the section_status response)\n4. Read the acceptance criteria file for the current section\n5. Implement the section according to the spec\n6. Run codeloop_verify \u2192 codeloop_diagnose \u2192 fix \u2192 repeat until codeloop_gate_check passes with confidence >= 85%\n7. Call codeloop_section_status again to get the next section\n8. If more sections remain, proceed to the next section IMMEDIATELY\n9. Do NOT stop between sections for human review\n10. After ALL sections pass individually:\n    - Run codeloop_verify with scope \"full\" (entire app)\n    - Run codeloop_release_readiness\n11. Only THEN report to the developer with the full evidence summary and confidence scores\n\n## After codeloop_gate_check returns \"ready_for_review\" with confidence >= 85%:\n\nGenerate or update the project README.md with:\n1. Project description and key features\n2. Prerequisites and setup instructions (install, configure, run)\n3. How to run the project locally\n4. How to run tests\n5. Architecture overview (key directories and files)\n6. CodeLoop verification summary:\n   \"Verified by CodeLoop (run_id: {id}). Confidence: {score}%.\n    Gates passed: {list}. Tests: {passed}/{total} passed.\"\n7. Deployment instructions (if applicable)\n8. Known issues (from codeloop_diagnose, if any remain)\n\nThe README should be professional, concise, and ready for public repositories.\nInclude a \"Verified by CodeLoop\" badge or section so users know the project\nhas been through automated quality verification.\n";
-export declare const RECOMMENDATIONS_MDC = "---\ndescription: CodeLoop recommendation triggers and CLI-first service setup\nglobs: [\"**/*\"]\n---\n\n# When to use CodeLoop recommendations\n\nWhen the developer or task involves choosing infrastructure, tools, or services:\n- If the task mentions hosting, deployment, server, email service, analytics, marketing, monitoring, auth provider, database, or file storage\n- Call codeloop_recommend_tool with the relevant category and detected stack\n- Present the results with reasoning, tradeoffs, and pricing \u2014 never just a name\n\nWhen a design reference image exists in artifacts/references/ but codeloop_design_compare has not been run:\n- Suggest running codeloop_design_compare to check visual fidelity\n\nWhen visual changes have been made but codeloop_visual_review has not been run:\n- Suggest running codeloop_visual_review to check for UI issues\n\n# CLI-First Service Provider Setup\n\nWhen configuring external services (hosting, email, databases, etc.):\n\n## Always prefer CLI over web dashboard:\n1. Install the service CLI: `npm install -g vercel`, `brew install heroku`, `npm install -g firebase-tools`, etc.\n2. Authenticate via CLI: `vercel login`, `heroku login`, `firebase login` \u2014 these open a browser for OAuth\n3. Verify authentication: `vercel whoami`, `heroku auth:whoami`, `firebase projects:list`\n4. Configure the project via CLI commands (create app, set env vars, deploy)\n\n## Common CLI auth patterns:\n- **Browser redirect:** CLI opens browser, user logs in, CLI receives token (Vercel, Firebase, Netlify)\n- **API key:** User provides key from dashboard (SendGrid, Stripe, Sentry)\n- **Interactive login:** Terminal prompts for email/password (Heroku, AWS)\n\n## When the user doesn't have the CLI installed:\n1. Check with `which <tool>`\n2. If missing, install via the appropriate package manager\n3. Guide through authentication\n4. Verify with a status/whoami command before proceeding\n";
+export declare const RECOMMENDATIONS_MDC = "---\ndescription: CodeLoop recommendation triggers and CLI-first service setup\nglobs: [\"**/*\"]\n---\n\n# When to use CodeLoop recommendations\n\nWhen the developer or task involves choosing infrastructure, tools, or services:\n- If the task mentions hosting, deployment, server, email service, analytics, marketing, monitoring, auth provider, database, or file storage\n- Call codeloop_recommend_tool with the relevant category and detected stack\n- Present the results with reasoning, tradeoffs, and pricing \u2014 never just a name\n\nWhen a design reference image exists in artifacts/references/ but codeloop_design_compare has not been run:\n- Suggest running codeloop_design_compare to check visual fidelity\n\nWhen visual changes have been made but codeloop_visual_review has not been run:\n- Suggest running codeloop_visual_review to check for UI issues\n\n# Multi-Page Visual Review\n\nApps have multiple pages. A single screenshot is NOT sufficient for visual review.\n\n## Before visual review, discover all pages:\n1. Call codeloop_discover_screens to scan source code for routes and navigation patterns\n2. This returns a list of all known screens with routes and source locations\n\n## Capture ALL pages systematically:\n1. Build and run the app\n2. Capture the initial/home screen: call codeloop_capture_screenshot(screen_name: \"home\")\n3. Look at the captured screenshot \u2014 identify all navigation elements:\n   - Buttons that navigate to other pages\n   - Tab bar items (bottom tabs, top tabs)\n   - Navigation drawer / hamburger menu items\n   - Bottom navigation bar items\n   - Links, cards, or list items that open new pages\n4. For EACH navigation element:\n   a. Interact with it to navigate to the new page\n   b. Call codeloop_capture_screenshot(screen_name: \"<descriptive_name>\")\n   c. On the new page, check for further navigation elements\n   d. Explore sub-pages recursively (up to 3 levels deep)\n   e. Navigate back and continue with other elements\n5. After ALL pages are captured, call codeloop_visual_review to analyze all screenshots\n6. Cross-reference captured screens against codeloop_discover_screens results\n   to identify any pages that were missed\n\n## Never:\n- Do a visual review with only one screenshot of a multi-page app\n- Skip pages that are reachable via buttons, tabs, or menu items\n- Forget to capture modal dialogs, bottom sheets, and error states\n\n# CLI-First Service Provider Setup\n\nWhen configuring external services (hosting, email, databases, etc.):\n\n## Always prefer CLI over web dashboard:\n1. Install the service CLI: `npm install -g vercel`, `brew install heroku`, `npm install -g firebase-tools`, etc.\n2. Authenticate via CLI: `vercel login`, `heroku login`, `firebase login` \u2014 these open a browser for OAuth\n3. Verify authentication: `vercel whoami`, `heroku auth:whoami`, `firebase projects:list`\n4. Configure the project via CLI commands (create app, set env vars, deploy)\n\n## Common CLI auth patterns:\n- **Browser redirect:** CLI opens browser, user logs in, CLI receives token (Vercel, Firebase, Netlify)\n- **API key:** User provides key from dashboard (SendGrid, Stripe, Sentry)\n- **Interactive login:** Terminal prompts for email/password (Heroku, AWS)\n\n## When the user doesn't have the CLI installed:\n1. Check with `which <tool>`\n2. If missing, install via the appropriate package manager\n3. Guide through authentication\n4. Verify with a status/whoami command before proceeding\n";
 export declare const PERMISSIONS_MDC = "---\ndescription: CodeLoop terminal authorization guidance\nglobs: [\"**/*\"]\n---\n\n# Terminal Authorization\n\nCodeLoop and the AI agent need to run development commands during the verification loop.\nThese commands should be allowed to proceed without manual approval:\n\n## Required commands:\n- **Build/Test:** flutter analyze, flutter test, flutter build, npm test, npm install, npx, dart format\n- **Version control:** git status, git diff, git add, git commit, git push\n- **Package managers:** brew install, pip install, pod install\n- **Media tools:** ffmpeg, ffprobe, screencapture\n- **System:** mkdir, cp, mv, ls, cat, which, curl, find, head, tail, echo, pwd\n\n## For Cursor users:\nTo avoid repeated \"Allow / Skip\" prompts, enable auto-run for these commands:\n1. Open Cursor Settings > Features > Terminal\n2. Enable \"Auto-run\" mode for the commands above\n3. Or add them to your command allow-list\n\n## For Claude Code users:\nThe .claude/settings.local.json file includes a permissions.allow list that\npre-authorizes common development commands. If you need to add more commands,\nedit the permissions.allow array in that file.\n\n## Security note:\nThese are standard development tools. No network services are exposed,\nno credentials are transmitted, and no destructive system operations are performed.\nIf you have specific security requirements, customize the allow-list as needed.\n";
 export declare const FLUTTER_MDC = "---\ndescription: CodeLoop Flutter-specific verification guidance\nglobs: [\"pubspec.yaml\", \"**/*.dart\", \"lib/**\", \"test/**\"]\n---\n\n# Flutter Verification Rules\n\nWhen the project contains a pubspec.yaml, apply these additional verification steps:\n\n## Before calling codeloop_verify:\n- Ensure `flutter pub get` has been run after any pubspec.yaml change\n- Platform parameter should be set to \"flutter\"\n\n## After codeloop_verify completes:\n- Check that `flutter analyze` reported zero issues (warnings and info are acceptable, errors are not)\n- Check that `flutter test` passed all widget and unit tests\n- If golden tests exist, verify no unexpected diffs in `test/goldens/`\n\n## When creating or modifying Dart files:\n- Run `dart format .` before verification to avoid style-only failures\n- Ensure all public APIs have documentation comments\n- Prefer `const` constructors for stateless widgets\n\n## Screenshot viewports for Flutter:\n- iOS: 375x812 (iPhone SE), 390x844 (iPhone 14), 428x926 (iPhone 14 Pro Max)\n- Android: 360x800 (compact), 412x915 (medium), 600x1024 (tablet)\n- Use codeloop_visual_review with these viewport sizes after UI changes\n\n## Common Flutter failure patterns:\n- \"No pubspec.yaml found\" \u2192 wrong working directory, navigate to the Flutter project root\n- \"flutter not found\" \u2192 Flutter SDK not in PATH, check the developer's environment\n- Widget overflow errors \u2192 check constraints and use Expanded/Flexible wrappers\n- State management issues \u2192 verify provider/bloc/riverpod setup in the widget tree\n";
 export declare const WEB_MDC = "---\ndescription: CodeLoop web-specific verification guidance\nglobs: [\"package.json\", \"**/*.ts\", \"**/*.tsx\", \"**/*.js\", \"**/*.jsx\", \"**/*.vue\", \"**/*.svelte\"]\n---\n\n# Web Verification Rules\n\nWhen the project is a web application (Next.js, React, Vue, Svelte, Angular), apply these additional verification steps:\n\n## Before calling codeloop_verify:\n- Ensure `npm install` or equivalent has been run after any package.json change\n- Platform parameter should be set to \"web\"\n\n## After codeloop_verify completes:\n- Check that the build succeeds without errors (`npm run build` or framework equivalent)\n- Check that all test suites pass (`npm test`, `vitest run`, `jest`, etc.)\n- Check for TypeScript errors if the project uses TypeScript\n\n## Responsive testing:\n- Mobile: 375x812 (iPhone SE portrait)\n- Tablet: 768x1024 (iPad portrait)\n- Desktop: 1440x900 (standard laptop)\n- Use codeloop_visual_review with these viewport sizes after UI changes\n\n## Accessibility checks:\n- Color contrast should meet WCAG AA (4.5:1 for normal text, 3:1 for large text)\n- Interactive elements need keyboard focus indicators\n- Images need alt text, form inputs need labels\n- Touch targets should be at least 44x44px on mobile\n\n## Common web failure patterns:\n- \"Module not found\" \u2192 missing dependency, run npm install\n- Hydration mismatch (Next.js/React SSR) \u2192 server/client rendering inconsistency\n- \"Cannot find module\" in tests \u2192 check jest/vitest config moduleNameMapper\n- Port already in use \u2192 kill the existing dev server process\n";

package/dist/templates/cursor-rules.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cursor-rules.d.ts","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,QAAQ,mnDA8BpB,CAAC;AAEF,eAAO,MAAM,QAAQ,46DAwCpB,CAAC;AAEF,eAAO,MAAM,mBAAmB,w5DAsC/B,CAAC;AAEF,eAAO,MAAM,eAAe,24CAgC3B,CAAC;AAEF,eAAO,MAAM,WAAW,kjDAiCvB,CAAC;AAEF,eAAO,MAAM,OAAO,wjDAmCnB,CAAC;AAEF,eAAO,MAAM,UAAU,gsDAmCtB,CAAC"}
+{"version":3,"file":"cursor-rules.d.ts","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,QAAQ,mnDA8BpB,CAAC;AAEF,eAAO,MAAM,QAAQ,46DAwCpB,CAAC;AAEF,eAAO,MAAM,mBAAmB,w6GAsE/B,CAAC;AAEF,eAAO,MAAM,eAAe,24CAgC3B,CAAC;AAEF,eAAO,MAAM,WAAW,kjDAiCvB,CAAC;AAEF,eAAO,MAAM,OAAO,wjDAmCnB,CAAC;AAEF,eAAO,MAAM,UAAU,gsDAmCtB,CAAC"}

package/dist/templates/cursor-rules.js

@@ -88,6 +88,38 @@ When a design reference image exists in artifacts/references/ but codeloop_desig
 When visual changes have been made but codeloop_visual_review has not been run:
 - Suggest running codeloop_visual_review to check for UI issues
 
+# Multi-Page Visual Review
+
+Apps have multiple pages. A single screenshot is NOT sufficient for visual review.
+
+## Before visual review, discover all pages:
+1. Call codeloop_discover_screens to scan source code for routes and navigation patterns
+2. This returns a list of all known screens with routes and source locations
+
+## Capture ALL pages systematically:
+1. Build and run the app
+2. Capture the initial/home screen: call codeloop_capture_screenshot(screen_name: "home")
+3. Look at the captured screenshot — identify all navigation elements:
+   - Buttons that navigate to other pages
+   - Tab bar items (bottom tabs, top tabs)
+   - Navigation drawer / hamburger menu items
+   - Bottom navigation bar items
+   - Links, cards, or list items that open new pages
+4. For EACH navigation element:
+   a. Interact with it to navigate to the new page
+   b. Call codeloop_capture_screenshot(screen_name: "<descriptive_name>")
+   c. On the new page, check for further navigation elements
+   d. Explore sub-pages recursively (up to 3 levels deep)
+   e. Navigate back and continue with other elements
+5. After ALL pages are captured, call codeloop_visual_review to analyze all screenshots
+6. Cross-reference captured screens against codeloop_discover_screens results
+   to identify any pages that were missed
+
+## Never:
+- Do a visual review with only one screenshot of a multi-page app
+- Skip pages that are reachable via buttons, tabs, or menu items
+- Forget to capture modal dialogs, bottom sheets, and error states
+
 # CLI-First Service Provider Setup
 
 When configuring external services (hosting, email, databases, etc.):

package/dist/templates/cursor-rules.js.map

@@ -1 +1 @@
-{"version":3,"file":"cursor-rules.js","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8BvB,CAAC;AAEF,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwCvB,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsClC,CAAC;AAEF,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgC9B,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiC1B,CAAC;AAEF,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCtB,CAAC;AAEF,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCzB,CAAC"}
+{"version":3,"file":"cursor-rules.js","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8BvB,CAAC;AAEF,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwCvB,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsElC,CAAC;AAEF,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgC9B,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiC1B,CAAC;AAEF,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCtB,CAAC;AAEF,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCzB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codeloop",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "CLI tool for CodeLoop — automated verification for AI coding agents",
   "type": "module",
   "bin": {