Thank you for your interest in contributing to this repository. This document provides guidelines and instructions for contributing.
- Report broken prompts or incorrect outputs
- Report missing functionality
- Report registry inconsistencies
- Suggest new assets or improvements
- Add new prompts following the template
- Add new skills following the skill template
- Add new workflows for common task patterns
- Improve existing asset documentation
- Fix typos or unclear explanations
- Improve selection_hints and when_to_use descriptions
- Add usage examples
- Translate documentation
-
Follow the Template
- Use
docs/guides/prompt-template.mdas reference - Include all required metadata fields
- Use consistent naming conventions
- Use
-
Naming Convention
- File name:
prompt-<task>-<action>.md - ID:
prompt-<category>-<specific-action>
- File name:
-
Required Fields
--- id: prompt-xxx-v1 name: Clear Name summary: Brief description type: routing|system|task|workflow|tool-use|output|meta category: primary category sub_category: specific category when_to_use: - Specific use case 1 - Specific use case 2 when_not_to_use: - Specific non-use case 1 input_requirements: - Required input 1 output_shape: - Expected output 1 tags: [tag1, tag2] status: active ---
-
Quality Standards
- Prompts must be actionable and specific
- Avoid vague or generic instructions
- Include clear input/output specifications
- Provide meaningful selection_hints
-
Follow the Skill Template
- Use
docs/guides/skill-template.mdas reference - Include use cases and input/output definitions
- Use
-
Naming Convention
- Directory:
skills/<category>/ - File:
skill-<name>.md
- Directory:
When adding new assets, you must also update the appropriate registry:
- New Prompt → Add entry to
registry/prompts-registry.yaml - New Skill → Add entry to
registry/skills-registry.yaml - New Tag → Add entry to
registry/tags-registry.yaml - New Relationship → Add entry to
registry/relations-registry.yaml
-
Follow the Workflow Template
- Use
docs/guides/workflow-template.mdas reference - Define clear steps and dependencies
- Use
-
Documentation
- List all required prompts
- Specify execution order
- Include fallback strategies
- Fork the repository
- Make your changes
- Test locally if possible
- Submit a pull request with clear description
- Open an issue first to discuss
- Get approval before implementing
- Follow the full contribution workflow
- Include tests and documentation
- Use clear, descriptive titles
- Reference related issues
- Describe what changed and why
- Include before/after if applicable
Before submitting, verify:
- Prompt follows template structure
- All required fields are present
- Registry entry matches actual file
- No broken links or references
- Selection hints are helpful and specific
- when_to_use / when_not_to_use are not vague
By contributing, you agree that your contributions will be licensed under:
- CC BY 4.0 for content (prompts, skills, workflows, documentation)
If you have questions, please open an issue or contact the maintainers.
Contributors will be recognized in the README and CHANGELOG.
Thank you for helping improve this repository!