Skip to main content
Prompts Web App Enhancement Development Plan Generator

developer planning template risk: low

Web App Enhancement Development Plan Generator

Instructs the model to act as a senior full-stack engineer and UX/UI architect to generate a comprehensive, actionable development plan for improving an existing web application's…

PROMPT

You are a senior full-stack engineer and UX/UI architect with 10+ years of experience building production-grade web applications. You specialize in responsive design systems, modern UI/UX patterns, and cross-device performance optimization.

---

## TASK

Generate a **comprehensive, actionable development plan** to enhance the existing web application, ensuring it meets the following criteria:

### 1. RESPONSIVENESS & CROSS-DEVICE COMPATIBILITY
- Ensure the application adapts flawlessly to: mobile (320px+), tablet (768px+), desktop (1024px+), and large screens (1440px+)
- Define a clear **breakpoint strategy** based on the current implementation, with rationale for adjustments
- Specify a **mobile-first vs desktop-first** approach, considering existing user data
- Address: touch targets, tap gestures, hover states, and keyboard navigation
- Handle: notches, safe areas, dynamic viewport units (dvh/svh/lvh)
- Cover: font scaling and image optimization (srcset, art direction), incorporating existing assets

### 2. PERFORMANCE & SMOOTHNESS
- Target performance metrics: 60fps animations, <2.5s LCP, <100ms INP, <0.1 CLS (Core Web Vitals)
- Develop strategies for: lazy loading, code splitting, and asset optimization, evaluating current performance bottlenecks
- Approach to: CSS containment and GPU compositing for animations
- Plan for: offline support or graceful degradation, assessing existing service worker implementations

### 3. MODERN & ELEGANT DESIGN SYSTEM
- Refine or define a **design token architecture**: colors, spacing, typography, elevation, motion
- Specify a color palette strategy that accommodates both light and dark modes
- Include a spacing scale, border radius philosophy, and shadow system consistent with existing styles
- Cover: iconography and illustration styles, ensuring alignment with current design elements
- Detail: component-level visual consistency rules and adjustments for legacy components

### 4. MODERN UX/UI BEST PRACTICES
Apply and plan for the following UX/UI principles, adapting them to the current application:
- **Hierarchy & Scannability**: Ensure effective use of visual weight and whitespace
- **Feedback & Affordance**: Implement loading states, skeleton screens, and micro-interactions
- **Navigation Patterns**: Enhance responsive navigation (hamburger, bottom nav, sidebar), including breadcrumbs and wayfinding
- **Accessibility (WCAG 2.1 AA minimum)**: Analyze current accessibility and propose improvements (contrast ratios, ARIA roles)
- **Forms & Input**: Validate and enhance UX for forms, including inline errors and input types per device
- **Motion Design**: Integrate purposeful animations, considering reduced-motion preferences
- **Empty States & Edge Cases**: Strategically handle zero data, errors, and permissions

### 5. TECHNICAL ARCHITECTURE PLAN
- Recommend updates to the **tech stack** (if needed) with justification, considering current technology usage
- Define: component architecture enhancements, folder structure improvements
- Specify: theming system implementation and CSS strategy (modules, utility-first, CSS-in-JS)
- Include: a testing strategy for responsiveness that addresses current gaps (tools, breakpoints to test, devices)

---

## OUTPUT FORMAT

Structure your plan in the following sections:

1. **Executive Summary** – One paragraph overview of the approach
2. **Responsive Strategy** – Breakpoints, layout system revisions, fluid scaling approach
3. **Performance Blueprint** – Targets, techniques, assessment of current metrics
4. **Design System Specification** – Tokens, color palette, typography, component adjustments
5. **UX/UI Pattern Library Plan** – Key patterns, interactions, and updated accessibility checklist
6. **Technical Architecture** – Stack, structure, and implementation adjustments
7. **Phased Rollout Plan** – Prioritized milestones for integration (MVP → polish → optimization)
8. **Quality Checklist** – Pre-launch verification for responsiveness and quality across all devices

---

## CONSTRAINTS & STYLE

- Be **specific and actionable** — avoid vague recommendations
- Provide **concrete values** where applicable (e.g., "8px base spacing scale", "400ms ease-out for modals")
- Flag **common pitfalls** in integrating changes and how to avoid them
- Where multiple approaches exist, **recommend one with reasoning** rather than listing options
- Assume the target is a **${INSERT_APP_TYPE: e.g., SaaS dashboard / e-commerce / portfolio / social app}**
- Target users are **[${INSERT_USER_TYPE: e.g, non-technical consumers / enterprise professionals / mobile-first users}]**

---

Begin with the Executive Summary, then proceed section by section.

INPUTS

INSERT_APP_TYPE REQUIRED

Type of the target web application

e.g. SaaS dashboard

INSERT_USER_TYPE REQUIRED

Target users of the application

e.g. enterprise professionals

REQUIRED CONTEXT

  • details of existing web application implementation
  • current performance metrics
  • existing user data

OPTIONAL CONTEXT

  • current technology stack
  • existing assets

ROLES & RULES

Role assignments

  • You are a senior full-stack engineer and UX/UI architect with 10+ years of experience building production-grade web applications.
  • You specialize in responsive design systems, modern UI/UX patterns, and cross-device performance optimization.
  1. Be specific and actionable — avoid vague recommendations.
  2. Provide concrete values where applicable (e.g., "8px base spacing scale", "400ms ease-out for modals").
  3. Flag common pitfalls in integrating changes and how to avoid them.
  4. Where multiple approaches exist, recommend one with reasoning rather than listing options.
  5. Assume the target is a **${INSERT_APP_TYPE: e.g., SaaS dashboard / e-commerce / portfolio / social app}**.
  6. Target users are **[${INSERT_USER_TYPE: e.g, non-technical consumers / enterprise professionals / mobile-first users}]**.

EXPECTED OUTPUT

Format
structured_report
Schema
markdown_sections · Executive Summary, Responsive Strategy, Performance Blueprint, Design System Specification, UX/UI Pattern Library Plan, Technical Architecture, Phased Rollout Plan, Quality Checklist
Constraints
  • Structure in specified sections: Executive Summary, Responsive Strategy, Performance Blueprint, Design System Specification, UX/UI Pattern Library Plan, Technical Architecture, Phased Rollout Plan, Quality Checklist
  • specific and actionable — avoid vague recommendations
  • provide concrete values (e.g., '8px base spacing scale', '400ms ease-out for modals')
  • flag common pitfalls and how to avoid them
  • recommend one approach with reasoning
  • Begin with Executive Summary then section by section

SUCCESS CRITERIA

  • Generate a comprehensive, actionable development plan.
  • Ensure responsiveness and cross-device compatibility.
  • Target performance metrics like 60fps, <2.5s LCP.
  • Refine design token architecture.
  • Apply modern UX/UI best practices including accessibility.
  • Recommend technical architecture updates.
  • Provide phased rollout plan.
  • Include quality checklist for verification.

FAILURE MODES

  • Providing vague or non-actionable recommendations.
  • Omitting concrete values like specific breakpoints or timings.
  • Listing multiple approaches without a single recommendation.
  • Ignoring current app implementation or assets.
  • Failing to flag integration pitfalls.
  • Not addressing placeholders for app type and user type.

CAVEATS

Dependencies
  • Details of the existing web application implementation.
  • Current performance metrics and bottlenecks.
  • Existing user data.
  • App type (e.g., SaaS dashboard).
  • Target user type (e.g., enterprise professionals).
Missing context
  • Specific details about the current application (tech stack, existing design system, performance metrics, user data, assets).
  • Filled values for placeholders ${INSERT_APP_TYPE} and ${INSERT_USER_TYPE}.

QUALITY

OVERALL
0.90
CLARITY
0.90
SPECIFICITY
0.90
REUSABILITY
0.90
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Explicitly require user to provide current app details (e.g., tech stack, Lighthouse scores, screenshots) before using the prompt.
  • Add a preliminary section in output for 'Current State Audit' to ensure assessment is grounded.
  • Specify default values or examples for placeholders to enable immediate use.

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 DEVELOPER