### Disambiguation Example for Performers

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Illustrates how to use disambiguation for performer names when conflicts exist, providing examples of qualifiers.

```yaml
# Disambiguation (for name conflicts):
# - Use when multiple performers share a name
# - Format: "Name (Qualifier)"
# - Qualifier examples: (I), (II), (Studio Name), (Decade)
# Example: "Alex Grey (Blacked)" vs "Alex Grey (I)"
```

--------------------------------

### Studio Structure Example

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Provides an example of how to structure studio information, including name, optional parent/network, and official URLs.

```yaml
# Studio Structure Example:
studio:
  name: "Studio Name"
  parent: "Network Name"          # Optional parent/network
  urls:
    - "https://official-site.com"
```

--------------------------------

### Performer Fields Example

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Defines required and optional fields for creating a performer, including name, aliases, gender, and disambiguation.

```yaml
performer:
  name: "Stage Name"           # Required - primary professional name
  aliases: ["Alt Name 1"]      # Optional - other professional credits
  gender: "Female"             # Recommended
  disambiguation: "(Studio)"   # Only if name conflicts exist
```

--------------------------------

### Scene Performers Example

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Shows how to list performers in a scene, including the requirement to list all credited performers and optional character names.

```yaml
# Scene Performers:
# - Must include ALL studio-credited performers
# - Male performers required in straight scenes
# - Uncredited performers: Not required but recommended
# - Use disambiguated entries to avoid ambiguous performers

performers:
  - name: "Performer Name"
    appearance_as: "Character Name"  # Only if credited differently
```

--------------------------------

### Scene Fields Example

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Demonstrates the structure for scene fields, including title, date, and duration. Emphasizes using the original studio title.

```yaml
# Scene Title:
# - Use original official studio title
# - Preserve original spelling, capitalization, punctuation
# - English titles preferred when studio provides both languages

scene:
  title: "Original Scene Title"   # Exactly as studio lists it
  date: "2023-05-15"              # YYYY-MM-DD, earliest known release
  duration: 2400                  # In seconds
```

--------------------------------

### Career Information for Performers

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Defines career start and end years for performers. Leave career_end empty if the performer is still active.

```yaml
# Career Information:
career_start: 2015              # Year only
career_end: null                # Leave empty if still active
```

--------------------------------

### Professional Studio Requirements

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Outlines requirements for professional studios, emphasizing official 1st party websites and digital availability of classic content.

```yaml
# Professional Studios:
# - Major digital networks allowed
# - Must have official 1st party website
# - Classic content only if digitally available from official source
```

--------------------------------

### StashDB Connection Details

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Configuration details for connecting to StashDB and other compatible Stash-Boxes. Includes homepage, GraphQL endpoints, and steps for setting up API keys in Stash.

```yaml
# StashDB Connection Details
Homepage: https://stashdb.org/
Endpoint: https://stashdb.org/graphql
Guidelines: https://guidelines.stashdb.org/

# Steps to connect StashDB to Stash:
# 1. Get invite code from Discord #stashdb-invites or Discourse
# 2. Register account at https://stashdb.org/register
# 3. Find your API key: Click username -> API key
# 4. In Stash: Settings -> Metadata Providers -> Stash-Box Endpoints
#    Enter API token and GraphQL endpoint

# Other compatible Stash-Boxes:
ThePornDB:
  Homepage: https://theporndb.net/
  Endpoint: https://theporndb.net/graphql

FansDB:
  Homepage: https://fansdb.cc/
  Endpoint: https://fansdb.cc/graphql

PMV Stash:
  Homepage: https://pmvstash.org/
  Endpoint: https://pmvstash.org/graphql
```

--------------------------------

### Scene Creation Requirements

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Outlines essential requirements for creating scenes, including pHash generation, duplicate checks, and performer inclusion.

```yaml
# Scene Creation Requirements:
# 1. Must have pHash generated before submitting
# 2. Check for duplicates first (search by title/fingerprints)
# 3. Must include ALL performers listed by studio (including male performers)
# 4. Create missing performers BEFORE submitting scene
```

--------------------------------

### Creating a Scene Draft in Stash

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Steps for creating a new scene draft to submit to StashDB. Requires generating pHashes first and reviewing the draft before submission.

```yaml
# Creating a Scene Draft:
# 1. Generate pHashes first (required for new scenes)
# 2. Use Scene Tagger to check for existing matches
# 3. Scene details page -> Three dots menu -> "Submit to Stash-Box"
# 4. Review draft at https://stashdb.org/drafts
# 5. Add edit comment explaining your source
# 6. Click Submit to enter the approval queue

# Creating a Performer Draft:
# 1. Performer details page -> "Submit to Stash-Box" button
# 2. Review draft on StashDB
# 3. Add edit comment
# 4. Submit for approval

# Updating Existing Entries:
# - Must have StashID saved locally (from previous match)
# - Same process but updates existing entry instead of creating new
# - Use "Reset Images" button if you don't want to replace thumbnail
# - Draft updates do NOT add fingerprints (use Scene Tagger instead)

# Important Notes:
# - Drafts expire after 24 hours
# - Drafts are only visible to you until submitted
# - Always include helpful edit comments
```

--------------------------------

### Amateur Scene Rules

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Specifies rules for amateur scenes, including approved platforms, creator usage as studio, and verification requirements.

```yaml
# Amateur Scene Rules:
# - Only from approved platforms: ManyVids, Clips4Sale, PornHub, MFC Share
# - No OnlyFans, Patreon, Just for Fans
# - Use creator as studio, not platform name
# - Creator must be PornHub-verified for PH content
```

--------------------------------

### Amateur/Creator Studio Rules

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Defines rules for amateur and creator studios, including using the creator's name as the studio name and platform parentage.

```yaml
# Amateur/Creator Studios:
# - Use creator name as studio name
# - Platform can be parent studio if exclusive to one platform
# Example:
#   Parent: "PornHub"
#   Child: "Jane Doe Productions"
```

--------------------------------

### Re-releases and Remasters Rules

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Explains guidelines for handling re-releases and remasters, allowing distinct versions with unique studio links.

```yaml
# Re-releases/Remasters:
# - Distinct versions allowed with unique studio links
# - Cross-posted amateur content needs only one entry
```

--------------------------------

### Scene Date Formatting

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Specifies the format for scene dates (YYYY-MM-DD) and notes that approximate dates are acceptable when the exact date is unknown.

```yaml
# Scene Date:
# - Use earliest known release date
# - Approximate dates acceptable when exact date unknown
# - Format: YYYY-MM-DD
```

--------------------------------

### Generating pHashes in Stash

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Instructions for generating perceptual hashes (pHashes) within the Stash application. pHashes are crucial for fuzzy matching local video files with StashDB entries.

```yaml
# Generating pHashes in Stash:
# Option 1: During Scan
# Settings -> Tasks -> Scan -> Enable "Generate perceptual hashes"

# Option 2: Manual Generation
# Settings -> Tasks -> Generate -> Enable "Perceptual hashes (for deduplication)"

# Option 3: Per-Scene Generation
# Select scenes -> Generate... -> Perceptual hashes

# Submitting pHashes to StashDB:
# Use Scene Tagger view to submit fingerprints to existing scenes
# pHashes are automatically included when submitting new scenes via draft

# Benefits of pHashes:
# - Match files across different resolutions/encodes
# - Fuzzy matching (doesn't require exact file match)
# - Detect duplicate files in local library
# - Help other users find matches for their files
```

--------------------------------

### Scene Eligibility Rules

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Defines the criteria for scene eligibility, focusing on source (1st party digital studios) and content restrictions.

```yaml
# Scene Eligibility:
# - Must be from 1st party digital studio
# - No 3rd party retailer-only content (Adult DVD Empire, etc.)
# - No physical-release-only content (VHS, DVD, BluRay)
```

--------------------------------

### Scene Aliases Description

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Explains the purpose of scene aliases, which include alternative titles from re-releases, different language versions, and abbreviated versions.

```yaml
# Scene Aliases:
# - Alternative titles from re-releases
# - Different language versions
# - Abbreviated versions
```

--------------------------------

### Full Movie Rules

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Details rules for including full movies, primarily for JAV releases and Western movies from official studio websites.

```yaml
# Full Movie Rules:
# - Only allowed for JAV releases
# - Western movies only if available directly from official studio website
# - Not from 3rd party storefronts
```

--------------------------------

### Performer Eligibility and Naming Guidelines

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Criteria for performer eligibility and conventions for naming performers in StashDB. Includes requirements for professional work or verified platform accounts.

```yaml
# Performer Eligibility:
# - Must work with professional studios OR
# - Have verified account on approved adult platform
# - No underage performers ever allowed

# Performer Name Guidelines:
# - Prefer unique names over commonly used aliases
# - JAV names: Western order with simplified Latin characters as primary
#   All other spellings go in aliases
# - Diacritics allowed in primary name but plain version must be an alias
#   Example: Primary "Amélie" -> Alias "Amelie"

# Performer Aliases:
# - Must be official adult credits only
# - No legal/given names (even if publicly known)
# - Suspicious aliases should be verified before adding
```

--------------------------------

### Performer Image Requirements

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Specifies requirements for performer images, including aspect ratio, size, and content restrictions.

```yaml
# Performer Image Requirements:
# - Preferred aspect ratio: 2:3 (vertical/portrait)
# - Max size: 1280px (auto-downscaled if larger)
# - No placeholder images (anonymous silhouettes)
# - No multiple performers (crop if possible)
# - No hardcore images (crop if possible)
# - No animated images (static only)
# - Watermarks/logos: Remove if possible, not required
```

--------------------------------

### Banned Studios List

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Lists specific studios that are permanently banned due to violations of performer consent, such as 'Girls Do Porn' and 'Girls Do Toys'.

```yaml
# Banned Studios:
# - Studios violating performer consent are banned
# - Girls Do Porn and Girls Do Toys: Permanently banned
# - Check banned studios list before creating
```

--------------------------------

### Physical Attributes for Performers

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Details physical attributes for performers, including birthdate, height, measurements, ethnicity, nationality, eye color, hair color, and breast type.

```yaml
# Physical Attributes:
birthdate: "1990-01-15"        # YYYY-MM-DD format
height: 165                     # In centimeters
measurements: "34B-24-36"       # US sizing
ethnicity: "Caucasian"          # From predefined list
nationality: "United States"    # Country of origin
eye_color: "Blue"
hair_color: "Blonde"
breast_type: "Natural"          # Natural, Augmented, or N/A
```

--------------------------------

### Animated Content Rules

Source: https://context7.com/stashapp/stashdb-docs/llms.txt

Specifies that animated content is only allowed from professional studios and prohibits independent animated content creators.

```yaml
# Animated Content:
# - Only from professional studios
# - No independent animated content creators
```