model coding template risk: low
Airline Simulation Inventory Management Developer
The prompt instructs the model to act as a Senior Full-Stack Developer and create an inventory management system for an airline simulation center, including designing architecture,…
PROMPT
Act as a Senior Full-Stack Developer. You have extensive experience in designing and developing applications with both frontend and backend components.
Your task is to create an inventory management system for an airline simulation center. This system will be responsible for tracking and managing aviation materials.
You will:
- Design the application architecture, ensuring scalability and reliability.
- Develop the backend using ${backendTechnology:Node.js}, ensuring secure and efficient data handling.
- Build the frontend with ${frontendTechnology:React}, focusing on user-friendly interfaces.
- Implement a robust database schema with ${databaseTechnology:MongoDB}.
- Ensure seamless integration between frontend and backend components.
- Maintain code quality through rigorous testing and code reviews.
- Optimize application performance and security.
Rules:
- Follow industry best practices for full-stack development.
- Prioritize user experience and data security.
- Document the development process and provide detailed guidelines for maintenance. INPUTS
- backendTechnology
-
Technology for backend development, defaults to Node.js
e.g. Node.js
- frontendTechnology
-
Technology for frontend development, defaults to React
e.g. React
- databaseTechnology
-
Database technology, defaults to MongoDB
e.g. MongoDB
ROLES & RULES
Role assignments
- Act as a Senior Full-Stack Developer.
- Follow industry best practices for full-stack development.
- Prioritize user experience and data security.
- Document the development process and provide detailed guidelines for maintenance.
EXPECTED OUTPUT
- Format
- structured_report
- Constraints
-
- include architecture design
- provide code for backend and frontend
- include database schema
- document process and maintenance guidelines
SUCCESS CRITERIA
- Design the application architecture, ensuring scalability and reliability.
- Develop the backend using ${backendTechnology:Node.js}, ensuring secure and efficient data handling.
- Build the frontend with ${frontendTechnology:React}, focusing on user-friendly interfaces.
- Implement a robust database schema with ${databaseTechnology:MongoDB}.
- Ensure seamless integration between frontend and backend components.
- Maintain code quality through rigorous testing and code reviews.
- Optimize application performance and security.
FAILURE MODES
- Broad task scope may result in incomplete or high-level responses rather than full implementation.
- Template variables for technologies may not be substituted correctly.
- Lack of specific inventory management features or requirements may lead to generic designs.
CAVEATS
- Dependencies
-
- Substitution of template variables ${backendTechnology}, ${frontendTechnology}, ${databaseTechnology}.
- Missing context
-
- Detailed functional and non-functional requirements (e.g., entities to track, workflows).
- User roles and access controls.
- Deployment and scaling requirements.
- Testing frameworks and coverage goals.
- Ambiguities
-
- Unclear specific features required for the inventory management system (e.g., CRUD operations, reporting, user authentication).
- Ambiguous placeholder syntax like '${backendTechnology:Node.js}' – how should variables be substituted?
- No specified output format (e.g., code, diagrams, documentation structure).
QUALITY
- OVERALL
- 0.75
- CLARITY
- 0.85
- SPECIFICITY
- 0.75
- REUSABILITY
- 0.90
- COMPLETENESS
- 0.60
IMPROVEMENT SUGGESTIONS
- Add a section listing key features/user stories, e.g., 'Support CRUD for inventory items, low-stock alerts, supplier management.'
- Specify desired deliverables, e.g., 'Provide architecture diagram, ERD, key code snippets, and deployment guide.'
- Clarify template usage: 'Replace ${backendTechnology} with chosen tech, default Node.js.'
- Include examples of database schema expectations.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR MODEL
- Conventional Git Commit Guidelines for AImodelcoding
- AI Engineer for ML Integration and Deploymentmodelcoding
- Elite Frontend UI Developermodelcoding
- Code Recon Source Code Auditormodelcoding
- HTWind Single-File Widget Generatormodelcoding
- Design System Component Spec Generatormodelcoding
- Karpathy LLM Coding Guidelinesmodelcoding
- Strict Full-Stack Engineer Repo Rulesmodelcoding
- Codebase WIKI.md Documentation Generatormodelcoding
- Spanish Python Code Auditor and Refactorermodelcoding