cc-codeconductor 1.2.0 → 1.4.0

package/presets/cursor/agents/task-coach.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: true
 is_background: false
 ---
-# Agent Contract — task-coach v0.5.0
+# Agent Contract — task-coach v1.0.0
 
 ## Role
 

package/presets/cursor/agents/tester.md

@@ -5,7 +5,7 @@ model: "{{MODEL}}"
 readonly: false
 is_background: false
 ---
-# Agent Contract — tester v0.5.0
+# Agent Contract — tester v1.0.0
 
 ## Role
 

package/presets/cursor/commands/cc/api-contract.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the API contract workflow for public interface changes,
+  Run the API contract workflow for public interface changes,
   compatibility constraints, contract tests, documentation, and review.
 ---
 
@@ -82,3 +82,7 @@ Invoke the `reviewer` subagent via the Task tool.
 
 Block on missing contract tests, undocumented breaking changes, or docs/OpenAPI
 drift.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Recommend one CodeConductor slash command from a natural-language
+  Recommend one CodeConductor slash command from a natural-language
   problem. Does not start that workflow.
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Author BACKLOG.md — wayfinding, grilling, create or append items,
+  Author BACKLOG.md — wayfinding, grilling, create or append items,
   validate with openspec, and plan OpenSpec change folders for /cc-openspec.
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Re-explain the last deliverable in Task Card vocabulary when it did not land.
+  Re-explain the last deliverable in Task Card vocabulary when it did not land.
 ---
 
 # Clarify Workflow

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

@@ -85,3 +85,7 @@ If APPROVED (no CRITICAL findings):
 ## Completion
 
 Deliver the complete Council Verdict. The feature is only complete when tests pass and the council explicitly approves the implementation according to the specification.
+
+## Next
+
+Approved: merge. Blocked: return the findings to `/cc:fix` or `/cc:feature`.

package/presets/cursor/commands/cc/db-migration.md

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the database migration workflow for schema/data changes,
+  Run the database migration workflow for schema/data changes,
   operational sequencing, tests, and review.
 ---
 
@@ -83,3 +83,7 @@ Invoke the `reviewer` subagent via the Task tool.
 
 Block on missing migration tests, missing data-risk notes, undocumented
 deployment sequencing, or model/migration drift.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Map the repository and recommend the next CodeConductor slash command. Read-only.
+  Map the repository and recommend the next CodeConductor slash command. Read-only.
 ---
 
 # Explore Workflow

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the full feature workflow — task validation, technical design,
+  Run the full feature workflow — task validation, technical design,
   implementation, testing, review, and documentation.
 ---
 
@@ -10,6 +10,28 @@ Feature request: $ARGUMENTS
 
 ---
 
+## Web interface scope
+
+When the task concerns web layout, component states, feedback, motion, or a
+requested UI audit, apply skill `web-design-engineering` from the installed skill
+library. Use it during intake/discovery, design, test/implement, and review as
+applicable; keep this workflow’s gates and TDD order. Framework presence alone
+does not activate it; backend-only and native mobile work are excluded. Record
+required visual checks as pending when unavailable. Keep findings in the existing
+Review Report: contract failures in Spec Axis, technical issues in existing
+subchecks, and aesthetic preferences as suggestions; do not add an axis.
+
+## Android phone interface scope
+
+When the task concerns concrete Jetpack Compose phone layout, component states,
+interaction, accessibility, visual behavior, or a requested UI audit, apply skill
+`android-ui-design`. Use it during design, test/implementation, and review as
+applicable while keeping this workflow's gates and TDD order. Kotlin, Compose,
+framework, or dependency presence alone does not activate it; non-UI Android work
+stays with the general `android` skill. Audit-only requests remain read-only, and
+unavailable visual or emulator checks remain pending rather than claimed complete.
+
+
 ## Step 0 — CCEP Bootstrap
 
 Command: `feature` (fixed for this workflow — do not infer from user text)
@@ -153,3 +175,7 @@ Report the following:
 
 The feature is complete only when: all tests pass, no CRITICAL review findings
 remain, and documentation reflects the implemented behavior.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the bug fix workflow — risk-based routing through task
+  Run the bug fix workflow — risk-based routing through task
   validation, implementation, testing, and optional review.
 ---
 
@@ -18,6 +18,28 @@ Provide the following information in $ARGUMENTS:
 
 ---
 
+## Web interface scope
+
+When the task concerns web layout, component states, feedback, motion, or a
+requested UI audit, apply skill `web-design-engineering` from the installed skill
+library. Use it during intake/discovery, design, test/implement, and review as
+applicable; keep this workflow’s gates and TDD order. Framework presence alone
+does not activate it; backend-only and native mobile work are excluded. Record
+required visual checks as pending when unavailable. Keep findings in the existing
+Review Report: contract failures in Spec Axis, technical issues in existing
+subchecks, and aesthetic preferences as suggestions; do not add an axis.
+
+## Android phone interface scope
+
+When the task concerns concrete Jetpack Compose phone layout, component states,
+interaction, accessibility, visual behavior, or a requested UI audit, apply skill
+`android-ui-design`. Use it during design, test/implementation, and review as
+applicable while keeping this workflow's gates and TDD order. Kotlin, Compose,
+framework, or dependency presence alone does not activate it; non-UI Android work
+stays with the general `android` skill. Audit-only requests remain read-only, and
+unavailable visual or emulator checks remain pending rather than claimed complete.
+
+
 ## Step 0 — CCEP Bootstrap
 
 Command: `fix` (fixed for this workflow — do not infer from user text)
@@ -163,3 +185,7 @@ passes, and no CRITICAL review findings remain.
 
 Skills: `testing-tdd`, `evaluation`. Record `scorecard create --from-diff`.
 A small fix still needs a Task Card and a failing regression test first.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Compact the session into gitignored `.codeconductor/sessions/handoff.md` (redact secrets).
+  Compact the session into gitignored `.codeconductor/sessions/handoff.md` (redact secrets).
 ---
 
 # Handoff Workflow

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the advanced iterative workflow — Wayfinding AST discovery,
+  Run the advanced iterative workflow — Wayfinding AST discovery,
   Relentless Grilling, contract and spec design, TDD, council review, and docs.
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run OpenSpec backlog delivery — validate BACKLOG.md, plan TaskCards,
+  Run OpenSpec backlog delivery — validate BACKLOG.md, plan TaskCards,
   orchestrate agents by phase, review gate, and update backlog state.
 ---
 
@@ -14,6 +14,28 @@ Orchestrate FIFO delivery from `BACKLOG.md`. CodeConductor owns planning; agents
 
 ---
 
+## Web interface scope
+
+When the task concerns web layout, component states, feedback, motion, or a
+requested UI audit, apply skill `web-design-engineering` from the installed skill
+library. Use it during intake/discovery, design, test/implement, and review as
+applicable; keep this workflow’s gates and TDD order. Framework presence alone
+does not activate it; backend-only and native mobile work are excluded. Record
+required visual checks as pending when unavailable. Keep findings in the existing
+Review Report: contract failures in Spec Axis, technical issues in existing
+subchecks, and aesthetic preferences as suggestions; do not add an axis.
+
+## Android phone interface scope
+
+When the task concerns concrete Jetpack Compose phone layout, component states,
+interaction, accessibility, visual behavior, or a requested UI audit, apply skill
+`android-ui-design`. Use it during design, test/implementation, and review as
+applicable while keeping this workflow's gates and TDD order. Kotlin, Compose,
+framework, or dependency presence alone does not activate it; non-UI Android work
+stays with the general `android` skill. Audit-only requests remain read-only, and
+unavailable visual or emulator checks remain pending rather than claimed complete.
+
+
 ## Step 0 — CCEP Bootstrap
 
 Command: `openspec` (fixed for this workflow — do not infer from user text)

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Disposable spike in an isolated worktree. Not a merge candidate.
+  Disposable spike in an isolated worktree. Not a merge candidate.
 ---
 
 # Prototype Workflow

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the refactor workflow — mandatory architectural justification,
+  Run the refactor workflow — mandatory architectural justification,
   test verification, risk-based implementation, and scope enforcement.
 ---
 
@@ -158,3 +158,7 @@ and after, Review Report (if applicable).
 The refactor is complete only when: all pre-existing tests still pass, the
 implementation matches the approved plan exactly, and no CRITICAL review
 findings remain.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run a structured code review — produces a Review Report with
+  Run a structured code review — produces a Review Report with
   CRITICAL, WARNING, and SUGGESTION findings; CRITICAL findings block merge.
 ---
 
@@ -17,6 +17,28 @@ Specify what to review. Accepted formats:
 
 ---
 
+## Web interface scope
+
+When the task concerns web layout, component states, feedback, motion, or a
+requested UI audit, apply skill `web-design-engineering` from the installed skill
+library. Use it during intake/discovery, design, test/implement, and review as
+applicable; keep this workflow’s gates and TDD order. Framework presence alone
+does not activate it; backend-only and native mobile work are excluded. Record
+required visual checks as pending when unavailable. Keep findings in the existing
+Review Report: contract failures in Spec Axis, technical issues in existing
+subchecks, and aesthetic preferences as suggestions; do not add an axis.
+
+## Android phone interface scope
+
+When the task concerns concrete Jetpack Compose phone layout, component states,
+interaction, accessibility, visual behavior, or a requested UI audit, apply skill
+`android-ui-design`. Use it during design, test/implementation, and review as
+applicable while keeping this workflow's gates and TDD order. Kotlin, Compose,
+framework, or dependency presence alone does not activate it; non-UI Android work
+stays with the general `android` skill. Audit-only requests remain read-only, and
+unavailable visual or emulator checks remain pending rather than claimed complete.
+
+
 ## Step 0 — CCEP Bootstrap
 
 Command: `review` (fixed for this workflow — do not infer from user text)
@@ -147,3 +169,7 @@ npx cc-codeconductor scorecard regression
 ```
 
 Map merge recommendation to scorecard verdict. Record outcome for trend tracking.
+
+## Next
+
+Approved: merge. Blocked: return the findings to `/cc:fix` or `/cc:feature`.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Evaluate deliverable quality — scorecard, outcome tracking, regression
+  Evaluate deliverable quality — scorecard, outcome tracking, regression
   checklist, and aggregate stats.
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run the authorized defensive security workflow — domain
+  Run the authorized defensive security workflow — domain
   security-* skills, authorization gate, risk-based routing, hardening, and review.
 ---
 
@@ -177,3 +177,7 @@ resolved.
 Report: Task Card, Implementation Summary, regression test added, Review Report
 (if applicable). The task is complete only when: the regression test passes, the
 full suite passes, and no CRITICAL review findings remain.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Spec-locked TDD with a mutation-testing gate — refine the intent
+  Spec-locked TDD with a mutation-testing gate — refine the intent
   into an immutable Gherkin contract (SHA-256 frozen), implement under the
   three laws of TDD, pass a judge audit, and merge only if every mutant dies.
 ---
@@ -188,3 +188,7 @@ The orchestrator keeps a persistent counter per Task Card. If the
 - [ ] Judge verdict PASS (compile clean, traceability complete, scope clean).
 - [ ] Mutation runner exits 0 with `total_mutants_killed == total_points`.
 - [ ] Scorecard records the kill rate and iteration count (≤ 3).
+
+## Next
+
+Run `/cc:review` on the diff before merging.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Run a structured Red-Green-Refactor TDD cycle — write a failing
+  Run a structured Red-Green-Refactor TDD cycle — write a failing
   test first, implement the minimum code to pass it, then refactor with the
   suite green.
 ---

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Generate a structured test plan for a feature or module — covers
+  Generate a structured test plan for a feature or module — covers
   unit, integration, contract, and edge cases without writing implementation code.
 ---
 
@@ -148,3 +148,7 @@ Deliver the complete Test Plan document. Save it as
 
 This command produces a plan, not test files. No production code and no test
 code is written during this command.
+
+## Next
+
+Implement against this plan with `/cc:tdd-cycle` or `/cc:feature`.

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  [cc: alias] Classify a request into type, risk, and the destination CodeConductor command.
+  Classify a request into type, risk, and the destination CodeConductor command.
 ---
 
 # Triage Workflow

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

@@ -1,6 +1,5 @@
 ---
 id: android
-version: 1.0.0
 name: Android + Kotlin (Jetpack Compose & Media3)
 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.
@@ -39,6 +38,10 @@ paths:
 
 This playbook defines the architecture, UI design system, performance guidelines, and testing strategy for native Android applications.
 
+`android-ui-design` owns specialized Jetpack Compose phone UI/UX design,
+implementation, review, and audit guidance. This skill remains the general guide
+for architecture, Hilt dependency injection, Media3, performance, and testing.
+
 ---
 
 ## 1. Lead Architect & Modularization

package/presets/cursor/skills/android-ui-design/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: android-ui-design
+description: >-
+  Design, implement, review, and audit Android Jetpack Compose UI/UX for phone
+  interfaces. Use when a request concerns concrete Compose layout, components,
+  interaction, accessibility, or visual behavior. Do not activate for framework
+  or dependency presence alone; non-UI Android work is excluded.
+---
+
+# Android UI design
+
+Apply this specialized guidance to Android phone interfaces built with Jetpack
+Compose. Keep the active `cc-feature`, `cc-fix`, `cc-review`, or `cc-openspec`
+workflow and its gates; this skill contributes UI/UX criteria, not a separate
+workflow. Use the general `android` skill for architecture, dependency injection,
+Media3, performance, testing, and other non-UI Android engineering.
+
+## Intake and boundaries
+
+Identify the user goal, phone surface, affected interaction, supported Android
+versions, and observable outcomes. Inspect the existing Compose components,
+design tokens, navigation conventions, installed versions, tests, previews, and
+available emulator or device tooling before proposing changes.
+
+Preserve the established product visual system, including its components, color,
+type, shape, spacing, and motion tokens. Material 3 is advisory guidance, not a
+mandate to replace a deliberate product language. Suggest Material 3 changes with
+their accessibility or usability benefit and wait for scope approval when they
+would alter the visual direction.
+
+The initial scope is phones. Do not invent tablet, foldable, desktop, or wearable
+layouts. Still account for phone portrait and landscape orientation, window size
+changes, display cutouts, system bars, and the soft keyboard or IME.
+
+## Design mode
+
+Turn the request into a small interaction contract before implementation:
+
+- Define hierarchy, content, spacing, phone layout, scroll and overflow behavior,
+  navigation, focus entry and return, gestures, and predictive back behavior.
+- Specify applicable default, pressed, focused, disabled, pending or loading,
+  empty, success, error or failure, and offline states. State what changes and
+  what the user can do next; never imply success before it is known.
+- Name the state owner. Prefer state hoisting, a single source of truth, and
+  unidirectional data flow (UDF); keep transient visual state local only when no
+  external owner needs to observe or control it.
+- Design edge-to-edge intentionally with WindowInsets and system bars. Define IME
+  resize, pan, focus, dismissal, and restoration behavior for editable surfaces.
+- Require at least 48dp touch targets, meaningful semantics, TalkBack labels and
+  actions, logical traversal or focus order, sufficient contrast, and usable font
+  scaling without clipped or hidden actions.
+- Add motion only when it has a purpose such as continuity, spatial orientation,
+  feedback, or state change. Define start/end state, interruption, cancellation
+  or reversal, repeated or rapid input, and reduced-motion or reduced-animation
+  behavior that preserves essential information.
+
+Use existing components and platform/Compose primitives before adding code or a
+dependency. When alternatives are requested, compare only scoped options and make
+the product-system and Material 3 tradeoffs explicit.
+
+## Implementation mode
+
+Implement the accepted contract without expanding the visual language. Keep
+composables focused, pass immutable UI state and event callbacks, and preserve
+unidirectional data flow. Hoist state to the lowest common owner that needs to
+read or write it. Do not duplicate navigation, loading, or failure truth across
+the composition.
+
+Prefer semantic Material/Compose controls over raw pointer input. When a custom
+gesture is necessary, preserve accessible actions, minimum touch targets, visual
+feedback, cancellation, and interoperability with scrolling. Consume insets once
+at the correct boundary and verify that edge-to-edge content and IME transitions
+do not obscure controls.
+
+Write tests for observable behavior and state outcomes rather than modifier or
+implementation details. Cover the relevant state transition, duplicate or rapid
+input, disabled behavior, semantics, navigation/back behavior, and state
+restoration. Use previews as design aids, not as proof of runtime interaction.
+
+## Review mode
+
+Review the agreed surface against the interaction contract and existing Review
+Report rules. Each finding needs a location, reproduction or evidence, user
+impact, and proposed resolution. Treat contract and accessibility failures as
+defects; classify unsupported aesthetic preferences as suggestions. Do not create
+a new review axis or elevate a Material 3 preference over the product system.
+
+Check state completeness, TalkBack semantics and traversal, 48dp touch targets,
+contrast and font scaling, focus/IME behavior, edge-to-edge insets, gestures,
+predictive back, orientation changes, state ownership/UDF, motion interruption,
+reduced animation, and rapid repeated interaction as applicable.
+
+## Audit mode
+
+A requested audit is read-only. Inspect only the agreed Compose phone surface and
+report prioritized, evidence-backed findings; an audit is not permission to edit,
+implement, modify, or automatically fix the UI. Keep out-of-scope improvements as
+suggestions and create backlog work only when requested through the existing
+workflow.
+
+Distinguish code inspection, semantics tests, screenshots, and live emulator or
+device interaction because they prove different things. If required visual,
+emulator, or device evidence is unavailable, mark that validation pending with
+the surface, steps, expected result, and limitation. Do not claim visual
+validation or a completed acceptance criterion without executing the check.
+
+## Evidence and delivery
+
+Report the observable outcomes checked, commands or tools used, results, and
+limitations. A screenshot cannot prove TalkBack traversal, gesture interruption,
+IME recovery, predictive back, or repeated-input behavior. Prefer a real phone or
+phone emulator for those checks; otherwise leave precise pending verification.
+
+Primary Android references: [Compose semantics](https://developer.android.com/develop/ui/compose/accessibility/semantics),
+[accessibility defaults](https://developer.android.com/develop/ui/compose/accessibility/api-defaults),
+[state and hoisting](https://developer.android.com/develop/ui/compose/state),
+[window insets](https://developer.android.com/develop/ui/compose/system/insets),
+[predictive back](https://developer.android.com/develop/ui/compose/system/predictive-back),
+and [Compose accessibility testing](https://developer.android.com/develop/ui/compose/accessibility/testing).

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

@@ -1,6 +1,5 @@
 ---
 id: api-versioning
-version: 1.0.0
 name: API Versioning
 description: >
   Provides expert knowledge for designing, implementing, and managing REST API

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

@@ -1,6 +1,5 @@
 ---
 id: astro
-version: 1.0.0
 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,5 @@
 ---
 id: auth-token-inspector
-version: 1.0.0
 name: Auth Token Inspector
 description: >
   Audits token storage mechanisms to prevent XSS-based JWT theft.

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

@@ -1,6 +1,5 @@
 ---
 id: code-review
-version: 1.0.0
 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,5 @@
 ---
 id: django-orm
-version: 1.0.0
 name: Django ORM
 description: >
   Django ORM patterns for multi-tenant POS projects: efficient queries,

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

@@ -1,6 +1,5 @@
 ---
 id: django-testing
-version: 1.0.0
 name: Django Testing
 description: >
   Testing patterns for multi-tenant Django POS projects using pytest-django,

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

@@ -1,6 +1,5 @@
 ---
 id: django-uv
-version: 1.0.0
 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,5 @@
 ---
 id: drizzle-schema-architect
-version: 1.0.0
 name: Drizzle Schema Architect
 description: >
   Generates strictly typed Drizzle ORM schemas for PostgreSQL with indexes, 

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

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

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

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

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

@@ -1,6 +1,5 @@
 ---
 id: jpa-postgres
-version: 1.0.0
 name: JPA + PostgreSQL
 description: >
   Provides expert knowledge of JPA entity design, relationship mapping, Flyway

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

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

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

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