ag-grid

Use BEFORE writing or changing any code that touches AG Grid, AG Charts or AG Studio - including adding or configuring columns, themes, styling, cell rendering, data or any grid/chart feature, and when planning such work. Grounds the code in the APIs that…

Update AG Grid, AG Charts and AG Studio dependencies to a newer version

Test skill that asks nothing and just states a fact. Use when asked to run the state-a-fact skill.

Apply the project's API rate-limit configuration. Use when asked to apply or update the API rate limit.

Test skill that prints progress lines and then asks one question. Use when asked to run the narrate-then-ask skill.

Test skill that asks three questions in order. Use when asked to run the ask-three-questions skill.

Test skill. Asks the user one question then confirms. Use when asked to run the single-question skill.

Test skill that asks only for a name. Use when asked to run the ask-name-only skill.

AG Charts runtime hot paths: which files run per datum, per frame or per interaction, the invariants each tier must hold, and how to evidence a performance claim. Use when reviewing a change that touches series, scene, data-model, scale, interaction or DOM…

Find the actual runtime default value of any AG Charts configuration option, and keep JSDoc `Default:` markers accurate. Use when documenting a default, verifying a change has not altered one, writing tests against default behaviour, or auditing whether a…

Migrate a series type from ratio-snapshot animation tests and manual -test docs pages to frame-trajectory coverage. Use when converting a series (area, pie, scatter, histogram, range-bar, candlestick, radar, …) to the trajectory harness.

Estimate complexity, effort, and risks for JIRA tickets, features, or projects. Generates structured reports with time estimates, dependencies, risk analysis, and known unknowns. Use when user asks to "estimate", "size", or "analyze complexity" of work items.

Technology stack and architectural constraints. Use when choosing technologies, adding dependencies, or understanding zero-dependency requirements.

Technology choices and architectural constraints for AG Grid. Use when choosing technologies, adding dependencies, or understanding zero-dependency requirements.

Full testing reference for AG Grid — behavioural vs package test layers, regression-test coverage, the complete runner flag reference (behave.sh / benches.sh / docs-e2e.sh), Vitest patterns, async waiting patterns (waitFor vs asyncSetTimeout), and…

Write or update Playwright example.spec.ts tests for AG Grid documentation examples, then run them with docs-e2e.sh to verify. Use when asked to write, add, extend, or fix e2e/Playwright tests for a docs page or a specific example, or when a docs example…