Skip to main content

​
Tips

​
Actions after requirement clarification (page steps)

After you submit your initial prompt, superun clarifies requirements, then moves into the page-steps phase. You can choose different actions depending on the situation. Page steps after requirement clarification Options：
  1. Looks good — start generation
  • If the page steps match your expectations, click Start generation
  • The system continues the flow from those steps
  1. 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
  1. 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.

​
Select and preview a concept

After starting generation, preview free Concept A. If you want another direction, commission a senior designer from the designer card. Each commission creates one additional concept.
  1. Open a completed concept to compare layout, content, and color. You can adjust its design theme in the right panel.
  2. Use Continue with this concept when satisfied. You do not need to wait for every other concept; work already started continues.
  3. Each user has one free first commission across projects. Later commissions are estimated at 50–100 Compute Credits, settled by actual usage after completion, and require the actual paying account’s balance to exceed 100 credits to start.
A free Concept A does not make later demo generation or development free. See Design concepts.

​
Automatic transition to Demo

After selecting a concept, you can open Demo to check progress. Once usage scenarios are ready and the current generation round ends, superun automatically opens Demo and shows the completion card. No extra “Got it — start the demo” confirmation is needed. Tab clicks only switch views and do not generate again. Use test data in the demo to validate pages, interactions, and usage flows before connecting real capabilities. Later demo generation, edits, and development are billed by actual usage.

​
Phased development to reduce rework

For complex projects, follow this order:
  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.
Do not change UI, database, and business logic at large scale before page structure is settled. Confirm scope in Free consultation, then execute in phases to reduce rework and repeated Compute Credit use.

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

While the build plan is pending confirmation, you can return to demo in one click. Typical cases:
  • 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.
After going back, adjust and validate the demo, then reorganize the build plan. This changes the current phase; unconfirmed build plans must be rechecked against the new demo; confirm impact on real data and completed capabilities before continuing.

​
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
Next steps after viewing the demo
  1. 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
Feature selection in build phase
  1. 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
Feature acceptance and continued development
  1. 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
Route switcher

​
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
Next: launch and operations

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

When the site errors or freezes, understand the problem before fixing. Common situations：
  • 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
Recommended debug flow：
  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
Avoid：
  • ❌ Asking the AI to change code at random on every error
  • ❌ Editing without analysis
  • ❌ Many consecutive edits that make things worse
Prefer：
  • ✅ 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

Think first; do not generate everything at once. Flow： Step 1 — chat first (click Free consultation at the bottom-right of the input):
  • Discuss ideas
  • Clarify structure
  • Ask whether the plan makes sense
  • Confirm direction and details
Step 2 — execute：
  • Generate or modify based on the discussion
  • Implement agreed scope
  • Keep direction correct
Benefits：
  • Avoid off-target generation
  • Save Compute Credits (consultation uses less)
  • Catch issues early
  • Clearer thinking

​
Point to a specific page or module

Reference the page or module and state the feature clearly. Good example：
Points：
  • Give the page path
  • Specify location (area, module)
  • Describe the feature to implement