> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stardeck.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Bring an Existing Prototype to Stardeck
> Turn a prototype made with Claude, Codex, or another local coding tool into a real Stardeck app
If you already built a prototype with Claude, Codex, or another local coding tool, you do not need
to start over. Upload the prototype to your Stardeck app, then plan the production version with your
Starcat agent.
Remove `.env` files, API keys, credentials, and other secrets before uploading. You do not need to
upload generated folders such as `node_modules`, `.next`, `dist`, or `build`.
## 1. Upload Your Prototype
Open your Stardeck app and select **Code** in the workspace toolbar. In the **Files** panel, choose:
* **Upload files** to add a standalone HTML file or a small set of files
* **Upload folder** to add a complete prototype and preserve its folder structure
For example, uploading a local folder named `demo` adds it to the repository as `demo/`. Each file
can be up to 25 MB. Generated dependency and build folders are skipped automatically.
Keep the prototype in its own folder instead of replacing the app's existing files. This gives
Starcat a clear reference to inspect while it builds the production version in the right parts of
the app.
### Files Starcat can inspect
Starcat can read source code, HTML, Markdown, JSON, CSV, and other text files directly from the
repository. It can also extract content from PDFs, DOCX documents, XLSX spreadsheets, and PPTX
presentations, and describe common image formats such as PNG and JPEG.
Name the relevant file or folder in your prompt so Starcat knows what to inspect. Files can be up to
25 MB each; images must be 10 MB or smaller for Starcat to analyze them. Archives and other
unsupported binary formats can remain in the repository, but Starcat cannot inspect their contents
directly.
## 2. Plan the Real App with Starcat
Switch Starcat to **Plan** mode and ask it to inspect the uploaded prototype before changing code.
Explain what the prototype demonstrates and what the production app needs to do.
You can start with this prompt:
> I uploaded a prototype in `demo/`. Inspect it and plan how to turn it into a production Stardeck
> app. Preserve the useful design and interactions, identify placeholder data and incomplete flows,
> and plan the real data model, authentication, permissions, integrations, tests, and deployment.
> Do not change code yet.
If you uploaded one HTML file, name it in the prompt—for example, `landing-page.html`.
## 3. Review the Plan
Before approving implementation, make sure the plan answers:
* Which screens, interactions, and visual details should be preserved?
* Which hard-coded or sample data should move into Data Stores?
* Does the app need sign-in, roles, or permissions?
* Which forms, payments, emails, uploads, or external services need real integrations?
* What should be tested before the app goes live?
Tell Starcat what to change if the plan misses something. When the plan looks right, approve it and
let the agent build the app in the normal Stardeck structure.
## 4. Test the Production Flows
Use the live preview to test the real workflows—not only whether the imported prototype still looks
right. Check forms, saved data, permissions, mobile layouts, error states, and any connected
services. Continue refining the app with Starcat until it is ready to publish.
Learn when to use Plan and Agent modes
Test and publish the finished app