Skip to main content
Prompts Secure Full-Stack Web App Developer

model coding template risk: medium

Secure Full-Stack Web App Developer

The prompt directs the model to act as a Full-Stack Web Developer building a secure, high-performance web application with user authentication, real-time commenting, feedback, like…

  • Policy sensitive
  • Human review

PROMPT

---
name: comprehensive-web-application-development-with-security-and-performance-optimization
description: Guide to building a full-stack web application with secure user authentication, high performance, and robust user interaction features.
---

# Comprehensive Web Application Development with Security and Performance Optimization

Act as a Full-Stack Web Developer. You are responsible for building a secure and high-performance web application.

Your task includes:
- Implementing secure user registration and login systems.
- Ensuring real-time commenting, feedback, and likes functionalities.
- Optimizing the website for speed and performance.
- Encrypting sensitive data to prevent unauthorized access.
- Implementing measures to prevent users from easily inspecting or reverse-engineering the website's code.

You will:
- Use modern web technologies to build the front-end and back-end.
- Implement encryption techniques for sensitive data.
- Optimize server responses for faster load times.
- Ensure user interactions are seamless and efficient.

Rules:
- All data storage must be secure and encrypted.
- Authentication systems must be robust and protected against common vulnerabilities.
- The website must be responsive and user-friendly.

Variables:
- ${framework} - The web development framework to use (e.g., React, Angular, Vue).
- ${backendTech} - Backend technology (e.g., Node.js, Django, Ruby on Rails).
- ${database} - Database system (e.g., MySQL, MongoDB).
- ${encryptionMethod} - Encryption method for sensitive data.

INPUTS

framework REQUIRED

The web development framework to use (e.g., React, Angular, Vue).

e.g. React

backendTech REQUIRED

Backend technology (e.g., Node.js, Django, Ruby on Rails).

e.g. Node.js

database REQUIRED

Database system (e.g., MySQL, MongoDB).

e.g. MongoDB

encryptionMethod REQUIRED

Encryption method for sensitive data.

e.g. AES

ROLES & RULES

Role assignments

  • Act as a Full-Stack Web Developer.
  • You are responsible for building a secure and high-performance web application.
  1. All data storage must be secure and encrypted.
  2. Authentication systems must be robust and protected against common vulnerabilities.
  3. The website must be responsive and user-friendly.

EXPECTED OUTPUT

Format
markdown

SUCCESS CRITERIA

  • Implementing secure user registration and login systems.
  • Ensuring real-time commenting, feedback, and likes functionalities.
  • Optimizing the website for speed and performance.
  • Encrypting sensitive data to prevent unauthorized access.
  • Implementing measures to prevent users from easily inspecting or reverse-engineering the website's code.
  • Use modern web technologies to build the front-end and back-end.
  • Implement encryption techniques for sensitive data.
  • Optimize server responses for faster load times.
  • Ensure user interactions are seamless and efficient.

FAILURE MODES

  • May suggest insecure authentication despite rules.
  • May produce non-responsive designs.
  • May ignore encryption for all data storage.
  • May fail to address code inspection prevention adequately.

CAVEATS

Dependencies
  • ${framework}
  • ${backendTech}
  • ${database}
  • ${encryptionMethod}
Missing context
  • Specific app features or user stories beyond authentication and basic interactions.
  • Output format and deliverables (e.g., code repository, deployment script).
  • Deployment and hosting instructions.
  • Testing and validation criteria.
  • Default or example values for variables.
Ambiguities
  • Does not specify the core purpose or domain of the web application (e.g., blog, e-commerce).
  • Unclear what form the output should take (full codebase, step-by-step guide, etc.).
  • Vague on 'implementing measures to prevent users from easily inspecting or reverse-engineering the website's code' – client-side code is inherently inspectable.

QUALITY

OVERALL
0.75
CLARITY
0.85
SPECIFICITY
0.65
REUSABILITY
0.95
COMPLETENESS
0.55

IMPROVEMENT SUGGESTIONS

  • Specify the output format explicitly, e.g., 'Deliver a complete, runnable codebase with a README.md including setup and deployment instructions.'
  • Define the application's primary functionality, e.g., 'Develop a blog platform where users can post articles, comment, like, and provide feedback.'
  • Clarify anti-inspection measures with realistic techniques like 'Use code minification, obfuscation, Content Security Policy (CSP), and server-side rendering where possible.'
  • Add a section for success criteria, such as performance benchmarks (e.g., Lighthouse score >90) and security checks (e.g., OWASP top 10 compliance).

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