Documentation Index
Fetch the complete documentation index at: https://docs.xpertai.cn/llms.txt
Use this file to discover all available pages before exploring further.
Turn repeatable tasks into discoverable slash commands inside the ChatKit composer.
/review, /debug, /summarize, or /test. A command can expand into a prompt, submit immediately, select required runtime capabilities, or notify the host application.
This gives teams a way to standardize common assistant workflows without forcing users to memorize long prompts.
How Users Discover Workflows
When a user types/ at the start of the composer, ChatKit opens a command palette. The palette can include:
- built-in ChatKit commands such as
/planand/pet - static commands configured by the host application
- runtime commands published by Xpert skills
- Skills, Plugins, and Sub-agents groups for capability selection
/ in the middle of a message after whitespace, ChatKit focuses on runtime capability tokens instead of global commands.
What a Prompt Workflow Can Do
A workflow command can:- insert a prompt draft into the composer
- write a raw slash invocation for backend expansion
- render a template and submit it as a user message
- attach runtime capabilities needed by the workflow
- notify the host application through a client action
/security-review src/app.ts workflow can submit a normalized review prompt and select the skill that contains the security review instructions.
Runtime Workflows from Skills
Xpert skills can publish workflow commands through the runtime capability response. ChatKit shows them in the same slash palette as host commands, so a skill can bring both the backend behavior and the user-facing shortcut that activates it. Runtime workflow commands are validated by the Xpert backend before they are exposed. They cannot bypass assistant permissions, skill access, plugin access, or runtime capability allow-list rules.Metadata and Observability
When a workflow command submits a prompt, ChatKit includes command metadata in the submitted human input. This makes it easier to audit which workflow produced a message, debug template behavior, or analyze workflow adoption. Metadata is informational. The backend should still enforce normal access control and workflow rules.Product Guidance
Good Prompt Workflows are:- short to type and easy to search
- specific to a recurring job
- opinionated enough to improve prompt quality
- paired with the runtime skills or plugins they require
- documented in user-facing language, not implementation language
/review, /explain, /test, /debug, /summarize, /draft, and /handoff.