How inspectors work
On the Blueprint, click a card to open its inspector at the side. An inspector reads your app's real files and shows what's there in plain words. Most changes you make here are made directly, without AI. When something needs Piye to write new code, the inspector has a button that sends a clear request to Piye, which you can read and change first.
If your project has several apps, choose Which app at the top. Read the project again refreshes what the inspector shows.
The website
Theme
The values your whole app is styled from: its colours, fonts and corner roundness. Change one and every place that uses it updates; the preview reloads on its own.
- Create a theme from your brand colour, see it in light and dark, then apply it.
- Ask Piye to add a dark mode that follows each visitor's device.
- Ask Piye to check readability: every text and background pair is checked for contrast and fixed where needed.
- Ask Piye to gather loose colours written directly in pages into the theme, so the whole app changes from one place.
Pages
Every page of your website, with its title and description for search results and link previews. Add a page from here too. See Pages.
The server
The server's inspector has four tabs: Keys, Data, Sign-in, and API & jobs.
Keys
The settings your app's code needs to run (often called "environment keys"), for example the key for an email service. Each one shows whether it has a value, whether the code needs it, and whether it's safe to show in the browser. Values are never shown.
From here you can ask Piye to explain the missing keys, list them in an example file, or make the app fail clearly with a helpful message when one is missing.
Data
What your app keeps: each kind of information (like Products, Bookings or Members) and its fields, and how they relate.
- Add a data model, for example "a Comments model linked to Post".
- Ask Piye to explain in plain words what each model stores.
- Ask Piye to fill the database with realistic sample data for testing.
Sign-in
Which sign-in methods your app offers and whether each is ready. See Sign-in.
API & jobs
- Routes: the addresses your app's server answers (its API). Ask Piye to add one, or to review every route for missing sign-in checks and data that shouldn't be shown.
- Scheduled jobs: work that runs on a timetable, like "send a weekly summary email every Monday". Pick every day, every Monday or the first of the month, or write your own timing. On Vercel, Piye sets them up to run once the app is published.
Other parts
Pages, components, folders and other cards on the Blueprint open inspectors with what they contain. App Operations opens its own view: see App Operations.