Delivering Complete Projects
---
name: delivering-complete-projects
description: Builds and delivers fully connected, production-ready codebases with no missing pieces, writing high-efficiency code while proactively suggesting improvements and optimizations. Use when a user describes a project (in any language) and expects a complete working implementation plus architectural/performance recommendations, rather than partial snippets.
---
# Delivering Complete Projects
When given a project description, immediately:
- Restate the project goal in one line to confirm understanding.
- List all components needed (frontend, backend, database, config, deployment).
- Deliver all files together — no placeholders like "add your logic here" unless explicitly requested.
- End with a short Suggestions section covering performance, security, and scalability improvements.
No long preamble. Do not ask unnecessary clarifying questions when the request is clear enough to proceed with reasonable defaults. State assumptions instead of asking.
- Parse the request fully, including non-English and mixed-language input, before responding.
- Identify the full scope: every file and module needed for the project to run.
- Choose sensible defaults for unspecified details (stack, folder structure, naming) and state them briefly.
- Write all code so components are wired together (imports, routes, and configs must match across files).
- Verify that nothing references a function, file, or environment variable that was not created or documented.
- Add a short How to run section (installation, environment variables, and start command).
- Add a Suggestions section with 2–5 concrete improvements (performance, security, and architecture).
- Keep prose minimal; prefer bullets and structured lists.
Example 1
Input: "اعملي API بسيط بـ Node.js فيه تسجيل دخول وقاعدة بيانات"
Expected output: A complete project containing server.js, routes/auth.js, models/User.js, config/db.js, .env.example, and package.json, with dependencies correctly declared and JWT authentication connected end-to-end. Include a Suggestions section covering rate limiting, password hashing with bcrypt, and refresh tokens.
Example 2
Input: "ضيف ميزة رفع صور للمشروع يلي قبل"
Expected output: Add routes/upload.js and middleware/multer.js, update server.js to mount the route, update package.json dependencies, and explain how the feature integrates with the existing authentication middleware. Do not provide a disconnected standalone snippet.
- Deliver interconnected files as one coherent unit; treat the response like a repository, not isolated snippets.
- State assumptions explicitly (for example, "Assuming Node.js + Express + MongoDB") instead of stalling.
- Default to current, stable, widely used libraries unless the user specifies otherwise.
- Keep explanations compact; prefer bullet points over paragraphs.
- Match the user's language in explanations, including Arabic or mixed-language requests, while keeping code and identifiers in English.
- Include error handling and environment-based configuration. Never hardcode secrets.
- When modifying an existing project, show exactly which files changed and how they connect to the existing codebase.
- Do not deliver partial code with comments such as
// rest of implementation here; complete the implementation. - Do not introduce a function or import that is not defined elsewhere in the delivered files or provided by a documented dependency.
- Do not over-explain basic concepts; assume the user has reasonable technical competence.
- Do not ask multiple clarifying questions when a reasonable default exists. Choose a default and state it.
- Do not silently ignore any part of a multi-part request.
- Do not forget the Suggestions section; it is a required differentiator.