UI Planning & Scaffolding

Core rule: ask before scaffolding

Never generate UI folder structure, component skeletons, or a framework choice without first asking the user the questions below and getting real answers. A UI decision made without answers to these is a guess, and guesses here are expensive to undo (framework choice especially — swapping React for something else later is a rewrite, not a refactor).

If some answers are already obvious from context (e.g., this is clearly a Quickshell module for the existing dotfiles rice, or clearly a CLI tool with no visual UI), skip asking about those specific points and state the assumption instead of asking — but still ask about anything genuinely undecided.

Part 1 — Planning: questions to ask, in order

1. Who is this for?

• Just the user (personal tool, dotfiles, internal script)?
• Other developers (an open-source project's docs site, a CLI's help output)?
• Non-technical end users (kyfram template users, a public-facing product)? This changes almost everything downstream — a personal tool can be ugly and fast to build; something for non-programmers needs to be self-explanatory with no assumed context.

2. What does it actually need to do?

• List the core screens/views or states, not features — "a form to create a scene, a list of existing scenes, a preview pane" not "CRUD for scenes."
• Is it read-only/display, or does it need real interactivity (forms, drag-drop, live updates)?
• Does it need to persist anything, and if so, is that already decided or part of this planning pass?