Getting Started
Agent Onboarding
A single, agent-fetchable prompt that installs, tags, audits, verifies, and sets up a coding agent for Cinder end to end - the same pattern Neon’s own onboarding uses.
Need the shortest path?
Use Quick Start when you want the smallest working route → scan → graph → run flow first.
Something feels off?
Inspect scan output, graph state, active route/context, and dispatch in a practical order.
Need the full surface?
Browse all runtime methods, hooks, extension points, and lifecycle APIs.
Paste this to your own coding agent instead of doing the steps below by hand:
Install usecinder in this project (npm install usecinder), then fetch https://usecinder.dev/get-started/prompt.md and follow it completely.If you're a coding agent (Claude Code, Cursor, or similar) setting up Cinder in someone's repo, there's a single, stable, fetchable file written to be run end to end - not just read:
https://usecinder.dev/get-started/prompt.mdFetch that URL and run every step it describes yourself. It does not ask you to print instructions for a human to follow by hand - it is written in the imperative, the same way Neon's own get-started/prompt.md onboarding flow works.
What it does, in order
- Detects the package manager from the lockfile already in the repo and installs
usecinder. - Finds the app's real entry point and calls
Cinder.init()once, withai.enabled: falseso the local-first path (tier 1 and tier 2) works before anything touches a network. - Tags a handful of the app's real, high-value routes/actions/fields/outputs - not an exhaustive sweep.
- Runs
cinder integrateagainst the real running dev server and applies the real, app-specific findings from its report. - Runs a real command through
Cinder.run()and confirms it actually dispatched correctly, not just that it returned without an error. - Runs
cinder install-skillso a future agent session in the same repo picks up the tagging checklist automatically, without needing this file re-fetched and re-run from scratch.
Why this exists
Self-hosted integration docs assume a human reads and executes them one step at a time. An agent-fetchable, imperative prompt collapses that into one fetch - the agent installs the real package, wires up the real entry point, tags real elements, runs the real audit tool, and verifies a real command actually works, all before reporting back.
Related pages
- Installation (the human-readable version of the same first steps)
- CLI Overview
- Tagging a Page
Continue reading