Learning · References

Copy page

Help & Tips

Practical guidance for prompting well, working with images and files, setting up integrations, and troubleshooting when something doesn’t go as planned.

The gap between a smooth build and a frustrating one usually comes down to how you prompt, not luck. These are the patterns worth knowing.

Section 01

How to Use Nuvra Tech

Plan Before You Prompt

The biggest time-saver isn’t a cleverer prompt, it’s figuring out what you want before you write one. You don’t need a full spec — just who it’s for, the one key action they should take, and what it should feel like.

Build One Piece at a Time

Large, all-in-one prompts tend to come back half-right in several places rather than fully right anywhere. Get a working foundation, check it, then add the next piece.

Be Specific — and Say What to Leave Alone

Every prompt modifies a real project, so it matters what you don’t want touched, not just what you want built.

Add a toast notification in the top-right corner when a form submits successfully, without changing the form itself.

Use Real Content

Skip “lorem ipsum” and “feature 1, feature 2.” Real words show intent and help you catch layout issues placeholders never would.

From Idea to Working App

Shape the idea first — a few clear sentences on who it’s for and what it should do beats a polished document you never finish. Decide whether to build frontend first (easier to debug, the better default if you’re newer to this) or frontend and backend together. Split the idea into buildable pieces rather than describing the whole app in one prompt, and validate with a rough version before you polish.

Section 02

Improve Your Results

Using Images

Point to an already-hosted image, upload one through a connected repository, or let users upload their own via Nuvra Cloud. A screenshot of a bug is often clearer than any description of it — the same trick works for quick content edits or as a style reference.

Using Video

Reference something already hosted — YouTube is the common case — or upload your own file through a connected repository. Compress video before uploading; a large file slows down cloning and preview startup.

Section 03

Setup & Integration Tips

Using npm Packages

Name a package and describe what to build with it in one prompt — useful for drag-and-drop boards, charts, and animation libraries that already have a well-built package. Check download count, maintenance activity, and community feedback before relying on one for anything critical.

Edit Google Files

Embed a Google Doc, Sheet, or Slides file directly in your app so collaborators keep editing in the interface they already know. Use the file’s /edit link, not /preview or /view — those are read-only by design.

Using Custom Google Fonts

Nuvra Tech doesn’t support uploading a custom font file, but web-safe fonts and the full Google Fonts library cover nearly everything most projects need — by name or by direct link.

21st.dev Integration

Copy a hand-crafted component’s generated prompt from 21st.dev, paste it into chat, and say exactly where it should go. A faster starting point than describing a polished UI element from scratch.

Section 04

Hosting & Ownership

Host Outside Nuvra Cloud

Move just your frontend to a hosting platform of your choice while your backend stays on Nuvra Cloud, or take on full self-hosting if you need custom infrastructure. Either path starts with connecting Git Sync first. Most projects never need this — start on Nuvra Cloud and move pieces out only if you hit a real constraint.

Section 05

Troubleshooting & Safety

Troubleshooting

Most issues fall into a handful of predictable categories:

Security Best Practices

Frontend code can be inspected by anyone — never let it hold a real secret. Row-level security rules are your actual access control; review them before real user data exists, not after. Make a security review part of adding any meaningful feature, not a one-time check before launch.

Debugging Prompts

Ask for analysis before a fix when something’s failing:

Here’s the failing console log: [paste it]. Analyze the error, and suggest a solution after understanding the dependencies. Don’t apply a fix yet — explain what you find first.

If a fix hasn’t converged after two or three tries, stop iterating in place. Revert to the last working version and come back with one precisely scoped prompt.

Previous

Integrations

Next

Changelog