first project

​

Before you start

• Scriptonia is running locally and accessible in your browser.
• Database and AI services are configured and responding.
• At least one payment method is enabled for testing (crypto or card).

---

​

Step 1 — Idea (/)

1. Open the home page.
2. Enter an idea, for example:
   • “A beginner-friendly crypto wallet with simple send and receive.”
   • “A landing page for a developer tool with pricing, documentation, and waitlist.”
3. Submit the idea.

The system returns:

• Initial analysis
• Feature suggestions
• Clarifying questions

You are guided to Intent.

---

​

Step 2 — Intent (/intent)

1. Answer the clarifying questions:
   • Target users
   • Core features vs optional features
   • Platform preference
2. Submit your answers.

The system produces:

• Refined title
• Description
• Feature list
• Target audience
• Technical notes

Requirements are fixed for the remainder of the workflow.

---

​

Step 3 — Platform (/platform)

1. Review available platform options:
   • Website
   • Web Application
   • Mobile Application
2. Each option displays:
   • Suggested tech stack
   • Cost estimate
   • Timeline
3. Select one platform to continue.

You are redirected to Payment.

---

​

Step 4 — Payment (/payment)

• Choose one available payment method.
• Complete the checkout flow.
• On successful confirmation, the workflow proceeds automatically.

---

​

Step 5 — Execution (/execution)

The system runs a coordinated execution process involving multiple specialized agents:

• Product planning
• UX structure
• Frontend specifications
• Backend specifications
• Infrastructure guidance
• Documentation

Progress is displayed during execution. Once completed, a project package is generated and you are taken to Completion.

---

​

Step 6 — Completion (/completion)

• Review the generated summary
• Download the project package, which includes:
  • Project overview
  • Product requirements
  • Planning documents
  • Technical specifications
  • Infrastructure notes
• Optionally connect a version-control provider to create a repository and upload the files.

---

​

Understanding the Workflow

The workflow is linear and session-based.

• A single session ties together:
  • Idea
  • Intent
  • Platform
  • Payment
  • Execution
  • Completion
• Stages must be completed in order
• Each step feeds structured context into the next

---

​

Workflow Stages

---

​

Agents in Execution

• Product Planner
• UX Designer
• Frontend Specialist
• Backend Specialist
• Infrastructure Specialist
• Technical Writer

Agents collaborate to produce a cohesive project blueprint.

---

​

What to Expect

---

​

Outputs

A downloadable project package containing:

• README.md — Project overview and setup
• Product and planning documents
• Frontend and backend specifications
• Prompt-based generation guides
• Infrastructure and deployment notes

---

​

Example package (Website)

ProjectName/
├── README.md
├── docs/
│ ├── PRD.md
│ ├── PLAN.md
│ └── CONTENT.md
├── frontend/
│ ├── structure.md
│ └── prompts/
│ └── generate_site.txt
├── backend/
│ └── architecture.md
├── infra/
│ └── hosting.md
└── meta/
└── repository_config.yaml

​

Timing

• Idea / Intent / Platform — Seconds per step
• Execution — Typically under a few minutes
• Download — Available immediately after completion

---

​

Example end-to-end

---

​

Tips for Success

---

​

Idea

• Be specific but scoped
• Mention 1–2 core features
• Avoid vague or overly broad ideas

---

​

Intent

• Answer all questions clearly
• Separate core vs optional features
• State platform preference if known

---

​

Platform

• Website — Marketing and content-focused
• Web Application — SaaS, dashboards, tools
• Mobile App — Native or store-distributed apps

---

​

When something goes wrong