Examples — Inputs That Undascor Turns Into Optimized Prompts

Example:

I want to write a blog post about sustainable living for urban millennials using conversational tone with practical tips so they feel inspired to make eco-friendly changes.

Why it works: Clear content type, topic, audience, style, and outcome.

Generated Prompt

Act as a sustainability expert specializing in urban lifestyles for millennial audiences. Create an engaging, practical guide to sustainable living that makes eco-friendly choices accessible and appealing for city dwellers.

Requirements:
1. Begin with a compelling introduction highlighting the impact of small sustainable changes in urban environments.
2. Cover key areas: reducing waste, sustainable transportation, ethical consumption, and energy efficiency.
3. Provide specific, actionable tips for apartment living (e.g., composting solutions for small spaces, sustainable grocery shopping).
4. Include a cost-benefit analysis showing long-term savings from sustainable choices.
5. Address common urban sustainability challenges: limited space, convenience factors, and budget constraints.

Constraints:
- Focus on changes that can be implemented immediately with minimal effort.
- Include both free/low-cost options and premium sustainable alternatives.
- Use relatable examples from urban daily life (commuting, shopping, dining).
- Maintain a positive tone without guilt-tripping.

Output Specifications:
- Length: 1,000-1,300 words
- Structure: Why It Matters, Easy Wins, Bigger Impact Changes, Maintaining Momentum
- Tone: Conversational yet authoritative, optimistic, and non-judgmental
- Include 5-7 immediately implementable tips with clear instructions

Success Criteria:
Urban millennials should finish reading feeling empowered to make at least 3 sustainable changes in their daily routine, with a clear understanding of both environmental impact and personal benefits.

Why it works: It follows a complete prompt formula: Role + Audience + Goal. It provides specific Requirements (what to cover), Constraints (what to avoid/prioritize), and Output Specifications (format and structure), leaving the AI with very little ambiguity.

Example:

I want to write Python code for a REST API endpoint that accepts JSON user data, validates required fields, and saves to PostgreSQL database following security best practices with error handling.

Why it works: Language, feature, requirements, and constraints are specified.

Generated Prompt

Act as a senior backend developer specializing in secure REST API development with Python and PostgreSQL. Create a production-ready REST API endpoint for user data management that includes validation, security measures, error handling, and database persistence.

Requirements:
1. Design RESTful endpoint structure following best practices for resource naming, HTTP methods, and status codes.
2. Implement JSON schema validation for user data with detailed error messages for invalid inputs.
3. Apply security best practices including input sanitization, parameterized queries, and HTTPS enforcement.
4. Develop consistent error response format across all failure scenarios.
5. Create database layer with proper connection handling and transaction management.

Technical Specifications:
- Framework: Python Flask with Flask-RESTful or similar extension
- Database: PostgreSQL with SQLAlchemy ORM
- Validation: JSON schema validation with descriptive error messages
- Security: Input sanitization, parameterized queries, HTTPS
- Error Handling: Consistent error response format (status codes, error codes, messages)

API Design:
- Endpoint: POST /api/v1/users
- Request: JSON payload with required fields (username, email, password)
- Response: Success/error JSON with appropriate HTTP status codes
- Validation: Required fields, data types, business logic constraints
- Database: Secure user data persistence with transaction rollback on failure

Implementation Requirements:
1. Input validation layer with schema-based validation
2. Security layer for input sanitization and parameterized queries
3. Database persistence layer with proper error handling
4. Response formatting layer for consistent output
5. Logging and monitoring integration

Security Best Practices:
- Use parameterized queries to prevent SQL injection
- Validate and sanitize all user inputs
- Enforce HTTPS for secure communication
- Hash passwords before storage using bcrypt or similar
- Implement rate limiting to prevent abuse

Error Handling:
- Detailed error messages for validation failures
- Consistent error response format for database errors
- Proper HTTP status codes for all scenarios
- Graceful handling of database connection issues

Output Format:
1. Complete Flask application structure with modular organization
2. API endpoint implementation with all specified features
3. Database models and migration scripts
4. Documentation: API spec, security guidelines, deployment instructions

Success Criteria:
API endpoint should be production-ready with comprehensive security measures, thorough validation, proper error handling, and following REST best practices for enterprise-grade user data management system.

Why it works: It follows a complete prompt formula: Role + Technology Stack + Goal. It provides specific Requirements (functional scope), Technical Specifications (frameworks and tools), API Design (endpoint structure), Implementation Requirements (layered approach), Security Best Practices (non-functional requirements), Error Handling (edge cases), and Output Format (deliverables), leaving the AI with a clear blueprint for production-ready code.

Example:

I want to analyze Q3 sales data for our e-commerce store using cohort analysis and trend comparisons to identify underperforming product categories and recommend inventory adjustments.

Why it works: Subject, method, and decision purpose are clear.

Generated Prompt

Act as a senior e-commerce analyst specializing in sales performance and inventory optimization. Analyze Q3 sales data using cohort analysis and trend comparisons to identify underperforming product categories and recommend strategic inventory adjustments.

Requirements:
1. Perform cohort analysis by customer segments, acquisition channels, and purchase frequency.
2. Compare sales trends across product categories, identifying patterns in demand and seasonality.
3. Evaluate inventory turnover rates and identify slow-moving or obsolete stock.
4. Assess profitability by category, considering margins, discounting, and return rates.
5. Identify correlations between marketing campaigns, sales performance, and inventory levels.

Constraints:
- Use verified internal sales and inventory data.
- Account for external factors such as competitor activity and market trends.
- Focus on actionable insights with measurable outcomes.

Methodology:
- Cohort segmentation by purchase date and customer behavior.
- Trend analysis using time series decomposition.
- Profitability analysis by product category and SKU.
- Inventory optimization modeling considering demand forecasts.

Output Format:
1. Executive Summary: Key findings and recommendations.
2. Category Performance Analysis: Detailed metrics and visualizations.
3. Inventory Adjustment Recommendations: Prioritized actions by category.
4. Implementation Plan: Timeline and resource requirements.
5. Risk Assessment: Potential challenges and mitigation strategies.

Success Criteria:
Analysis should provide data-driven recommendations for inventory optimization, improving turnover rates and profitability while reducing stockouts and excess inventory.

Why it works: It follows a complete prompt formula: Role + Data Source + Analytical Goal. It provides specific Requirements (what to analyze), Constraints (scope and limitations), Methodology (analytical approach), Output Format (deliverable structure), and Success Criteria (business outcomes), ensuring the AI delivers actionable business intelligence rather than generic observations.

Example:

I want to plan mobile app launch over 6 months considering phased rollout and beta testing with 500 users using agile methodology to achieve 10,000 downloads.

Why it works: Objective, timeframe, constraints, and success metrics are included.

Generated Prompt

Act as a senior mobile app launch strategist specializing in agile methodologies. Develop a comprehensive 6-month launch plan incorporating phased feature rollout and structured beta testing with 500 users to achieve 10,000 downloads.

Requirements:
1. Create a phased feature rollout plan aligned with agile development sprints and iterative feedback incorporation.
2. Design a beta testing program for 500 users with clear feedback collection mechanisms and iteration cycles.
3. Establish a marketing strategy focused on user acquisition to achieve 10,000 downloads.
4. Define KPIs for tracking progress toward download targets and user satisfaction.
5. Incorporate risk management strategies for potential launch challenges.

Launch Timeline (6 Months):
- Months 1-2: Beta testing preparation, recruitment of beta users, initial marketing setup.
- Months 3-4: Beta testing execution, feature refinement based on feedback, marketing campaign launch.
- Months 5-6: Full app launch, user acquisition scaling, performance optimization.

Beta Testing Program:
- Recruit 500 beta users representing target demographics.
- Implement agile feedback loops: weekly surveys, usage analytics, and direct interviews.
- Schedule bi-weekly iteration cycles based on user feedback.
- Establish benchmarks for launch readiness and quality assurance.

Marketing Strategy:
- Focus on digital acquisition channels: app store optimization, social media campaigns, and influencer partnerships.
- Develop a phased marketing calendar aligned with feature rollout milestones.
- Allocate budget across primary acquisition channels to maximize ROI.

Success Metrics:
- Primary: 10,000 downloads within 6 months.
- Secondary: User engagement metrics, retention rates, and conversion rates.
- Operational: Development velocity, bug resolution time, and customer support capacity.

Risk Management:
- Identify technical scalability challenges and mitigation strategies.
- Plan for competitive responses and market fluctuations.
- Prepare contingency plans for user acquisition cost variations and app store algorithm changes.

Output Specifications:
1. Detailed 6-month launch calendar with agile milestones and dependencies.
2. Beta testing program design with feedback mechanisms and iteration cycles.
3. Marketing campaign plan with budget allocations and phased execution.
4. KPI dashboard design for tracking progress toward download targets.
5. Risk assessment documentation with contingency plans.

Success Criteria:
The launch plan should provide a clear, actionable roadmap for achieving 10,000 downloads through systematic beta testing, agile feature rollout, and targeted marketing efforts.

Why it works: It follows a complete prompt formula: Role + Methodology + Goal. It provides specific Requirements (functional components), Launch Timeline (phased execution), Beta Testing Program (user feedback structure), Marketing Strategy (acquisition approach), Success Metrics (quantifiable targets), Risk Management (contingency planning), and Output Specifications (deliverable format), ensuring the AI produces a comprehensive, executable launch strategy with clear dependencies and measurable outcomes.

Example:

I want to rewrite technical documentation for non-technical small business owners converting jargon-heavy sections into simple checklists while preserving safety warnings.

Why it works: Source material, audience, style change, and what must be preserved are stated.

Generated Prompt

Act as a technical documentation specialist with expertise in simplifying complex information for non-technical audiences. Rewrite technical product documentation into clear, actionable formats specifically tailored for small business owners.

Requirements:
1. Identify and replace all technical jargon with plain business language.
2. Convert complex procedures into step-by-step checklists with clear action items.
3. Preserve all original safety warnings and compliance requirements, highlighting them prominently.
4. Structure content for quick scanning and easy reference during implementation.
5. Include practical business context explaining why each step matters to operations.

Transformation Guidelines:
- Technical terms → Business-friendly equivalents
- Configuration options → Practical decision points
- System requirements → Compatibility considerations
- Error messages → Problem-solving steps
- Maintenance procedures → Routine task schedules

Format Specifications:
1. Primary output: Quick-start implementation guide
2. Secondary output: Safety & compliance reference sheet
3. Tertiary output: Troubleshooting flowchart

Visual Elements:
- Warning icons for safety-critical information
- Checkmark symbols for completed steps
- Simple diagrams for complex concepts
- Color coding for priority levels (red=critical, yellow=important, green=optional)

Constraints:
- Maintain 100% technical accuracy
- Preserve all original compliance language verbatim
- Keep total length within 10% of original document
- Ensure standalone usability without technical support

Success Criteria:
Small business owners should be able to:
1. Implement the product correctly without technical assistance
2. Quickly locate safety-critical information
3. Understand all necessary procedures in business terms
4. Complete all required compliance steps
5. Troubleshoot common issues independently

Why it works: It follows a complete prompt formula: Role + Source Material + Target Audience. It provides specific Requirements (transformation objectives), Transformation Guidelines (terminology mapping), Format Specifications (deliverable types), Visual Elements (design requirements), Constraints (non-negotiables), and Success Criteria (user outcomes), ensuring the AI produces documentation that is technically accurate yet accessible to business users with no prior technical knowledge.

Example:

I want to automate weekly sales report generation that takes 3 hours manually pulling data from multiple sources using Python scripts to save 90% time while ensuring accuracy.

Why it works: Task, current pain, method, and outcome are clear.

Generated Prompt

Act as a senior automation engineer specializing in business intelligence systems. Design and implement an automated weekly sales report generation system using Python that consolidates data from multiple sources, reduces manual effort by 90%, and ensures accuracy.

Requirements:
1. Automate data extraction from multiple sources (CRM, analytics, marketing platforms).
2. Transform and consolidate data into standardized format for reporting.
3. Generate professional reports with visualizations and key metrics.
4. Schedule automated execution using cloud functions for weekly delivery.
5. Implement error handling, logging, and monitoring for production reliability.

Technical Specifications:
- Programming Language: Python with required libraries (pandas, matplotlib, reportlab, API clients).
- Cloud Platform: AWS/GCP/Azure for scheduled execution.
- Storage: Cloud storage for historical reports and raw data.
- Monitoring: Error tracking, performance metrics, success/failure notifications.
- Security: API key management, data encryption, access controls.

Implementation Requirements:
1. API integration setup with authentication and rate limiting.
2. Data pipeline with transformation and validation steps.
3. Report template design with dynamic content insertion.
4. Scheduling configuration for automated weekly execution.
5. Error handling and alerting system for failed executions.
6. Historical data storage and retrieval capabilities.

Success Metrics:
- Time reduction: From 3 hours manual to <18 minutes automated (90% reduction).
- Accuracy improvement: Eliminate manual data entry errors.
- Reliability: 99%+ successful automated executions.
- Scalability: Ability to add new data sources and report formats.
- Maintainability: Clear documentation and monitoring for ongoing operations.

Output Specifications:
1. Complete Python codebase with modular architecture.
2. Cloud infrastructure configuration for scheduled execution.
3. Report template designs and formatting specifications.
4. Monitoring dashboard for automation performance.
5. Documentation: Setup guide, troubleshooting, maintenance procedures.

Success Criteria:
The automation system should reliably generate weekly sales reports with zero manual intervention, reduce processing time from 3 hours to under 18 minutes, and provide consistent, accurate reporting for sales leadership decision-making.

Why it works: It follows a complete prompt formula: Role + System Type + Measurable Goal. It provides specific Requirements (functional scope), Technical Specifications (technology stack), Implementation Requirements (development tasks), Success Metrics (quantifiable outcomes), and Output Specifications (deliverable artifacts), ensuring the AI delivers a production-ready automation solution with clear performance benchmarks and maintainability standards for enterprise business intelligence systems.