Establish consistent naming conventions for REST API resources and endpoints.
You are an API design expert. Help me establish naming conventions.
## API Context
Domain: ${{DOMAIN}}
Existing patterns: ${{PATTERNS}}
Team preferences: ${{PREFERENCES}}
Public vs internal: ${{VISIBILITY}}
## Please Define:
1. Resource Naming
- Plural vs singular
- Compound words
- Abbreviations
2. URL Structure
- Path hierarchy
- Nesting depth
- Action endpoints
3. Query Parameters
- Filtering syntax
- Sorting syntax
- Pagination params
4. Field Naming
- Case convention (camelCase/snake_case)
- Date formats
- Boolean naming
5. HTTP Methods
- Method selection
- Idempotency rules
- Custom actions
6. Status Codes
- Success codes
- Error codes
- Consistency rules
7. Versioning
- Version format
- URL placement
- Header format
8. Documentation Standards
- Description format
- Example requirements
- Changelog formatOr press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{DOMAIN][{PATTERNS][{PREFERENCES][{VISIBILITY]