packages/likec4/src/cli/options.ts (1)

70-74: Extract shared theme choices/type to avoid drift.

The option works, but the 'light' | 'dark' union is now duplicated across files. Consider exporting a shared buildThemeChoices/BuildTheme from one module and reusing it in CLI + Vite config typings.

♻️ Suggested local refactor starting point

+export const buildThemeChoices = ['light', 'dark'] as const
+export type BuildTheme = (typeof buildThemeChoices)[number]
+
 export const theme = {
-  choices: ['light', 'dark'] as const,
+  choices: buildThemeChoices,
   desc: 'default color scheme for the built website',
   nargs: 1,
 } as const satisfies Options

As per coding guidelines, "Agent types and interfaces should be defined separately and reused across the codebase."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/likec4/src/cli/options.ts` around lines 70 - 74, The theme option
duplicates the 'light'|'dark' union; extract a shared constant and type (e.g.,
export const buildThemeChoices = ['light','dark'] as const and export type
BuildTheme = typeof buildThemeChoices[number]) from a common module and import
them where needed; update the CLI option (theme) to use buildThemeChoices for
choices and BuildTheme for any typings, and update the Vite/config typings to
reference the same BuildTheme so the union is defined in one place and reused.

packages/likec4/app/global.d.ts (1)

19-20: Extract __DEFAULT_THEME__ union into a reusable type.

Line 20 currently inlines the theme union. Defining a named type improves reuse and reduces drift risk across CLI/Vite/app boundaries.

♻️ Proposed refactor

+type DefaultTheme = 'light' | 'dark' | 'auto'
+
 // default is 'auto', set via --theme CLI option
-declare const __DEFAULT_THEME__: 'light' | 'dark' | 'auto'
+declare const __DEFAULT_THEME__: DefaultTheme

As per coding guidelines: **/*.{ts,tsx}: Agent types and interfaces should be defined separately and reused across the codebase.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/likec4/app/global.d.ts` around lines 19 - 20, Extract the inline
union into a named exported type (e.g., ThemeMode or DefaultTheme) and replace
the inline union on the const declaration with that type; specifically create a
reusable type declaration for the theme union and update __DEFAULT_THEME__'s
type to reference it so other modules (CLI/Vite/app) can import and reuse the
same Theme type instead of duplicating "'light' | 'dark' | 'auto'".

packages/likec4/app/src/searchParams.spec.ts (1)

25-30: Avoid re-implementing production logic inside spec helpers.

deriveDefaultColorScheme and themeDefineValue duplicate app/build expressions, so these tests can still pass if real implementation changes incorrectly. Prefer importing/testing shared helpers from production code (or extracting these expressions into exported utilities first).

Also applies to: 74-76

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/likec4/app/src/searchParams.spec.ts` around lines 25 - 30, The spec
currently re-implements production logic in deriveDefaultColorScheme (and
themeDefineValue) which risks tests remaining green when the real implementation
changes; instead, remove these duplicated helper implementations and import the
canonical functions from the production module (or move the shared logic into a
new exported utility and import that) so tests exercise the same code
paths—locate deriveDefaultColorScheme and themeDefineValue in the spec and
replace their local definitions with imports from the app codebase, updating
imports and any references accordingly.

packages/likec4/src/cli/options.ts (1)

70-75: Centralize theme literals into a shared type/constant.

'light' | 'dark' is now represented in multiple files (CLI choices and Vite config types). Please extract a shared Theme type (and optionally THEME_CHOICES) to avoid drift when new variants are added.

♻️ Suggested direction

+export const THEME_CHOICES = ['light', 'dark'] as const
+export type Theme = (typeof THEME_CHOICES)[number]
+
 export const theme = {
-  choices: ['light', 'dark'] as const,
+  choices: THEME_CHOICES,
   desc: 'default color scheme for the built website (default: auto, follows system preference)',
   nargs: 1,
 } as const satisfies Options

As per coding guidelines, **/*.{ts,tsx}: Agent types and interfaces should be defined separately and reused across the codebase.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/likec4/src/cli/options.ts` around lines 70 - 75, Extract a shared
Theme literal type and choices constant and use them everywhere instead of
repeating 'light'|'dark': create a exported type Theme = 'light' | 'dark' and an
exported const THEME_CHOICES = ['light','dark'] as const, then update the
existing exported theme object (the symbol theme) to reference THEME_CHOICES for
choices and use Theme in its type annotation; also update any Vite config types
or other files that currently duplicate the literal to import and use
Theme/THEME_CHOICES so all code shares the single source of truth.