mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios
synced 2026-05-01 18:07:20 +00:00
882b76f942
- README: centered header, badge row (license, agents, skills, hooks, rules, Claude Code, Ko-fi), "Why This Exists" motivation section, table of contents, "Collaborative Not Autonomous" section, community section - Add GitHub issue templates (bug report + feature request) - Add pull request template with checklist - Add .github/FUNDING.yml with Ko-fi link - Gitignore internal planning docs, remove from tracking Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
40 lines
865 B
Markdown
40 lines
865 B
Markdown
---
|
|
name: Feature Request
|
|
about: Suggest a new agent, skill, hook, or improvement
|
|
title: "[Feature] "
|
|
labels: enhancement
|
|
assignees: ''
|
|
---
|
|
|
|
## Summary
|
|
|
|
A brief description of what you'd like added or changed.
|
|
|
|
## Type
|
|
|
|
- [ ] New agent
|
|
- [ ] New skill (slash command)
|
|
- [ ] New hook
|
|
- [ ] New rule
|
|
- [ ] New template
|
|
- [ ] Improvement to existing component
|
|
- [ ] Other:
|
|
|
|
## Problem / Motivation
|
|
|
|
What problem does this solve? What workflow does it improve?
|
|
|
|
## Proposed Solution
|
|
|
|
How do you think this should work? Include details like:
|
|
- For agents: what domain, what tier, what tools
|
|
- For skills: what the workflow looks like, what it outputs
|
|
- For hooks: what event triggers it, what it validates
|
|
|
|
## Alternatives Considered
|
|
|
|
Any other approaches you've thought about.
|
|
|
|
## Additional Context
|
|
|
|
Examples, references, or screenshots that help explain the request.
|