Use agent skills
Install five skills that teach Claude Code, Cursor, Codex, and other coding agents to tune, extend, wire, and upgrade gridcn grids.
gridcn ships five agent skills for tasks that cross many docs pages. Each skill gives the agent an ordered procedure, the failures that stay silent, and a check that tells it to stop.
Before you start, install a coding agent that supports skills, such as Claude Code, Cursor, or Codex.
- Install all five skills in your project:
pnpm dlx skills add DammersCode/gridcn
- Check that the five
gridcn-*folders are in your agent's skills folder, such as.claude/skills/. - Ask the agent by skill name, for example:
Use gridcn-performance to audit the grid on the orders page. - Read the It is working if line of that skill below. Stop when it holds.
Skills
| Skill | What it does | Reach for it when | Install |
|---|---|---|---|
gridcn-performance | Audits the grid integration against the memoization and virtualization traps. | The grid is slow to scroll, type, or edit, or a code review touches grid props. | |
gridcn-custom-cell-type | Builds a cell type that pastes, sorts, and edits like the built-in types. | You build a cell type, or a custom type renders as plain text. | |
gridcn-data-source | Picks plain data, pagination, or scroll mode, and moves sort and filter to the server. | You connect the grid to a backend or to more rows than one request can carry. | |
gridcn-addons | Installs add-ons and wires each output to the correct place. | You add one or more add-ons, or an add-on has no effect. | |
gridcn-upgrade | Merges a newer gridcn release into your installed source and keeps your edits. | You pull a newer gridcn release into source that you already installed. |
The copy button in the Install column copies the command for that one skill.
Each skill is also served as raw markdown at https://gridcn.vercel.app/skills/<name>/SKILL.md. The gridcn-version metadata field of a skill names the last gridcn release. A skill also teaches the APIs that CHANGELOG.md lists for installs from main.
gridcn-performance
The skill works through a checklist, cheapest check first:
- a bounded grid height, so virtualization can start
- stable
columnsanddatareferences - stable members of each plugin in
plugins - no formatter allocation inside a custom
Cell updateCellsfor high-rate feeds
Most identity traps show only as a development console warning. The skill gives the agent the exact warning text to search for.
It is working if the development console shows no warning while you scroll and edit. Every grid message starts with [data-grid ([data-grid] or [data-grid-<add-on>]). The React DevTools Profiler then shows renders only for the rows that enter the viewport.
gridcn-custom-cell-type
The skill builds a cell type in order. First the value pipeline: toText, fromText, clearValue, isEmpty, and compare. Then Cell and Editor. Then the registration and the GridCellTypes type augmentation. It also covers failures that are quiet:
- A
cellTypesentry merges over the built-in types. An entry set tonullremoves that type. - A
typekey that matches no entry renders the column as plain text, and only a development warning reports it. - Call
rejectText()infromTextfor text that does not parse. The cell keeps its value, and the grid reports the text, as the built-in types do. AfromTextthat throws another error rejects that cell too, and the paste continues. ReturnclearValue()only to empty the cell on purpose. - A portaled editor without
data-grid-cell-editorcommits on blur when the focus moves into its portaled content.
It is working if fromText(toText(value)) returns the value, pasted garbage leaves the cell unchanged, Enter commits and moves down, and Escape keeps the original value.
gridcn-data-source
The skill picks one base for the rows: plain data, pagination, or scroll mode. If values change live, it adds streaming on top. If the server sends rows in pages or scroll-mode blocks, a client sort, filter, or search sees only the loaded rows. So the skill moves them to the server. The skill also handles stale page answers and the combinations that the add-ons do not support, such as scroll mode with pagination.
It is working if every sort, filter, and search path covers the full result, or the page states that it covers only the loaded rows.
gridcn-addons
The skill installs each add-on and puts each output where it belongs:
- each add-on hook that returns a
pluginputs it into onepluginsarray on the provider keymapgoes on the provider- toolbar pieces go inside
DataGridToolbar
It also checks the rules for combined add-ons. The app needs one NuqsAdapter, and each grid needs one useDataGridPresence() call. On a scroll-mode grid, URL state needs server sort and server filter.
It is working if each add-on shows its documented behavior and the console shows no development warning.
gridcn-upgrade
gridcn is source that you own. In a Git project, the skill asks which branch to use. It pins a commit, reads the changelog and the 2.0 breaking changes for breaking entries, and runs --dry-run. It checks git log for your edits. It overwrites the files that you did not edit and merges your edits into the others. Then it checks barrel imports, aliases, and new dependencies.
It is working if your type check and build pass, the skill applied every breaking entry, and the smoke test from Verify the install passes.
In a Git project, commit or stash your changes before you run gridcn-upgrade. Without Git, back
up your edited files first. The skill asks before it overwrites, but a reinstall that overwrites an
edited file discards the edits.