Theme Factory

Do Not Assume

• React components
• Next.js routing
• client-side SPA hydration
• separate frontend repo

If the user explicitly asks for React, treat that as a new requirement and confirm architecture impact first.

Preferred Reading Order

Before editing UI/theme files, inspect:

1. vite.config.ts
2. src/components/layouts/
3. related files under src/modules/<module>/views/
4. public/assets/
5. any theme HTML source referenced by layout helpers

Workless Placement Rules

Use these destinations consistently:

• src/modules/<module>/views/ Module-owned page builders or view helpers
• src/components/layouts/ Shared layout fragments or page shell helpers
• public/assets/ Generated/build output only

Do not edit generated CSS in public/assets unless the user explicitly asks to patch the built artifact.

Theme Adaptation Workflow

When adapting an external theme:

1. Identify whether the source is static HTML, CSS, or component code.
2. Strip framework-specific assumptions that do not exist in Workless.
3. Preserve only the visual language, layout ideas, spacing system, and useful patterns.
4. Rebuild the output into:
   • Tailwind classes in source files, or
   • reusable server-rendered view helpers
5. Keep asset paths compatible with public/assets.

Visual Direction

Aim for:

• admin/dashboard-friendly composition
• strong hierarchy and readable density
• reusable shells instead of page-specific hacks
• bold but maintainable Tailwind usage

Avoid:

• copying vendor template structure blindly
• scattering CSS across generated output
• introducing front-end dependencies not already used by the repo

Verification

At minimum:

1. confirm source files, not generated files, were edited
2. confirm asset paths match current Vite output rules
3. confirm the result still fits server-rendered usage

If the task changes asset generation, also inspect vite.config.ts.