commandkit 1.2.0-dev.20260208011555 → 1.2.0-dev.20260208122102

package/README.md

@@ -6,43 +6,62 @@
     <a href="https://www.npmjs.com/package/commandkit"><img src="https://img.shields.io/npm/dt/commandkit?maxAge=3600" alt="npm downloads" /></a>
 </div>
 
-<p align="center">The discord.js meta-framework for building powerful, modular, and extensible Discord bots with ease.</p>
+<p align="center">Stop rebuilding command and event handlers for every new discord.js bot. CommandKit does it for you — and a lot more.</p>
+
+## Why CommandKit?
+
+Every new discord.js project starts the same way: write a command handler, write an event handler, set up interaction collectors, register slash commands with the API, figure out a project structure. It's hours of boilerplate before you write any real bot logic.
+
+Most existing discord.js frameworks solve this by giving you a handler class you instantiate and point at a folder — and that's about it. They're loaders, not frameworks. Others like Sapphire go further and have decent features, but require heavy OOP boilerplate where everything is a class extending a base class.
+
+CommandKit takes a different approach entirely. It works like a proper meta-framework — think **Next.js for Discord bots**. It ships with a smart CLI that handles bundling, TypeScript/JSX compilation, hot-reloading, command registration, and project scaffolding automatically. You run `commandkit dev` and everything just works — zero configuration.
+
+The design philosophy is **convention over configuration**: put a file in `src/app/commands/` and it's a command. Put a file in `src/app/events/` and it's an event listener. Export a `chatInput` function and it handles slash commands. Export a `message` function in the same file and it handles prefix commands too. No registration calls, no base classes, no decorators. The framework knows what to do with your code based on where it is and what it exports — so you skip the setup and go straight to building.
 
 ## Features
 
-- Beginner friendly 🚀
-- Suitable for both beginners and advanced users 👶👨‍💻
-- Slash + context menu commands + prefix commands support ✅
-- Automatic command registration and updates 🤖
-- Command middlewares for easy command management 🛠️
-- Localization support through `@commandkit/i18n` plugin 🌍
-- Plugin system to extend functionality 🔌
-- Built-in command line interface for easy development 🖥️
-- Out-of-the-box support for TypeScript and JavaScript 📜
-- Built-in customizable cache system for speedy data storage and retrieval 🗄️
-- User installable/guild scoped commands 🔧
-- Custom events support 🔔
-- JSX support for declaring Discord interaction components and modals 🎨
-- Easy to use interaction components and modals system (forget about collectors) 🧩
-- Less boilerplate code, more productivity 💪
-- and much more...
+### Automatic command and event handling
+Drop your command files in a folder, export a function, and they just work. Slash commands, context menu commands, and prefix commands are all supported under a single unified command structure — no separate handler for each type. Commands are automatically registered and kept in sync with Discord. Events work the same way: create a file, export a listener, and CommandKit handles the rest.
 
-## Getting Started
+### JSX components for Discord UI
+discord.js builder chains (`ActionRowBuilder` → `ButtonBuilder` → `setCustomId` → ...) get messy fast. CommandKit lets you write Discord components in JSX — the same declarative syntax used in React — so your UI code is clean and readable.
+
+### Built-in component handlers (no more collectors)
+Buttons get `onClick`. Modals get `onSubmit`. Select menus get `onSelect`. Define a component and its behavior in one place — no `InteractionCollector` setup, no timeout management, no cleanup boilerplate.
 
-Get started by checking out the [documentation](https://commandkit.dev).
+### Command middlewares
+Run logic before or after any command executes — permission checks, cooldowns, logging, analytics — without touching the command itself. A proper middleware layer, like you'd find in Express.
 
-## Installation
+### Unified prefix commands
+Message-based (prefix) commands live in the same file as your slash commands and context menus. One command file handles all input types. No separate handler needed.
 
-[![npm](https://nodei.co/npm/commandkit.png)](https://nodei.co/npm/commandkit/)
+### Caching with Redis support
+The `@commandkit/cache` plugin gives you a customizable caching layer — in-memory by default, Redis-backed when you need persistence. Just add the `'use cache'` directive to any function.
 
-To create a new CommandKit project, you can use the following command:
+### Plugin system with custom events
+Extend CommandKit through plugins that hook into the framework lifecycle. Plugins can emit custom events — for example, listening to an external webhook and firing events your bot can react to. This isn't a wrapper around `node:events`; it's a structured extension system for building modular, decoupled bot features. Official plugins include `@commandkit/i18n` for localization and `@commandkit/analytics` for usage tracking.
 
+### AI-powered command execution
+The `@commandkit/ai` plugin lets users interact with your bot through natural language. Instead of memorizing slash command names, users just talk to your bot — and the AI figures out which command to run. Built on the [AI SDK](https://ai-sdk.dev) with support for Google Gemini, OpenAI, and more. Includes built-in tools, custom tool support, lifecycle hooks, and per-user model selection.
+
+### Zero-config TypeScript and JavaScript
+Native TypeScript and JSX support with no configuration. No `tsconfig.json` fiddling, no separate build step, no bundler setup. The CLI handles compilation, bundling, hot-reloading, and project scaffolding.
+
+## Who is this for?
+
+- **Beginners** who don't want to spend hours building handlers before they can do anything useful
+- **Experienced developers** tired of rebuilding the same boilerplate for every new bot project
+- **Teams and freelancers** who need a reliable, structured foundation they can build on quickly
+
+CommandKit has been used in production client projects and has saved hours of setup time on each one. It's not overhead — it's the setup work you'd do anyway, already done well.
+
+## Getting Started
 
 ```bash
 npm create commandkit
 ```
 
-This will prompt you to enter few details about your project. Once you have entered the details, you can simply run `commandkit dev` to start the bot application.
+Follow the prompts, then run `commandkit dev` to start your bot. Check out the [documentation](https://commandkit.dev) for guides and API reference.
 
 ## Support and Suggestions
 

package/dist/cli/information.js

@@ -1,6 +1,6 @@
 const require_chunk = require('../chunk-kSYXY2_d.js');
 const require_constants = require('../constants-CeIMhMD0.js');
-const require_version = require('../version-Du5sIQO0.js');
+const require_version = require('../version-BQuDarCv.js');
 let node_fs = require("node:fs");
 node_fs = require_chunk.__toESM(node_fs);
 let node_path = require("node:path");

package/dist/index.js

@@ -19,7 +19,7 @@ const require_MessageCommandParser = require('./MessageCommandParser-VMFFGs0R.js
 const require_CommandsRouter = require('./CommandsRouter-D5mGRFEr.js');
 const require_EventsRouter = require('./EventsRouter-Be5NDOX4.js');
 require('./router-CtcApqrw.js');
-const require_version = require('./version-Du5sIQO0.js');
+const require_version = require('./version-BQuDarCv.js');
 const require_file = require('./file-DqI3v90P.js');
 const require_separator = require('./separator-DGwA_b1J.js');
 const require_text_display = require('./text-display-BVuG7dT-.js');

package/dist/{version-Du5sIQO0.js → version-BQuDarCv.js}

@@ -6,7 +6,7 @@
 /**
 * The current version of CommandKit.
 */
-const version = "1.2.0-dev.20260208011555";
+const version = "1.2.0-dev.20260208122102";
 
 //#endregion
 Object.defineProperty(exports, 'version', {
@@ -15,4 +15,4 @@ Object.defineProperty(exports, 'version', {
     return version;
   }
 });
-//# sourceMappingURL=version-Du5sIQO0.js.map
+//# sourceMappingURL=version-BQuDarCv.js.map

package/dist/{version-Du5sIQO0.js.map → version-BQuDarCv.js.map}

@@ -1 +1 @@
-{"version":3,"file":"version-Du5sIQO0.js","names":[],"sources":["../src/version.ts"],"sourcesContent":["/**\n * @private\n */\nfunction $version(): string {\n  'use macro';\n  return require('../package.json').version;\n}\n\n/**\n * The current version of CommandKit.\n */\nexport const version: string = $version();\n"],"mappings":";;;;;;;;AAWA,MAAa,UAA4B"}
+{"version":3,"file":"version-BQuDarCv.js","names":[],"sources":["../src/version.ts"],"sourcesContent":["/**\n * @private\n */\nfunction $version(): string {\n  'use macro';\n  return require('../package.json').version;\n}\n\n/**\n * The current version of CommandKit.\n */\nexport const version: string = $version();\n"],"mappings":";;;;;;;;AAWA,MAAa,UAA4B"}

package/dist/version.js

@@ -1,3 +1,3 @@
-const require_version = require('./version-Du5sIQO0.js');
+const require_version = require('./version-BQuDarCv.js');
 
 exports.version = require_version.version;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "commandkit",
   "description": "Beginner friendly command & event handler for Discord.js",
-  "version": "1.2.0-dev.20260208011555",
+  "version": "1.2.0-dev.20260208122102",
   "license": "GPL-3.0-only",
   "type": "commonjs",
   "main": "./dist/index.js",
@@ -187,7 +187,7 @@
     "tsx": "^4.19.2",
     "typescript": "^5.9.3",
     "vitest": "^3.0.5",
-    "tsconfig": "0.0.0-dev.20260208011555"
+    "tsconfig": "0.0.0-dev.20260208122102"
   },
   "engines": {
     "node": ">=24"