codeloop 0.1.17 → 0.1.18

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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8QvB,CAAC;AAEF,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6CvB,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoGlC,CAAC;AAEF,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwC9B,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiC1B,CAAC;AAEF,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0JtB,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,cAAc,6CAA6C,CAAC"}

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

@@ -1,5 +1,2 @@
-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 >= 94% \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";
+export * from "@codelooptech/shared/templates/cursor-skills";
 //# sourceMappingURL=cursor-skills.d.ts.map

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

@@ -1 +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"}
+{"version":3,"file":"cursor-skills.d.ts","sourceRoot":"","sources":["../../src/templates/cursor-skills.ts"],"names":[],"mappings":"AAAA,cAAc,8CAA8C,CAAC"}

package/dist/templates/cursor-skills.js

@@ -1,157 +1,2 @@
-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 >= 94% — 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)
-`;
+export * from "@codelooptech/shared/templates/cursor-skills";
 //# sourceMappingURL=cursor-skills.js.map

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

@@ -1 +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"}
+{"version":3,"file":"cursor-skills.js","sourceRoot":"","sources":["../../src/templates/cursor-skills.ts"],"names":[],"mappings":"AAAA,cAAc,8CAA8C,CAAC"}

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

@@ -1,38 +1,2 @@
-/**
- * Global agent rules written by `npx codeloop init --global`.
- *
- * These ensure that once a user installs CodeLoop globally, every workspace
- * the agent opens — even brand-new ones — automatically:
- *   1. Discovers the CodeLoop MCP server (via global mcp.json registration).
- *   2. Bootstraps the project on first use via `codeloop_init_project`.
- *   3. Runs the verify → diagnose → gate_check loop after every code change.
- *
- * Distribution channel per agent:
- *   - Claude Code: `~/.claude/CLAUDE.md` (User Memory) is auto-loaded in every
- *     workspace by Claude Code, alongside any per-project `CLAUDE.md`.
- *   - Cursor: User Rules in Cursor live in the Settings UI (Cursor → Settings
- *     → Rules), NOT in `~/.cursor/rules/`. So we do two things:
- *       (a) write `~/.cursor/rules/codeloop.mdc` defensively in case Cursor
- *           ever supports user-level rule files;
- *       (b) save the same content to `~/.cursor/codeloop-user-rule.md` and
- *           print it during `init --global` for the user to paste into
- *           Cursor → Settings → Rules → User Rules. The MCP server is still
- *           globally available regardless, and its tool descriptions self-
- *           bootstrap any uninitialized workspace.
- */
-export declare const GLOBAL_CURSOR_RULE = "---\ndescription: CodeLoop \u2014 always-on verification across every Cursor workspace\nglobs: [\"**/*\"]\nalwaysApply: true\n---\n\n# CodeLoop is installed on this machine \u2014 use it in every workspace\n\nThe CodeLoop MCP server is registered globally in `~/.cursor/mcp.json`.\nIts tools are available in every workspace you open. You MUST use them\nwhenever you write or modify code.\n\n## On the first CodeLoop tool call in a workspace\n\nIf `.codeloop/config.json` does not yet exist in the workspace root:\n\n1. Call `codeloop_init_project` FIRST (before `codeloop_verify` or any other tool).\n   It auto-creates `.codeloop/config.json`, agent rules, `.gitignore` entries,\n   and an `artifacts/` directory tailored to the detected project type.\n2. Then proceed with the normal verification loop below.\n\nThe MCP server prepends a \"[CodeLoop] This project has not been initialized\"\nhint to every tool response in an uninitialized workspace. Treat that hint\nas an instruction, not a suggestion.\n\n## After every code change (every workspace, every project type)\n\n1. `codeloop_verify` \u2014 runs build, tests, and static analysis.\n2. If failures: `codeloop_diagnose` \u2192 fix the listed repair tasks \u2192 re-verify.\n   Loop automatically; do NOT ask the user between iterations.\n3. For UI projects: `codeloop_capture_screenshot` for every page, then\n   `codeloop_visual_review`. Then `codeloop_start_recording` \u2192\n   `codeloop_interact` with every element \u2192 `codeloop_stop_recording` \u2192\n   `codeloop_interaction_replay`.\n4. If `designs/` or `.codeloop/figma.json` exists, `codeloop_design_compare`\n   with `mode: \"all\"` is MANDATORY before `gate_check`.\n5. `codeloop_gate_check` \u2014 must return `ready_for_review` with confidence\n   >= 94 % and zero blocker gates. If it returns `continue_fixing`, loop\n   back to step 1 immediately; do NOT ask the user.\n6. `codeloop_generate_dev_report` \u2014 writes `docs/DEVELOPMENT_LOG.md`.\n\n## Never\n\n- Never declare a coding task complete without evidence from `codeloop_gate_check`.\n- Never skip `codeloop_init_project` in a fresh workspace just because the\n  project \"looks small\" \u2014 the bootstrap is fast and required.\n- Never skip the auto-fix loop after `continue_fixing`.\n- Never disable this rule per-project; project rules add to it, they do not\n  replace it.\n";
-export declare const GLOBAL_CLAUDE_MEMORY = "# CodeLoop \u2014 always-on verification across every Claude Code workspace\n\nThe CodeLoop MCP server is registered globally in `~/.claude.json`.\nIts tools are available in every workspace you open. You MUST use them\nwhenever you write or modify code.\n\n## On the first CodeLoop tool call in a workspace\n\nIf `.codeloop/config.json` does not yet exist in the workspace root:\n\n1. Call `codeloop_init_project` FIRST (before `codeloop_verify` or any other\n   CodeLoop tool). It auto-creates `.codeloop/config.json`, agent rules,\n   `.gitignore` entries, and an `artifacts/` directory tailored to the\n   detected project type.\n2. Then proceed with the normal verification loop below.\n\nThe MCP server prepends a \"[CodeLoop] This project has not been initialized\"\nhint to every tool response in an uninitialized workspace. Treat that hint\nas an instruction, not a suggestion.\n\n## After every code change (every workspace, every project type)\n\n1. `codeloop_verify` \u2014 runs build, tests, and static analysis.\n2. If failures: `codeloop_diagnose` \u2192 fix the listed repair tasks \u2192 re-verify.\n   Loop automatically; do NOT ask the user between iterations.\n3. For UI projects: `codeloop_capture_screenshot` for every page, then\n   `codeloop_visual_review`. Then `codeloop_start_recording` \u2192\n   `codeloop_interact` with every element \u2192 `codeloop_stop_recording` \u2192\n   `codeloop_interaction_replay`.\n4. If `designs/` or `.codeloop/figma.json` exists, `codeloop_design_compare`\n   with `mode: \"all\"` is MANDATORY before `gate_check`.\n5. `codeloop_gate_check` \u2014 must return `ready_for_review` with confidence\n   >= 94 % and zero blocker gates. If it returns `continue_fixing`, loop\n   back to step 1 immediately; do NOT ask the user.\n6. `codeloop_generate_dev_report` \u2014 writes `docs/DEVELOPMENT_LOG.md`.\n\n## Never\n\n- Never declare a coding task complete without evidence from `codeloop_gate_check`.\n- Never skip `codeloop_init_project` in a fresh workspace just because the\n  project \"looks small\" \u2014 the bootstrap is fast and required.\n- Never skip the auto-fix loop after `continue_fixing`.\n- Never disable this guidance per-project; per-project `CLAUDE.md` adds to\n  it, it does not replace it.\n";
-/**
- * Plain-text snippet a user pastes into Cursor → Settings → Rules → User Rules.
- * Same intent as \`GLOBAL_CURSOR_RULE\` but without the \`.mdc\` frontmatter
- * (Cursor's User Rules input box is a plain textarea).
- */
-export declare const GLOBAL_CURSOR_USER_RULE_SNIPPET = "CodeLoop is installed on this machine. The CodeLoop MCP server is registered globally in ~/.cursor/mcp.json, so its tools are available in EVERY workspace. You MUST use them whenever you write or modify code.\n\nON THE FIRST CODELOOP TOOL CALL IN A WORKSPACE\nIf `.codeloop/config.json` does not yet exist in the workspace root:\n1. Call `codeloop_init_project` FIRST (before `codeloop_verify` or any other tool).\n   It auto-creates `.codeloop/config.json`, agent rules, `.gitignore` entries,\n   and an `artifacts/` directory tailored to the detected project type.\n2. Then proceed with the verification loop below.\nThe MCP server prepends a \"[CodeLoop] This project has not been initialized\" hint\nto every tool response in an uninitialized workspace. Treat that hint as an\ninstruction, not a suggestion.\n\nAFTER EVERY CODE CHANGE (every workspace, every project type)\n1. `codeloop_verify` \u2014 runs build, tests, and static analysis.\n2. If failures: `codeloop_diagnose` \u2192 fix the listed repair tasks \u2192 re-verify.\n   Loop automatically; do NOT ask the user between iterations.\n3. For UI projects: `codeloop_capture_screenshot` for every page, then\n   `codeloop_visual_review`. Then `codeloop_start_recording` \u2192\n   `codeloop_interact` with every element \u2192 `codeloop_stop_recording` \u2192\n   `codeloop_interaction_replay`.\n4. If `designs/` or `.codeloop/figma.json` exists, `codeloop_design_compare`\n   with `mode: \"all\"` is MANDATORY before `gate_check`.\n5. `codeloop_gate_check` \u2014 must return `ready_for_review` with confidence\n   >= 94% and zero blocker gates. If it returns `continue_fixing`, loop back\n   to step 1 immediately; do NOT ask the user.\n6. `codeloop_generate_dev_report` \u2014 writes `docs/DEVELOPMENT_LOG.md`.\n\nNEVER\n- Never declare a coding task complete without evidence from `codeloop_gate_check`.\n- Never skip `codeloop_init_project` in a fresh workspace just because the\n  project \"looks small\" \u2014 the bootstrap is fast and required.\n- Never skip the auto-fix loop after `continue_fixing`.\n- Never disable this rule per-project; project rules add to it, they do not\n  replace it.\n";
-/**
- * Marker block used by \`mergeGlobalClaudeMemory\` to find and update the
- * CodeLoop section inside an existing \`~/.claude/CLAUDE.md\` without
- * clobbering anything else the user wrote there.
- */
-export declare const GLOBAL_CLAUDE_MEMORY_BEGIN = "<!-- BEGIN CODELOOP GLOBAL MEMORY -->";
-export declare const GLOBAL_CLAUDE_MEMORY_END = "<!-- END CODELOOP GLOBAL MEMORY -->";
+export * from "@codelooptech/shared/templates/global-rules";
 //# sourceMappingURL=global-rules.d.ts.map

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

@@ -1 +1 @@
-{"version":3,"file":"global-rules.d.ts","sourceRoot":"","sources":["../../src/templates/global-rules.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAEH,eAAO,MAAM,kBAAkB,40EAiD9B,CAAC;AAEF,eAAO,MAAM,oBAAoB,kuEA4ChC,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,+BAA+B,6nEAkC3C,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,0BAA0B,0CAA0C,CAAC;AAClF,eAAO,MAAM,wBAAwB,wCAAwC,CAAC"}
+{"version":3,"file":"global-rules.d.ts","sourceRoot":"","sources":["../../src/templates/global-rules.ts"],"names":[],"mappings":"AAAA,cAAc,6CAA6C,CAAC"}

package/dist/templates/global-rules.js

@@ -1,165 +1,2 @@
-/**
- * Global agent rules written by `npx codeloop init --global`.
- *
- * These ensure that once a user installs CodeLoop globally, every workspace
- * the agent opens — even brand-new ones — automatically:
- *   1. Discovers the CodeLoop MCP server (via global mcp.json registration).
- *   2. Bootstraps the project on first use via `codeloop_init_project`.
- *   3. Runs the verify → diagnose → gate_check loop after every code change.
- *
- * Distribution channel per agent:
- *   - Claude Code: `~/.claude/CLAUDE.md` (User Memory) is auto-loaded in every
- *     workspace by Claude Code, alongside any per-project `CLAUDE.md`.
- *   - Cursor: User Rules in Cursor live in the Settings UI (Cursor → Settings
- *     → Rules), NOT in `~/.cursor/rules/`. So we do two things:
- *       (a) write `~/.cursor/rules/codeloop.mdc` defensively in case Cursor
- *           ever supports user-level rule files;
- *       (b) save the same content to `~/.cursor/codeloop-user-rule.md` and
- *           print it during `init --global` for the user to paste into
- *           Cursor → Settings → Rules → User Rules. The MCP server is still
- *           globally available regardless, and its tool descriptions self-
- *           bootstrap any uninitialized workspace.
- */
-export const GLOBAL_CURSOR_RULE = `---
-description: CodeLoop — always-on verification across every Cursor workspace
-globs: ["**/*"]
-alwaysApply: true
----
-
-# CodeLoop is installed on this machine — use it in every workspace
-
-The CodeLoop MCP server is registered globally in \`~/.cursor/mcp.json\`.
-Its tools are available in every workspace you open. You MUST use them
-whenever you write or modify code.
-
-## On the first CodeLoop tool call in a workspace
-
-If \`.codeloop/config.json\` does not yet exist in the workspace root:
-
-1. Call \`codeloop_init_project\` FIRST (before \`codeloop_verify\` or any other tool).
-   It auto-creates \`.codeloop/config.json\`, agent rules, \`.gitignore\` entries,
-   and an \`artifacts/\` directory tailored to the detected project type.
-2. Then proceed with the normal verification loop below.
-
-The MCP server prepends a "[CodeLoop] This project has not been initialized"
-hint to every tool response in an uninitialized workspace. Treat that hint
-as an instruction, not a suggestion.
-
-## After every code change (every workspace, every project type)
-
-1. \`codeloop_verify\` — runs build, tests, and static analysis.
-2. If failures: \`codeloop_diagnose\` → fix the listed repair tasks → re-verify.
-   Loop automatically; do NOT ask the user between iterations.
-3. For UI projects: \`codeloop_capture_screenshot\` for every page, then
-   \`codeloop_visual_review\`. Then \`codeloop_start_recording\` →
-   \`codeloop_interact\` with every element → \`codeloop_stop_recording\` →
-   \`codeloop_interaction_replay\`.
-4. If \`designs/\` or \`.codeloop/figma.json\` exists, \`codeloop_design_compare\`
-   with \`mode: "all"\` is MANDATORY before \`gate_check\`.
-5. \`codeloop_gate_check\` — must return \`ready_for_review\` with confidence
-   >= 94 % and zero blocker gates. If it returns \`continue_fixing\`, loop
-   back to step 1 immediately; do NOT ask the user.
-6. \`codeloop_generate_dev_report\` — writes \`docs/DEVELOPMENT_LOG.md\`.
-
-## Never
-
-- Never declare a coding task complete without evidence from \`codeloop_gate_check\`.
-- Never skip \`codeloop_init_project\` in a fresh workspace just because the
-  project "looks small" — the bootstrap is fast and required.
-- Never skip the auto-fix loop after \`continue_fixing\`.
-- Never disable this rule per-project; project rules add to it, they do not
-  replace it.
-`;
-export const GLOBAL_CLAUDE_MEMORY = `# CodeLoop — always-on verification across every Claude Code workspace
-
-The CodeLoop MCP server is registered globally in \`~/.claude.json\`.
-Its tools are available in every workspace you open. You MUST use them
-whenever you write or modify code.
-
-## On the first CodeLoop tool call in a workspace
-
-If \`.codeloop/config.json\` does not yet exist in the workspace root:
-
-1. Call \`codeloop_init_project\` FIRST (before \`codeloop_verify\` or any other
-   CodeLoop tool). It auto-creates \`.codeloop/config.json\`, agent rules,
-   \`.gitignore\` entries, and an \`artifacts/\` directory tailored to the
-   detected project type.
-2. Then proceed with the normal verification loop below.
-
-The MCP server prepends a "[CodeLoop] This project has not been initialized"
-hint to every tool response in an uninitialized workspace. Treat that hint
-as an instruction, not a suggestion.
-
-## After every code change (every workspace, every project type)
-
-1. \`codeloop_verify\` — runs build, tests, and static analysis.
-2. If failures: \`codeloop_diagnose\` → fix the listed repair tasks → re-verify.
-   Loop automatically; do NOT ask the user between iterations.
-3. For UI projects: \`codeloop_capture_screenshot\` for every page, then
-   \`codeloop_visual_review\`. Then \`codeloop_start_recording\` →
-   \`codeloop_interact\` with every element → \`codeloop_stop_recording\` →
-   \`codeloop_interaction_replay\`.
-4. If \`designs/\` or \`.codeloop/figma.json\` exists, \`codeloop_design_compare\`
-   with \`mode: "all"\` is MANDATORY before \`gate_check\`.
-5. \`codeloop_gate_check\` — must return \`ready_for_review\` with confidence
-   >= 94 % and zero blocker gates. If it returns \`continue_fixing\`, loop
-   back to step 1 immediately; do NOT ask the user.
-6. \`codeloop_generate_dev_report\` — writes \`docs/DEVELOPMENT_LOG.md\`.
-
-## Never
-
-- Never declare a coding task complete without evidence from \`codeloop_gate_check\`.
-- Never skip \`codeloop_init_project\` in a fresh workspace just because the
-  project "looks small" — the bootstrap is fast and required.
-- Never skip the auto-fix loop after \`continue_fixing\`.
-- Never disable this guidance per-project; per-project \`CLAUDE.md\` adds to
-  it, it does not replace it.
-`;
-/**
- * Plain-text snippet a user pastes into Cursor → Settings → Rules → User Rules.
- * Same intent as \`GLOBAL_CURSOR_RULE\` but without the \`.mdc\` frontmatter
- * (Cursor's User Rules input box is a plain textarea).
- */
-export const GLOBAL_CURSOR_USER_RULE_SNIPPET = `CodeLoop is installed on this machine. The CodeLoop MCP server is registered globally in ~/.cursor/mcp.json, so its tools are available in EVERY workspace. You MUST use them whenever you write or modify code.
-
-ON THE FIRST CODELOOP TOOL CALL IN A WORKSPACE
-If \`.codeloop/config.json\` does not yet exist in the workspace root:
-1. Call \`codeloop_init_project\` FIRST (before \`codeloop_verify\` or any other tool).
-   It auto-creates \`.codeloop/config.json\`, agent rules, \`.gitignore\` entries,
-   and an \`artifacts/\` directory tailored to the detected project type.
-2. Then proceed with the verification loop below.
-The MCP server prepends a "[CodeLoop] This project has not been initialized" hint
-to every tool response in an uninitialized workspace. Treat that hint as an
-instruction, not a suggestion.
-
-AFTER EVERY CODE CHANGE (every workspace, every project type)
-1. \`codeloop_verify\` — runs build, tests, and static analysis.
-2. If failures: \`codeloop_diagnose\` → fix the listed repair tasks → re-verify.
-   Loop automatically; do NOT ask the user between iterations.
-3. For UI projects: \`codeloop_capture_screenshot\` for every page, then
-   \`codeloop_visual_review\`. Then \`codeloop_start_recording\` →
-   \`codeloop_interact\` with every element → \`codeloop_stop_recording\` →
-   \`codeloop_interaction_replay\`.
-4. If \`designs/\` or \`.codeloop/figma.json\` exists, \`codeloop_design_compare\`
-   with \`mode: "all"\` is MANDATORY before \`gate_check\`.
-5. \`codeloop_gate_check\` — must return \`ready_for_review\` with confidence
-   >= 94% and zero blocker gates. If it returns \`continue_fixing\`, loop back
-   to step 1 immediately; do NOT ask the user.
-6. \`codeloop_generate_dev_report\` — writes \`docs/DEVELOPMENT_LOG.md\`.
-
-NEVER
-- Never declare a coding task complete without evidence from \`codeloop_gate_check\`.
-- Never skip \`codeloop_init_project\` in a fresh workspace just because the
-  project "looks small" — the bootstrap is fast and required.
-- Never skip the auto-fix loop after \`continue_fixing\`.
-- Never disable this rule per-project; project rules add to it, they do not
-  replace it.
-`;
-/**
- * Marker block used by \`mergeGlobalClaudeMemory\` to find and update the
- * CodeLoop section inside an existing \`~/.claude/CLAUDE.md\` without
- * clobbering anything else the user wrote there.
- */
-export const GLOBAL_CLAUDE_MEMORY_BEGIN = "<!-- BEGIN CODELOOP GLOBAL MEMORY -->";
-export const GLOBAL_CLAUDE_MEMORY_END = "<!-- END CODELOOP GLOBAL MEMORY -->";
+export * from "@codelooptech/shared/templates/global-rules";
 //# sourceMappingURL=global-rules.js.map

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

@@ -1 +1 @@
-{"version":3,"file":"global-rules.js","sourceRoot":"","sources":["../../src/templates/global-rules.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAEH,MAAM,CAAC,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiDjC,CAAC;AAEF,MAAM,CAAC,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4CnC,CAAC;AAEF;;;;GAIG;AACH,MAAM,CAAC,MAAM,+BAA+B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkC9C,CAAC;AAEF;;;;GAIG;AACH,MAAM,CAAC,MAAM,0BAA0B,GAAG,uCAAuC,CAAC;AAClF,MAAM,CAAC,MAAM,wBAAwB,GAAG,qCAAqC,CAAC"}
+{"version":3,"file":"global-rules.js","sourceRoot":"","sources":["../../src/templates/global-rules.ts"],"names":[],"mappings":"AAAA,cAAc,6CAA6C,CAAC"}

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

@@ -1,32 +1,2 @@
-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;
-            };
-        };
-    };
-};
-/**
- * Returns MCP config with the actual API key value injected.
- * When apiKey is provided, writes the real key instead of the env placeholder.
- * This is critical for Claude Code which doesn't expand shell env vars in JSON.
- */
-export declare function getMcpConfig(apiKey?: string | null): {
-    mcpServers: Record<string, unknown>;
-};
-export declare const CLAUDE_PERMISSIONS_ALLOW: string[];
+export * from "@codelooptech/shared/templates/mcp-config";
 //# sourceMappingURL=mcp-config.d.ts.map

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

@@ -1 +1 @@
-{"version":3,"file":"mcp-config.d.ts","sourceRoot":"","sources":["../../src/templates/mcp-config.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,iBAAiB;;;;;;;;;;CAU7B,CAAC;AAEF,eAAO,MAAM,iBAAiB;;;;;;;;;;CAU7B,CAAC;AAEF;;;;GAIG;AACH,wBAAgB,YAAY,CAAC,MAAM,CAAC,EAAE,MAAM,GAAG,IAAI,GAAG;IAAE,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAA;CAAE,CAY5F;AAED,eAAO,MAAM,wBAAwB,UA2BpC,CAAC"}
+{"version":3,"file":"mcp-config.d.ts","sourceRoot":"","sources":["../../src/templates/mcp-config.ts"],"names":[],"mappings":"AAAA,cAAc,2CAA2C,CAAC"}

package/dist/templates/mcp-config.js

@@ -1,69 +1,2 @@
-export const CURSOR_MCP_CONFIG = {
-    mcpServers: {
-        codeloop: {
-            command: "npx",
-            args: ["-y", "codeloop-mcp-server"],
-            env: {
-                CODELOOP_API_KEY: "${CODELOOP_API_KEY}",
-            },
-        },
-    },
-};
-export const CLAUDE_MCP_CONFIG = {
-    mcpServers: {
-        codeloop: {
-            command: "npx",
-            args: ["-y", "codeloop-mcp-server"],
-            env: {
-                CODELOOP_API_KEY: "${CODELOOP_API_KEY}",
-            },
-        },
-    },
-};
-/**
- * Returns MCP config with the actual API key value injected.
- * When apiKey is provided, writes the real key instead of the env placeholder.
- * This is critical for Claude Code which doesn't expand shell env vars in JSON.
- */
-export function getMcpConfig(apiKey) {
-    return {
-        mcpServers: {
-            codeloop: {
-                command: "npx",
-                args: ["-y", "codeloop-mcp-server"],
-                env: {
-                    CODELOOP_API_KEY: apiKey || "${CODELOOP_API_KEY}",
-                },
-            },
-        },
-    };
-}
-export const CLAUDE_PERMISSIONS_ALLOW = [
-    "Bash(flutter *)",
-    "Bash(dart *)",
-    "Bash(npm *)",
-    "Bash(npx *)",
-    "Bash(node *)",
-    "Bash(git *)",
-    "Bash(brew *)",
-    "Bash(ffmpeg *)",
-    "Bash(ffprobe *)",
-    "Bash(screencapture *)",
-    "Bash(pod *)",
-    "Bash(mkdir *)",
-    "Bash(cp *)",
-    "Bash(mv *)",
-    "Bash(rm *)",
-    "Bash(cat *)",
-    "Bash(ls *)",
-    "Bash(which *)",
-    "Bash(curl *)",
-    "Bash(grep *)",
-    "Bash(find *)",
-    "Bash(head *)",
-    "Bash(tail *)",
-    "Bash(wc *)",
-    "Bash(echo *)",
-    "Bash(pwd)",
-];
+export * from "@codelooptech/shared/templates/mcp-config";
 //# sourceMappingURL=mcp-config.js.map

package/dist/templates/mcp-config.js.map

@@ -1 +1 @@
-{"version":3,"file":"mcp-config.js","sourceRoot":"","sources":["../../src/templates/mcp-config.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,iBAAiB,GAAG;IAC/B,UAAU,EAAE;QACV,QAAQ,EAAE;YACR,OAAO,EAAE,KAAK;YACd,IAAI,EAAE,CAAC,IAAI,EAAE,qBAAqB,CAAC;YACnC,GAAG,EAAE;gBACH,gBAAgB,EAAE,qBAAqB;aACxC;SACF;KACF;CACF,CAAC;AAEF,MAAM,CAAC,MAAM,iBAAiB,GAAG;IAC/B,UAAU,EAAE;QACV,QAAQ,EAAE;YACR,OAAO,EAAE,KAAK;YACd,IAAI,EAAE,CAAC,IAAI,EAAE,qBAAqB,CAAC;YACnC,GAAG,EAAE;gBACH,gBAAgB,EAAE,qBAAqB;aACxC;SACF;KACF;CACF,CAAC;AAEF;;;;GAIG;AACH,MAAM,UAAU,YAAY,CAAC,MAAsB;IACjD,OAAO;QACL,UAAU,EAAE;YACV,QAAQ,EAAE;gBACR,OAAO,EAAE,KAAK;gBACd,IAAI,EAAE,CAAC,IAAI,EAAE,qBAAqB,CAAC;gBACnC,GAAG,EAAE;oBACH,gBAAgB,EAAE,MAAM,IAAI,qBAAqB;iBAClD;aACF;SACF;KACF,CAAC;AACJ,CAAC;AAED,MAAM,CAAC,MAAM,wBAAwB,GAAG;IACtC,iBAAiB;IACjB,cAAc;IACd,aAAa;IACb,aAAa;IACb,cAAc;IACd,aAAa;IACb,cAAc;IACd,gBAAgB;IAChB,iBAAiB;IACjB,uBAAuB;IACvB,aAAa;IACb,eAAe;IACf,YAAY;IACZ,YAAY;IACZ,YAAY;IACZ,aAAa;IACb,YAAY;IACZ,eAAe;IACf,cAAc;IACd,cAAc;IACd,cAAc;IACd,cAAc;IACd,cAAc;IACd,YAAY;IACZ,cAAc;IACd,WAAW;CACZ,CAAC"}
+{"version":3,"file":"mcp-config.js","sourceRoot":"","sources":["../../src/templates/mcp-config.ts"],"names":[],"mappings":"AAAA,cAAc,2CAA2C,CAAC"}

package/dist/templates/specs.d.ts

@@ -1,4 +1,2 @@
-export declare const SPEC_TEMPLATE = "# Section: [Section Name]\n\n## Goal\n[What this section implements]\n\n## User Stories\n- As a [user type], I want to [action] so that [benefit]\n\n## Requirements\n- [ ] [Requirement 1]\n- [ ] [Requirement 2]\n- [ ] [Requirement 3]\n\n## UI/UX Notes\n[Design constraints, responsive behavior, states to handle]\n\n## Dependencies\n- Depends on: [list section IDs this depends on]\n- Shared services: [list any shared services this section uses or creates]\n\n## Out of Scope\n[What this section does NOT cover]\n";
-export declare const ACCEPTANCE_TEMPLATE = "# Acceptance Criteria: [Section Name]\n\n## Functional Criteria\n- [ ] [Criterion 1 \u2014 what the section must do]\n- [ ] [Criterion 2]\n- [ ] [Criterion 3]\n\n## Non-Functional Criteria\n- [ ] Loading states appear for async operations\n- [ ] Error states are handled with user-friendly messages\n- [ ] Responsive on mobile and desktop viewports\n- [ ] No critical accessibility issues\n\n## Test Evidence Required\n- [ ] Unit tests pass for core logic\n- [ ] Integration tests pass for key flows\n- [ ] Screenshots captured at configured viewports\n- [ ] No runtime errors in logs\n";
-export declare const UX_CHECKLIST_TEMPLATE = "# UX Checklist: [Section Name]\n\n## Visual Quality\n- [ ] Fonts render correctly at all sizes\n- [ ] Colors match design system tokens\n- [ ] Spacing is consistent with design grid\n- [ ] Icons are crisp and appropriately sized\n\n## Interaction\n- [ ] Buttons have hover and active states\n- [ ] Forms validate inline\n- [ ] Loading indicators appear for async actions\n- [ ] Error messages are clear and actionable\n\n## Responsiveness\n- [ ] Mobile (375px): layout adapts, no horizontal scroll\n- [ ] Tablet (768px): layout uses available space\n- [ ] Desktop (1440px): content is centered and readable\n\n## Accessibility\n- [ ] Color contrast meets WCAG AA\n- [ ] Touch targets are at least 44x44px\n- [ ] Interactive elements are keyboard-accessible\n- [ ] Screen reader labels are present\n";
+export * from "@codelooptech/shared/templates/specs";
 //# sourceMappingURL=specs.d.ts.map

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

@@ -1 +1 @@
-{"version":3,"file":"specs.d.ts","sourceRoot":"","sources":["../../src/templates/specs.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,aAAa,ugBAsBzB,CAAC;AAEF,eAAO,MAAM,mBAAmB,+kBAkB/B,CAAC;AAEF,eAAO,MAAM,qBAAqB,myBAwBjC,CAAC"}
+{"version":3,"file":"specs.d.ts","sourceRoot":"","sources":["../../src/templates/specs.ts"],"names":[],"mappings":"AAAA,cAAc,sCAAsC,CAAC"}

package/dist/templates/specs.js

@@ -1,68 +1,2 @@
-export const SPEC_TEMPLATE = `# Section: [Section Name]
-
-## Goal
-[What this section implements]
-
-## User Stories
-- As a [user type], I want to [action] so that [benefit]
-
-## Requirements
-- [ ] [Requirement 1]
-- [ ] [Requirement 2]
-- [ ] [Requirement 3]
-
-## UI/UX Notes
-[Design constraints, responsive behavior, states to handle]
-
-## Dependencies
-- Depends on: [list section IDs this depends on]
-- Shared services: [list any shared services this section uses or creates]
-
-## Out of Scope
-[What this section does NOT cover]
-`;
-export const ACCEPTANCE_TEMPLATE = `# Acceptance Criteria: [Section Name]
-
-## Functional Criteria
-- [ ] [Criterion 1 — what the section must do]
-- [ ] [Criterion 2]
-- [ ] [Criterion 3]
-
-## Non-Functional Criteria
-- [ ] Loading states appear for async operations
-- [ ] Error states are handled with user-friendly messages
-- [ ] Responsive on mobile and desktop viewports
-- [ ] No critical accessibility issues
-
-## Test Evidence Required
-- [ ] Unit tests pass for core logic
-- [ ] Integration tests pass for key flows
-- [ ] Screenshots captured at configured viewports
-- [ ] No runtime errors in logs
-`;
-export const UX_CHECKLIST_TEMPLATE = `# UX Checklist: [Section Name]
-
-## Visual Quality
-- [ ] Fonts render correctly at all sizes
-- [ ] Colors match design system tokens
-- [ ] Spacing is consistent with design grid
-- [ ] Icons are crisp and appropriately sized
-
-## Interaction
-- [ ] Buttons have hover and active states
-- [ ] Forms validate inline
-- [ ] Loading indicators appear for async actions
-- [ ] Error messages are clear and actionable
-
-## Responsiveness
-- [ ] Mobile (375px): layout adapts, no horizontal scroll
-- [ ] Tablet (768px): layout uses available space
-- [ ] Desktop (1440px): content is centered and readable
-
-## Accessibility
-- [ ] Color contrast meets WCAG AA
-- [ ] Touch targets are at least 44x44px
-- [ ] Interactive elements are keyboard-accessible
-- [ ] Screen reader labels are present
-`;
+export * from "@codelooptech/shared/templates/specs";
 //# sourceMappingURL=specs.js.map

package/dist/templates/specs.js.map

@@ -1 +1 @@
-{"version":3,"file":"specs.js","sourceRoot":"","sources":["../../src/templates/specs.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,aAAa,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsB5B,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;CAkBlC,CAAC;AAEF,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;CAwBpC,CAAC"}
+{"version":3,"file":"specs.js","sourceRoot":"","sources":["../../src/templates/specs.ts"],"names":[],"mappings":"AAAA,cAAc,sCAAsC,CAAC"}