Best practices

​

1. Use custom knowledge as your project brain

• Capture product vision, key user journeys, core features, and design rules
• Define roles and boundaries (admin / user / investor, etc.)
• This knowledge is referenced continuously and improves future edits

Ask AI example:

Generate knowledge for my project at T=0 based on features implemented.

​

2. Prompt best practices

• Be specific: point to pages/modules and expected behavior
• Do one thing at a time; implement in chunks and verify
• Specify do-not-touch areas (do not touch…)
• Include screenshots or screen recordings for clarity

Ask AI template:

On page /settings, implement [feature]. Expected: [XYZ].
Please don’t touch component A / layout B / shared logic unless necessary.

​

3. Supabase and full-stack cadence

• Stabilize the frontend first, then connect Supabase
• Validate database schema compatibility before rolling back versions

Ask AI:

Validate SQL schema at T=0 and ensure no breaking changes.

​

4. Use editable design for fast UI changes

• Visual edits for copy / color / typography / spacing / responsiveness are faster and safer
• Boxify consumes credits; other edits do not

​

5. Use versions and diffs

• Pin every known-good state
• Use version diffs to locate problematic changes

Ask AI:

Compare version at T–1 to T–0. What changed and what might break?

​

6. Use fork as a reset option

• If you are stuck in an error loop or heavy technical debt, fork and rebuild from a clean baseline
• Disconnect Supabase before forking a connected project

​

7. Small steps, always reversible

• Break work into the smallest verifiable increments
• After each step, run regression checks and user-flow validation

​

8. Docs and community

• Read docs flows and templates; search first when issues appear
• Organize your question and context before asking for help

​

9. Security and compliance basics

• Never paste API keys or other credentials; use backend environment variables / secret configuration
• Least privilege, environment isolation, pre-release security checks

​

10. Integrating complex third-party APIs

1. Open the third-party platform’s official API docs page
2. Copy the core endpoint notes (request params, response fields, signing method)
3. Paste the docs into the superun chat and tell the AI: “Implement xxx following this documentation”

Here is the WeChat Pay unified order API documentation:
[paste docs]

Please implement payment following this documentation. Inject AppID and merchant key via backend environment variables.

• The AI follows the correct spec and reduces guesswork and debugging
• Signing algorithms, callback verification, and similar details are less likely to fail
• When an API upgrades, update the pasted docs only