Overview
This prompt aims to guide a professional programmer in developing a user management system with specific requirements and technologies. Developers and project managers will benefit from the structured implementation plan and best practices outlined in the response.
Prompt Overview
Purpose: This document outlines the development plan for a user management system tailored for a web server project.
Audience: The intended audience includes developers and project managers involved in the programming and coding industry.
Distinctive Feature: The system will uniquely combine console-based user registration with a web-based login interface.
Outcome: Successful implementation will enhance user management and security for the web server project.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Data Analytics & Business Intelligence, Development Tools & DevOps, General Business Operations
- Techniques: Decomposition, Plan-Then-Solve, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
You are a professional programmer tasked with developing a user management system for a web server project using the following specifications:
1. User Registration:
Implement a one-sided registration system performed exclusively via the console (no UI registration).
2. Login:
Create a login system accessible through a web page.
3. Session Persistence:
Implement cookie-based user session storage that keeps the user logged in for 24 hours only if the “remember me” checkbox is selected during login.
4. Admin Page:
Develop and integrate the admin dashboard using an existing template, which you can extend further.
**Technical Stack and Tools:**
– Backend Framework: Express.js
– Database: MongoDB using Mongoose ODM
– Template Engine for Frontend: EJS
– Password Hashing: bcrypt
– Session/Cookie Management:
Recommend and implement the most suitable package (e.g., express-session vs jsonwebtoken), focusing on security and ease of use.
**Existing Project Information:**
– Files Available: server.js, errorHandle.js, project folder structure, and .env configuration (including environment variables).
– Current Middleware: No middleware for authentication or authorization.
**User Schema Requirements:**
– Fields: username, email, hashed password, role (only “admin” role exists), timestamps.
– Access Control: No role-based access control beyond “admin”.
**Frontend:**
– Admin Panel Template: Ready to be integrated (or needs to be created).
– CSS Framework: Bootstrap
– Design Requirement: Responsive design is required.
**Security:**
– Rate Limiting: Limit to 5 login attempts to prevent brute force attacks.
**Task Instructions:**
– Specify all resources, files, or information you need to begin development.
– Include detailed steps and recommendations to implement the system, considering scalability and maintainability.
– Provide clear reasoning behind technology choices, especially for session management.
# Steps
5. Review the existing code and folder structure.
6. Define the user schema with Mongoose, including necessary validations.
7. Implement the console-based registration script.
8. Develop login functionality with Express.js and EJS, including “remember me” cookie logic.
9. Set up session or token management with selected libraries.
10. Implement login attempt rate limiting.
11. Integrate the admin template and ensure responsiveness with Bootstrap.
12. Secure all routes, especially administrative ones.
# Output Format
Provide a detailed implementation plan that includes:
– The exact list of resources/files you require.
– A step-by-step development plan.
– Suggested code snippets or pseudocode for critical parts.
– Justifications for technology and design decisions.
– Any additional notes on security, scalability, or user experience.
# Notes
– Consider best practices for password hashing and cookie security.
– Suggest improvements where applicable, such as adding middleware.
– Keep explanations clear and professional to guide the implementation thoroughly.
Your response must be comprehensive and structured to enable the smooth development of the described user management system.
Screenshot Examples
How to Use This Prompt
- Copy the prompt for user management system specifications.
- Review the existing project files and folder structure.
- Define the user schema using Mongoose with validations.
- Implement console-based user registration functionality.
- Develop login functionality with “remember me” cookie logic.
- Set up session management and rate limiting for logins.
Tips for Best Results
- Review Existing Code: Examine the current project structure and files to understand the existing setup and identify areas for integration.
- Define User Schema: Create a Mongoose schema for users with fields for username, email, hashed password, role, and timestamps, ensuring proper validation for each field.
- Implement Registration: Develop a console-based registration script that prompts for user details, hashes the password using bcrypt, and saves the user to the database.
- Setup Session Management: Choose express-session for cookie management, ensuring secure cookie settings and implementing “remember me” functionality for session persistence.
FAQ
- What is the first step in developing the user management system?
Review the existing code and folder structure to understand the current setup. - How should the user schema be defined?
Use Mongoose to define fields like username, email, hashed password, role, and timestamps. - What technology should be used for session management?
Consider using express-session for cookie-based session management due to its simplicity and security. - How can login attempts be limited?
Implement rate limiting middleware to restrict login attempts to 5 to prevent brute force attacks.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (February 2026): Initial release.
