CopilotHub
SearchPromptsInstructionsAgentsToolsMCPs
  1. Home
  2. Instructions
  3. Collections Development
Back to Instructions

Collections Development

Coding standards for collections.instructions

javascript
0 downloads
28 views
0

Tags

testing
best-practices

Related Instructions

View all →

Python Docstring Standards

*.py

Write clear and consistent Python docstrings

python
python
documentation
+1
1
117

TypeScript Error Handling

*.ts

Comprehensive error handling patterns for TypeScript applications

typescript
typescript
error-handling
+1
0
101

React Component Best Practices

*.tsx

Guidelines for creating maintainable and performant React components

typescript
react
react
typescript
+2
0
116

WordPress Development — Copilot Instructions

Coding standards for wordpress.instructions

typescript
testing
security
+5
1
185

VueJS 3 Development Instructions

Coding standards for vuejs3.instructions

typescript
react
testing
security
+6
0
157

Update Code from Shorthand

Edit the code file ${REQUIRED_FILE}.

javascript
1
106
Browse More Instructions

CopilotHub

A curated collection of prompts, instructions, agents, and tools for AI-powered development.

Quick Links

  • Prompts
  • Instructions
  • Agents
  • Tools
  • MCPs
  • Search

Browse by Category

  • Code Generation
  • Debugging
  • Documentation
  • Refactoring
  • Testing
  • Security

Legal

  • Guidelines
  • About
  • Privacy Policy
  • Terms of Service

Community

GitHub

© 2026 CopilotHub.

Collections Development

Collection Instructions

When working with collections in the awesome-copilot repository:

  • Always validate collections using node validate-collections.js before committing
  • Follow the established YAML schema for collection manifests
  • Reference only existing files in the repository
  • Use descriptive collection IDs with lowercase letters, numbers, and hyphens
  • Keep collections focused on specific workflows or themes
  • Test that all referenced items work well together

Collection Structure

  • Required fields: id, name, description, items
  • Optional fields: tags, display
  • Item requirements: path must exist, kind must match file extension
  • Display options: ordering (alpha/manual), show_badge (true/false)

Validation Rules

  • Collection IDs must be unique across all collections
  • File paths must exist and match the item kind
  • Tags must use lowercase letters, numbers, and hyphens only
  • Collections must contain 1-50 items
  • Descriptions must be 1-500 characters

Best Practices

  • Group 3-10 related items for optimal usability
  • Use clear, descriptive names and descriptions
  • Add relevant tags for discoverability
  • Test the complete workflow the collection enables
  • Ensure items complement each other effectively

File Organization

  • Collections don't require file reorganization
  • Items can be located anywhere in the repository
  • Use relative paths from repository root
  • Maintain existing directory structure (prompts/, instructions/, agents/)

Generation Process

  • Collections automatically generate README files via npm start
  • Individual collection pages are created in collections/ directory
  • Main collections overview is generated as README.collections.md
  • VS Code install badges are automatically created for each item