cc-codeconductor 1.2.0 → 1.4.0

package/presets/agy/skills/web-design-engineering/SKILL.md

@@ -0,0 +1,101 @@
+---
+name: web-design-engineering
+description: >-
+  Design, implement, and review web interface layout, component states, feedback,
+  and motion within the current CodeConductor workflow. Use for concrete web UI
+  work or requested UI audits, not backend-only tasks or native mobile apps.
+---
+
+# Web design engineering
+
+Apply this guidance to the web surface in scope. A React or Tailwind dependency
+alone is not a trigger. Keep the existing feature, fix, review, or OpenSpec flow;
+this skill adds contextual criteria, not commands, agents, gates, or score weights.
+
+## Intake and discovery
+
+Translate vague requests into observable behavior: “responsive feedback” might
+mean showing a pending state immediately after submit while preventing duplicate
+submissions. Identify the user objective, affected surface, relevant states, and
+acceptance checks in the Task Card. Ask only about ambiguities that affect scope.
+
+Inspect existing components, design tokens, documented visual decisions, installed
+dependencies and versions, and available browser, component-preview, and test tools.
+Reuse the product's visual language and accessible components. Consult official
+documentation for the installed version when an API is uncertain. Prefer existing
+capabilities and browser primitives; a small transition does not justify a library.
+
+## Design and implementation
+
+Record relevant decisions in the Technical Plan or OpenSpec design.md:
+
+- For static UI: hierarchy, readable content, spacing, responsive layout, overflow,
+  semantics, contrast, and focus visibility. Do not invent motion to fill a checklist.
+- For interactive components: default, pending, success, failure, disabled, and
+  empty states as applicable; pointer, touch, keyboard, focus entry and return.
+  Acknowledge input promptly without implying success before it is known.
+- If motion serves the task, name its purpose and weigh frequency, waiting cost,
+  and context. Specify start/end states, exit, rapid repeated input, cancellation
+  or reversal, and reduced-motion behavior that preserves essential information.
+  Use continuity or direct manipulation when it helps users understand the action.
+- Reuse motion tokens. Choose properties and tools appropriate to the component;
+  inspect layout/paint cost when relevant instead of assuming smoothness from code.
+  No duration, easing curve, animation technique, or visual style is universally
+  forbidden. Explain tradeoffs against the contract and product conventions.
+- When alternatives are explicitly requested, compare scoped options and their
+  tradeoffs before choosing. Do not build a variant selector or prototype framework.
+
+Agree checks before implementation. Preserve the workflow's test-before-implement
+order and use its evidence mechanism when required. Test observable state changes
+and interaction outcomes, not just CSS strings. Implement only the accepted scope.
+Tailwind skills own responsive conventions; framework skills own implementation;
+PageSpeed owns performance measurement; evaluation owns the scorecard.
+
+## Review and delivery
+
+Use the existing Review Report and its severity/verdict rules. Map contract failures
+to Spec Axis and technical issues to existing subchecks such as Correctness,
+Architecture alignment, Performance, or Test coverage. Preserve Standards Axis;
+do not add a design axis or rerank the two axes. Ground each finding in a location,
+reproduction or evidence, user impact, and a proposed resolution. Aesthetic
+preferences alone are suggestions, not blocking defects. Respect documented
+product choices unless evidence demonstrates a contract or technical failure.
+
+For a requested audit, inspect only the agreed surface and prioritize findings by
+impact and evidence. Report out-of-scope opportunities as suggestions. Create
+backlog items through the existing cc-backlog workflow only when requested; deliver
+those items later through OpenSpec. An audit is not permission to implement fixes.
+
+Report checks actually performed, their results, and limitations. Code inspection,
+DOM tests, screenshots, and live interaction checks establish different evidence.
+A screenshot cannot prove interruption or keyboard behavior. If a required visual
+or interaction check cannot run, mark it pending with the surface, steps, expected
+result, and missing tool/environment. Do not claim visual validation from code or
+mark the unmet acceptance criterion complete.
+
+## Example acceptance
+
+For a dismissible web dialog using existing tokens: opening from the keyboard
+places focus inside; Escape during entry closes it without reopening on a stale
+completion callback and returns focus to its trigger. With reduced motion enabled,
+the same actions work without the spatial transition. Check rapid open/close in
+the browser and record the result; if unavailable, keep that check pending.
+For a static pricing page, verify content hierarchy and no horizontal overflow at
+the agreed viewports; no animation is required.
+
+## Provenance and boundaries
+
+Original CodeConductor adaptation informed by Emil Kowalski's
+[design engineering](https://github.com/emilkowalski/skills/blob/main/skills/emil-design-eng/SKILL.md),
+[animation construction](https://github.com/emilkowalski/skills/blob/main/skills/animate/SKILL.md),
+and [interaction principles](https://github.com/emilkowalski/skills/blob/main/skills/apple-design/SKILL.md).
+Additional references: [review](https://github.com/emilkowalski/skills/blob/main/skills/review-animations/SKILL.md),
+[audits](https://github.com/emilkowalski/skills/blob/main/skills/improve-animations/SKILL.md),
+[opportunities](https://github.com/emilkowalski/skills/blob/main/skills/find-animation-opportunities/SKILL.md),
+[vocabulary](https://github.com/emilkowalski/skills/blob/main/skills/animation-vocabulary/SKILL.md),
+[library selection](https://github.com/emilkowalski/skills/blob/main/skills/pick-ui-library/SKILL.md),
+[component guidance](https://github.com/emilkowalski/skills/blob/main/skills/ask-sonner/SKILL.md),
+and [alternatives](https://github.com/emilkowalski/skills/blob/main/skills/prototype/SKILL.md).
+These are provenance, not runtime prerequisites. This skill does not install or
+synchronize upstream skills, adopt promotional responses or mandatory author
+formats, prescribe an Apple identity, or cover Expo/Swift native development.

package/presets/agy/workflows/cc-api-contract.md

@@ -95,3 +95,7 @@ or docs/OpenAPI drift.
 
 Report the final Task Card, Technical Plan, implementation summary, test report,
 review report, docs updated, compatibility impact, and residual risks.
+
+## Next
+
+Run `/cc-review` on the diff before merging.

package/presets/agy/workflows/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.
 ---
 
@@ -9,7 +9,7 @@ description: >-
 Problem: $ARGUMENTS
 
 This is a **router**, not a delivery workflow. Recommend exactly one command.
-Do **not** run the recommended `/cc:` command unless the human confirms.
+Do **not** run the recommended `/cc-` command unless the human confirms.
 
 ---
 
@@ -31,13 +31,13 @@ The catalog is only:
 
 | Slash | When |
 | ----- | ---- |
-| `/cc:feature` | new behavior |
-| `/cc:fix` | bug / regression |
-| `/cc:refactor` | structure, no behavior change |
-| `/cc:review` | inspect a diff/PR |
-| `/cc:tdd-cycle` | red → green → refactor |
-| `/cc:backlog` | create or append BACKLOG.md / objectives |
-| `/cc:openspec` | BACKLOG / BC-xxx delivery |
+| `/cc-feature` | new behavior |
+| `/cc-fix` | bug / regression |
+| `/cc-refactor` | structure, no behavior change |
+| `/cc-review` | inspect a diff/PR |
+| `/cc-tdd-cycle` | red → green → refactor |
+| `/cc-backlog` | create or append BACKLOG.md / objectives |
+| `/cc-openspec` | BACKLOG / BC-xxx delivery |
 
 If the CLI is unavailable, apply the same catalog and the same priority:
 backlog (author) vs openspec (deliver) → tdd-cycle → review → refactor → fix → feature (default).
@@ -53,4 +53,4 @@ Print:
 
 **STOP.** Wait for the human. Do not invoke the recommended workflow.
 
-For a full preset inventory (skills, commands on disk), use `/cc:help` / `cc-help`.
+For a full preset inventory (skills, commands on disk), use `/cc-help` / `cc-help`.

package/presets/agy/workflows/cc-council.md

@@ -86,3 +86,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/agy/workflows/cc-db-migration.md

@@ -95,3 +95,7 @@ undocumented deployment sequencing, or model/migration drift.
 
 Report migration files changed, model files changed, tests run, lock risk, data
 risk, operational sequencing, rollback/forward-fix notes, and residual risk.
+
+## Next
+
+Run `/cc-review` on the diff before merging.

package/presets/agy/workflows/cc-explore.md

@@ -28,10 +28,10 @@ If `graphify-out/graph.json` exists, run `graphify query "$ARGUMENTS"`. Invoke `
 
 ## Step 2 — Suggest next command (orchestrator)
 
-Recommend exactly one next slash command (`/cc:feature`, `/cc:fix`, `/cc:refactor`, `/cc:review`, `/cc:backlog`, `/cc:openspec`, `/cc:triage`, …) with a one-sentence rationale. Do not start that workflow.
+Recommend exactly one next slash command (`/cc-feature`, `/cc-fix`, `/cc-refactor`, `/cc-review`, `/cc-backlog`, `/cc-openspec`, `/cc-triage`, …) with a one-sentence rationale. Do not start that workflow.
 
 ---
 
 ## Completion
 
-Report the Repo Map and the recommended next `/cc:` command.
+Report the Repo Map and the recommended next `/cc-` command.

package/presets/agy/workflows/cc-feature.md

@@ -9,6 +9,28 @@ description:
 
 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 to the human:
 
 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/agy/workflows/cc-fix.md

@@ -19,6 +19,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 @@ resolved.
 Report: Task Card, Implementation Summary, regression test added, Review Report
 (if applicable). The fix 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/agy/workflows/cc-handoff.md

@@ -31,7 +31,7 @@ errors instead of pasting dumps. If unresolved credential material remains, stop
 and wait for a human (CCEP `stopOnHighRisk`).
 
 Include: goal, Task Card status (no secret fields), files touched, test
-pass/fail (not log dumps), open questions, and the next `/cc:` command.
+pass/fail (not log dumps), open questions, and the next `/cc-` command.
 
 Do not edit source or tests.
 

package/presets/agy/workflows/cc-openspec.md

@@ -11,6 +11,28 @@ Scope: $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 — Validate (mandatory gate)
 
 Run `npx cc-codeconductor openspec validate`. If invalid, show errors and recommendations, then **STOP**.

package/presets/agy/workflows/cc-prototype.md

@@ -36,4 +36,4 @@ Invoke `implementer` in a Git worktree that is not a merge candidate. Label the
 
 ## Completion
 
-Report bounds, worktree path, and what was learned. Recommend `/cc:feature` or `/cc:fix` if the spike should become real work.
+Report bounds, worktree path, and what was learned. Recommend `/cc-feature` or `/cc-fix` if the spike should become real work.

package/presets/agy/workflows/cc-refactor.md

@@ -29,7 +29,7 @@ behavioral consequences.
 If coverage is insufficient:
 
 1. **STOP**. Report the coverage gap to the human.
-2. Suggest invoking `/cc:test-plan` first to establish coverage.
+2. Suggest invoking `/cc-test-plan` first to establish coverage.
 3. Do not proceed with the refactor until coverage is confirmed.
 
 ---
@@ -159,3 +159,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/agy/workflows/cc-review.md

@@ -18,6 +18,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)
@@ -138,7 +160,7 @@ If any CRITICAL findings exist:
 - The Review Report status is **BLOCKED**
 - Report all CRITICAL findings to the human
 - Do not proceed until each CRITICAL finding is resolved
-- After resolution, invoke `/cc:review` again on the same target
+- After resolution, invoke `/cc-review` again on the same target
 
 If no CRITICAL findings exist:
 
@@ -152,3 +174,7 @@ If no CRITICAL findings exist:
 
 Deliver the complete Review Report. Never summarize or omit findings. Every
 finding must include a location and an actionable description.
+
+## Next
+
+Approved: merge. Blocked: return the findings to `/cc-fix` or `/cc-feature`.

package/presets/agy/workflows/cc-security.md

@@ -178,3 +178,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/agy/workflows/cc-spec-mutation.md

@@ -189,3 +189,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/agy/workflows/cc-tdd-cycle.md

@@ -260,5 +260,5 @@ The TDD cycle is complete when:
 **Cycle status**: complete | blocked (reason)
 ```
 
-If the behavior requires additional test cases, start a new `/cc:tdd-cycle` with
+If the behavior requires additional test cases, start a new `/cc-tdd-cycle` with
 the next scenario. One cycle = one behavior.

package/presets/agy/workflows/cc-test-plan.md

@@ -143,7 +143,7 @@ tester produces the plan in this format:
 Show the Test Plan to the human before any tests are written.
 
 The Test Plan is an artifact for review and approval. Writing test code is a
-separate action — invoke `/cc:feature` or add a test task to the board to
+separate action — invoke `/cc-feature` or add a test task to the board to
 implement from this plan.
 
 ---
@@ -155,3 +155,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/claude/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 @@ Adopt the **Reviewer** role as defined in `CLAUDE.md`.
 
 Block on missing contract tests, undocumented breaking changes, or docs/OpenAPI
 drift.
+
+## Next
+
+Run `/cc:review` on the diff before merging.

package/presets/claude/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/claude/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/claude/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/claude/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/claude/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 @@ Adopt the **Reviewer** role as defined in `CLAUDE.md`.
 
 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/claude/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/claude/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)
@@ -158,3 +180,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/claude/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)
@@ -190,3 +212,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/claude/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/claude/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/claude/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.
 ---
 
@@ -12,6 +12,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.
+
+
 ## Planning Principles — tracer bullet and blocking edges
 
 A **tracer bullet** is a vertical slice of work: one `BC-NNN` backlog item that goes discover → design → test → implement → review and produces a demoable result, sized to fit inside a single agent's context window without needing an intermediate `/clear`.

package/presets/claude/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