all opencode features deeply integrated inside Discord. each project is a channel. each session a thread
About the project
Kimaki is a Discord-based orchestrator for OpenCode, an AI coding agent that edits files on a user's machine. It maps each project to a Discord channel and each coding session to a thread, allowing users to start, resume, search, and fork work through conversations. Catalogue add-ons provide Kimaki-related workflows for coding agents.
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
Opinionated TypeScript npm package template for ESM packages. Enforces src→dist builds with tsc, strict TypeScript defaults, explicit exports, and publish-safe package metadata. Relative source imports must use .ts or .tsx (never .js); tsc rewrites them via rewriteRelativeImportExtensions. Use this when creating or…
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package or GitHub repo, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include…
Debug and administer Kimaki itself. Use when sessions do not respond, the bot shows errors, you need the Kimaki or OpenCode service logs, want to profile the bot, restart it (only when asked), connect a model provider with kimaki login, check who may use the bot, or file a Kimaki bug report. ALWAYS load when Kimaki…
Share a local dev server with the user through a public URL. Use when the user should open a localhost app in a browser, test a webhook or OAuth callback against a local server, or preview a dev server from Discord. Runs kimaki tunnel in a named background tuistory session. ALWAYS load before starting a dev server the…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: