Troubleshooting

Guidelines and best practices for building and debugging your apps.

1. Core Build Instructions

Use these rules every time you generate or repair an app:

  • • Use Meteor v3.4 with native Blaze.

  • • Never agree to modify config.js for Rspack.

  • • Add functionality inside the app so each user can change their own password.

  • •Create an admin user at startup with:

    • Email:
    • Password:

  • •The startup admin must have access to:

    • Listing all app users
    • Editing all app users
    • Changing all app user passwords

  • • After first login, change the default admin password immediately.

  • •Be precise about user roles and clearly explain:

    • What each role can do
    • Which database records each role can access
    • Which screens each role can view or edit

  • • Build the app step by step.

  • • Do not try to build the entire app in a single prompt.

Recommended Role Logic

Admin
  • • Full access to all users, screens, and records
  • • Can list, edit, create, disable, and reset passwords for all users
Authenticated User
  • • Access only to their own account and permitted app screens
  • • Can update their own password
Guest / Public User
  • • Access only to explicitly public pages or screens

2. Styling Instructions

Apply these UI rules consistently:

  • • Use native Bootstrap light theme.

  • • Use native Bootstrap dark theme.

  • • Set Bootstrap light theme as default.

  • • Add a theme switcher in the top bar so users can switch to dark theme.

  • • Keep the graphics ultra minimal.

  • •Prefer:

    • Clean spacing
    • Simple cards
    • Subtle borders
    • Minimal shadows
    • Restrained color usage

  • • Transform all alert messages into beautiful minimal Bootstrap modal popups.

  • • Avoid raw browser alerts or visually harsh warning boxes unless absolutely necessary.

UI Behavior Expectations

  • • Success messages should appear in a clean Bootstrap modal
  • • Error messages should appear in a minimal, readable Bootstrap modal
  • • Confirmation actions should also use Bootstrap modal dialogs
  • • Theme switching should work consistently across all main screens

3. When Build Fails Instead of Deploying

If the build fails, follow this recovery process:

    1. First, try once again using the Debug BE button on the failed job.
    1. If that does not solve the issue, create a new job using only the parts of the prompt that originally failed.
    1. Do not repeat the whole app request if only one part failed.
    1. Isolate the broken part and retry with a smaller, focused prompt.

When Deployment Succeeds but the App is Broken

If deployment succeeds but the result is not correct — for example:

  • • White screen

  • • Incomplete UI

  • • Broken navigation

  • • Unexpected behavior

  • • Missing data

  • • Buttons not working

Then do the following:

    1. Try Running Debug
    1. Or open Chrome Developer Console
    1. Copy the client-side errors
    1. Create a new Soloron job with this message:

try to fix the debug log from client: ...

    1. Paste the exact console error after the colon
    1. Keep the message focused on the actual debug output
    1. Prefer exact error logs over generic descriptions