cc-codeconductor 1.4.2 → 1.5.1

package/presets/cursor/commands/cc/fix.md

@@ -44,11 +44,10 @@ unavailable visual or emulator checks remain pending rather than claimed complet
 
 Command: `fix` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command fix "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command fix "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile fix --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command fix --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile fix --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command fix --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command fix --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
    Canonical delivery order is test-before-implement whenever both phases apply.
 
 ---

package/presets/cursor/commands/cc/handoff.md

@@ -11,11 +11,10 @@ Handoff request: $ARGUMENTS
 
 Command: `handoff` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command handoff "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command handoff "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile handoff --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command handoff --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile handoff --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command handoff --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command handoff --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 
@@ -34,6 +33,10 @@ pass/fail (not log dumps), open questions, the next `/cc:` command, plus links
 to the Delivery Ledger and verification evidence when they exist. Do not repeat
 the original request or transcript.
 
+If a Delivery Ledger exists, run `npx cc-codeconductor odd handoff --id <ledger-id> --output json`
+and use its `handoff` envelope as the source for these fields. Secret redaction
+still applies.
+
 Do not edit source or tests.
 
 ---

package/presets/cursor/commands/cc/iterative.md

@@ -14,11 +14,10 @@ Iterative request: $ARGUMENTS
 
 Command: `iterative` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command iterative "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command iterative "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile iterative --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command iterative --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile iterative --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command iterative --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command iterative --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
    Canonical delivery order is test-before-implement whenever both phases apply.
 
 ---

package/presets/cursor/commands/cc/odd.md

@@ -7,11 +7,12 @@ description: Create or resume an opt-in Delivery Ledger for substantial authoriz
 ## Step 0 — CCEP Bootstrap
 
 ```bash
-bun run dev ccep parse --command odd "$ARGUMENTS"
-bun run dev ccep resolve --command odd "$ARGUMENTS"
-bun run dev ccep profile --command odd
+bun run dev ccep profile odd --output json
+bun run dev ccep compile --command odd --phase <phase-id> "$ARGUMENTS" --view prompt --output json
 ```
 
+Pass each subagent only the compiled `prompt` for its phase.
+
 Create a ledger only after authorization and tracked coordination. Read-only and small work do not create state.
 
 When ODD has verification evidence, include its RDD receipt in the ledger

package/presets/cursor/commands/cc/openspec.md

@@ -40,11 +40,10 @@ unavailable visual or emulator checks remain pending rather than claimed complet
 
 Command: `openspec` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command openspec "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command openspec "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile openspec --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command openspec --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile openspec --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command openspec --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command openspec --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
    Canonical delivery order is test-before-implement whenever both phases apply.
 
 ---
@@ -155,7 +154,7 @@ For each pending TaskCard, run:
 npx cc-codeconductor openspec next
 ```
 
-Invoke the agent named on the card with **isolated** context (`/clear` between phases unless continuation is required):
+Invoke the agent named on the card as a subagent with **isolated** context (subagents already start fresh; do not `/clear` the main session between phases):
 
 | Phase | Agent | Role |
 |-------|-------|------|
@@ -211,4 +210,4 @@ Report completion: Task Cards executed, scorecard verdict, change folder path, f
 
 ## Skill
 
-Apply `.claude/skills/openspec/SKILL.md` for backlog format rules and state transitions.
+Apply `.cursor/skills/openspec/SKILL.md` for backlog format rules and state transitions.

package/presets/cursor/commands/cc/pagespeed.md

@@ -8,11 +8,10 @@ Produces a prioritized report in the current working directory.
 
 Command: `pagespeed` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command pagespeed "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command pagespeed "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile pagespeed --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command pagespeed --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile pagespeed --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command pagespeed --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command pagespeed --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 
@@ -63,9 +62,8 @@ the following steps in order:
    the output filename: `{YYYY-MM-DD}_pagespeed-{hostname}-claude.md`.
 
 2. **Collect** — Call the PageSpeed Insights API for the requested strategy
-   (`mobile`, `desktop`, or `both`). Prefer the Bun scripts in
-   `~/.claude/skills/pagespeed-perf/scripts/run.ts` if Bun is available.
-   Otherwise, use `WebFetch` to call the PSI endpoint directly.
+   (`mobile`, `desktop`, or `both`) using `WebFetch` to call the PSI endpoint
+   directly.
 
 3. **Analyze** — Extract Core Web Vitals (LCP, INP, CLS, FCP, TTFB, TBT),
    identify the LCP element, enumerate third-party scripts by blocking time,

package/presets/cursor/commands/cc/prototype.md

@@ -11,11 +11,10 @@ Prototype request: $ARGUMENTS
 
 Command: `prototype` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command prototype "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command prototype "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile prototype --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command prototype --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile prototype --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command prototype --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command prototype --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 

package/presets/cursor/commands/cc/refactor.md

@@ -37,11 +37,10 @@ If coverage is insufficient:
 
 Command: `refactor` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command refactor "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command refactor "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile refactor --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command refactor --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile refactor --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command refactor --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command refactor --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 

package/presets/cursor/commands/cc/review.md

@@ -43,11 +43,10 @@ unavailable visual or emulator checks remain pending rather than claimed complet
 
 Command: `review` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command review "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command review "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile review --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command review --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile review --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command review --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command review --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 
@@ -113,6 +112,37 @@ Evaluate the diff against the following checklist:
 
 ---
 
+## Severity Rubric
+
+Classify every finding using these concrete anchors — not general judgment —
+so the same finding gets the same category on any run.
+
+**CRITICAL** (always):
+
+- Unauthenticated access to a protected resource
+- Injection (SQL, command, XSS) reachable from untrusted input
+- A secret or credential present in the diff
+- A destructive operation with no confirmation
+- The build or test suite is broken
+- A direct contradiction of an explicit acceptance criterion
+
+**WARNING**:
+
+- Missing test for a new branch or edge case
+- An error is silently swallowed — no log, no propagation
+- A change outside the declared scope
+- Inconsistent with an established pattern already in the module
+- Missing input validation in an internal function (not exposed at a trust boundary)
+
+**SUGGESTION**:
+
+- Style or naming
+- Minor readability
+- Speculative refactor that wasn't requested
+- Non-blocking micro-optimization
+
+---
+
 ## Step 3 — Review Report
 
 Produce a structured Review Report with findings in three categories:

package/presets/cursor/commands/cc/scorecard.md

@@ -14,11 +14,10 @@ Scope: $ARGUMENTS
 
 Command: `scorecard` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command scorecard "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command scorecard "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile scorecard --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command scorecard --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile scorecard --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command scorecard --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command scorecard --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 

package/presets/cursor/commands/cc/security.md

@@ -47,11 +47,10 @@ payloads, malware, or attack procedures.
 
 Command: `security` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command security "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command security "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile security --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command security --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile security --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command security --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command security --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
    Canonical delivery order is test-before-implement whenever both phases apply.
 
 ---
@@ -62,7 +61,7 @@ If `graphify-out/graph.json` exists, run `graphify query "$ARGUMENTS"` (and
 `graphify path` / `graphify explain` when needed). Then invoke `repo-explorer`
 to map modules, conventions, and impact radius. Do not write code in this step.
 Record a Repo Map artifact before intake. Load the matching `security-*` skill
-for the named domain (see `.claude/skills/security-*/SKILL.md`). Keep the OWASP
+for the named domain (see `.cursor/skills/security-*/SKILL.md`). Keep the OWASP
 `security` skill for application-security reviews.
 
 ---

package/presets/cursor/commands/cc/spec-mutation.md

@@ -22,11 +22,10 @@ Describe what behavior you want to implement. Include:
 
 Command: `spec-mutation` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command spec-mutation "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command spec-mutation "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile spec-mutation --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command spec-mutation --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile spec-mutation --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command spec-mutation --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command spec-mutation --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
    Canonical delivery order is test-before-implement whenever both phases apply.
 
 ---

package/presets/cursor/commands/cc/tdd-cycle.md

@@ -22,11 +22,10 @@ Describe what behavior you want to implement. Include:
 
 Command: `tdd-cycle` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command tdd-cycle "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command tdd-cycle "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile tdd-cycle --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command tdd-cycle --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile tdd-cycle --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command tdd-cycle --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command tdd-cycle --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
    Canonical delivery order is test-before-implement whenever both phases apply.
 
 ---

package/presets/cursor/commands/cc/test-plan.md

@@ -24,11 +24,10 @@ proceeding.
 
 Command: `test-plan` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command test-plan "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command test-plan "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile test-plan --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command test-plan --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile test-plan --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command test-plan --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command test-plan --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 

package/presets/cursor/commands/cc/triage.md

@@ -11,11 +11,10 @@ Triage request: $ARGUMENTS
 
 Command: `triage` (fixed for this workflow — do not infer from user text)
 
-1. Run: `npx cc-codeconductor ccep parse --command triage "$ARGUMENTS" --output json`
-2. Run: `npx cc-codeconductor ccep resolve --command triage "$ARGUMENTS" --output json`
-3. Run: `npx cc-codeconductor ccep profile triage --output json`
-4. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command triage --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
-5. Delegate to subagents using compiled CCEP prompts — never forward raw `$ARGUMENTS` to planners.
+1. Run: `npx cc-codeconductor ccep profile triage --output json` to get the phases and their roles.
+2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command triage --phase <phase-id> "$ARGUMENTS" --view prompt --output json`
+3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command triage --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.
+4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `$ARGUMENTS` to planners.
 
 ---
 

package/presets/cursor/skills/android/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: android
-name: Android + Kotlin (Jetpack Compose & Media3)
+name: android
 description: >
   Provides expert knowledge for building modern native Android apps using Kotlin, Jetpack Compose, Material Design 3, MVI architecture, Hilt dependency injection, and Media3/ExoPlayer.
 

package/presets/cursor/skills/api-versioning/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: api-versioning
-name: API Versioning
+name: api-versioning
 description: >
   Provides expert knowledge for designing, implementing, and managing REST API
   versioning strategies with deprecation workflows.
@@ -39,6 +39,7 @@ quality:
   reviewed_by: codeconductor-core
   version: 0.1.0
 ---
+
 # API Versioning
 
 ## Versioning Strategies

package/presets/cursor/skills/astro/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: astro
-name: Astro
+name: astro
 description: >
   Provides expert knowledge for building Astro 5+ sites with Islands Architecture, Content Collections, TypeScript, and performance-first rendering strategies.
 

package/presets/cursor/skills/auth-token-inspector/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: auth-token-inspector
-name: Auth Token Inspector
+name: auth-token-inspector
 description: >
   Audits token storage mechanisms to prevent XSS-based JWT theft.
 user-invokable: true

package/presets/cursor/skills/code-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: code-review
-name: Code Review
+name: code-review
 description: >
   Provides a structured framework for conducting thorough code reviews covering correctness, security, architecture alignment, performance, and technical debt.
 

package/presets/cursor/skills/django-orm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: django-orm
-name: Django ORM
+name: django-orm
 description: >
   Django ORM patterns for multi-tenant POS projects: efficient queries,
   bulk operations, transactions, and multi-schema upload paths.
@@ -40,9 +40,8 @@ outputs:
 quality:
   reviewed_by: codeconductor-core
   version: 0.1.0
-paths:
-  - "**/*.py"
 ---
+
 ## When to Use
 
 - Writing or reviewing queryset code in any `apps/*/`
@@ -458,5 +457,4 @@ def on_order_save(sender, instance, created, **kwargs):
 - **Annotation examples**: `apps/pos/views.py` lines 59-75
 - **Exists usage**: `apps/catalog/views.py` line 112
 - **Upload paths**: `apps/catalog/models.py`
-- **Django ORM docs**:
-  <https://docs.djangoproject.com/en/5.2/topics/db/queries/>
+- **Django ORM docs**: https://docs.djangoproject.com/en/5.2/topics/db/queries/

package/presets/cursor/skills/django-testing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: django-testing
-name: Django Testing
+name: django-testing
 description: >
   Testing patterns for multi-tenant Django POS projects using pytest-django,
   RequestFactory, and mocks. No factories, no complex conftest.

package/presets/cursor/skills/django-uv/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: django-uv
-name: Django + UV
+name: django-uv
 description: >
   Provides expert knowledge for building Django 5+ projects with UV as the package manager, domain-driven app structure, ruff for linting, and pytest-django for testing.
 

package/presets/cursor/skills/drizzle-schema-architect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: drizzle-schema-architect
-name: Drizzle Schema Architect
+name: drizzle-schema-architect
 description: >
   Generates strictly typed Drizzle ORM schemas for PostgreSQL with indexes, 
   foreign keys, and Zod schema deduction.

package/presets/cursor/skills/fastapi-pydantic-strict/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: fastapi-pydantic-strict
-name: FastAPI Pydantic Strict
+name: fastapi-pydantic-strict
 description: >
   Enforces Pydantic v2 strict models, asynchronous dependency generators, and uv environment setup.
 user-invokable: true

package/presets/cursor/skills/jpa-nplusone-detector/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: jpa-nplusone-detector
-name: JPA N+1 Query Detector
+name: jpa-nplusone-detector
 description: >
   Audits Hibernate database interactions to prevent N+1 query problems in JVM apps.
 user-invokable: true

package/presets/cursor/skills/jpa-postgres/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: jpa-postgres
-name: JPA + PostgreSQL
+name: jpa-postgres
 description: >
   Provides expert knowledge of JPA entity design, relationship mapping, Flyway
   migrations, and PostgreSQL-specific optimizations.
@@ -40,10 +40,8 @@ outputs:
 quality:
   reviewed_by: codeconductor-core
   version: 0.1.0
-paths:
-  - "**/*.kt"
-  - "**/*.java"
 ---
+
 # JPA + PostgreSQL
 
 ## Entity Design

package/presets/cursor/skills/livewire-alpine-bridge/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: livewire-alpine-bridge
-name: Livewire Alpine Bridge
+name: livewire-alpine-bridge
 description: >
   Schedules reactive frontend states cleanly using entangle directives in PHP and JS.
 user-invokable: true

package/presets/cursor/skills/nextjs-typescript/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: nextjs-typescript
-name: Next.js + TypeScript
+name: nextjs-typescript
 description: >
   Provides expert knowledge for building Next.js 15+ applications with the App Router, TypeScript, Server Components, Server Actions, and TanStack Query.
 

package/presets/cursor/skills/pagespeed-perf/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: pagespeed-perf
-name: PageSpeed Performance Audit
+name: pagespeed-perf
 description: >
   Web Performance Engineering — analyzes Core Web Vitals using the PageSpeed
   Insights API (PSI v5) and applies the 80/20 principle: identify the 20% of

package/presets/cursor/skills/python/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: python
-name: Python
+name: python
 description: >
   Python development best practices: clean code, patterns,
   type hints, decorators, context managers, and architecture.
@@ -39,9 +39,8 @@ outputs:
 quality:
   reviewed_by: codeconductor-core
   version: 0.1.0
-paths:
-  - "**/*.py"
 ---
+
 ## When to Use
 
 - Writing any Python code in the project
@@ -606,7 +605,7 @@ items = items_to_keep
 
 ## Resources
 
-- **PEP 8** — Style Guide: <https://peps.python.org/pep-0008/>
-- **PEP 484** — Type Hints: <https://peps.python.org/pep-0484/>
-- **Real Python**: <https://realpython.com/>
-- **Python Docs**: <https://docs.python.org/3/>
+- **PEP 8** — Style Guide: https://peps.python.org/pep-0008/
+- **PEP 484** — Type Hints: https://peps.python.org/pep-0484/
+- **Real Python**: https://realpython.com/
+- **Python Docs**: https://docs.python.org/3/

package/presets/cursor/skills/python-django-stack/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: python-django-stack
-name: Python Django Stack
+name: python-django-stack
 description: >
   Python and Django conventions for multi-tenant SaaS POS projects:
   views, services, naming, JSON APIs, PDFs, and cart patterns.

package/presets/cursor/skills/python-fastapi-stack/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: python-fastapi-stack
-name: Python FastAPI Stack
+name: python-fastapi-stack
 description: >
   FastAPI conventions for REST APIs: routers, Pydantic v2 schemas, dependency
   injection, error handling, pagination, and project structure.

package/presets/cursor/skills/security/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: security
-name: Security
+name: security
 description: >
   Provides expert knowledge for implementing and reviewing application security following OWASP Top 10 (2021), with stack-specific patterns for Spring Boot, Django, Next.js, and Astro.
 

package/presets/cursor/skills/seo-analytics-injector/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: seo-analytics-injector
-name: SEO Analytics Injector
+name: seo-analytics-injector
 description: >
   Verifies and injects Google Tag Manager (GTM), GA4 event triggers, and optimized meta tags.
 user-invokable: true

package/presets/cursor/skills/spring-auth-auditor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 id: spring-auth-auditor
-name: Spring Auth Auditor
+name: spring-auth-auditor
 description: >
   Secures Spring Security filters, JWT validations, OAuth2 setups, and CORS/CSRF headers.
 user-invokable: true