> ## Documentation Index
> Fetch the complete documentation index at: https://neo.tvk.company/llms.txt
> Use this file to discover all available pages before exploring further.

# Neo Skills

> Use AI skills to update and migrate Neo projects faster

Neo Skills give compatible AI coding agents focused workflows for Neo projects. They help the agent understand what to do, where to find the right Neo documentation, and how to turn that guidance into useful project changes.

The first skill is `update-neo`, built for upgrading a project from one Neo version to another. Run it with `/update-neo` to start a guided update flow that checks Neo release notes, finds affected code, and helps apply migration steps.

<Note>
  Skills guide the AI agent, but you still stay in control. Review the diff before keeping changes, especially when the agent edits multiple files.
</Note>

## Why use Neo Skills?

<CardGroup cols={2}>
  <Card title="Update with context" icon="book-open">
    Give the agent a workflow that starts from Neo's official docs and release notes.
  </Card>

  <Card title="Migrate faster" icon="arrows-rotate">
    Move through version updates with less manual searching, scanning, and repetitive editing.
  </Card>

  <Card title="Keep changes reviewable" icon="list-check">
    The skill is designed around focused project edits that you can inspect before accepting.
  </Card>

  <Card title="Built for the future" icon="sparkles">
    Skills are how Neo can ship higher-level AI workflows as the framework grows.
  </Card>
</CardGroup>

## Install

Install Neo Skills with the skills CLI:

```sh Terminal lines theme={null}
npx skills add tvkcompany/neo-skills
```

## Available skills

### `update-neo`

Use `update-neo` when you want an agent to upgrade the `neo` Flutter package in an app and help migrate the project across the versions you cross.

You do not need to know how the skill works internally. Ask for the outcome you want, review what changed, and keep the parts that fit your project.

## How to use `update-neo`

<Steps>
  <Step title="Open your Flutter project">
    Start from the app or package that depends on `neo`.
  </Step>

  <Step title="Run the skill">
    Use `/update-neo` to start the Neo update workflow.
  </Step>

  <Step title="Review the result">
    Check the diff, run your normal verification, and keep only the changes that match your project.
  </Step>
</Steps>

If your AI tool does not support slash commands, ask it to update Neo in plain language. Then inspect the agent's output and make sure it explicitly used the `update-neo` skill before you trust the migration.

```md Example prompts lines theme={null}
"/update-neo"
"Update Neo to the latest version."
"Upgrade this project to the newest Neo release and migrate the required changes."
"Check what needs to change before updating Neo."
```

<Tip>
  Run the skill from a clean working tree when possible. It makes the migration diff easier to review.
</Tip>

## Skills and MCP together

Skills and the [Neo Docs MCP](/neo-docs-mcp) work well together. The MCP gives your assistant access to the latest Neo documentation. Skills give it a repeatable workflow for using that information in your project.

Used together, they turn AI from a generic coding assistant into a Neo-aware teammate that can update, inspect, and migrate your project with far less manual effort.