Redesign a SaaS interface with GLM 5.2 and Command Code

Connect the route and define the user task

Thanks to Command Code for sponsoring this video.

The recording uses Command Code and its /design Skill to work on Scripti. Its arena placement, cost comparison and “daily driver” language are claims and judgements from July.

1. Follow the install, login and model-selection sequence shown at 1:38.
2. Confirm the intended model before changing code.
3. Save a checkpoint and describe the user task the redesign should improve.
4. Preserve the functional behaviour and real product claims that the page already needs.

Choose the design pass deliberately

The walkthrough covers re-layout, redesign, finish and motion. These are different requests rather than a reason to regenerate everything repeatedly.

1. Inspect the existing hierarchy and choose the specific design problem.
2. Run the relevant pass and review the actual page.
3. Compare layout, readability and the main task with the original brief.
4. Use motion only where it supports the interaction and inspect its effect on use.

Run the pre-ship and repository checks

The later section tours review, sharing, memory and other working commands. An attractive screenshot is still only one part of the result.

1. Test important navigation and inputs in the changed interface.
2. Inspect the diff and the project’s relevant checks.
3. Keep useful design decisions in project memory with their context.
4. Share the reviewed version with its limitations instead of presenting a concept as an approved launch.

The takeaway

Judge this redesign by the working interface and review evidence. Historical ranking and price language do not establish a current model comparison.