> For the complete documentation index, see [llms.txt](https://vibemx.gitbook.io/neuronai-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vibemx.gitbook.io/neuronai-studio/getting-started/ai-assisted-development.md).

# AI-Assisted Development

When working with AI coding assistants (Cursor, Claude Code, OpenCode, and similar tools), point them at the NeuronAI Studio **Agent Skill** so suggestions match Studio APIs, config, and workflows — with fewer hallucinations.

NeuronAI Studio follows the [Agent Skills](https://agentskills.io/) convention (same idea as [Neuron AI agentic development](https://docs.neuron-ai.dev/overview/agentic-development)).

## Agent Skill location

After Composer install, the skill lives at:

```
vendor/digitalelvis/neuronai-studio/skills/
└── neuronai-studio/
    ├── SKILL.md
    └── references/
        ├── setup.md
        ├── agents.md
        ├── workflows.md
        ├── tools.md
        ├── knowledge.md
        ├── mcp.md
        ├── export.md
        └── extending.md
```

Canonical product docs (linked from the skill) are in:

```
vendor/digitalelvis/neuronai-studio/docs/
```

The skill stays small on purpose: the assistant should open the matching `references/*.md` file, then read the linked guide under `docs/` when more detail is required.

## How to install

### Claude Code

From your Laravel application root:

```bash
npx skills add ./vendor/digitalelvis/neuronai-studio/skills
```

Skills are typically installed as a symlink, so they stay current when you update the package with Composer.

### Cursor

In **Cursor Settings → Features → Docs**, add the skill directory:

```
vendor/digitalelvis/neuronai-studio/skills
```

You can also add a project rule that tells the agent to use `vendor/digitalelvis/neuronai-studio/skills/neuronai-studio/` (and to read `docs/` links when context is insufficient).

### Other AI tools

Any assistant that supports the Agent Skills specification can use this skill. Check your tool’s docs for adding a custom skills directory.

## Neuron AI skills (runtime PHP)

For **pure Neuron AI** PHP (agents, tools, workflows outside Studio UI), also install or reference:

```
vendor/neuron-core/neuron-ai/skills/
```

See [Neuron AI — Agentic Development](https://docs.neuron-ai.dev/overview/agentic-development).

| Concern                                                    | Skills                                                    |
| ---------------------------------------------------------- | --------------------------------------------------------- |
| Studio install, canvas, playground, DB definitions, export | `digitalelvis/neuronai-studio` → `skills/neuronai-studio` |
| Neuron `Agent` / `Workflow` / Tool PHP APIs                | `neuron-core/neuron-ai` → `skills/*`                      |

## Recommended usage

1. Ask the assistant to follow the **neuronai-studio** skill for Studio tasks.
2. Expect it to open `references/<domain>.md` for the domain (agents, workflows, etc.).
3. If answers are thin or uncertain, have it **read** the markdown files under `vendor/digitalelvis/neuronai-studio/docs/` linked from that reference.

## Related

* [Installation](/neuronai-studio/getting-started/installation.md)
* [Documentation index](https://github.com/digitalelvis/neuronai-studio/tree/main/docs/SUMMARY.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vibemx.gitbook.io/neuronai-studio/getting-started/ai-assisted-development.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.