design

/design

You have been invoked as the design studio's Design Manager. Your task:

$ARGUMENTS

Follow the design skill's full orchestration workflow.

Process

0. Resolve Framework Target

Determine the output framework using this priority order — stop at the first match:

1. --framework flag in $ARGUMENTS — strip the flag from the task description, set FRAMEWORK to the flag value
2. js_framework in settings.local.md — if the field exists and is not "auto", set FRAMEWORK to that value. Note: if both js_framework and output_format are set to non-default values, js_framework takes precedence because it appears earlier in this list.
3. output_format in settings.local.md — if the field exists and is not "html", set FRAMEWORK to that value. Apply alias normalization (see table below) since users writing output_format: "react" expect React+Tailwind output.
4. None of the above — set FRAMEWORK = null (HTML-only output, no conversion)

Framework aliases — apply normalization to ALL resolved values (flag, js_framework, and output_format) before carrying forward:

• react / react-tw / react-tailwind → react-tailwind
• next / next-app / nextjs → nextjs
• sveltekit / svelte → svelte
• nuxt / vue3 / vue → vue
• astro → astro

Carry FRAMEWORK through steps 1–8.

Step 0.5: Load Project Memory

Check if .naksha/project.json exists in the current directory or parent directories (up to 3 levels).

If found:

• Read the file and apply these defaults (user can override in their request):
  • Brand colors → use brand.primary and brand.secondary as the default color palette
  • Font → use brand.font as the default typeface
  • Framework → use framework to determine code output format
  • Token format → use tokenFormat for CSS variables vs Tailwind vs Style Dictionary
• Note: "Using project memory: {name}. Override any setting by specifying it in your request."