Say hello, or lend a hand
dronAIcharya is open source under the MIT license. Everything happens on GitHub — questions, bug reports, security disclosures, and contributions of curriculum, personas, fixes, and translations are all welcome.
Ways to reach the project
Report a bug or request a feature
Open an issue. Describe what you expected, what happened, your editor and version, and steps to reproduce.
github.com/dibakshya01/dronAIcharya/issues →
Ask a question
Start a discussion for setup help, teaching ideas, or anything that isn't quite a bug. (If Discussions aren't enabled, open an issue labelled "question".)
github.com/dibakshya01/dronAIcharya/discussions →
Disclose a vulnerability privately
Found a way the hooks could be abused, or a secret could leak? Please use a private GitHub Security Advisory, or open an issue describing the impact without exploit details and ask to take it private.
Private advisory · see SECURITY.md →
Contribute
Curriculum, personas, fixes and translations are all welcome. Read CONTRIBUTING.md, keep PRs small and focused, and have new content fact-checked.
CONTRIBUTING.md →
Four things we hold to
A tutor that teaches wrong things is worse than none. These keep the project honest.
Teach, don't just do
Every change should serve the teaching contract — understanding first, the learner in control, honesty throughout.
Be factually correct
Cite sources for anything non-obvious and flag uncertainty. New content gets fact-checked before it ships.
No impersonation
No real-person or trademarked-character names in personas or docs — use original archetypes.
No secrets, ever
Never commit keys or tokens, in examples or fixtures. Teach .env and .gitignore instead.
Run the checks
All green, plus a clear description of what you changed and why.
claude plugin validate . --strict # manifests + structure
bash tests/test-hooks.sh # guardrail safety
bash tests/validate-content.sh # JSON/schema + frontmatter
By participating you agree to the Code of Conduct.
Thanks for helping teach people to build.
Star the repo, open an issue, or send a small focused PR. Every bit helps.