AI Prompts Library

Chatbot flow for [USE CASE]:

**Greeting** → Options
**Intent Detection** → Branch
**Info Gathering** → Validate input
**Resolution** → Provide solution
**Escalation** → Seamless handoff to human

**NLP**: Variations, typos, synonyms, context
**Personality**: Consistent tone, emojis (if appropriate)
**Fallbacks**: "I'm not sure" → human handoff
**Analytics**: Track paths, drop-offs, resolution rate

Friendly, efficient, helpful.

Create structured A/B test hypothesis:

**Test Subject**: [PAGE/FEATURE]
**Current Metric**: [VALUE]

**Hypothesis**: If [CHANGE] then [EXPECTED OUTCOME] because [REASONING]

**Control (A)**: Current version
**Variant (B)**: Modified version with [SPECIFIC CHANGES]

**Success Metrics**:
- Primary: [METRIC]
- Secondary: [METRICS]

**Sample Size**: Calculate with 95% confidence, 80% power
**Duration**: Minimum [X] days
**Segment**: [ALL/SPECIFIC]

**Risks**: [POTENTIAL ISSUES]
**Rollback Plan**: [IF NEGATIVE IMPACT]

Write user story following Agile best practices:

**Epic**: [EPIC NAME]

**User Story**:
As a [USER ROLE]
I want to [ACTION/FEATURE]
So that [BENEFIT/VALUE]

**Acceptance Criteria** (Given-When-Then):
1. Given [CONTEXT], When [ACTION], Then [EXPECTED RESULT]
2. Given [CONTEXT], When [ACTION], Then [EXPECTED RESULT]
3. [ADD MORE AS NEEDED]

**Technical Notes**:
- Dependencies: [SYSTEMS/APIS]
- Edge Cases: [SCENARIOS]
- Performance: [REQUIREMENTS]

**Definition of Done**:
- [ ] Code complete & reviewed
- [ ] Unit tests (>80% coverage)
- [ ] Integration tests pass
- [ ] Documentation updated
- [ ] Acceptance criteria validated

**Story Points**: [ESTIMATE]
**Priority**: [HIGH/MEDIUM/LOW]

Design comprehensive API error response:

```json
{
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable error message",
    "details": "Detailed explanation",
    "timestamp": "2025-10-02T02:00:00Z",
    "request_id": "uuid",
    "documentation_url": "https://docs.example.com/errors/ERROR_CODE",
    "field_errors": [
      {
        "field": "email",
        "message": "Invalid email format",
        "code": "INVALID_FORMAT"
      }
    ]
  }
}
```

**Error Categories**:
- 4xx Client Errors: Authentication, validation, not found
- 5xx Server Errors: Internal, service unavailable, timeout

**Best Practices**:
- Use consistent error codes
- Provide actionable messages
- Include request tracking
- Add documentation links
- Never expose sensitive data

Optimize [WEB APP/API/DATABASE] performance:

**Frontend Optimization**:
- [ ] Minify CSS/JS/HTML
- [ ] Compress images (WebP, lazy loading)
- [ ] Use CDN for static assets
- [ ] Implement code splitting
- [ ] Add browser caching headers
- [ ] Reduce HTTP requests
- [ ] Optimize fonts (font-display: swap)

**Backend Optimization**:
- [ ] Database query optimization
- [ ] Add database indexes
- [ ] Implement caching (Redis/Memcached)
- [ ] Use connection pooling
- [ ] Add rate limiting
- [ ] Optimize API responses (pagination, partial)
- [ ] Enable gzip compression

**Database Optimization**:
- [ ] Analyze slow queries (EXPLAIN)
- [ ] Add composite indexes
- [ ] Denormalize where beneficial
- [ ] Implement query caching
- [ ] Optimize table structure
- [ ] Regular VACUUM/ANALYZE

**Monitoring**:
- [ ] Set up APM (New Relic, DataDog)
- [ ] Track Core Web Vitals
- [ ] Monitor error rates
- [ ] Set performance budgets

Security audit following OWASP Top 10:

**1. Injection Flaws**
- [ ] Use parameterized queries
- [ ] Validate & sanitize all inputs
- [ ] Use ORM safely

**2. Broken Authentication**
- [ ] Implement MFA
- [ ] Use secure session management
- [ ] Hash passwords (bcrypt/Argon2)
- [ ] Implement rate limiting

**3. Sensitive Data Exposure**
- [ ] Encrypt data at rest & in transit (TLS 1.3)
- [ ] Don't log sensitive data
- [ ] Use secure key management

**4. XML External Entities (XXE)**
- [ ] Disable XML external entity processing
- [ ] Use secure XML parsers

**5. Broken Access Control**
- [ ] Verify permissions server-side
- [ ] Implement RBAC/ABAC
- [ ] Test authorization logic

**6. Security Misconfiguration**
- [ ] Remove default credentials
- [ ] Disable directory listing
- [ ] Keep dependencies updated
- [ ] Use security headers (CSP, HSTS)

**7. XSS (Cross-Site Scripting)**
- [ ] Escape output
- [ ] Use Content Security Policy
- [ ] Sanitize HTML inputs

**8. Insecure Deserialization**
- [ ] Validate serialized data
- [ ] Use signing/encryption

**9. Using Components with Known Vulnerabilities**
- [ ] Regular dependency audits
- [ ] Automated security scanning
- [ ] Subscribe to security advisories

**10. Insufficient Logging & Monitoring**
- [ ] Log security events
- [ ] Monitor for anomalies
- [ ] Set up alerting

[modern/classical/futuristic] [residential/commercial/public] interior design, [specific room], [design style: minimalist/bohemian/industrial/scandinavian], natural lighting through [windows/skylights], [materials: wood/concrete/glass], [color palette], photorealistic architectural visualization, magazine quality, professional rendering, --ar 16:9 --v 6 --q 2

Technical diagram showing [system/process], clean infographic style, [flowchart/architecture/network] diagram, labeled components, [color-coded: blue for input, green for process, red for output], arrows showing data flow, professional, suitable for [documentation/presentation], white background, high contrast

45s animated explainer for [PRODUCT/CONCEPT]. Scenes: 1) Problem (0-10s: show pain point with icons), 2) Solution Intro (10-20s: product reveal), 3) How It Works (20-35s: 3-step process animation), 4) Benefits (35-40s: key advantages), 5) CTA (40-45s). Style: Modern flat design, smooth transitions, [brand colors], kinetic typography, professional voiceover timing. 16:9, 30fps.

Design email newsletter for [AUDIENCE]:

**Subject Line** (40-50 chars):
- Main: [BENEFIT-FOCUSED]
- A/B: [CURIOSITY-BASED]

**Preview Text**: [EXPAND ON SUBJECT]

**Header**:
- Logo + brand colors
- Navigation links (optional)

**Hero Section**:
- Headline: [MAIN MESSAGE]
- Hero image/GIF
- Primary CTA button

**Content Blocks** (2-4):
1. **[SECTION 1]**
   - Image (left/right)
   - Headline + 2-3 sentences
   - CTA link

2. **[SECTION 2]**
   - Content
   - CTA

**Footer**:
- Social media icons
- Unsubscribe link (required)
- Physical address (CAN-SPAM)
- Preferences center

**Technical**:
- Mobile-responsive
- 600px max width
- Web-safe fonts
- Alt text for images
- Plain-text version

Build content marketing strategy for [BUSINESS]:

**1. Audience Research**
- Primary persona: [DEMOGRAPHICS + PSYCHOGRAPHICS]
- Pain points: [LIST]
- Content consumption habits: [PLATFORMS + FORMATS]

**2. Content Pillars** (3-5 themes)
1. [PILLAR 1] - Addresses [PAIN POINT]
2. [PILLAR 2] - Showcases [EXPERTISE]
3. [PILLAR 3] - Provides [VALUE]

**3. Content Types & Distribution**
- Blog posts (2x/week): SEO-focused, evergreen
- Social media (daily): Engagement, community
- Email (weekly): Nurture, retention
- Video (2x/month): Education, demos
- Podcast (optional): Thought leadership

**4. Editorial Calendar**
- Q1: [THEMES]
- Q2: [THEMES]
- Q3: [THEMES]
- Q4: [THEMES]

**5. SEO Strategy**
- Target keywords (head, long-tail)
- Content clusters
- Internal linking

**6. Promotion Plan**
- Organic: SEO, social, email
- Paid: Ads, sponsored posts
- Partnerships: Guest posts, collabs

**7. Metrics**
- Traffic, engagement, conversions
- Content ROI
- Top performers

**8. Repurposing Strategy**
- Blog → Social posts + email + video
- Webinar → Blog series + clips
- Research → Infographic + ebook

Design database schema for [APPLICATION]:

**Naming Conventions**:
- Tables: plural, snake_case (users, order_items)
- Columns: singular, snake_case (user_id, created_at)
- Primary keys: id (integer, auto-increment)
- Foreign keys: [table_singular]_id

**Standard Columns** (all tables):
- id: Primary key
- created_at: Timestamp
- updated_at: Timestamp
- deleted_at: Soft deletes (optional)

**Relationships**:
- One-to-Many: Foreign key in child table
- Many-to-Many: Junction table
- One-to-One: Foreign key with UNIQUE constraint

**Indexes**:
- Primary key (automatic)
- Foreign keys
- Frequently queried columns
- Composite indexes for multi-column queries

**Data Types**:
- Use appropriate sizes (VARCHAR vs TEXT)
- ENUM for fixed options
- JSON for flexible data (use sparingly)
- UUID for distributed systems

**Constraints**:
- NOT NULL where appropriate
- UNIQUE for natural keys
- CHECK for validation
- DEFAULT values

**Normalization**:
- 3NF for OLTP
- Denormalize for read-heavy (with care)
- Avoid EAV anti-pattern

**Example Schema**:
```sql
CREATE TABLE users (
  id SERIAL PRIMARY KEY,
  email VARCHAR(255) UNIQUE NOT NULL,
  password_hash VARCHAR(255) NOT NULL,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_users_email ON users(email);
```