Using Rise with AI Agents

When to use this

Use the Rise App Builder skill when an AI agent is building, configuring, or deploying an application on Rise. It provides decision routing, safety invariants, CLI commands, and rise.toml guidance that an agent should prefer over general container-platform assumptions.

Install the skill

Install the bundled skill into the default Claude Code and Crush-compatible skills directory:

rise skill install

Restart the AI tool after installation. Use rise skill list to verify the installation or rise skill install --target <directory> for another skills location.

Load the skill remotely

An agent does not need the skill installed locally. Point it to the hosted files:

• Rise App Builder SKILL.md
• CLI cheatsheet
• rise.toml reference

The user documentation llms.txt also lists these files under AI Skills, so an agent starting from the documentation root can discover them automatically.

Granting the agent access

The skill tells the agent to log in with rise login --device. The agent then hands you a link on your Rise instance and a code. Open the link, check that the page shows the same code, and click Approve. Only approve a code your agent just showed you: approving signs that CLI in as you.

The CLI keeps one token per Rise URL, so the session you approve replaces any login already stored on that machine.

Recommended prompt

This prompt automatically uses the documentation URL of the page you are viewing, including PR previews:

You are working on an application deployed with Rise.

AUTHORITATIVE SOURCES
1. Read /rise/user/llms.txt to discover the available Rise documentation.
2. Read /rise/user/skills/rise-app-builder/SKILL.md before making changes.
3. Load the skill's CLI and rise.toml reference files when they apply to the task.

OPERATING RULES
- Treat the hosted skill and documentation as authoritative over prior knowledge.
- Follow the skill's routing decisions and core invariants.
- Inspect the existing application before changing configuration or deployment files.
- Do not guess Rise CLI flags, rise.toml fields, authentication flows, or deployment defaults.

TASK
<Describe the application change or deployment outcome you want.>