Contribute with your assistant

Contributions require a coding assistant. You own the idea, constraints, tradeoffs, evidence review, submission and acceptance. Your assistant inspects the project, reproduces behavior, implements accepted work, runs checks and prepares evidence you can inspect.

Start with existing GitHub issues. Ask your assistant to identify the owning repository and related work. Describe the app problem, exact versions, expected and actual behavior, reproduction, and the smallest useful outcome. Review the evidence, then open an issue proposal or join the existing one.

A maintainer agrees on scope before a linked PR. Build and exercise that change, keep its documentation/tutorial current, and return the source identities and verification. A performance claim also includes its workload, baseline, repeated results and decision under the research standard.

Use Discord for human community conversation. Actionable contributions return to a GitHub issue before their PR. Reports and showcase requests stay with the project. Maintainers confirm permission and agreed credit in the issue before publishing a project feature.

For your first app, follow the installation guide and Pet Tracker tutorial. Use the docs MCP and available Minecart context. Open one page, create/edit a record, restart and verify persistence, then inspect one assistant-built change. Check current tool releases in the ecosystem tracker.

The public website adopts this workflow. Cross-repository issue-template installation and mandatory automated policy checks remain separate work. Humans review the proposal and its evidence throughout.