ag-dev

Grounds AG Grid, AG Charts, and AG Studio code in version-accurate documentation and APIs.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/serhii-baksheiev/ag-grid-interview-lab --skill ag-dev-serhii-baksheiev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ag-dev
Source: https://github.com/serhii-baksheiev/ag-grid-interview-lab/tree/main/.agents/skills/ag-dev
Command: npx skills add https://github.com/serhii-baksheiev/ag-grid-interview-lab --skill ag-dev-serhii-baksheiev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding assistants often write AG Grid, AG Charts, or AG Studio code using deprecated, removed, or invented APIs because training data lags behind current library versions. This Skill forces documentation-grounded development so generated code matches the exact product version installed in the project. ## Core Features & Use Cases - Version-aware documentation lookup: Detects the AG product, framework (React, Angular, Vue, or JavaScript), and installed version, then builds correct archived documentation URLs from curated slug indexes. - Product-specific recommendations: Ships curated guidance for grid, charts, and studio covering known LLM failure modes, major version transitions (e.g. v33 Theming API, v13 module registration), and common mistakes like unregistered modules or missing container heights. - Built-in feature preference: Directs the agent to use purpose-built grid features (sorting, filtering, aggregation, export) instead of hand-rolled primitives like custom valueGetters or cell renderers. - Use Case: When asked to add server-side pagination to an AG Grid 36 React app, the agent consults the grid documentation index and recommendations first, then writes code using the Server-Side Row Model APIs that actually exist in v36 rather than recalled v28 patterns. ## Quick Start Use the ag-dev skill before writing any AG Grid, AG Charts, or AG Studio code to verify the correct APIs for the installed version.

Frequently Asked Questions about ag-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write AG Grid code that matches my installed version?

Determine the version from package.json or node_modules, then consult the documentation index to build an archived docs URL for that exact version. This avoids using deprecated APIs from older training data or APIs that do not yet exist in your version.

Why is my AG Grid feature not working after configuration?

A feature that does nothing is usually an unregistered module, not a wrong API. Check the browser console for error #200 naming the required module, verify ag-grid-enterprise is in package.json, register the module, and re-test before changing approaches.

Does AG Charts use AgChart.create or AgCharts.create?

The correct API is AgCharts.create(options) from ag-charts-community; AgChart and AgEnterpriseCharts are outdated names. Financial charts use AgCharts.createFinancialChart and gauges use AgCharts.createGauge, not AgCharts.create.

When should I use a custom cell renderer versus a built-in AG Grid feature?

Prefer the built-in feature whenever one exists for sorting, filtering, aggregation, or export, since the grid's UI and state management understand it natively. Custom renderers and valueGetters are opaque application code that must re-implement that behavior manually.

Can AG Studio be configured with grid-style rowData and columnDefs?

No. AG Studio configures data through the data property as an AgDataSourcesDefinition with sources of plain objects, and it has no top-level column definitions. The API is created imperatively via createStudio(rootDiv, properties) from the ag-studio package.