Getting Started with Neexo AI

Onboarding for Neexo teams: pick a stack, install Copilot or Cursor plugins, share llms.txt with any assistant, and work cost-consciously.

CopilotCursorKilo
AuthorNeexoCore
Updated
onboardingcopilotcursorneexo

Prerequisites

  • VS Code with GitHub Copilot or Cursor (Kilo uses the same hub via AGENTS.md / APIs)
  • Access to the NeexoCore GitHub organization
  • Access to your project repositories

Step 1: Pick your stack

Open the start wizard and choose a playbook that matches your project (e.g. multi-tenant SaaS, Unity, Figma HMI). It recommends plugins and catalog resources for that stack.

Browse all playbooks: awesome.neexo.dk/playbooks

Step 2: Install for your IDE

GitHub Copilot

Register the marketplace once:

copilot plugin marketplace add NeexoCore/awesome-neexo

Install the baseline trio:

copilot plugin install neexo-guardrails@awesome-neexo
copilot plugin install neexo-developer@awesome-neexo
copilot plugin install neexo-planning@awesome-neexo

Add stack-specific plugins as needed (neexo-unity, neexo-figma, neexo-blender).

Cursor or Kilo

npx awesome-neexo init --cursor --stack saas-multi-tenant
npx awesome-neexo doctor

Or install from the Cursor marketplace listed in .cursor-plugin/marketplace.json.

See the compatibility matrix for per-category IDE support.

Step 3: Give your agent one link

For teammates who are not IDE power users, share:

https://awesome.neexo.dk/llms.txt

Any assistant reads the discovery file and fetches guardrails, the right playbook, and only the resources it needs. Human copy-paste page: awesome.neexo.dk/for-ai.

Daily workflow

Autocomplete for routine code — still the cheapest and fastest path.

Chat or agent mode for explanation, planning, review, or multi-file changes. Give a goal, file scope, constraints, and the smallest validation command you expect.

Use neexo-planning skills for brainstorming, session diaries, and handoffs between agents or teammates.

Planning workflow: neexo-brainstormscoped-plan or plan-feature-change → implementation.

Install any bundled skill: open skills/neexo-brainstorm#install, copy the agent prompt, or download the ZIP.

Prompt pattern

Fix the validation bug in <file or folder>.
Only inspect related files and tests.
Do not change UI.
Run or suggest the smallest relevant validation command.

More templates: awesome.neexo.dk/prompts

Model and cost awareness

  • Prefer narrow scope and smaller models for local edits.
  • Escalate to larger models only for architecture or cross-cutting refactors.
  • Guardrails in neexo-guardrails reinforce budget-conscious prompting — keep them enabled.

Next steps

Raw content

Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md

## Prerequisites

- VS Code with GitHub Copilot **or** Cursor (Kilo uses the same hub via `AGENTS.md` / APIs)
- Access to the NeexoCore GitHub organization
- Access to your project repositories

## Step 1: Pick your stack

Open the [start wizard](https://awesome.neexo.dk/start) and choose a playbook that matches your project (e.g. multi-tenant SaaS, Unity, Figma HMI). It recommends plugins and catalog resources for that stack.

Browse all playbooks: [awesome.neexo.dk/playbooks](https://awesome.neexo.dk/playbooks)

## Step 2: Install for your IDE

### GitHub Copilot

Register the marketplace once:

```bash
copilot plugin marketplace add NeexoCore/awesome-neexo
```

Install the baseline trio:

```bash
copilot plugin install neexo-guardrails@awesome-neexo
copilot plugin install neexo-developer@awesome-neexo
copilot plugin install neexo-planning@awesome-neexo
```

Add stack-specific plugins as needed (`neexo-unity`, `neexo-figma`, `neexo-blender`).

### Cursor or Kilo

```bash
npx awesome-neexo init --cursor --stack saas-multi-tenant
npx awesome-neexo doctor
```

Or install from the [Cursor marketplace](https://awesome.neexo.dk/setup) listed in `.cursor-plugin/marketplace.json`.

See the [compatibility matrix](https://awesome.neexo.dk/compatibility) for per-category IDE support.

## Step 3: Give your agent one link

For teammates who are not IDE power users, share:

```text
https://awesome.neexo.dk/llms.txt
```

Any assistant reads the discovery file and fetches guardrails, the right playbook, and only the resources it needs. Human copy-paste page: [awesome.neexo.dk/for-ai](https://awesome.neexo.dk/for-ai).

## Daily workflow

**Autocomplete** for routine code — still the cheapest and fastest path.

**Chat or agent mode** for explanation, planning, review, or multi-file changes. Give a goal, file scope, constraints, and the smallest validation command you expect.

Use **neexo-planning** skills for brainstorming, session diaries, and handoffs between agents or teammates.

**Planning workflow:** `neexo-brainstorm` → `scoped-plan` or `plan-feature-change` → implementation.

Install any bundled skill: open [skills/neexo-brainstorm#install](https://awesome.neexo.dk/skills/neexo-brainstorm#install), copy the agent prompt, or download the ZIP.

## Prompt pattern

```text
Fix the validation bug in <file or folder>.
Only inspect related files and tests.
Do not change UI.
Run or suggest the smallest relevant validation command.
```

More templates: [awesome.neexo.dk/prompts](https://awesome.neexo.dk/prompts)

## Model and cost awareness

- Prefer narrow scope and smaller models for local edits.
- Escalate to larger models only for architecture or cross-cutting refactors.
- Guardrails in `neexo-guardrails` reinforce budget-conscious prompting — keep them enabled.

## Next steps

- [Setup guide](https://awesome.neexo.dk/setup) — marketplace and VS Code settings
- [Cookbook](https://awesome.neexo.dk/cookbook) — copy-paste workflows
- [Contributing patterns](../../docs/contributing-patterns.md) — if you want to add hub content

Next steps

Matched by shared tags and category. Browse all cookbook