Set up with an AI assistant

GridCue ships an agent skill: instructions a coding assistant loads when you ask it to add GridCue. It walks the assistant through setup in order and checks each step. It also keeps it to the rules that matter, such as keeping your Jev key off the browser. It reads these docs for every API detail, so it stays current.

Install

For Claude Code, Cursor, Codex, GitHub Copilot, and other assistants the skills CLI supports:

npx skills add JH3lou/GridCue --skill gridcue

Or as a Claude Code plugin:

claude plugin marketplace add JH3lou/GridCue
claude plugin install gridcue@gridcue

Then ask

In your app's folder, try:

Add GridCue to this app's accounts table.

The assistant works through these steps, and checks each one before the next:

1. Reads your stack: Vite or Next.js, and TanStack Table v9 or plain rows.
2. Installs gridcue, wires the keyless Mock Provider, and confirms a request previews.
3. Picks the command bar that fits your app: the plain-CSS GridCueBar, or the shadcn command bar.
4. Describes your domain from your real columns, and tests three requests in your own words.
5. Turns on Jev behind your own endpoint, if you want it, and checks no key reaches the browser.
6. Offers to write evals on your schema.

What it won't do

• Put a provider key in client code, or in a VITE_ or NEXT_PUBLIC_ variable.
• Send your rows to a model, or skip marking sensitive columns restricted.
• Bypass preview, apply, or undo, or have a model write grid state directly.
• Wire GridCue to change data: it only changes the view.

It stops and asks you before adding a server your app doesn't have, and when a column might be sensitive.

The skill's source is in skills/gridcue.