Design Approach Selection
Read the decision matrix to provide one recommendation for the interface the user is working on.
Decision matrix: ~/.sdlc/stages/20-design/DECIDE.md (~ is the current user's home directory)
Usage
- First run
~/.sdlc/bin/check-update.sh. It is normally silent and only outputs a line when the knowledge base is behind the remote version — if there is output, inform the user, then continue. It is throttled and will not make a network request every time. - If the following points are unknown, ask one at a time: How long will this interface last? Roughly how many screens? Does it need brand recognition?
- Read the DECIDE.md above, and locate yourself based on the "Judgment Criteria" and "Recommended Path" sections.
- Give a clear recommendation with reasoning — do not list all options and let the user choose.
- If this interface will be generated by an agent, you must read the "Differences When Executed by an Agent" section — it explains how to avoid a template-like feel.
This skill is only responsible for selecting the approach. After the selection, specific visual implementation should be handed over to implementation skills such as frontend-design.
Do not recite the entire DECIDE.md.