adaptable-dev

Summary

The day-to-day Skill for a project that already has AdapTable
Designs from the docs for the installed version, then checks what it wrote

The adaptable-dev AI Skill helps you to add and change AdapTable features in your project.

The AI Skill covers and can help you with all elements in AdapTable including:

Adaptable Options
Initial State
AdapTable Modules (e.g. Layouts, Format Columns, Alerts etc.)
AdapTableQL Expressions
AdapTable API calls
Custom UI components (e.g. toolbars, menus, tool panels, Settings panels etc.)

Caution

Do not use this to add AdapTable for first time (use adaptable-setup) or for pure AG Grid work (use ag-dev)
Nor for a Grid that is misbehaving (use adaptable-debug) or to upgrade versions (use adaptable-upgrade)

adaptable-devAI Skill

Add a Calculated Column called notionalUsd — notional times fxRate, shown in USD with no decimals — and put it after notional in the Trading Layout

Add an Alert that warns when pnl drops below zero

Add a Calculated Column that doubles the rating, and put it first in the current Layout

Add a custom toolbar to the Dashboard with a button that clears all Column Filters

How it Works

The agent finds the installed version, then designs from the docs for that version.

The workflow is as follows:

It confirms the feature exists, reads how it behaves, reads the exact shape, and copies one demo
It decides where the change belongs
Before it writes, it applies the known mistakes for that feature: Expression kinds, State shapes, and the traps for your framework
After it writes, it checks the Expression, the State and setup, and fixes what checks name (up to 3 rounds)
It reports what changed, which docs page each shape came from, and the checks that ran

Deep Dive

Where AdapTable functionality belongs, and the Rules the Skill uses

One of the key things the Skill does is teach where each piece of functionality in AdapTable belongs:

The thing is…	It belongs in…
a persistable, user-facing object (Layout, Alert, Filter, Calculated Column, Report etc.)	`initialState`, with a unique `Name` and other properties as needed
a design-time callback, permission, Action Column or custom function	Adaptable Options Functions do not serialise into State
a runtime change	The Adaptable API (`adaptableApi.<module>Api`) Called after the ready event
column visibility, order, width, pinning, sorting, grouping, aggregation	The Layout in `initialState` Not ColDef `hide`, `pinned`, `width`, `sort`, `rowGroup` or `aggFunc`
conditional styling, formats, sparklines, badges	Format or Styled Columns in `initialState` Not `cellStyle`, `valueFormatter`, `valueGetter` or a renderer
column typing	The ColDef (`cellDataType`)

The Skill has a set of important rules which it always works by:

Declarative first — if a user can see, toggle, edit or save it, it's Initial State; code is what State cannot express. Action Columns are the exception: their controls are functions, so they live in Adaptable Options
Saved State merges over initialState — editing initialState does not reset what users already saved; runtime changes go through the State API, and a deliberate replacement uses Revision, not a changed state key
Expressions are AdapTableQL, checked per Module — the Module decides which kinds and functions are legal; functions are looked up with aql functions, not recalled
Column references are ids from the project, taken from the columnDefs source — never invented header names


What the agent asks	The agent asks you questions and stops in the chat and waits for an answer It does not ask on every step It asks only when a choice is hard to undo, and then carries on It has no questions of its own It will not change the state key or saved State unless you confirm
What it writes	Your source only: the Initial State, Adaptable Options or component code the task needs
What it runs	The Agent will run various tasks as part of its operation You do not run these - the agent does: `detect`, `docs list`, `docs search`, `docs get`, `docs demo`, `aql functions`, `check expression`, `check state` and `check setup` With the app running, it reads the page: `getState()` and `getLogs()` If it cannot open the page, it asks you to paste those calls into the browser console and paste the results back
When it is finished	The code compiles `check state`, `check expression` and `check setup` are clean for everything it produced Each new piece of State, each API call and each Adaptable Option traces back to a docs page or demo for the installed version

Deep Dive

Taking a look inside the Skill

After you install the Skill, adaptable-dev looks like this:

adaptable-dev/
├── SKILL.md                  # description + procedure
├── VERSION.md                # the version checked against /.well-known/skills/VERSION
└── references/
    ├── recommendations.md    # the mistakes agents keep making, per feature area
    └── _shared/              # the same in every Skill
        ├── grounding.md
        ├── docs-protocol.md
        ├── validation-loop.md
        ├── conversation.md
        ├── guards.md
        ├── capabilities.md
        └── agents-snippet.md

adaptable-dev

Summary

Caution

How it Works

Deep Dive

Where AdapTable functionality belongs, and the Rules the Skill uses

Deep Dive

Taking a look inside the Skill

Examples

Create a Calculated Column

Skill

Create a Calculated Column

Create an Alert

Skill

Create an Alert

Edit an Alert

Skill

Edit the pnl Alert to fire when status changes

Create a Format Column

Skill

Create a Conditional Style showing negative values as red

Build a Scheduled Export

Skill

Schedule an export to run every morning

Answer a Code Question

Skill

A code-related question, with nothing changed

Check the Initial State

Skill

Check the Initial State

Audit the Setup

Skill

Audit our AdapTable setup

Column Defs vs Layout

Skill

Check if any Column definitions are fighting a Layout

AdapTable Resources