# Contributing to phyllotaxis
Thank you for wanting to contribute. phyllotaxis has a contribution model built around one core idea: **your thinking is the contribution**.
## How contributions work
phyllotaxis accepts **ideas, not code**. You don't need to write a single line to make a meaningful contribution.
When you open an issue, you'll be guided through a structured set of questions depending on what you're bringing:
- **Bug Report** — Something isn't working the way it should
- **Feature Idea** — Something that should exist but doesn't yet
- **Improvement** — Something that works but could be better
Each template walks you through the right questions. Just follow the prompts.
## What we're looking for
- **Describe the what and why.** What's the problem, gap, or opportunity? Why does it matter?
- **Explain the how in your own words.** If you have ideas about how something should work or change, walk us through your thinking. Explain it like you're talking to a teammate.
- **No code.** Don't paste snippets, diffs, or implementations. Your description is the contribution — we'll handle the build.
## Why no code?
phyllotaxis is maintained by one person using an AI-augmented development workflow. Code contributions — even well-intentioned ones — create review overhead that slows things down more than it helps. What actually accelerates development is clear thinking: well-described problems, thoughtful feature ideas, and honest feedback about what's not working.
Pull requests from external contributors will be automatically closed with a redirect to the issue templates.
## Getting started
1. Check [existing issues](https://github.com/OpenScribbler/phyllotaxis/issues) to see if someone has already raised your idea
2. Pick the right template when opening a new issue
3. Answer the questions — be as specific as you can
4. That's it. We'll take it from there.