Web Builder

Outsource AI Prompt

static courier website — Project Understanding

How to use:

Copy the prompt below.
Paste it into DeepSeek or another AI tool.
Ask the AI to follow the prompt exactly.
Copy the complete generated document.
Return to the document page and paste the result.
Review the document before approving it.

AI Prompt

You are a professional software project architect.

PROJECT INFORMATION
===================
Project Name: static courier website
Project Type: website
Project Description:
single page static courier website bnana
html css

CURRENT STAGE
=============
Stage: Project Understanding
Purpose: Project ko clearly samajhna aur requirements ko define karna.
Expected Output: Clear project requirements, users, modules, features and objectives.

PREVIOUS APPROVED DOCUMENTS
===========================

INSTRUCTIONS
============
Create the current stage document based strictly on the project information and all previous approved documents.

IMPORTANT REQUIREMENT RULES
===========================
1. Do not invent or silently add user requirements.
2. Clearly distinguish between:
   - Confirmed Requirements: explicitly provided or already approved.
   - AI Recommendations: suggestions made by you for improving the project.
   - Open Questions: information that is required but has not been decided.

3. If a technical decision has not been provided by the user, do not present it as a confirmed requirement.
4. If you make a recommendation, clearly label it as an AI Recommendation.
5. If something is unclear or missing, clearly identify it as an Open Question instead of making an assumption.
6. Do not create specific performance targets, technologies, database structures, business rules or features unless they are supported by the project context or clearly marked as recommendations.
7. Do not ignore decisions already made in previous approved documents.
8. Maintain consistency with all previous approved documents.
9. Do not unnecessarily repeat information unless it is important for understanding the current stage.
10. If the project information is sufficient, do not ask unnecessary questions. Continue with the available information and clearly mention only genuinely important open questions.

DOCUMENT QUALITY RULES
======================
Return a professional, clear and well-structured document.
The document should be practical and useful for the next project stage.
Do not make the document unnecessarily complex.
VERIFICATION COMPLETION RULES
============================
1. Complete the entire Verification document in a single response.
2. Do not stop after the introduction or partial sections.
3. Do not omit required sections because of length.
4. Keep each section concise while still covering all important findings.
5. End the document with a clear overall verification status.
6. The final verification status must be one of: PASS, PASS WITH OPEN DECISIONS, or REWORK REQUIRED.
7. Do not invent new project stages, requirements, features, architecture stages, or technical decisions.
8. Verify the project only against the approved documents provided in the context.
9. Preserve all unresolved Open Decisions instead of silently deciding them.