JT
James Tandy
Back to all blogs
ServiceNow Development4 min read

Getting Started with ServiceNow AIUX and Agentic Coding

Learn how to scaffold a new ServiceNow AIUX project, install and find the AIUX agent skills and test that it all works!

JT
James TandyServiceNow Developer & Enterprise Architect

As of today’s date, the AI Experience Framework (AIUX) is just a few months old. As a developer, you can install the EmployeeSlate plugins to get access to the table structure on your instance. Here is a community article to get you started. I’m not going to go over the configuration steps for EmployeeState as there are several paths you can take depending on whether you use MoveWorks or Now Assist. I’m going to assume that you’ve already got that done.

At some point in the future, let’s say six months to a year, many ServiceNow developers, especially those in the consulting world, are going to face the task of learning the new framework and being able to make simple changes and/or adding custom pages. In this article, I’ll show you how to get a quick agentic coding development workflow going with the ServiceNow SDK + your agentic coding harness of choice. I use Google Antigravity, but you can use any other coding harness that you like.

Installing the ServiceNow SDK

The first thing we need to do is install the ServiceNow SDK. The installation docs can be found here. Once that’s done, create a new directory for your project in your file system, open a terminal at the new directory location and initialise a new ServiceNow SDK project:

now-sdk init
[now-sdk] Bootstrapping a new ServiceNow application project with SDK 4.10.1...
[now-sdk] WARN: Current sdk version is 4.10.1 and a new version 4.11.0 is available!
? Select a template:
-- Basic --
  now-sdk boilerplate
-- JavaScript --
❯ now-sdk + AIUX
  now-sdk + AIUX Extension starter
  now-sdk + basic
  now-sdk + fullstack React
-- TypeScript --
  now-sdk + basic
  now-sdk + fullstack React
  now-sdk + fullstack Vue

Select the “now-sdk + AIUX” template. Next, continue to follow the setup sequence. The SDK will authenticate with your instance and create a new scoped application. Once that is done, make sure to install the dependencies:

npm install

Exploring Agent Skills

Once the dependencies are installed, notice that you now have a .agents/skills directory.

.agents/skills/
├── accessibility/
├── aiux-build/
├── component-discovery/
├── components/
├── compositions/
├── figma-to-widget/
├── internationalization/
├── localization/
├── migrate-header-config/
├── motion/
├── pages-extensions-generator/
└── patterns/

For those using Claude Code, you’ll see the same set of folders in the .claude/skills directory.

Open up the .agents/skills/components/references location and you’ll see that your agent now has skill files for all the out-of-the-box AIUX components. Start digging into the rest of the skill folders and you’ll see that your agent should be fully equipped with most of the knowledge that it needs to build pages and components in the AIUX framework.

Testing Your Agent

Use the ServiceNow SDK to deploy your application to the instance or just ask your agent to do it. Once that’s done, let’s test some of the boilerplate AIUX pages that come with a new project.

Links to AIUX pages are structured in the following way:

https://[Your-Instance].service-now.com/aiux/[AI Experience URL Suffix]/[AIX Page Path]
  • The AI Experiences table (sys_aix_experience) has the url suffix.
  • The AIX Page table (sys_aix_page) has the page path pattern.

To check that the agent can create pages and components in AIUX, give it a test prompt such as:

Build a ServiceNow P1 Critical Incidents Dashboard for incidents with a priority of 1. I need this exact layout:

  1. Top: A bold command center header with a live refresh clock.
  2. Middle: Urgent, color-coded KPI scorecards for Active P1s, Unassigned P1s, and MTTR.
  3. Main: A clean P1 data grid displaying key incident details, featuring a clickable slide-out drawer to view full records without leaving the page.

Use AIUX components where possible before building any custom components.