For agents

Install Lunnoa Cursor and Claude skills, then discover and deploy with @lunnoa/client.

Coding agents (Cursor, Claude Code) should start from the packaged skills, not the whole docs tree. Human guides below remain the canonical detail.

Install the skills

@lunnoa/client publishes two skills under skills/:

Skill	Job
`lunnoa-solution-design`	Interview the human, map intent to Lunnoa primitives, write a build brief
`lunnoa-client`	Implement: auth, CLI discovery, codegen, `define*` / runs / CLI deploy, React hooks

After npm install @lunnoa/client, copy or enable them from:

skills-paths.txt

node_modules/@lunnoa/client/skills/lunnoa-solution-design/node_modules/@lunnoa/client/skills/lunnoa-client/

into your app’s .cursor/skills/ (Cursor) or Claude Code skills path. In the SDK repo, the same files live under skills/ (source of truth) and are mirrored into .cursor/skills/ for local work.

Prefer solution-design first when requirements are unclear, then lunnoa-client.

Partner paste block

Drop this into a new chat so the agent has credentials and the right skill order:

partner-prompt.txt

Use @lunnoa/client skills: lunnoa-solution-design then lunnoa-client.LUNNOA_URL=… LUNNOA_API_KEY=lna_… (server only). Project ID=…Start by interviewing me, then: npx @lunnoa/client tools list --json --for-agentand tools get <actionId> --json. Do not invent catalogue action ids.

Never put an lna_ key in browser code or client-bundled env vars. See Authentication.

Agent playbook (short)

Clarify with lunnoa-solution-design (trigger, actor, data, HITL, auth pattern).
Auth: Pattern A (createServerClient + server lna_) or Pattern B (createBrowserClient + JWT).
Discover: npx @lunnoa/client tools list --json --for-agent, then tools get <actionId> --json. Also apps, connections, agents, workflows, entity-types, projects, features. SDK equivalent: workflowApps.list(). Do not invent catalogue action ids. See Discovery and CLI.
Codegen for typed UIs: npx @lunnoa/client codegen …. See Codegen.
Run vs deploy: Ad-hoc: actions.run, runs.start, workflows.execute. Durable: npx @lunnoa/client workflows|agents|entity-types deploy. Entity types are workspace-scoped (no --project-id). See Run actions, Start runs, CLI.
Entity attributes: Unknown keys are rejected unless the type allows them; use extensions for flexible bags. See Entities.
Boundary: Client defineAction is not toolkit createAction. Use @lunnoa/toolkit only for in-platform integration apps.

Related guides

Guide	When
Authentication	Pattern A vs B, CORS, keys
Agents	End-to-end define, deploy, and chat
Define locally	`defineWorkflow` / `defineAgent` / `defineEntityType` / `defineAction`
Entities	Strict attributes, `extensions`, type deploy
React hooks	Headless progress, chat, inbox, entities
Agent chat	SSE UIMessage streaming
CLI	`tools list` / `tools get`, then deploy
TypeScript client SDK	Full human index