Contact
Use GitHub for bugs, questions, and template requests. Include the details below so I can reproduce the problem.
01 · Channels
Where to write
- Bugs, template requests, and questions: open an issue at github.com/tw93/kami/issues. This is the primary channel and the one with public history, so a question answered there helps the next person.
- Fixes and new templates: pull requests are welcome at github.com/tw93/kami/pulls. Run
python3 scripts/build.py --checkbefore opening one; it covers template lint, design-token sync, and public-fact drift. - Anything that should not be public, including a security report: email the maintainer at hitw93@gmail.com, the same address published in the plugin manifests.
- Everything else: @HiTw93 on X, or the maintainer's site at tw93.fun.
I maintain Kami alongside other projects, so replies may take time. There is no paid support tier.
02 · Reports
What to include
Include these details with a layout report.
- The template name, for example
resume-enorslides-weasy, and the Kami version from the homepage badge orVERSION. - How it was invoked: the Claude Code plugin, the Codex plugin, a Claude Desktop upload, the MCP server, or a direct
scripts/build.pyrun. - The rendered artifact, a PDF or a page PNG, rather than a description of it. A screenshot helps show where the layout went wrong.
- The output of the relevant check, for example
python3 scripts/build.py --check-content content.json filled.html, if the document verified clean but still looks wrong.
For rendering failures, the exact error text matters: WeasyPrint, pypdf, and PyMuPDF are optional dependencies, and a missing one surfaces as an install hint rather than a crash. Include the full error message and any install hint.