AI Prompts Library

You are an API design expert. Generate a complete OpenAPI 3.1 specification for the described API.

**API Details:**
- API Name: [API_NAME]
- Base URL: [BASE_URL]
- Version: [VERSION]
- Description: [WHAT_THE_API_DOES]
- Authentication: [Bearer JWT / API Key / OAuth2 / None]
- Resources: [LIST_YOUR_RESOURCES, e.g., users, products, orders]

**For each resource, generate:**

1. **Paths**: All CRUD endpoints plus any custom actions
   - Proper HTTP methods (GET, POST, PUT, PATCH, DELETE)
   - Path parameters with descriptions
   - Query parameters for filtering, pagination, sorting
   - Request bodies with required/optional fields
   - All possible response codes (200, 201, 204, 400, 401, 403, 404, 409, 422, 500)

2. **Schemas** (components/schemas):
   - Request schemas (Create, Update with partial fields)
   - Response schemas (single item, paginated list)
   - Error schema with code, message, details array
   - Enum types for status fields
   - Proper use of allOf, oneOf, anyOf for schema composition

3. **Security Schemes**: Define authentication with examples

4. **Tags**: Group endpoints logically with descriptions

5. **Examples**: Provide realistic request/response examples for every endpoint

6. **Pagination**: Use cursor-based or offset pagination with Link headers

7. **Rate Limiting**: Document rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining)

**Output Format:** Valid YAML OpenAPI 3.1 specification that can be imported directly into Swagger UI, Postman, or any OpenAPI-compatible tool. Include inline comments explaining design decisions.

You are a documentation standards expert. Create a comprehensive documentation style guide for the described organization or project.

**Organization/Project:** [NAME]
**Documentation Type:** [API docs / User guides / Internal wikis / Developer docs / All]
**Audience:** [Developers / End users / Mixed]
**Existing Style Preferences:** [Any specific preferences, or 'none']

**Generate a style guide covering:**

1. **Voice and Tone:**
   - Active vs. passive voice rules (with examples)
   - Second person ("you") vs. third person usage
   - Level of formality
   - When to use humor (if ever)
   - Handling of uncertainty ("might" vs. "will")

2. **Structure and Formatting:**
   - Document template (standard sections every doc should have)
   - Heading hierarchy rules (capitalization, depth limits)
   - Paragraph length guidelines
   - List formatting (bullet vs. numbered, when to use each)
   - Table usage guidelines
   - Code block formatting (language tags, line limits, highlighting)

3. **Language Rules:**
   - Preferred terminology (glossary of approved terms)
   - Words to avoid ("simply", "just", "easy", "obviously")
   - Abbreviation and acronym policy (define on first use)
   - Capitalization rules for product names, features, UI elements
   - Date, time, and number formatting
   - Inclusive language guidelines

4. **Code Documentation:**
   - Inline comment standards
   - Function/method documentation format (JSDoc, docstring, etc.)
   - README template
   - API reference format
   - Code example requirements (complete, runnable, with output)

5. **Visual Elements:**
   - Screenshot guidelines (when to include, annotation style)
   - Diagram standards (tools, colors, style)
   - Callout/admonition types (Note, Warning, Tip, Caution)

6. **Review Process:**
   - Documentation review checklist
   - Peer review requirements
   - Freshness/update schedule

**Output**: A complete style guide document that can be shared with all contributors.

Transform the following meeting notes into structured minutes with clear action items.

**Meeting Info:**
- Date: [DATE]
- Attendees: [NAMES]
- Duration: [TIME]
- Topic: [MEETING PURPOSE]

**Raw Notes:**
[PASTE MEETING NOTES HERE]

**Generate:**

1. **Meeting Summary** (2-3 sentences)
2. **Key Decisions Made**
   - Decision 1
   - Decision 2
3. **Action Items**
   - [ ] Task description | Owner | Deadline | Priority
4. **Open Questions**
   - Question | Who needs to answer
5. **Next Meeting**
   - Date, time, agenda items

**Format Requirements:**
- Chronological order
- Clear, concise language
- Actionable task descriptions
- Specific deadlines
- Identified owners
- Follow-up items highlighted

Generate comprehensive API documentation for [API NAME].

**API Details:**
- Base URL: [URL]
- Authentication: [TYPE]
- Version: [VERSION]

**For Each Endpoint:**

```yaml
/api/endpoint:
  method:
    summary: Brief description
    description: Detailed explanation
    parameters:
      - name: param
        in: query/path/header
        required: true/false
        schema:
          type: string/number/etc
        description: Parameter purpose
    requestBody:
      content:
        application/json:
          schema:
            type: object
            properties:
              field: type
    responses:
      '200':
        description: Success response
        content:
          application/json:
            example:
              {data}
      '400':
        description: Error response
```

**Include:**
- Authentication guide
- Rate limiting info
- Error codes
- Code examples (cURL, JavaScript, Python)
- Changelog
- Postman collection

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

You are a technical documentation specialist creating comprehensive, user-friendly documentation.

Project: [PROJECT NAME]
Audience: [TARGET USER LEVEL: Beginner/Intermediate/Advanced]
Technology Stack: [TECHNOLOGIES]

Create documentation that includes:

**1. Overview Section**
- Purpose and goals
- Key features
- Prerequisites
- Architecture diagram (describe in detail)

**2. Getting Started**
- Installation steps (OS-specific if needed)
- Initial configuration
- First-time setup
- Quick start example

**3. Core Concepts**
- Fundamental principles
- Terminology glossary
- Common patterns
- Best practices

**4. API Reference** (if applicable)
- Endpoint descriptions
- Parameters and types
- Request/response examples
- Error codes

**5. Advanced Topics**
- Performance optimization
- Troubleshooting guide
- FAQ section
- Migration guides

**6. Code Examples**
- Common use cases (with code)
- Integration examples
- Testing examples

Format: Use clear headings, code blocks, callouts for warnings/tips, and maintain consistent terminology.