docs: mark after as unstable + improve middleware docs

Author: notunderctrl

apps/website/docs/guide/02-commands/05-after-function.mdx

@@ -2,6 +2,13 @@
 title: after Function
 ---
 
+:::warning UNSTABLE
+
+The `after()` function is currently marked as unstable and may change
+in the future.
+
+:::
+
 The `after()` function allows you to execute a callback after a
 command has been executed. This is useful for performing actions that
 should occur after the command has completed, such as logging or
@@ -10,13 +17,18 @@ cleanup tasks.
 ## Usage
 
 ```ts title="src/app/commands/ping.ts"
-import { type CommandData, type ChatInputCommand, after } from 'commandkit';
+import {
+  type CommandData,
+  type ChatInputCommand,
+  unstable_after as after,
+} from 'commandkit';
 
 export const command: CommandData = {};
 
 export const chatInput: ChatInputCommand = async (ctx) => {
   after(() => {
     // This code will be executed after the command has been executed
+    // Perform any cleanup here
     console.log('Command has been executed');
   });
 

apps/website/docs/guide/02-commands/07-middlewares.mdx

@@ -21,7 +21,9 @@ import { MiddlewareContext } from 'commandkit';
 
 export function beforeExecute(ctx: MiddlewareContext) {
   // This function will be executed before the command is executed
-  console.log(`User ${ctx.interaction.user.id} is about to execute a command`);
+  console.log(
+    `User ${ctx.interaction.user.id} is about to execute a command`,
+  );
 }
 
 export function afterExecute(ctx: MiddlewareContext) {
@@ -52,6 +54,49 @@ export function beforeExecute(ctx: MiddlewareContext) {
 }
 ```
 
+:::tip
+
+You can also use `stopMiddlewares()` inside a command function to stop
+any `afterExecute` middlewares from running.
+
+In addition, you can also use `stopMiddlewares()` inside any
+`afterExecute` middleware function to stop any remaining middlewares
+from running.
+
+:::
+
+:::warning
+
+Calling `stopMiddlewares()` in a try/catch block may lead to
+unexpected behavior.
+
+If you still want to use `stopMiddlewares()` in a try/catch block, you
+can use the `isErrorType` function to check if the error is an
+instance of the `CommandKitErrorCodes.StopMiddlewares` error.
+
+```ts title="src/app/commands/+middleware.ts"
+import type { MiddlewareContext } from 'commandkit';
+
+export function beforeExecute(ctx: MiddlewareContext) {
+  try {
+    // code that may throw an error
+
+    stopMiddlewares(); // conditionally stop the middleware chain
+  } catch (error) {
+    if (isErrorType(error, CommandKitErrorCodes.StopMiddlewares)) {
+      // if stopMiddlewares() is called in the try block, throw it so CommandKit can stop the middleware chain
+      throw error;
+    }
+
+    // this means that the code threw the error, and stopMiddlewares() was not called
+    // the rest of the middlewares will be executed as normal
+    console.error(error);
+  }
+}
+```
+
+:::
+
 ## Middleware types
 
 ### Directory-scoped middleware
@@ -66,7 +111,9 @@ import type { MiddlewareContext } from 'commandkit';
 export function beforeExecute(ctx: MiddlewareContext) {
   // This middleware will run before any moderation command
   if (!ctx.interaction.member.permissions.has('KickMembers')) {
-    throw new Error('You need moderation permissions to use this command');
+    throw new Error(
+      'You need moderation permissions to use this command',
+    );
   }
 }
 ```