Project planning & prompt writing guide

​

Tips

​

Actions after requirement clarification (page steps)

1. Looks good — start generation

• If the page steps match your expectations, click Start generation
• The system continues the flow from those steps

2. Not what I want, but hard to describe

• If something feels off but you are not sure how to say it
• Click Not sure yet
• The model will offer new options to choose from

3. I have ideas and want adjustments

• If you want to change the page steps
• Type your requirements in the chat
• The model combines your input and generates updated options

💡 Tip： Use the clarification phase fully so later generation matches your expectations. If you are not satisfied, adjust before moving on.

​

Style selection and theme preview

1. Pick a style

• Click any generated style to select it
• Each style represents a different design direction

2. Preview themes

• Use the theme color picker at the bottom of the page
• Slide through colors to see how each theme looks on the selected style

3. Apply a theme

• Click a theme to select and apply it
• The theme applies to the current style immediately

4. Confirm and continue

• When style and theme look right
• Click Continue with this style in the top-right
• The app is generated with your choices

💡 Tip： Explore style and theme combinations. Hover to preview themes before you commit.

​

Generate a demo version

1. Click “Got it — start the demo”

• After style generation, click this to create the demo
• The demo uses system-generated test data

2. Try the app

• The demo is a simple preview
• You can switch pages and perform basic actions
• It shows flows and interaction patterns

3. Validate design

• See how the app looks in practice
• Check whether design meets expectations
• Confirm flows make sense

4. Review and confirm

• When the demo is ready, the chat will notify you
• Click View demo → in the top navigation bar
• Confirm the demo effect

💡 Tip： Demos are a fast way to validate design and features before full build.

​

Phased development to reduce rework

1. Ideation： Define target users, core features, and business flows.
2. Demo： Confirm page structure, interaction paths, and visual style.
3. Build： Add database, login, permissions, and other backend capabilities.
4. Validation： Use code review and automated tests.
5. Launch： Confirm domain, compliance filing, data, and publish status.

​

One-click back to demo while build plan is “pending confirmation”

• Key pages or flows are not confirmed;
• The demo diverges from real business processes;
• Build scope is too large and needs splitting;
• You need to reconfirm UI/UX before database, login, or permissions.

​

Build phase

1. Next steps after viewing the demo

• After the demo, select the features you need
• Generate demo first — deeper demo for selected features
• Generate demo and build together — real features with real data plus a follow-up feature list
• Or click Next: build implementation in the nav bar to go straight to the feature list

2. Choosing features in the build phase

• Follow the model’s recommended order, or select all
• Pick what you need
• Continue in the chat stream or on the Build tab
• After you continue, superun implements your selections

3. Acceptance and continued development

• When selected features are done, test them
• Report issues in chat until behavior matches expectations
• Then continue with remaining features or describe new requirements

4. Route switcher

• If admin or other standalone routes are not reachable by clicking in the UI
• Use the route switcher in the middle of the nav bar
• Pick a route from the dropdown to jump directly

​

Launch and operations

• Click Next: launch & operations for publish, SEO, analytics, performance, and related launch features
• These features tie to going live
• One-click publish
• SEO optimization and related tools

​

Save Compute Credits: when something breaks, do not let the AI change things blindly

• Errors or freezes — try Troubleshoot more than once if needed
• Refresh does not lose data; the model can be unstable while work finished but the page did not update

1. Understand： Copy the error and ask the AI what it means and where the issue might be
2. Confirm approach： Discuss fixes with the AI
3. Then change： Apply changes only after the approach is clear

• ❌ Asking the AI to change code at random on every error
• ❌ Editing without analysis
• ❌ Many consecutive edits that make things worse

• ✅ Understand the error first
• ✅ Find root cause
• ✅ Plan the fix
• ✅ Then execute

​

Save Compute Credits: use chat mode to think, then let the AI act

• Discuss ideas
• Clarify structure
• Ask whether the plan makes sense
• Confirm direction and details

• Generate or modify based on the discussion
• Implement agreed scope
• Keep direction correct

• Avoid off-target generation
• Save Compute Credits (consultation uses less)
• Catch issues early
• Clearer thinking

​

Point to a specific page or module

On the settings page (/settings), in the notification settings area, add an email notification toggle.

• Give the page path
• Specify location (area, module)
• Describe the feature to implement