Agent Skills

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 when the work is done.

pnpm dlx skills add DammersCode/gridcn

Skills

The copy button in the Install column copies the command for that one skill. The command above the table installs all five.

Each skill is also served as raw markdown at https://gridcn.vercel.app/skills/<name>/SKILL.md. The gridcn-version field in its frontmatter names the gridcn release the skill targets.

gridcn-performance

What it does. The skill audits a grid integration against a checklist. The cheapest checks come first:

• bounded grid height, so virtualization can start
• stable columns and data references
• stable class-name functions and click handlers
• stable plugin objects in plugins
• no formatter allocation inside a custom Cell
• updateCells for high-rate feeds

Most of these traps show only as a warning in the development console. The skill gives the agent the exact warning text to search for.

When to reach for it. Scrolling stutters, typing lags, or an edit is slow. Also use it when you review code that passes props or callbacks into the grid.

It is working if the development console shows no [data-grid] warning while you scroll and edit, and the React DevTools Profiler shows only the rows that enter the viewport rendering.

gridcn-custom-cell-type

What it does. 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 the failures that show no error:

• A cellTypes entry set to null removes that type. The prop merges over the built-ins and never replaces them wholesale.
• An unknown type key renders the column as plain text.
• A fromText that throws stops the paste.
• A portaled editor without data-grid-cell-editor closes on the first click.

When to reach for it. You add a currency, rating, tag, or color column. Also use it when a custom type renders as plain text, does not open an editor, or breaks on paste, fill, or sort.

It is working if fromText(toText(value)) returns the value, pasted garbage clears the cell, Enter commits and moves down, and Escape keeps the original value.

gridcn-data-source

What it does. The skill selects one base for the rows: plain data, pagination, or lazy loading. It adds streaming on top when values change live. For a lazy or paged grid, it moves sort, filter, and search to the server. Otherwise these gestures see only the loaded rows. The skill also handles stale page responses, lazy.reset() on a sort change, and the combinations that the add-ons do not support.

When to reach for it. You connect the grid to an API, the dataset is too large for one request, or sort and filter must cover rows that are not loaded.

It is working if every sort, filter, and search path covers the full dataset, or the page states that it covers only the loaded rows.

gridcn-addons

What it does. The skill installs each add-on and puts each output where it belongs:

• the add-on's plugin into the plugins array on the provider, and keymap on the provider
• toolbar pieces inside DataGridToolbar

It combines every add-on's plugin into one plugins array. It also checks the rules that apply when you combine add-ons: one NuqsAdapter, one useDataGridPresence() call, and no URL state on a lazy grid.

When to reach for it. You add an add-on, you combine several add-ons in one grid, or an installed add-on renders nothing.

It is working if each add-on shows its documented behavior and the console shows no development warning.

gridcn-upgrade

What it does. gridcn is source that you own, not an npm dependency. An update re-runs the install and merges the upstream files with your copy. In a Git project, the skill first asks you whether to upgrade on the current branch or on a new branch. Then it reads the changelog for breaking entries. It sorts every installed file with --dry-run, overwrites only the files that you did not edit, and merges your edits into the others. Then it checks the aliases and the imports.

When to reach for it. You update to a newer release, you pull one upstream fix, or you changed installed files and want to keep the changes.

It is working if your type check and build pass, every breaking entry has its replacement, and the smoke test from Installation passes.

Related

• Installation
• Performance
• Custom cell types
• Lazy loading
• Add-ons
• Project status