> For the complete documentation index, see [llms.txt](https://ludicore-ai.gitbook.io/ludicore-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ludicore-ai.gitbook.io/ludicore-ai/slash-commands.md). # Slash Commands LudiCore offers specialized slash commands designed to streamline your game development workflow. Each command is tailored for specific tasks, ensuring you receive the most relevant and helpful support for your needs. Watch the overview video to see the commands in action, or keep reading to learn more about how each one can elevate your development process. {% embed url="" %} ## Available Commands **`/chat`**\ Designed for general discussions, conceptual explanations, and high-level guidance in game development. **Key Features:** * Delivers detailed explanations of game development concepts. * Offers step-by-step guidance for implementing game systems. * Assists with project onboarding and debugging. * Handles engine-specific questions and provides project overviews. * Supplies code snippets for quick reference. **Best Used For:** * Learning game development concepts. * Understanding optimization techniques. * Receiving high-level project architecture advice. * Debugging workflows. * Answering engine-specific queries. **Example Usage:** * `/chat explain object pooling and its benefits` * `/chat how would I make a 2D bullet hell game?` *** **`/script`**\ Focused on code creation, modification, and management with seamless file handling capabilities. It functions similarly to other AI copilots like GitHub Copilot or Cursor but is tailored for game development. **Key Features:** * Creates new script files. * Modifies existing scripts with search/replace functionality. * Includes an "Insert All Code" button for quick implementation. * Provides user control through an approval system for code changes. **Best Used For:** * Creating new features. * Debugging existing code. * Refactoring code for clarity or performance. * Adding thorough code documentation. * Simplifying script creation and editing. **Special Feature:**\ The **"Insert All Code"** button: * Automatically creates new scripts if they don’t exist. * Modifies existing scripts with clear change suggestions. * Ensures user approval before applying changes. These commands make LudiCore your go-to tool for smarter, faster, and more efficient game development.
## Understanding Search/Replace Blocks in `/script` Mode We strongly suggest using VSCode with LudiCore for its intuitive interface when reviewing code changes. After pressing "Insert All," the modified file will display two blocks: the first showing the original code and the second showing the updated version. To manage changes: * Select **Accept Incoming Change** to approve the updates. * Select **Accept Current Change** to reject them and keep the original code.
**Example Usage:** * `/script generate a player controller script` * `/script implement a dash feature in my character's movement script` ## `/prototype` **Key Features:** * Creates and manipulates game objects seamlessly. * Arranges and organizes scene elements. * Adjusts component properties with ease. * Supports the creation of basic materials, prefabs, and UI elements. * Enables rapid prototyping for quick iteration. **Current Limitations:** * Does not support direct script creation or editing. * Uses basic prototyping assets for object creation, such as capsule characters, solid color materials, or primitive UI elements. **Best Used For:** * Setting up scenes quickly. * Creating and arranging game objects. * Adjusting component properties. * Prototyping scene layouts. * Modifying or creating basic prefabs. **Special Features:** * Every command taken by the AI is displayed in a sequential list, giving you the option to: * Execute specific commands you find important. * Use **Execute All** to apply every command at once. * View detailed descriptions of commands with **View Command**, ensuring full transparency before applying changes. * All changes can be reversed instantly with **CTRL+Z** on Windows or **CMD+Z** on Mac for complete flexibility. With these tools, prototyping and scene management become faster, more intuitive, and highly customizable.
**Example Usage:**\ /prototype create a square arena with a player in the center\ /prototype spawn 5 enemies randomly around the player ## `/default` The default mode intelligently selects the most suitable response type based on your query. If you’re unsure which slash command to use, this is the perfect starting point. **Key Features:** * Automatically determines the most appropriate command type for your input. * Seamlessly switches between chat, script, and prototype behaviors. * Designed for newcomers who may not know which command to choose. * Offers the flexibility of all command types while maintaining context and relevance. **Example Usage:** * `/default how do I implement player movement?` The assistant will analyze your query and may use `/script` to provide code or `/chat` to explain the concept first. For a specific behavior, switch to the desired slash command to refine the response. ## Best Practices **For New Users:** * Start with `/default` to familiarize yourself with the system. * Gradually explore specific commands as you learn their functions and purposes. **For Experienced Users:** * Leverage specific commands for precise and targeted responses. * Combine commands in your workflow (e.g., use `/prototype` to set up the scene, then `/script` to add behaviors). **Break Down Tasks:** * Divide your goal into smaller, manageable tasks for better results. * Instead of asking for everything in one step, use multiple prompts to achieve your objective incrementally. **Provide Context:** * Include details about specific objects, scripts, or assets to unlock LudiCore's full potential. * Drag and reference objects or scripts directly to help the AI understand what needs modification. **For Optimal Results:** * Be clear and specific in your queries. * Use `/chat` to gain a conceptual understanding before diving into implementation. * Switch to `/script` for coding tasks and modifications. * Opt for `/prototype` when you need quick scene adjustments or object creation. By following these tips, you can maximize LudiCore’s capabilities and streamline your game development process. ## Tips * Always review suggested changes, especially when using `/script` * Use `/chat` when unsure about implementation details * Combine `/prototype` with `/script` for full feature implementation * Remember that `/default` is smart but specific commands give more controlled responses --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ludicore-ai.gitbook.io/ludicore-ai/slash-commands.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.