Requirements Document (PRD)
The requirements document (PRD, Product Requirements Document) is the solution specification produced by AI before formally generating the website code. It is the most critical confirmation step in the entire website-building process.
Why the PRD Is Important
In one sentence: the PRD is your low-cost error-correction opportunity.
| Stage | Cost of Changing Requirements |
|---|---|
| Before PRD generation (description stage) | Lowest |
| During PRD confirmation | Low — only change the document, not the code |
| After website generation | Medium to high — requires AI conversation modification, consuming Credits and time |
| After publishing online | Highest — also need to republish and clear cache |
Example: If the PRD misses the "Contact Us" page, adding it at the PRD stage is just adding one line; adding it after the website is generated requires AI to create a new page, adjust navigation, and adapt styles, consuming significantly more.
So: please spend 3–5 minutes reading the PRD carefully. These few minutes can save tens of minutes later.
What the PRD Contains
A typical PRD contains the following:
| Section | Content |
|---|---|
| Website positioning | Website goals and target user groups |
| Page structure | Which pages are needed and their hierarchical relationships |
| Page details | Which sections each page contains and what each section displays |
| Feature list | Interactive features such as forms, booking, login, search |
| Data structure | What data needs to be stored (e.g., articles, products, booking records) |
| Visual style | Color scheme, font tendency, overall tone |
Generating the PRD
Trigger Method
During AI's requirement follow-up, click "Generate requirements document directly."
Or continue answering AI's follow-up questions; AI will automatically enter the PRD generation stage when it has enough information.
Generation Process
The interface shows:
- "Generating requirements document…"
- "Requirements document generating…"
The generated document is presented as requirements.md and can be viewed in the right panel.
Reviewing the PRD
Review Checklist
Please check item by item:
Page Structure
- Are all needed pages present? (Commonly missed: Contact Us, About Us, Privacy Policy)
- Are there any redundant pages? (Unneeded pages increase later maintenance costs)
- Is the navigation structure reasonable? Are main pages in the top-level navigation?
Feature Completeness
- Does the form include all the fields you want to collect?
- If visitor login is needed, is it mentioned in the PRD?
- If data storage is needed (booking, registration, messaging), is it clearly written?
- Do functions such as search, filtering, and pagination meet expectations?
Content Planning
- For content you need to continuously update in the backend (e.g., news, cases), does the PRD plan the corresponding data tables?
- Do content classification dimensions match actual business?
Visual Style
- Does the color description match brand tone?
- Does the style tone (business/lively/minimal) match expectations?
Special Reminder: Confirm Data Storage Needs
If your website needs to save visitor-submitted data (booking, registration, messaging, orders), please confirm that the PRD explicitly mentions this, and note:
- Data storage depends on database capability, which some plans do not support.
- If the plan does not support it, you will be prompted to upgrade or skip during generation. Choosing skip means data cannot be saved.
Editing the PRD
Operation Method
Click "Edit Requirements Document" to enter edit mode and directly modify the document content.
Modification Suggestions
Rewrite in clear language, for example:
Add missing pages
Original: Includes Home, Product Center, and About Us pages.
Modified: Includes Home, Product Center, About Us, Contact Us, and News Updates pages.
News Updates supports independently publishing articles in the backend and filtering by category.
Clarify feature details
Original: Provides a contact form.
Modified: Provides a contact form collecting fields: name (required), company name,
phone number (required), email, requirement description (required).
After submission, save to database and viewable in the backend.
Adjust visual description
Original: Modern minimalist style.
Modified: Modern minimalist style. Primary color #1E3A8A dark blue, auxiliary color light gray #F5F5F5,
accent color orange #FF6A00 for buttons. Sans-serif fonts, right-angle borders,
ample white space between sections.
Modification Principles
- Specific is better than vague: Write "three-column card layout" instead of "make the layout nicer."
- Clarify required fields: Mark which form fields are required.
- Explain data sources: Is the content fixed or does it need backend maintenance?
After editing, confirm and click "Generate App Now" → "Confirm Generate App."
Viewing the PRD After Generation
Entry Point
Management backend → Requirements Document
Status Descriptions
| Situation | Description |
|---|---|
| PRD generated | Full content viewable; at this point it is read-only |
| PRD not generated | Shows "App has not generated a requirements document" |
Note: After the website is generated, the PRD becomes read-only and cannot be edited. Because at this point the real state of the website is determined by code, changing the document will not affect the website.
Value of Read-Only PRD
Although it cannot be changed, it is still useful:
| Use | Description |
|---|---|
| Cross-check | Verify whether the generated result matches the original plan |
| Team communication | Explain the design intent to colleagues or clients |
| Reference for later iterations | When making new requests, refer to the PRD's wording style |
| Handover material | Documentation when handing over website maintenance to others |
Frequently Asked Questions
Q: What if PRD generation fails or the content is obviously wrong?
A: You can redescribe the requirements in the conversation and let AI regenerate. If it is still unsatisfactory, we recommend breaking down the requirements more structurally (listing page list and feature list in points) before retrying.
Q: Can I generate the website directly without looking at the PRD?
A: Technically you can directly click confirm, but strongly not recommended. Skipping review often leads to generated results deviating from expectations, ultimately costing more time to fix.
Q: A feature written in the PRD is missing after generation. What should I do?
A: Possible reasons:
- The feature depends on a capability not supported by the current plan (database/premium plugin) and was skipped during generation. Check for relevant prompts.
- AI missed it during implementation. You can point out in the conversation: "The XX feature mentioned in the PRD was not implemented, please supplement."
Q: Can I write the PRD myself and upload it directly?
A: Yes. When creating the website, upload your existing requirements document through "Upload files" (single file maximum 10 MB). AI will read the content as the basis for generation. This is very efficient for projects with clear plans.
Q: After the website has been modified many times, is the PRD still accurate?
A: The PRD reflects the initial plan and will not automatically update with subsequent modifications. After multiple iterations, there will be differences between the PRD and the actual website. Please take the actual website as the standard and use the PRD as historical reference.