Creating Tasks & Prompts

Create and manage AI content in the Moxn web app

This guide walks through creating Tasks, Prompts, and Messages in the Moxn web app at moxn.dev.

Dashboard Overview

When you log in, the dashboard shows your workspace:

The dashboard displays:

• Tasks: Your prompt collections
• API Keys: Manage keys for SDK access
• Workspace info: Team and usage details

Creating a Task

A Task is your top-level container—think of it like a Git repository for a specific AI feature.

1. Navigate to Tasks

   From the dashboard, click Tasks in the sidebar.

2. Click Create Task

   Click the Create Task button in the top right.

3. Fill in details

   • Name: A descriptive name (e.g., “Customer Support Bot”)
   • Description: What this task is for
4. Create

   Click Create to create your task with a default “main” branch.

Tasks List

Each task card shows:

• Task name and description
• Last updated time
• Entity type badge

Task Organization

Organize tasks by:

• Feature: One task per AI feature

• Team: One task per team’s prompts

• Project: One task per project

• Your Workspace

  • Customer Support Bot (Task)
  • Search Assistant (Task)
  • Document Analyzer (Task)

Creating a Prompt

Prompts are templates for LLM invocations within a task.

1. Open your Task

   Click on the task where you want to create the prompt.

2. Click Create Prompt

   Click Create Prompt or the + button.

3. Enter details

   • Name: The prompt’s name (e.g., “Product Help”)
   • Description: What this prompt does
   • Folder: Optional folder path (e.g., “support/tier1”)
4. Create

   Click Create to add the prompt.

Task Detail View

When you open a task, you see the Prompts tab:

The task detail page shows:

• Prompts tab: All prompts in this task
• Schemas tab: Input schemas and user-defined schemas
• Traces tab: Execution logs from SDK invocations

Prompt Naming

Use folders to organize prompts:

• Customer Support Bot
  • support/
    • product-help
    • billing-questions
  • classification/
    • query-classifier
  • escalation/
    • escalation-handler

The folder structure is stored in the prompt name itself.

Adding Messages

Messages are the content blocks that make up your prompt.

1. Open your Prompt

   Click on the prompt to open the editor.

2. Add a Message

   Click Add Message or the + in the messages panel.

3. Choose role

   Select the message role:

   • System: Instructions for the LLM
   • User: User input template
   • Assistant: Example responses (for few-shot)
4. Write content

   Use the rich text editor to write your message content.

Prompt Detail View

Opening a prompt shows its components:

The prompt page displays:

• Input Schema: Auto-generated from message variables
• Tools: Attached schemas for function calling
• Message Templates: The ordered list of messages

Message Types

Role	Purpose	Example
System	LLM instructions	”You are a helpful customer support agent…”
User	User input template	Customer asks: {{query}}
Assistant	Example output	”I’d be happy to help with that…”

Rich Content

The editor supports:

• Text: Plain text content
• Variables: Dynamic values from your code
• Images: Inline images
• Files: PDF documents
• Code blocks: Formatted code snippets

Creating Messages for Reuse

Messages can be shared across prompts. Create standalone messages:

1. Go to Messages

   In your task, click Messages in the sidebar.

2. Create Message

   Click Create Message.

3. Configure

   • Name: Descriptive name (e.g., “Standard System Prompt”)
   • Role: system, user, or assistant
   • Content: The message content
4. Use in Prompts

   When adding messages to prompts, select existing messages to reuse them.

Benefits of Reuse

• Update once, affects all prompts using it
• Consistent instructions across prompts
• Easier maintenance

Message Ordering

Drag and drop to reorder messages within a prompt:

• Prompt: Product Help
  1. System Prompt (system)
  2. Context Template (user)
  3. Query Template (user)

The order determines the conversation flow sent to the LLM.

Prompt Settings

Configure prompt behavior:

Completion Config

Set default model settings:

• Provider: Anthropic, OpenAI, Google
• Model: claude-sonnet-4-20250514, gpt-4o, etc.
• Max Tokens: Maximum response length
• Temperature: Creativity (0-1)

Tools

Attach tools for function calling:

1. Create a Schema with tool definitions
2. Attach to the prompt
3. Configure tool_choice (auto, required, specific tool)

Structured Output

For JSON responses:

1. Create a Schema defining the output structure
2. Attach as structured output
3. Responses will conform to the schema

Deleting Content

Deletes are tracked per-branch and take effect on commit.

To delete:

1. Click the … menu on the item
2. Select Delete
3. Confirm the deletion

The item remains in other branches until you merge.

Best Practices

Start with system prompts

Write clear system instructions first. They set the tone for everything.

Use descriptive names

Names appear in code and logs. Make them meaningful.

Test before committing

Use the Studio to test prompts before committing changes.

Create reusable system prompts

Share common instructions across prompts to ensure consistency.

Next Steps

Variables & Properties

Add dynamic variables to messages

Branching & Committing

Version control your prompts

Working with Prompts

Use prompts in your code

Entity Model

Understand the data model