Investigate migrating XBuilder frontend styling to Tailwind CSS

[nighca]

Background

To improve the efficiency of AI-assisted frontend development in XBuilder, we are considering migrating the current styling implementation approach to Tailwind CSS.

Before making that change, we need a clear assessment of whether the migration is practical, how much work it would require, and what migration approach would be the most suitable for the project.

What this issue is about

Investigate the feasibility of migrating XBuilder frontend styling to Tailwind CSS and determine a concrete migration plan.

Investigation scope

1. Review the current styling approach used in XBuilder frontend code.
2. Evaluate whether Tailwind CSS fits the existing component structure, build pipeline, and development workflow.
3. Estimate the migration cost, including code changes, design consistency risks, and maintenance impact.
4. Identify the main technical risks, compatibility concerns, and possible blockers.
5. Compare possible migration strategies, for example:
   • full migration
   • incremental migration
   • hybrid approach for selected areas first
6. Propose a recommended implementation plan if the migration is worth doing.

Expected output

1. A feasibility conclusion.
2. A rough workload estimate.
3. A list of major risks and constraints.
4. A recommended migration strategy and execution steps.

Notes

This issue is for research and planning first, not for directly migrating the codebase in the same task.