Our AI skills give coding agents such as Claude and Codex the expertise to build and maintain your AG Studio, AG Grid and AG Charts applications from our official guidance.
We are actively developing and releasing new versions of our skills. Feedback is welcome - open an issue on GitHub.
Setup Copy Link
One skills package covers all of our products: AG Studio, AG Grid and AG Charts.
Installation Copy Link
A skill is a folder of files that you install in your project repository or your home directory. Use the skills CLI to copy the files from the ag-grid/skills repository to your machine:
npx skills add ag-grid/skills Updating Copy Link
We refine the skills and extend them to cover new Studio, Grid and Charts releases, so update at any time to pick up the latest guidance:
npx skills update ag-grid/skills Skills Copy Link
We currently provide two skills, ag-dev and ag-update. If there's something else you'd like to see, open an issue to suggest a skill.
ag-dev Copy Link
ag-dev is a general development assistant that helps agents write correct code on the first attempt.
The ag-dev skill includes a list of rules for the agent to follow to avoid common LLM pitfalls, debugging guidance, and instructions for accessing version-matched documentation to ensure that your agent uses the APIs for the installed version of the library.
Once the ag-dev skill is installed, coding harnesses like Claude Code and Codex will often automatically use it when planning or writing code that interacts with our libraries. Simply installing the skill will improve the results you get during development. However, because automatic triggering is best-effort, for the most consistent results we recommend explicitly telling your agent to use the ag-dev skill, especially when working on complicated tasks:
Help me configure a custom data engine that runs queries against my REST API (use the ag-dev skill) ag-update Copy Link
Upgrading across major versions normally means reading every release's breaking changes and working out which ones touch your code. The ag-update skill hands that work to your coding agent: it reads the AG Studio migration documentation, checks it against your repository, and produces a Markdown file listing the changes needed to move to a new version.
To let the skill detect everything for you, invoke it from your coding agent:
Use the ag-update skill to upgrade my-appYou can also tell it exactly what to update, down to individual projects and target versions.
Use the ag-update skill to update all projects in this monorepo
except apps/demo-app to AG Studio v3 Example run Copy Link
A typical run, updating a single project to AG Studio v3, looks like this:
> Use the ag-update skill to update the reporting/dashboard project to AG Studio v3
Determining scope → AG_UPDATE_SCOPE.md
- reporting/dashboard
- ag-studio-react@2.1.0 -> 3.0.0
- ag-grid-community@36.1.0 -> 36.2.0
Continue with these projects and target versions? yes
Determining changes → AG_UPDATE_CHANGES.md
There are 3 behaviour changes, in each case I need to know whether
to accept the new behaviour or restore the old behaviour.
> accept the first two, mitigate the third
AG_UPDATE_CHANGES.md is ready to apply.AG_UPDATE_CHANGES.md contains an entry for each change, grouped by product and version transition, labelled BREAKING or BEHAVIOUR, and paired with how to mitigate it:
## Studio v2.x -> v3.x
### BEHAVIOUR: Charts limit how many legend series they draw
Change: A chart that splits its series by a legend field now ranks
legend members by the first plotted measure and drops the rest,
where a chart whose legend produced more series than the chart's
own limit previously failed to render at all.
Mitigation: Set `format.seriesLimit.max` to choose your own budget,
or `format.seriesLimit.enabled: false` to plot every member. Applying the plan Copy Link
The skill plans the upgrade, it does not perform it. It finishes once AG_UPDATE_CHANGES.md is written, so review the generated files first.
For the best results, start a new agent session, or clear the context of the current one, then ask the agent to work from the plan:
Plan and apply the update described in AG_UPDATE_CHANGES.mdThe agent bumps the versions in package.json, reinstalls dependencies, applies each change in the plan, and validates the result against your typecheck and build.