Prompts are structured workflows that guide you through complex tasks. Instead of remembering which tools to use in which order, you can start a prompt and follow along.

Creates a complete range configuration from your description.

Usage:

Create a range with: Windows domain controller, 3 workstations, SCCM server, and Splunk monitoring

Note The more detailed the instructions, the quicker the LLM will accomplish your task and the greater chance it meets your intent. Especially helpful to name desired roles even if the names aren't exact.

What it does:

1. Analyzes your requirements
2. Researches available roles and templates
3. Builds a valid configuration
4. Validates against schemas
5. Optionally saves the configuration file

Parameters:

• requirements: Description of what you want to build
• roles: Optional specific roles to include
• save_config: Whether to save the configuration file (true/false)

Safely executes Ludus CLI commands with built-in safety checks.

Usage:

Deploy my range for user TestUser

What it does:

1. Determines the correct CLI command
2. Checks current system state
3. Warns about destructive operations
4. Executes the command safely

Parameters:

• command_intent: What you want to accomplish
• target_user: User to operate on (admin only)
• confirm_destructive: Confirmation for dangerous operations

1. Press the + symbol near the chat input field

2.Select "Add from Ludus"

3. Select the appropriate prompt

4. Fill in prompt fields with appropriate data

Prompts guide you through each step:

1. Clarify requirements if needed
2. Research necessary components
3. Build and validate configurations
4. Execute operations safely

Prompts will show you what they're going to do before taking action. You can:

• Review the planned configuration
• Modify requirements
• Cancel if something looks wrong

Be Specific Instead of: "Create a Windows lab" Try: "Create a Windows domain with 1 DC, 2 workstations, and SCCM"

Mention Key Requirements

• Operating systems needed
• Number of machines
• Specific software or roles
• Network requirements
• User or admin operations

Use Save Options

• Set save_config: true if you want to keep the configuration
• Specify where to save custom configurations
• Use descriptive filenames

Verify Before Deploying

• Review the configuration before deployment
• Check resource requirements
• Confirm you have necessary permissions

Use Prompts for:

• Creating new ranges
• Complex multi-step operations
• When you're not sure which tools to use
• Learning the proper workflow

Use Individual Tools for:

• Quick single operations
• When you know exactly what tool you need
• Checking status or getting information
• Debugging specific issues

1. Start with a prompt: "Create a range with Windows AD, SCCM, and 3 client machines"

2. Follow the guidance:

   • Prompt researches available roles
   • Builds configuration step by step
   • Validates everything

3. Review and save:

   • Check the generated configuration
   • Save with a descriptive name
   • Note any warnings or requirements

4. Deploy when ready:

   • Use execution prompt or tools
   • Monitor deployment progress
   • Verify successful deployment

This approach handles the complexity while keeping you in control of the process.