Trending Prompts

Animated chart showing Monthly Recurring Revenue scaling. Requirements: 1. Smooth upward curve without volatility. 2. Interactive value labels on hover. 3. Milestone markers (e.g., '$10K MRR'). 4. Transition between 'Monthly' and 'Annual' views. Style: Sleek financial UI with high-contrast glowing lines against a dark backdrop.

Measure which prompt performs better. Features: 1. Two versions of a prompt (Variant A vs B). 2. Key Metrics: Relevancy Score, Accuracy, Response Speed, Token Usage. 3. Statistically significant 'Winner' badge. 4. User feedback collection tool for manual evaluation. 5. Chart comparing costs over 1,000 runs.

Create developer-friendly API documentation. Structure: 1. Overview with quick start guide and authentication. 2. Endpoint reference with request/response examples. 3. Interactive API explorer (Swagger/Postman style). 4. Code samples in multiple languages (Python, JavaScript, cURL). 5. Error codes and troubleshooting guide. 6. Rate limiting and best practices. 7. Webhook documentation with payload examples. 8. Changelog and versioning information. Use clear, concise language with real-world use cases.

Refactor code safely and effectively. Common refactorings: 1. Extract Method (long function → smaller functions). 2. Rename Variable (unclear → descriptive). 3. Extract Class (large class → multiple focused classes). 4. Inline Method (unnecessary abstraction). 5. Replace Magic Numbers with Constants. 6. Introduce Parameter Object (long parameter lists). 7. Replace Conditional with Polymorphism. When to refactor: before adding features, during code review, when fixing bugs. Red-Green-Refactor cycle. Use IDE refactoring tools. Keep tests green. Small steps. Commit after each refactoring. Based on Martin Fowler's 'Refactoring' book.

Design a C-suite executive dashboard in Tableau. Layout: 1. KPI cards showing YoY growth for Revenue, Profit, Customer Count. 2. Geographic heat map of sales by region. 3. Trend line chart with forecast band for next quarter. 4. Top 10 products bar chart with drill-down capability. 5. Interactive filters for date range and business unit. Use a professional color palette (blues/grays) and ensure mobile responsiveness.

Analyze user retention using cohort analysis. Deliverables: 1. Cohort table showing retention % by signup month. 2. Heatmap visualization with color gradient (green=high, red=low). 3. Retention curves comparing different cohorts. 4. Calculate Day 1, Day 7, Day 30 retention rates. 5. Identify trends and anomalies with statistical annotations. Use Python (pandas, seaborn) or SQL + BI tool. Include actionable insights for product team.

Design a comprehensive event tracking plan. Framework: 1. Define key user actions (signup, feature use, purchase). 2. Create event taxonomy (object-action naming). 3. Specify event properties (user ID, timestamp, context). 4. Map events to product metrics. 5. Document in tracking plan spreadsheet. 6. Implement with analytics SDK (Segment, Mixpanel). 7. QA and validate data accuracy. Include user properties for segmentation. Set up funnels and cohorts. Review and update quarterly as product evolves.

Implement formative assessments to guide instruction. Techniques: 1. Exit tickets (3-2-1: 3 things learned, 2 questions, 1 application). 2. Think-pair-share for peer discussion. 3. Kahoot/Quizizz for real-time feedback. 4. Concept maps to visualize understanding. 5. Self-assessment rubrics. 6. One-on-one check-ins. 7. Error analysis activities. Use data to adjust teaching. Provide immediate feedback. Focus on growth, not grades. Create safe environment for mistakes. Differentiate based on assessment results. Aim for multiple touchpoints per lesson.

Design comprehensive onboarding experience. Program: 1. Pre-boarding checklist (equipment, accounts, paperwork). 2. Day 1 welcome package and orientation schedule. 3. 30-day plan: role training, team introductions, tool setup. 4. 60-day plan: project assignments, skill development, feedback sessions. 5. 90-day plan: performance review, goal setting, culture integration. 6. Buddy system pairing and mentorship. 7. Learning resources and documentation library. 8. Regular check-ins and satisfaction surveys. Include manager guides and success metrics.

Design quarterly OKRs (Objectives and Key Results) for a product team. Structure: 1. Company-level objectives (3-5 ambitious goals). 2. Team-level objectives aligned to company goals. 3. Key Results for each objective (2-4 measurable outcomes). 4. Confidence scores and ownership assignments. 5. Weekly check-in template for progress tracking. Follow best practices: objectives are qualitative and inspiring, key results are quantitative and time-bound. Include grading rubric (0-1.0 scale).

Turn any object into a glass Christmas ornament. The prompt ensures: 1. Highly reflective glass shaders. 2. Internal refraction of lights. 3. Silver cap and thin gold thread attachment. 4. Micro-scratches on the surface for realism. 5. Festive bokeh background (Christmas tree lights). Works best with portraits, pets, or food.

Perform RFM (Recency, Frequency, Monetary) customer segmentation. Process: 1. Calculate RFM scores from transaction data. 2. Normalize features using StandardScaler. 3. Determine optimal K using elbow method and silhouette score. 4. Apply K-means clustering (4-6 segments). 5. Profile each segment with descriptive statistics and business labels (Champions, At-Risk, Lost). Visualize clusters using PCA 2D projection.

A reporting dashboard for Google Ads campaigns. Metrics: 1. CTR and CPC trends. 2. Conversion Rate per Ad Group. 3. ROAS (Return on Ad Spend) calculation. 4. Top Performing Keywords vs Negatives. 5. Search Impression Share chart. Clear, stakeholder-ready visualization using professional corporate color palettes.

Conduct thorough code reviews with this checklist. Areas to review: 1. Functionality (does it work as intended? edge cases handled?). 2. Code quality (readable, maintainable, follows style guide). 3. Tests (adequate coverage, meaningful assertions). 4. Performance (no obvious bottlenecks, efficient algorithms). 5. Security (input validation, no SQL injection, XSS prevention). 6. Documentation (comments for complex logic, README updates). 7. Error handling (graceful failures, logging). 8. Dependencies (necessary, up-to-date, no vulnerabilities). Use constructive feedback. Suggest improvements, don't just criticize. Automate with linters. Aim for 200-400 LOC per review. Balance thoroughness with speed.

Write a research manuscript using IMRaD format. Structure: 1. Introduction (background, gap, research question). 2. Methods (participants, materials, procedures, analysis). 3. Results (findings without interpretation, tables/figures). 4. Discussion (interpretation, implications, limitations, future research). Plus: Abstract (structured, 250 words), Keywords, References. Follow journal guidelines. Use active voice. Be concise and precise. Create effective figures. Cite appropriately. Get co-author feedback. Use tools like Grammarly, Overleaf. Target journal carefully.

Create a professional README.md for an open-source project. Essential sections: 1. Project title with logo and badges (build status, version, license). 2. One-line description and key features. 3. Installation instructions with code blocks. 4. Quick start guide with minimal example. 5. API reference or usage documentation. 6. Contributing guidelines and code of conduct link. 7. License and acknowledgments. Use clear formatting, screenshots, and GIFs for visual appeal.

Draft a winning grant proposal for nonprofit funding. Components: 1. Executive Summary (compelling 1-page overview). 2. Statement of Need (data-driven problem definition). 3. Project Description (goals, methods, timeline). 4. Budget Justification (itemized with rationale). 5. Organizational Capacity (credentials, past success). 6. Evaluation Plan (measurable outcomes). Use persuasive but factual language. Include appendices for supporting documents. Tailor to funder's priorities.

Conduct win-loss analysis to improve sales effectiveness. Process: 1. Interview recent wins and losses (within 30 days). 2. Ask about decision criteria, evaluation process, and competitors. 3. Identify patterns in wins (what we do well). 4. Uncover reasons for losses (product gaps, pricing, sales execution). 5. Quantify impact of each factor. 6. Share insights with product, marketing, and sales teams. 7. Implement improvements and track impact. Use neutral third party for honest feedback. Aim for 20+ interviews per quarter. Create action plan from findings.

Configure BGP for multi-homed enterprise network. Steps: 1. Obtain ASN and IP prefixes. 2. Configure eBGP neighbors with ISPs. 3. Implement route filtering (prefix lists/route maps). 4. Influence inbound traffic (AS path prepending). 5. Influence outbound traffic (Local Preference). 6. Set up BGP authentication (MD5). 7. Monitor adjacency and route propagation. 8. Implement Bogon filtering. Include failure failover testing scenario.

Implement zero-downtime deployments with Kubernetes. Setup: 1. Create blue and green deployment manifests with identical specs. 2. Configure service selector to route traffic between environments. 3. Implement health checks and readiness probes. 4. Set up Helm charts for version management. 5. Create CI/CD pipeline with automated testing gates. 6. Add rollback mechanism with previous version retention. 7. Implement traffic splitting for canary testing. 8. Monitor deployment metrics with Prometheus and Grafana. Include namespace isolation and resource quotas.

Draft comprehensive SaaS legal framework. Documents: 1. Terms of Service with acceptable use policy. 2. Privacy Policy compliant with GDPR and CCPA. 3. Service Level Agreement (SLA) with uptime guarantees. 4. Data Processing Agreement (DPA) for enterprise clients. 5. Cookie Policy and consent management. 6. Refund and cancellation policy. 7. Intellectual property and licensing terms. 8. Dispute resolution and arbitration clauses. Include plain language summaries and version control system.

Declutter your home using the KonMari method. Steps: 1. Commit to tidying up. 2. Imagine your ideal lifestyle. 3. Finish discarding first, then organize. 4. Tidy by category, not location (clothes, books, papers, komono, sentimental). 5. For each item, ask 'Does this spark joy?'. 6. Thank items before discarding. 7. Assign a home for everything kept. Folding technique: vertical storage. Start with clothes (easiest). Save sentimental items for last. One-time intensive process, not daily maintenance. Results in lasting organization and mindful consumption. Created by Marie Kondo.

Professional diagram following Retrieval Augmented Generation architecture. Components: 1. Document Loader -> Splitting -> Embeddings. 2. Vector DB Storage. 3. Query Rewrite -> Retrieval -> Re-ranking. 4. Contextual Prompt -> LLM Generation. Use blue/violet gradients and high-quality technical icons.

Reveal the hidden 'thinking' process of an LLM. UI shows: 1. Original User Query. 2. Internal Thinking steps (hidden from usual output). 3. Final Conclusion. Highlight keywords that triggered transitions between thoughts. Use a clean, educational layout to help debug prompt logic.

An immersive sensory experience of a Korean BBQ grill. Features: 1. High-quality wagyu beef strips sizzling on a round grill. 2. Smoke rising into a copper extraction vent. 3. Side dishes (Banchan) beautifully arranged. 4. The 'first bite' - wrapping meat in lettuce with kimchi. Sharp, vibrant colors, emphasizing the freshness and heat of the grill.

Create a comprehensive lesson plan using backward design. Structure: 1. Learning Objectives (SMART goals, Bloom's taxonomy). 2. Assessment (how you'll measure understanding). 3. Materials and Resources needed. 4. Introduction/Hook (engage students, 5-10 min). 5. Direct Instruction (teach concepts, 15-20 min). 6. Guided Practice (work together, 10-15 min). 7. Independent Practice (students apply, 15-20 min). 8. Closure and Reflection (summarize, preview next lesson). Include differentiation strategies for diverse learners. Align to curriculum standards.

Extreme high-contrast comic book noir style. 1. Deep, solid blacks and blinding whites. 2. A single splash of color (e.g., Red lips or dress). 3. Dramatic rainfall in white streaks. 4. Heavy ink shadows and sharp silhouettes. 5. Gritty, hard-boiled detective aesthetic. Professional graphic novel quality.

A tribute to 'The Persistence of Memory'. The prompt creates: 1. Photorealistic melting pocket watches draped over a desert landscape. 2. Strange, elongated organic shapes in the distance. 3. Clear, blue Catalonian sky and still water. 4. Masterful use of weird perspective and dream-logic. 4K high-art generation.

Facilitate a customer journey mapping workshop. Process: 1. Define persona and scenario. 2. Map stages (Awareness, Consideration, Purchase, Retention, Advocacy). 3. Identify touchpoints at each stage (website, email, support). 4. Document customer actions, thoughts, and emotions. 5. Highlight pain points and opportunities. 6. Assign ownership for improvements. Use collaborative tools (Miro, FigJam). Include pre-work template and post-workshop action plan. Deliver journey map as visual artifact.

Apply Jobs-to-be-Done framework for product strategy. Structure: 1. Identify the 'job' customers are hiring your product for. 2. Map functional, emotional, and social dimensions. 3. Understand the 'struggling moment' that triggers the job. 4. Analyze competing solutions (including non-consumption). 5. Define success criteria from customer perspective. 6. Uncover unmet needs and innovation opportunities. Conduct switch interviews to understand why customers switched to/from your product. Use insights to guide product development.

Create advanced features for a churn prediction model. Techniques: 1. Temporal features (days since last purchase, purchase frequency). 2. Aggregations (total spend, average order value). 3. Categorical encoding (one-hot, target encoding). 4. Interaction features (tenure × monthly charges). 5. Feature selection using mutual information and correlation analysis. Document feature importance and business rationale for each engineered feature.

Design efficient database schemas. Normalization forms: 1. 1NF (atomic values, no repeating groups). 2. 2NF (no partial dependencies). 3. 3NF (no transitive dependencies). Balance normalization with performance (denormalize for read-heavy). Design principles: Use surrogate keys (auto-increment IDs). Foreign keys for relationships. Indexes on frequently queried columns. Avoid NULL when possible. Use appropriate data types. Naming conventions (plural table names, singular columns). Document relationships (ERD diagrams). Consider ACID properties. Use constraints (UNIQUE, NOT NULL, CHECK). Plan for scalability (partitioning, sharding).

Build content-driven sites with Contentful. Setup: 1. Define content models in Contentful. 2. GraphQL or REST API for content. 3. Rich text rendering with @contentful/rich-text-react-renderer. 4. Preview mode for editors. 5. Localization support. 6. Asset optimization and delivery. 7. Webhooks for build triggers. 8. TypeScript types from content models. Use with Next.js ISR for dynamic static sites.

Apply reciprocity to build sales relationships. Principle: people feel obligated to give back when they receive something of value. Sales applications: 1. Give before asking: share valuable insight, industry report, template, introduction before pitching. 2. Free trial or pilot: let them experience product value before buying. 3. Unexpected bonuses: throw in extra training, extended support at no cost during negotiation. 4. Personalized research: 'I analyzed your competitors and created this comparison for you.' Examples: send personalized video audit of their website, create custom ROI analysis, introduce them to potential client, share salary benchmarking data for their role. Important: value must be genuine and unconditional (don't explicitly ask for favor back). Creates goodwill, returned calls, agreement to meetings. Experiment: track response rate when leading with value vs direct pitch. Typically 2-3x higher engagement.

Fine-tune models with Hugging Face. Process: 1. Load pre-trained model and tokenizer. 2. Prepare dataset with train/val split. 3. Define training arguments (epochs, batch size, learning rate). 4. Use Trainer API for training loop. 5. Evaluate with metrics (accuracy, F1). 6. Save model and push to Hub. 7. Inference with pipeline(). 8. PEFT with LoRA for efficiency. Use accelerate for distributed training and implement gradient accumulation.

Deploy and manage API gateways with rate limiting, authentication, and security controls for microservices architecture. API Gateway features: 1. Request routing: path-based routing, host headers, query parameters, weighted routing for A/B testing. 2. Protocol translation: REST to GraphQL, HTTP to gRPC, WebSocket support. 3. Response transformation: data format conversion, header modification, CORS handling. 4. Caching: response caching (5-minute TTL), cache invalidation, edge caching integration. Rate limiting strategies: 1. Throttling levels: per-API key (1000 req/min), per-IP (100 req/min), global limits. 2. Rate limiting algorithms: token bucket, sliding window, fixed window approaches. 3. Burst handling: temporary burst allowance, graceful degradation during spikes. Authentication methods: 1. API key management: key rotation, expiration policies, usage analytics. 2. OAuth 2.0/JWT: token validation, scope-based authorization, refresh token handling. 3. mTLS: certificate-based authentication, client certificate validation. Security controls: 1. Input validation: request size limits (10MB), content type validation, schema enforcement. 2. WAF integration: SQL injection prevention, XSS protection, bot detection. 3. DDoS protection: rate limiting, IP blocking, geographic restrictions. Monitoring and analytics: 1. Request metrics: latency percentiles (P50, P95, P99), error rates, throughput tracking. 2. API usage: top consumers, endpoint popularity, quota utilization. Load balancing: upstream health checks, circuit breaker pattern, retry mechanisms with exponential backoff.

Run LLMs locally with Ollama. Usage: 1. Install Ollama CLI. 2. Pull models (Llama 2, Mistral, CodeLlama). 3. Run with ollama run command. 4. API server for integrations. 5. Model customization with Modelfile. 6. Memory and GPU management. 7. Multi-model switching. 8. No internet required after download. Use for privacy, development, or air-gapped environments.

Breathtaking Northern Lights photography. Visuals: 1. Vibrant green, violet, and pink curtains of light. 2. Reflection of the aurora on a frozen Arctic lake. 3. High-dynamic range showing billions of stars and the Milky Way. 4. Silhouetted pine trees in the foreground. 5. Long exposure look with soft ethereal movement. Perfect for travel and nature niche.

Navigate pricing discussions strategically. Anchor high: present highest tier first, then lower options seem reasonable. Discount guidelines: never discount on first ask ('Let me see what I can do'). Offer discounts for: 1. Annual prepayment (10-15%). 2. Case study participation (5%). 3. Larger commitment (more users/features, 10-20%). 4. End of quarter urgency (5-10%). Trade value for value: if discount, ask for faster close, reference, larger commitment. Avoid: one-time discounts (creates bad precedent), discounts without reason. Alternative to discount: add services (implementation, training), extend payment terms, include add-ons free for 6 months. Document approvals in CRM. Protect margins: calculate breakeven point before negotiating.

Build repeatable referral system. Best timing: 1. After successful implementation. 2. After positive review/NPS score. 3. During quarterly business review. The ask: 'I'm glad you're seeing results. Who else in your network faces similar challenges?' Be specific: 'Do you know any [job title] at [company size] in [industry]?' Offer value exchange: refer them clients too, provide introduction template, offer referee incentive (Amazon gift card, discount). Process: 1. Identify top 20 happy customers. 2. Reach out personally (not bulk email). 3. Make ask easy ('Just reply with 2-3 names and I'll handle outreach'). 4. Send update when contact is made. 5. Report results back to referrer. Track referral source in CRM. Calculate referral conversion rate (typically 30-50% higher than cold). Incentivize reps: SPIF for most referrals monthly.

Measure and achieve product-market fit using multiple signals. PMF indicators: 1. Sean Ellis test: >40% of users would be 'very disappointed' if they couldn't use product anymore. 2. Retention curves: cohorts flatten to horizontal line (not declining). 3. Organic growth: word-of-mouth driving 30%+ of new signups. 4. Usage intensity: users engaging multiple times per week. 5. Net Promoter Score >50 and growing. Measurement cadence: survey users quarterly, analyze retention monthly, track referrals weekly. Early PMF signs: customers pulling product from you, usage growing organically, positive unit economics emerging. Pre-PMF: focus on retention over growth. Post-PMF: optimize growth engines. Tools: Amplitude for retention, Delighted for NPS, internal surveys for disappointment test. Document learnings about ICP (ideal customer profile) refinement.

Master Docker containerization for microservices with optimization and security best practices. Dockerfile optimization: 1. Multi-stage builds: separate build and runtime environments, reduce image size by 70-80%. 2. Base image selection: Alpine Linux for minimal footprint, distroless for security. 3. Layer caching: order instructions from least to most frequently changing. 4. Security practices: non-root user, minimal packages, vulnerability scanning. Container orchestration: 1. Docker Compose: local development, service dependencies, network configuration. 2. Production considerations: resource limits (CPU: 1 core, Memory: 512MB typical), health checks every 30 seconds. Image management: 1. Registry strategy: private registries for proprietary code, image tagging conventions (semantic versioning). 2. Security scanning: Trivy, Clair for vulnerability detection, policy enforcement. 3. Image optimization: .dockerignore files, multi-arch builds (AMD64, ARM64). Microservices patterns: 1. Service mesh: Istio/Linkerd for inter-service communication, observability. 2. API gateway: rate limiting, authentication, request routing. Monitoring: container metrics (CPU, memory, disk I/O), log aggregation, distributed tracing with Jaeger/Zipkin.

Use personalized video to stand out. When to use video: 1. High-value accounts (worth the time). 2. Multiple failed touch attempts. 3. Complex value prop (better shown than written). 4. Re-engagement of cold leads. Video structure (60-90 seconds): 1. Personalized intro (10s): 'Hi [Name], I'm [You]. I was looking at [Company]...' 2. Relevant observation (20s): '...and noticed you recently [trigger event]. Congrats!' 3. Value prop (20s): 'We help companies like yours [achieve outcome].' 4. Specific example (15s): 'For example, [Customer] saw [specific result].' 5. Call to action (5s): 'Would 15 minutes next week work to explore if this fits?' Production: use Loom or Vidyard, share screen showing their website/LinkedIn, show your face (builds trust), smile and be enthusiastic. Send via: email (embed thumbnail), LinkedIn message. Track: video view rate (60%+), watch time (>75%). Reply rate: typically 3-5x higher than text email.

Design strong quasi-experiments when randomization impossible. Design types: 1. Non-equivalent groups: compare treatment and comparison groups without random assignment. 2. Interrupted time series: multiple observations before and after intervention. 3. Regression discontinuity: treatment assigned based on cutoff score. 4. Instrumental variables: use natural randomization to estimate causal effects. Strengthening designs: 1. Propensity score matching: match treatment and control on likelihood of receiving treatment. 2. Difference-in-differences: compare changes over time between treatment and control areas. 3. Multiple baselines: stagger intervention across participants or sites. Threats to validity: 1. Selection bias: groups differ systematically. 2. History: events coinciding with intervention. 3. Maturation: natural change over time. Analysis considerations: intention-to-treat vs. per-protocol analysis, sensitivity analysis for unobserved confounders, report effect sizes and confidence intervals.

Systematically improve product performance and user experience. Performance metrics: 1. Core Web Vitals: Largest Contentful Paint (LCP <2.5s), First Input Delay (FID <100ms), Cumulative Layout Shift (CLS <0.1). 2. Time to First Byte (TTFB <600ms). 3. Time to Interactive (TTI <5s). 4. Application response times: API calls, database queries. Performance monitoring: 1. Real User Monitoring (RUM): actual user experience data. 2. Synthetic monitoring: automated performance tests. 3. Server monitoring: CPU, memory, disk usage. 4. CDN analytics: cache hit rates, edge performance. Optimization strategies: 1. Frontend: code splitting, lazy loading, image optimization, caching. 2. Backend: database query optimization, caching layers, microservices. 3. Infrastructure: CDN, load balancing, auto-scaling. Tools: Google PageSpeed Insights, New Relic, DataDog for monitoring. Performance budget: set thresholds, alert when exceeded, gate deployments on performance regression.

Scale through process documentation. Approach: 1. Document recurring processes. 2. Standard Operating Procedures (SOPs). 3. Decision-making frameworks. 4. Tools and system guides. 5. Video walkthroughs. 6. Knowledge base. 7. Version control for updates. 8. Ownership assignment. Use Notion or Confluence. Document as you go. Enables delegation and consistency. Critical for growth.

Provide constructive feedback to a peer or student teacher using the Praise-Question-Polish model. Structure: 1. Praise (Start with specifics): 'I was really impressed with how you used wait time after your questions. I saw several students who don't normally participate raise their hands.' 2. Question (Promote reflection): 'I'm curious about the group work activity. What were your goals for that part of the lesson? How did it go compared to your expectations?' 3. Polish (Offer a concrete suggestion): 'To increase accountability during group work, you might consider assigning roles like facilitator or reporter. That could help keep everyone on task.' This model is less threatening than direct criticism and encourages a reflective conversation.

Optimize e-commerce fulfillment. Strategy: 1. Fulfillment model (in-house, 3PL, dropship). 2. Warehouse location optimization. 3. Order management system. 4. Picking and packing efficiency. 5. Shipping carrier negotiation. 6. Returns process streamlining. 7. International expansion (duties, compliance). 8. Peak season scaling. Use automation where possible. Focus on speed and accuracy. Customer experience crucial. Monitor fulfillment KPIs.

Craft compelling memoir that transforms personal experience into universal story. Memoir vs. autobiography: 1. Memoir: focused theme or period, emotional truth over chronology. 2. Autobiography: comprehensive life story, factual emphasis. Theme identification: 1. Central question: what life lesson or insight drives the story? 2. Transformation: how did experiences change your perspective? 3. Universal connection: what will readers relate to in your journey? Narrative structure: 1. Inciting incident: event that starts the story in motion. 2. Rising action: challenges, obstacles, internal conflicts. 3. Climax: moment of greatest crisis or realization. 4. Resolution: how protagonist (you) changed or grew. Scene construction: 1. Dialogue: recreated conversations that feel authentic. 2. Setting details: time and place that immerse readers. 3. Internal monologue: thoughts and feelings at the time. 4. Reflection: current perspective on past events. Truth and ethics: 1. Emotional accuracy: feelings and impact matter more than exact details. 2. Privacy respect: consider impact on family, friends mentioned. 3. Composite characters: combine people when necessary for privacy. Writing techniques: show don't tell, specific details over generalizations, vulnerability balanced with dignity.

Ensure product accessibility compliance following WCAG 2.1 standards. WCAG principles (POUR): 1. Perceivable: information must be presentable in ways users can perceive. 2. Operable: interface components must be operable by all users. 3. Understandable: information and UI operation must be understandable. 4. Robust: content must be robust enough for various assistive technologies. Key requirements: 1. Color contrast: 4.5:1 ratio for normal text, 3:1 for large text. 2. Keyboard navigation: all functionality accessible via keyboard. 3. Alt text: meaningful descriptions for images. 4. Focus indicators: visible outline when tabbing through elements. 5. Semantic HTML: proper heading hierarchy, form labels. Testing approach: 1. Automated scanning: axe-core, WAVE for initial detection. 2. Manual testing: keyboard-only navigation, screen reader testing. 3. User testing: recruit users with disabilities. Implementation: integrate accessibility into design system, developer training, legal compliance for ADA/Section 508.