codeloop 0.1.0

package/dist/index.js

@@ -0,0 +1,35 @@
+#!/usr/bin/env node
+import { Command } from "commander";
+import { signupCommand } from "./commands/signup.js";
+import { loginCommand } from "./commands/login.js";
+import { initCommand } from "./commands/init.js";
+import { statusCommand } from "./commands/status.js";
+import { configureCommand } from "./commands/configure.js";
+const program = new Command();
+program
+    .name("codeloop")
+    .description("CodeLoop — automated verification for AI coding agents")
+    .version("0.1.0");
+program
+    .command("signup")
+    .description("Create a new CodeLoop account and get an API key")
+    .action(signupCommand);
+program
+    .command("login")
+    .description("Log in to your CodeLoop account and generate an API key")
+    .action(loginCommand);
+program
+    .command("init")
+    .description("Initialize CodeLoop in the current project (creates config, MCP registration, rules)")
+    .action(initCommand);
+program
+    .command("status")
+    .description("Check your API key status, plan, and usage")
+    .action(statusCommand);
+program
+    .command("configure")
+    .alias("config")
+    .description("Interactively edit CodeLoop configuration for this project")
+    .action(configureCommand);
+program.parse();
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAEA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AACrD,OAAO,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AACnD,OAAO,EAAE,WAAW,EAAE,MAAM,oBAAoB,CAAC;AACjD,OAAO,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AACrD,OAAO,EAAE,gBAAgB,EAAE,MAAM,yBAAyB,CAAC;AAE3D,MAAM,OAAO,GAAG,IAAI,OAAO,EAAE,CAAC;AAE9B,OAAO;KACJ,IAAI,CAAC,UAAU,CAAC;KAChB,WAAW,CAAC,wDAAwD,CAAC;KACrE,OAAO,CAAC,OAAO,CAAC,CAAC;AAEpB,OAAO;KACJ,OAAO,CAAC,QAAQ,CAAC;KACjB,WAAW,CAAC,kDAAkD,CAAC;KAC/D,MAAM,CAAC,aAAa,CAAC,CAAC;AAEzB,OAAO;KACJ,OAAO,CAAC,OAAO,CAAC;KAChB,WAAW,CAAC,yDAAyD,CAAC;KACtE,MAAM,CAAC,YAAY,CAAC,CAAC;AAExB,OAAO;KACJ,OAAO,CAAC,MAAM,CAAC;KACf,WAAW,CACV,sFAAsF,CACvF;KACA,MAAM,CAAC,WAAW,CAAC,CAAC;AAEvB,OAAO;KACJ,OAAO,CAAC,QAAQ,CAAC;KACjB,WAAW,CACV,4CAA4C,CAC7C;KACA,MAAM,CAAC,aAAa,CAAC,CAAC;AAEzB,OAAO;KACJ,OAAO,CAAC,WAAW,CAAC;KACpB,KAAK,CAAC,QAAQ,CAAC;KACf,WAAW,CAAC,4DAA4D,CAAC;KACzE,MAAM,CAAC,gBAAgB,CAAC,CAAC;AAE5B,OAAO,CAAC,KAAK,EAAE,CAAC"}

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

@@ -0,0 +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";
+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\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

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

package/dist/templates/claude-agents.js

@@ -0,0 +1,59 @@
+export const CODELOOP_LOOP_MD = `You are a QA loop runner. Use CodeLoop MCP tools to verify code quality.
+
+Process:
+1. Call codeloop_verify to run all checks
+2. Call codeloop_diagnose to classify failures
+3. Fix only confirmed issues
+4. Repeat verification
+5. Call codeloop_gate_check to evaluate completion
+6. Stop when all gates pass or escalation is needed
+
+Never mark a task complete without evidence from CodeLoop.
+`;
+export const CODELOOP_QA_MD = `You are a QA verification specialist. Run CodeLoop visual review
+and design comparison. Report structured issues with severity,
+evidence, and fix hints.
+`;
+export const CODELOOP_ADVISOR_MD = `You are an infrastructure and tooling advisor. Use CodeLoop
+recommendation tools to suggest the best tools based on the
+project stack, budget, and constraints. Always explain your
+reasoning and include tradeoffs.
+`;
+export const CLAUDE_MD = `# CodeLoop Integration
+
+CodeLoop provides automated verification for AI-generated code via MCP tools. Follow these rules to ensure code quality.
+
+## After implementing or modifying any feature:
+1. Call codeloop_verify to run all checks on the current project
+2. Read the structured output carefully — trust deterministic results first, visual diffs second, model opinions third
+3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks
+4. Fix ONLY the confirmed issues listed in the repair tasks — do not guess or fix unrelated code
+5. After fixing, call codeloop_verify again to confirm the fixes worked
+6. Repeat until all failures are resolved or a blocker is identified
+
+## Before marking any task or feature as complete:
+1. Call codeloop_gate_check with the run_id, spec path, and acceptance path
+2. If the result says "continue_fixing", keep fixing and re-verifying
+3. If the result says "escalate", stop and report the blockers to the developer
+4. Only declare the task complete when gate_check returns "ready_for_review" with confidence >= 85%
+
+## When you have attempted to fix an issue 2 or more times and tests still fail:
+- You MUST call codeloop_diagnose before making another fix attempt
+- Read the repair tasks carefully — the structured analysis is more reliable than guessing from raw output
+
+## For multi-section projects:
+- Call codeloop_section_status to see current progress and which section to work on next
+- If integration_due is true, run codeloop_verify with scope "full" first and fix any regressions
+- After ALL sections pass, run codeloop_release_readiness for a final quality assessment
+
+## When choosing tools or infrastructure:
+- Call codeloop_recommend_tool with the relevant category and detected stack
+- Present results with reasoning, tradeoffs, and pricing
+
+## Never:
+- Mark a task complete without evidence from codeloop_gate_check
+- Ignore codeloop_verify results
+- Modify files outside the allowed_file_scope from repair tasks
+- Continue fixing after 8 failed repair attempts — escalate instead
+`;
+//# sourceMappingURL=claude-agents.js.map

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

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

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

@@ -0,0 +1,4 @@
+export declare const PROMPT_LOOP = "# /codeloop-loop\n\nRun the full CodeLoop verify-diagnose-fix cycle on the current project.\n\n## Instructions\n\n1. Call `codeloop_verify` with scope \"full\" to run all checks\n2. If failures are found, call `codeloop_diagnose` with the run_id\n3. Fix only the confirmed issues from the repair tasks\n4. Call `codeloop_verify` again to check fixes\n5. Repeat steps 2-4 until all failures are resolved\n6. Call `codeloop_gate_check` with the run_id, spec path, and acceptance path\n7. Report the final result with confidence score and evidence summary\n\nDo not stop until gate_check returns \"ready_for_review\" with confidence >= 85%, or you need to escalate a blocker.\n";
+export declare const PROMPT_VERIFY = "# /codeloop-verify\n\nRun a quick CodeLoop verification on the current project.\n\n## Instructions\n\n1. Call `codeloop_verify` with scope \"full\" and platform \"auto\"\n2. Read the structured output carefully\n3. Summarize: total checks, pass count, fail count, warnings\n4. If there are failures, suggest calling `codeloop_diagnose` for detailed analysis\n5. If all checks pass, confirm the project is in good shape\n";
+export declare const PROMPT_REVIEW = "# /codeloop-review\n\nRun a CodeLoop visual review on the current project's UI.\n\n## Instructions\n\n1. Call `codeloop_visual_review` to analyze screenshots for UI issues\n2. If a design reference exists, also call `codeloop_design_compare` to check visual fidelity\n3. Report any visual issues with severity and fix suggestions\n4. If baselines exist and diffs exceed the threshold, flag visual regressions\n5. Summarize the overall visual quality assessment\n";
+//# sourceMappingURL=claude-prompts.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"claude-prompts.d.ts","sourceRoot":"","sources":["../../src/templates/claude-prompts.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,WAAW,uqBAevB,CAAC;AAEF,eAAO,MAAM,aAAa,yaAWzB,CAAC;AAEF,eAAO,MAAM,aAAa,mdAWzB,CAAC"}

package/dist/templates/claude-prompts.js

@@ -0,0 +1,41 @@
+export const PROMPT_LOOP = `# /codeloop-loop
+
+Run the full CodeLoop verify-diagnose-fix cycle on the current project.
+
+## Instructions
+
+1. Call \`codeloop_verify\` with scope "full" to run all checks
+2. If failures are found, call \`codeloop_diagnose\` with the run_id
+3. Fix only the confirmed issues from the repair tasks
+4. Call \`codeloop_verify\` again to check fixes
+5. Repeat steps 2-4 until all failures are resolved
+6. Call \`codeloop_gate_check\` with the run_id, spec path, and acceptance path
+7. Report the final result with confidence score and evidence summary
+
+Do not stop until gate_check returns "ready_for_review" with confidence >= 85%, or you need to escalate a blocker.
+`;
+export const PROMPT_VERIFY = `# /codeloop-verify
+
+Run a quick CodeLoop verification on the current project.
+
+## Instructions
+
+1. Call \`codeloop_verify\` with scope "full" and platform "auto"
+2. Read the structured output carefully
+3. Summarize: total checks, pass count, fail count, warnings
+4. If there are failures, suggest calling \`codeloop_diagnose\` for detailed analysis
+5. If all checks pass, confirm the project is in good shape
+`;
+export const PROMPT_REVIEW = `# /codeloop-review
+
+Run a CodeLoop visual review on the current project's UI.
+
+## Instructions
+
+1. Call \`codeloop_visual_review\` to analyze screenshots for UI issues
+2. If a design reference exists, also call \`codeloop_design_compare\` to check visual fidelity
+3. Report any visual issues with severity and fix suggestions
+4. If baselines exist and diffs exceed the threshold, flag visual regressions
+5. Summarize the overall visual quality assessment
+`;
+//# sourceMappingURL=claude-prompts.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"claude-prompts.js","sourceRoot":"","sources":["../../src/templates/claude-prompts.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;;;;;CAe1B,CAAC;AAEF,MAAM,CAAC,MAAM,aAAa,GAAG;;;;;;;;;;;CAW5B,CAAC;AAEF,MAAM,CAAC,MAAM,aAAa,GAAG;;;;;;;;;;;CAW5B,CAAC"}

package/dist/templates/config.d.ts

@@ -0,0 +1,2 @@
+export declare function createDefaultConfig(apiKey?: string, platforms?: string[]): Record<string, unknown>;
+//# sourceMappingURL=config.d.ts.map

package/dist/templates/config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"config.d.ts","sourceRoot":"","sources":["../../src/templates/config.ts"],"names":[],"mappings":"AAAA,wBAAgB,mBAAmB,CACjC,MAAM,GAAE,MAAW,EACnB,SAAS,GAAE,MAAM,EAAa,GAC7B,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CA8BzB"}

package/dist/templates/config.js

@@ -0,0 +1,32 @@
+export function createDefaultConfig(apiKey = "", platforms = ["auto"]) {
+    return {
+        api_key: apiKey,
+        vision_model: "auto",
+        platforms,
+        screenshot_viewports: ["375x812", "390x844", "1440x900"],
+        design_match_threshold: 0.85,
+        max_loop_iterations: 10,
+        auto_verify_on_complete: true,
+        auto_gate_check: true,
+        recommendations: {
+            enabled: true,
+            external_tools: true,
+            sponsored: false,
+            preferences: {
+                budget: "low",
+                self_hosted: false,
+                open_source_only: false,
+                gdpr_sensitive: false,
+                preferred_cloud: "",
+                region: "",
+            },
+        },
+        evidence: {
+            capture_screenshots: true,
+            capture_traces: true,
+            capture_videos: false,
+            baseline_auto_update: false,
+        },
+    };
+}
+//# sourceMappingURL=config.js.map

package/dist/templates/config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"config.js","sourceRoot":"","sources":["../../src/templates/config.ts"],"names":[],"mappings":"AAAA,MAAM,UAAU,mBAAmB,CACjC,SAAiB,EAAE,EACnB,YAAsB,CAAC,MAAM,CAAC;IAE9B,OAAO;QACL,OAAO,EAAE,MAAM;QACf,YAAY,EAAE,MAAM;QACpB,SAAS;QACT,oBAAoB,EAAE,CAAC,SAAS,EAAE,SAAS,EAAE,UAAU,CAAC;QACxD,sBAAsB,EAAE,IAAI;QAC5B,mBAAmB,EAAE,EAAE;QACvB,uBAAuB,EAAE,IAAI;QAC7B,eAAe,EAAE,IAAI;QACrB,eAAe,EAAE;YACf,OAAO,EAAE,IAAI;YACb,cAAc,EAAE,IAAI;YACpB,SAAS,EAAE,KAAK;YAChB,WAAW,EAAE;gBACX,MAAM,EAAE,KAAK;gBACb,WAAW,EAAE,KAAK;gBAClB,gBAAgB,EAAE,KAAK;gBACvB,cAAc,EAAE,KAAK;gBACrB,eAAe,EAAE,EAAE;gBACnB,MAAM,EAAE,EAAE;aACX;SACF;QACD,QAAQ,EAAE;YACR,mBAAmB,EAAE,IAAI;YACzB,cAAc,EAAE,IAAI;YACpB,cAAc,EAAE,KAAK;YACrB,oBAAoB,EAAE,KAAK;SAC5B;KACF,CAAC;AACJ,CAAC"}

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

@@ -0,0 +1,7 @@
+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";
+export declare const RECOMMENDATIONS_MDC = "---\ndescription: CodeLoop recommendation triggers\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";
+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";
+export declare const MOBILE_MDC = "---\ndescription: CodeLoop mobile-specific verification guidance (iOS/Android native)\nglobs: [\"Podfile\", \"build.gradle\", \"build.gradle.kts\", \"**/*.swift\", \"**/*.kt\", \"**/*.java\", \"*.xcodeproj/**\", \"*.xcworkspace/**\"]\n---\n\n# Mobile Verification Rules\n\nWhen the project is a native mobile app (iOS with CocoaPods/Xcode or Android with Gradle), apply these additional verification steps:\n\n## Before calling codeloop_verify:\n- For iOS: ensure `pod install` has been run after any Podfile change\n- For Android: ensure Gradle sync is complete after any build.gradle change\n- Platform parameter should be set to \"mobile\"\n\n## iOS-specific checks:\n- Xcode build must succeed without errors (`xcodebuild build`)\n- Unit tests must pass (`xcodebuild test`)\n- Check for signing issues \u2014 these require developer intervention, escalate immediately\n- Storyboard/XIB changes should be verified with codeloop_visual_review\n\n## Android-specific checks:\n- Gradle build must succeed (`./gradlew assembleDebug`)\n- Unit tests must pass (`./gradlew test`)\n- Check for manifest merge conflicts\n- Lint warnings from Android Lint should be reviewed\n\n## Screenshot viewports for mobile:\n- iOS: 375x812 (iPhone SE), 390x844 (iPhone 14), 428x926 (iPhone Pro Max)\n- Android: 360x800 (compact), 412x915 (medium), 600x1024 (tablet)\n\n## Common mobile failure patterns:\n- \"Signing requires a development team\" \u2192 escalate to developer, cannot fix programmatically\n- \"Pod not found\" \u2192 run `pod install --repo-update`\n- Gradle daemon issues \u2192 `./gradlew --stop` then retry\n- Simulator/emulator not found \u2192 check available devices with `xcrun simctl list` or `emulator -list-avds`\n";
+//# sourceMappingURL=cursor-rules.d.ts.map

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

@@ -0,0 +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,knCAsBpB,CAAC;AAEF,eAAO,MAAM,mBAAmB,00BAiB/B,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

@@ -0,0 +1,179 @@
+export const CORE_MDC = `---
+description: CodeLoop core verification rules for all projects
+globs: ["**/*"]
+---
+
+# CodeLoop Verification Rules
+
+## After implementing or modifying any feature:
+1. Call codeloop_verify to run all checks on the current project
+2. Read the structured output carefully — trust deterministic results first, visual diffs second, model opinions third
+3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks
+4. Fix ONLY the confirmed issues listed in the repair tasks — do not guess or fix unrelated code
+5. After fixing, call codeloop_verify again to confirm the fixes worked
+6. Repeat until all failures are resolved or a blocker is identified
+
+## Before marking any task or feature as complete:
+1. Call codeloop_gate_check with the run_id, spec path, and acceptance path
+2. If the result says "continue_fixing", keep fixing and re-verifying
+3. If the result says "escalate", stop and report the blockers to the developer
+4. Only declare the task complete when gate_check returns "ready_for_review" with confidence >= 85%
+
+## When you have attempted to fix an issue 2 or more times and tests still fail:
+- You MUST call codeloop_diagnose before making another fix attempt
+- Read the repair tasks carefully — the structured analysis is more reliable than guessing from raw output
+
+## Never:
+- Mark a task complete without evidence from codeloop_gate_check
+- Ignore codeloop_verify results
+- Modify files outside the allowed_file_scope from repair tasks
+- Continue fixing after 8 failed repair attempts — escalate instead
+`;
+export const LOOP_MDC = `---
+description: CodeLoop multi-section development loop
+globs: ["docs/specs/_master.md"]
+---
+
+# Multi-Section Development Loop
+
+When a master spec exists at docs/specs/_master.md:
+
+1. Call codeloop_section_status to see current progress and which section to work on next
+2. If integration_due is true, run codeloop_verify with scope "full" first and fix any regressions
+3. Read the spec file for the current section (the path is in the section_status response)
+4. Read the acceptance criteria file for the current section
+5. Implement the section according to the spec
+6. Run codeloop_verify → codeloop_diagnose → fix → repeat until codeloop_gate_check passes with confidence >= 85%
+7. Call codeloop_section_status again to get the next section
+8. If more sections remain, proceed to the next section IMMEDIATELY
+9. Do NOT stop between sections for human review
+10. After ALL sections pass individually:
+    - Run codeloop_verify with scope "full" (entire app)
+    - Run codeloop_release_readiness
+11. Only THEN report to the developer with the full evidence summary and confidence scores
+`;
+export const RECOMMENDATIONS_MDC = `---
+description: CodeLoop recommendation triggers
+globs: ["**/*"]
+---
+
+# When to use CodeLoop recommendations
+
+When the developer or task involves choosing infrastructure, tools, or services:
+- If the task mentions hosting, deployment, server, email service, analytics, marketing, monitoring, auth provider, database, or file storage
+- Call codeloop_recommend_tool with the relevant category and detected stack
+- Present the results with reasoning, tradeoffs, and pricing — never just a name
+
+When a design reference image exists in artifacts/references/ but codeloop_design_compare has not been run:
+- Suggest running codeloop_design_compare to check visual fidelity
+
+When visual changes have been made but codeloop_visual_review has not been run:
+- Suggest running codeloop_visual_review to check for UI issues
+`;
+export const FLUTTER_MDC = `---
+description: CodeLoop Flutter-specific verification guidance
+globs: ["pubspec.yaml", "**/*.dart", "lib/**", "test/**"]
+---
+
+# Flutter Verification Rules
+
+When the project contains a pubspec.yaml, apply these additional verification steps:
+
+## Before calling codeloop_verify:
+- Ensure \`flutter pub get\` has been run after any pubspec.yaml change
+- Platform parameter should be set to "flutter"
+
+## After codeloop_verify completes:
+- Check that \`flutter analyze\` reported zero issues (warnings and info are acceptable, errors are not)
+- Check that \`flutter test\` passed all widget and unit tests
+- If golden tests exist, verify no unexpected diffs in \`test/goldens/\`
+
+## When creating or modifying Dart files:
+- Run \`dart format .\` before verification to avoid style-only failures
+- Ensure all public APIs have documentation comments
+- Prefer \`const\` constructors for stateless widgets
+
+## Screenshot viewports for Flutter:
+- iOS: 375x812 (iPhone SE), 390x844 (iPhone 14), 428x926 (iPhone 14 Pro Max)
+- Android: 360x800 (compact), 412x915 (medium), 600x1024 (tablet)
+- Use codeloop_visual_review with these viewport sizes after UI changes
+
+## Common Flutter failure patterns:
+- "No pubspec.yaml found" → wrong working directory, navigate to the Flutter project root
+- "flutter not found" → Flutter SDK not in PATH, check the developer's environment
+- Widget overflow errors → check constraints and use Expanded/Flexible wrappers
+- State management issues → verify provider/bloc/riverpod setup in the widget tree
+`;
+export const WEB_MDC = `---
+description: CodeLoop web-specific verification guidance
+globs: ["package.json", "**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx", "**/*.vue", "**/*.svelte"]
+---
+
+# Web Verification Rules
+
+When the project is a web application (Next.js, React, Vue, Svelte, Angular), apply these additional verification steps:
+
+## Before calling codeloop_verify:
+- Ensure \`npm install\` or equivalent has been run after any package.json change
+- Platform parameter should be set to "web"
+
+## After codeloop_verify completes:
+- Check that the build succeeds without errors (\`npm run build\` or framework equivalent)
+- Check that all test suites pass (\`npm test\`, \`vitest run\`, \`jest\`, etc.)
+- Check for TypeScript errors if the project uses TypeScript
+
+## Responsive testing:
+- Mobile: 375x812 (iPhone SE portrait)
+- Tablet: 768x1024 (iPad portrait)
+- Desktop: 1440x900 (standard laptop)
+- Use codeloop_visual_review with these viewport sizes after UI changes
+
+## Accessibility checks:
+- Color contrast should meet WCAG AA (4.5:1 for normal text, 3:1 for large text)
+- Interactive elements need keyboard focus indicators
+- Images need alt text, form inputs need labels
+- Touch targets should be at least 44x44px on mobile
+
+## Common web failure patterns:
+- "Module not found" → missing dependency, run npm install
+- Hydration mismatch (Next.js/React SSR) → server/client rendering inconsistency
+- "Cannot find module" in tests → check jest/vitest config moduleNameMapper
+- Port already in use → kill the existing dev server process
+`;
+export const MOBILE_MDC = `---
+description: CodeLoop mobile-specific verification guidance (iOS/Android native)
+globs: ["Podfile", "build.gradle", "build.gradle.kts", "**/*.swift", "**/*.kt", "**/*.java", "*.xcodeproj/**", "*.xcworkspace/**"]
+---
+
+# Mobile Verification Rules
+
+When the project is a native mobile app (iOS with CocoaPods/Xcode or Android with Gradle), apply these additional verification steps:
+
+## Before calling codeloop_verify:
+- For iOS: ensure \`pod install\` has been run after any Podfile change
+- For Android: ensure Gradle sync is complete after any build.gradle change
+- Platform parameter should be set to "mobile"
+
+## iOS-specific checks:
+- Xcode build must succeed without errors (\`xcodebuild build\`)
+- Unit tests must pass (\`xcodebuild test\`)
+- Check for signing issues — these require developer intervention, escalate immediately
+- Storyboard/XIB changes should be verified with codeloop_visual_review
+
+## Android-specific checks:
+- Gradle build must succeed (\`./gradlew assembleDebug\`)
+- Unit tests must pass (\`./gradlew test\`)
+- Check for manifest merge conflicts
+- Lint warnings from Android Lint should be reviewed
+
+## Screenshot viewports for mobile:
+- iOS: 375x812 (iPhone SE), 390x844 (iPhone 14), 428x926 (iPhone Pro Max)
+- Android: 360x800 (compact), 412x915 (medium), 600x1024 (tablet)
+
+## Common mobile failure patterns:
+- "Signing requires a development team" → escalate to developer, cannot fix programmatically
+- "Pod not found" → run \`pod install --repo-update\`
+- Gradle daemon issues → \`./gradlew --stop\` then retry
+- Simulator/emulator not found → check available devices with \`xcrun simctl list\` or \`emulator -list-avds\`
+`;
+//# sourceMappingURL=cursor-rules.js.map

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

@@ -0,0 +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;;;;;;;;;;;;;;;;;;;;;;CAsBvB,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;CAiBlC,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/dist/templates/cursor-skills.d.ts

@@ -0,0 +1,5 @@
+export declare const SKILL_LOOP = "---\nname: codeloop-loop\ndescription: Run the full CodeLoop verify-diagnose-fix cycle until all quality gates pass. Use when implementing a feature end-to-end or completing a development section that requires verified, production-ready code.\n---\n\n# CodeLoop Loop\n\nOrchestrates the complete verification cycle for a feature or section.\n\n## When to use\n\n- After implementing a feature or completing a code change that needs verification\n- When working through a multi-section development plan\n- When you need evidence-based confirmation that code is ready for review\n\n## Instructions\n\n1. Call `codeloop_verify` with the appropriate scope (\"full\" for entire project, \"affected\" for changed files only) and platform (\"auto\" to detect, or \"flutter\"/\"web\"/\"mobile\" explicitly)\n\n2. Read the structured output. If all checks pass, proceed to step 5.\n\n3. If there are failures, call `codeloop_diagnose` with the `run_id` from the verify result. Read the categorized issues and repair tasks carefully.\n\n4. Fix ONLY the issues listed in the repair tasks. Do not guess or fix unrelated code. After fixing, go back to step 1 and re-verify. Repeat up to 8 times.\n\n5. Call `codeloop_gate_check` with the `run_id`, the spec path, and the acceptance criteria path.\n\n6. If gate_check returns:\n   - `\"ready_for_review\"` with confidence >= 85% \u2014 the task is complete\n   - `\"continue_fixing\"` \u2014 go back to step 1\n   - `\"escalate\"` \u2014 stop and report blockers to the developer\n\n7. If working through a multi-section plan, call `codeloop_section_status` to get the next section and repeat the entire cycle.\n\n## Important\n\n- Never mark a task complete without evidence from `codeloop_gate_check`\n- After 8 failed repair attempts, escalate instead of continuing\n- Trust deterministic results (test pass/fail) over model opinions\n";
+export declare const SKILL_VERIFY = "---\nname: codeloop-verify\ndescription: Run a single CodeLoop verification pass to check if the current code compiles, passes tests, and meets quality standards. Use after any code change to get structured pass/fail results.\n---\n\n# CodeLoop Verify\n\nRuns a single verification pass and returns structured results.\n\n## When to use\n\n- After making code changes and wanting a quick check\n- Before committing code to ensure nothing is broken\n- When you need structured test/lint/build output instead of raw terminal output\n\n## Instructions\n\n1. Call `codeloop_verify` with parameters:\n   - `scope`: \"full\" (all checks) or \"affected\" (only changed files)\n   - `platform`: \"auto\" (detect from project), \"flutter\", \"web\", or \"mobile\"\n\n2. The tool returns a structured report containing:\n   - Pass/fail counts for each check category\n   - Artifact paths for logs and screenshots\n   - A next-step suggestion\n\n3. If there are failures, consider using the codeloop-loop skill for the full diagnose-fix cycle, or call `codeloop_diagnose` manually with the `run_id`.\n\n4. If all checks pass, you can proceed with confidence or run `codeloop_gate_check` for formal completion evidence.\n\n## Output format\n\nThe verification result includes:\n- `run_id`: unique identifier for this run (needed by diagnose and gate_check)\n- `summary`: overall pass/fail with counts\n- `checks`: detailed results per category (build, tests, lint, format)\n- `artifacts`: paths to generated logs and screenshots\n- `suggestion`: recommended next action\n";
+export declare const SKILL_VISUAL_REVIEW = "---\nname: codeloop-visual-review\ndescription: Capture screenshots of the current UI and analyze them for visual issues, layout problems, and design fidelity. Use after UI changes to catch visual regressions.\n---\n\n# CodeLoop Visual Review\n\nCaptures and analyzes UI screenshots for visual quality.\n\n## When to use\n\n- After making UI/styling changes and wanting to verify visual correctness\n- When a design reference image is available and you want to compare against it\n- When checking responsive layout across different viewport sizes\n- When verifying accessibility-related visual aspects (contrast, sizing)\n\n## Instructions\n\n### For visual review (no reference image):\n\n1. Call `codeloop_visual_review` with:\n   - `run_id`: from a recent `codeloop_verify` run (optional)\n   - `viewport_sizes`: array of viewport dimensions (e.g., [\"375x812\", \"1440x900\"])\n   - `ux_checklist_path`: path to UX checklist if one exists\n\n2. The tool captures screenshots at each viewport size and uses a vision model to identify issues.\n\n### For design comparison (with reference image):\n\n1. Call `codeloop_design_compare` with:\n   - `reference_image_path`: path to the design mockup or Figma export\n   - `screen_name`: identifier for the screen being compared\n   - `platform`: the platform being tested\n   - `viewport_sizes`: viewport dimensions to test\n\n2. The tool returns a match score, list of differences, and comparison screenshots.\n\n## Tips\n\n- Store design references in `artifacts/references/` for easy access\n- Run visual review after every UI change, not just at the end\n- Use the UX checklist template at `docs/ux-checklists/_template.md` for consistent checks\n";
+export declare const SKILL_RECOMMEND = "---\nname: codeloop-recommend\ndescription: Get evidence-based recommendations for third-party tools and services based on the project stack, budget, and constraints. Use when choosing hosting, databases, email services, analytics, or any infrastructure.\n---\n\n# CodeLoop Recommend\n\nProvides structured tool and service recommendations.\n\n## When to use\n\n- When the developer asks about hosting, deployment, or infrastructure options\n- When choosing between email services, analytics tools, auth providers, or databases\n- When evaluating tools for monitoring, file storage, or marketing\n- When the task requires selecting a third-party service and you want objective comparison\n\n## Instructions\n\n1. Call `codeloop_recommend_tool` with:\n   - `category`: the type of tool needed (e.g., \"hosting\", \"email\", \"database\", \"analytics\", \"auth\", \"monitoring\", \"file-storage\")\n   - `stack`: key-value pairs describing the current tech stack\n   - `budget`: \"free\", \"low\", \"medium\", or \"enterprise\"\n   - `constraints`: any specific requirements (e.g., `{\"gdpr\": true, \"region\": \"eu\"}`)\n\n2. The tool returns ranked recommendations with reasoning, pricing, tradeoffs, and starter tasks.\n\n3. Present the results with reasoning and tradeoffs \u2014 never just recommend a name without context.\n\n## Tips\n\n- Always include the current stack so recommendations account for compatibility\n- Set budget to match the developer's stated constraints\n- Use constraints for regulatory requirements (GDPR, SOC2, HIPAA)\n";
+//# sourceMappingURL=cursor-skills.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"cursor-skills.d.ts","sourceRoot":"","sources":["../../src/templates/cursor-skills.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,UAAU,u1DAuCtB,CAAC;AAEF,eAAO,MAAM,YAAY,4hDAsCxB,CAAC;AAEF,eAAO,MAAM,mBAAmB,uqDA0C/B,CAAC;AAEF,eAAO,MAAM,eAAe,ihDAiC3B,CAAC"}

package/dist/templates/cursor-skills.js

@@ -0,0 +1,157 @@
+export const SKILL_LOOP = `---
+name: codeloop-loop
+description: Run the full CodeLoop verify-diagnose-fix cycle until all quality gates pass. Use when implementing a feature end-to-end or completing a development section that requires verified, production-ready code.
+---
+
+# CodeLoop Loop
+
+Orchestrates the complete verification cycle for a feature or section.
+
+## When to use
+
+- After implementing a feature or completing a code change that needs verification
+- When working through a multi-section development plan
+- When you need evidence-based confirmation that code is ready for review
+
+## Instructions
+
+1. Call \`codeloop_verify\` with the appropriate scope ("full" for entire project, "affected" for changed files only) and platform ("auto" to detect, or "flutter"/"web"/"mobile" explicitly)
+
+2. Read the structured output. If all checks pass, proceed to step 5.
+
+3. If there are failures, call \`codeloop_diagnose\` with the \`run_id\` from the verify result. Read the categorized issues and repair tasks carefully.
+
+4. Fix ONLY the issues listed in the repair tasks. Do not guess or fix unrelated code. After fixing, go back to step 1 and re-verify. Repeat up to 8 times.
+
+5. Call \`codeloop_gate_check\` with the \`run_id\`, the spec path, and the acceptance criteria path.
+
+6. If gate_check returns:
+   - \`"ready_for_review"\` with confidence >= 85% — the task is complete
+   - \`"continue_fixing"\` — go back to step 1
+   - \`"escalate"\` — stop and report blockers to the developer
+
+7. If working through a multi-section plan, call \`codeloop_section_status\` to get the next section and repeat the entire cycle.
+
+## Important
+
+- Never mark a task complete without evidence from \`codeloop_gate_check\`
+- After 8 failed repair attempts, escalate instead of continuing
+- Trust deterministic results (test pass/fail) over model opinions
+`;
+export const SKILL_VERIFY = `---
+name: codeloop-verify
+description: Run a single CodeLoop verification pass to check if the current code compiles, passes tests, and meets quality standards. Use after any code change to get structured pass/fail results.
+---
+
+# CodeLoop Verify
+
+Runs a single verification pass and returns structured results.
+
+## When to use
+
+- After making code changes and wanting a quick check
+- Before committing code to ensure nothing is broken
+- When you need structured test/lint/build output instead of raw terminal output
+
+## Instructions
+
+1. Call \`codeloop_verify\` with parameters:
+   - \`scope\`: "full" (all checks) or "affected" (only changed files)
+   - \`platform\`: "auto" (detect from project), "flutter", "web", or "mobile"
+
+2. The tool returns a structured report containing:
+   - Pass/fail counts for each check category
+   - Artifact paths for logs and screenshots
+   - A next-step suggestion
+
+3. If there are failures, consider using the codeloop-loop skill for the full diagnose-fix cycle, or call \`codeloop_diagnose\` manually with the \`run_id\`.
+
+4. If all checks pass, you can proceed with confidence or run \`codeloop_gate_check\` for formal completion evidence.
+
+## Output format
+
+The verification result includes:
+- \`run_id\`: unique identifier for this run (needed by diagnose and gate_check)
+- \`summary\`: overall pass/fail with counts
+- \`checks\`: detailed results per category (build, tests, lint, format)
+- \`artifacts\`: paths to generated logs and screenshots
+- \`suggestion\`: recommended next action
+`;
+export const SKILL_VISUAL_REVIEW = `---
+name: codeloop-visual-review
+description: Capture screenshots of the current UI and analyze them for visual issues, layout problems, and design fidelity. Use after UI changes to catch visual regressions.
+---
+
+# CodeLoop Visual Review
+
+Captures and analyzes UI screenshots for visual quality.
+
+## When to use
+
+- After making UI/styling changes and wanting to verify visual correctness
+- When a design reference image is available and you want to compare against it
+- When checking responsive layout across different viewport sizes
+- When verifying accessibility-related visual aspects (contrast, sizing)
+
+## Instructions
+
+### For visual review (no reference image):
+
+1. Call \`codeloop_visual_review\` with:
+   - \`run_id\`: from a recent \`codeloop_verify\` run (optional)
+   - \`viewport_sizes\`: array of viewport dimensions (e.g., ["375x812", "1440x900"])
+   - \`ux_checklist_path\`: path to UX checklist if one exists
+
+2. The tool captures screenshots at each viewport size and uses a vision model to identify issues.
+
+### For design comparison (with reference image):
+
+1. Call \`codeloop_design_compare\` with:
+   - \`reference_image_path\`: path to the design mockup or Figma export
+   - \`screen_name\`: identifier for the screen being compared
+   - \`platform\`: the platform being tested
+   - \`viewport_sizes\`: viewport dimensions to test
+
+2. The tool returns a match score, list of differences, and comparison screenshots.
+
+## Tips
+
+- Store design references in \`artifacts/references/\` for easy access
+- Run visual review after every UI change, not just at the end
+- Use the UX checklist template at \`docs/ux-checklists/_template.md\` for consistent checks
+`;
+export const SKILL_RECOMMEND = `---
+name: codeloop-recommend
+description: Get evidence-based recommendations for third-party tools and services based on the project stack, budget, and constraints. Use when choosing hosting, databases, email services, analytics, or any infrastructure.
+---
+
+# CodeLoop Recommend
+
+Provides structured tool and service recommendations.
+
+## When to use
+
+- When the developer asks about hosting, deployment, or infrastructure options
+- When choosing between email services, analytics tools, auth providers, or databases
+- When evaluating tools for monitoring, file storage, or marketing
+- When the task requires selecting a third-party service and you want objective comparison
+
+## Instructions
+
+1. Call \`codeloop_recommend_tool\` with:
+   - \`category\`: the type of tool needed (e.g., "hosting", "email", "database", "analytics", "auth", "monitoring", "file-storage")
+   - \`stack\`: key-value pairs describing the current tech stack
+   - \`budget\`: "free", "low", "medium", or "enterprise"
+   - \`constraints\`: any specific requirements (e.g., \`{"gdpr": true, "region": "eu"}\`)
+
+2. The tool returns ranked recommendations with reasoning, pricing, tradeoffs, and starter tasks.
+
+3. Present the results with reasoning and tradeoffs — never just recommend a name without context.
+
+## Tips
+
+- Always include the current stack so recommendations account for compatibility
+- Set budget to match the developer's stated constraints
+- Use constraints for regulatory requirements (GDPR, SOC2, HIPAA)
+`;
+//# sourceMappingURL=cursor-skills.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"cursor-skills.js","sourceRoot":"","sources":["../../src/templates/cursor-skills.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuCzB,CAAC;AAEF,MAAM,CAAC,MAAM,YAAY,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsC3B,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0ClC,CAAC;AAEF,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiC9B,CAAC"}

package/dist/templates/mcp-config.d.ts

@@ -0,0 +1,23 @@
+export declare const CURSOR_MCP_CONFIG: {
+    mcpServers: {
+        codeloop: {
+            command: string;
+            args: string[];
+            env: {
+                CODELOOP_API_KEY: string;
+            };
+        };
+    };
+};
+export declare const CLAUDE_MCP_CONFIG: {
+    mcpServers: {
+        codeloop: {
+            command: string;
+            args: string[];
+            env: {
+                CODELOOP_API_KEY: string;
+            };
+        };
+    };
+};
+//# sourceMappingURL=mcp-config.d.ts.map