The World's Best AI Prompts Library

Analyze Asimov's Three Laws of Robotics in the context of modern AI. Law 1: Do no harm. Law 2: Obey orders. Law 3: Protect existence. Paradoxes and loopholes (e.g., The Zeroth Law). Relevance to autonomous vehicles.

Explain the concept of Quantum Entanglement using simple analogies. Analogy: Magic dice that always show the same number when rolled, no matter how far apart they are. Key concepts: Spooky action at a distance, connection, information state. Avoid jargon. Use 'alice' and 'bob' characters.

Fine-tune BERT model for custom sentiment analysis. Steps: 1. Data preprocessing (tokenize, pad, mask). 2. Load pre-trained BERT model (Hugging Face Transformers). 3. Define custom classification head. 4. Configure optimizer (AdamW) and scheduler. 5. Implement training loop with validation. 6. Handle class imbalance (weighted loss). 7. Evaluate metrics (F1-score, accuracy). 8. Quantize model for inference efficiency. Include usage example.

Secure your applications against common vulnerabilities. OWASP Top 10: 1. Injection (SQL, NoSQL, OS commands - use parameterized queries). 2. Broken Authentication (implement MFA, secure password storage with bcrypt). 3. Sensitive Data Exposure (encrypt data at rest and in transit, HTTPS). 4. XML External Entities (disable XXE in parsers). 5. Broken Access Control (enforce authorization checks). 6. Security Misconfiguration (disable debug mode, update dependencies). 7. XSS (sanitize user input, use CSP headers). 8. Insecure Deserialization (validate serialized data). 9. Using Components with Known Vulnerabilities (dependency scanning). 10. Insufficient Logging (log security events). Use security headers, rate limiting.

Generate a week of Stoic journaling prompts. Themes: 1. Memento Mori (Remembering death). 2. Dichotomy of Control (What is up to us). 3. Amor Fati (Loving one's fate). 4. Negative Visualization (Preparing for adversity). 5. The View from Above (Perspective). 6. Sympatheia (Interconnectedness). 7. Review of the Day. Include quote interpretation for each.

Develop comprehensive penetration testing plan. Stages: 1. Scope definition and rules of engagement. 2. Reconnaissance and information gathering (OSINT). 3. Vulnerability scanning (automated tools). 4. Exploitation phase (SQLi, XSS, privilege escalation). 5. Post-exploitation and lateral movement. 6. Data exfiltration simulation. 7. Reporting with risk severity (CVSS) and remediation steps. 8. Debriefing and re-testing. Include social engineering scenarios and physical security assessment.

Conduct Solidity smart contract security audit. Checklist: 1. Reentrancy vulnerability check. 2. Integer overflow/underflow analysis. 3. Access control verification (modifiers). 4. Gas optimization review. 5. External call safety. 6. Front-running mitigation. 7. Logic error detection. 8. Test coverage analysis (Hardhat/Foundry). Include formal verification results.

Build production churn prediction system. Pipeline: 1. Perform exploratory data analysis and visualization. 2. Engineer features (RFM, engagement scores, usage patterns). 3. Handle class imbalance with SMOTE or class weights. 4. Train multiple models (XGBoost, Random Forest, Neural Network). 5. Implement cross-validation and hyperparameter tuning. 6. Create SHAP values for model interpretability. 7. Build prediction API with FastAPI. 8. Set up monitoring for model drift. Include feature importance analysis and business impact metrics.

Reduce BigQuery costs for a high-volume analytics workload. Strategies: 1. Partition tables by date and cluster by high-cardinality columns. 2. Use materialized views for frequently-run aggregations. 3. Implement query result caching and avoid SELECT *. 4. Set up cost controls with custom quotas per project. 5. Analyze query execution plans to identify expensive operations. Provide before/after cost comparison and ROI calculation. Include monitoring dashboard for ongoing cost tracking.

Architect HIPAA-compliant patient data storage system. Requirements: 1. Data encryption at rest (AES-256). 2. Data encryption in transit (TLS 1.3). 3. Role-Based Access Control (RBAC). 4. Audit logging of all access events. 5. Business Associate Agreement (BAA) with could provider. 6. Automated backup and disaster recovery. 7. De-identification mechanisms for research. 8. Intrusion Detection System (IDS). Include breach notification protocol.

Build enterprise-grade LLM fine-tuning system. Pipeline: 1. Implement data preprocessing and quality validation. 2. Set up LoRA (Low-Rank Adaptation) for efficient training. 3. Configure distributed training across multiple GPUs. 4. Implement gradient checkpointing for memory optimization. 5. Add automated evaluation with ROUGE, BLEU, and custom metrics. 6. Create A/B testing framework for model comparison. 7. Set up MLflow for experiment tracking. 8. Implement model versioning and deployment pipeline. Include cost monitoring and training time optimization.

High-end product packaging for Matcha tea. Design: 1. Washi paper texture. 2. Single vertical line of Japanese kanji. 3. Geometric green shapes (minimalism). 4. A small, elegant gold-leaf seal. 5. Macro photography on a grey stone surface. Peaceful, premium, and sophisticated. Designed for luxury retail niche.

Professional lighting setup for Apple-style product photography. Focus points: 1. Soft top-down key light for overall brightness. 2. High-intensity rim light to define the white plastic edges. 3. Subsurface scattering for realistic translucence on the silicone tips. 4. Ultra-clean reflection of a softbox on the charging case. Zero noise, 100% polish.

Implement GitOps workflow using ArgoCD. Setup: 1. Install ArgoCD on Kubernetes cluster. 2. Connect Git repository as source of truth. 3. Create Application manifests for each microservice. 4. Configure automated sync policies. 5. Set up health checks and sync waves. 6. Implement progressive delivery with Argo Rollouts (canary, blue-green). 7. RBAC for team access control. Use separate repos for app code and manifests. Include rollback procedures and disaster recovery plan.

Write a detailed PRD for a new feature. Sections: 1. Overview (problem statement, goals, success metrics). 2. User personas and use cases. 3. User stories with acceptance criteria. 4. Functional requirements (detailed specifications). 5. Non-functional requirements (performance, security, scalability). 6. Design mocks and user flows. 7. Technical considerations and dependencies. 8. Launch plan and rollout strategy. 9. Open questions and risks. Use clear, unambiguous language. Collaborate with engineering and design. Keep as living document.

Write helpful, human UX microcopy for common scenarios. Examples: 1. Form validation errors (specific, actionable). 2. Empty states (encouraging, with clear next steps). 3. Loading messages (reassuring, branded). 4. Success confirmations (celebratory but brief). 5. 404 pages (helpful navigation options). Follow principles: be clear, be concise, be human. Avoid technical jargon and blame. Provide solutions, not just problems. Include tone of voice guidelines for consistency.