Ui Builder Patterns
CheckedHelps with UI components, patterns as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add serac-labs/serac --skill ui-builder-patterns -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
groeimetai
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned groeimetai/snow-flow at af3ad2b3c0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- af3ad2b3c0
- Scanned
- 1 file, 400 lines
About this skill
What it does
This skill provides information and guidance on building user interfaces within ServiceNow's UI Builder framework. It explains key architectural concepts, terminology like Macroponents, Components, Data Brokers, Client State, and Events, and outlines common page structures used in Next Experience workspaces. The skill aims to help users understand how to construct and manage UI elements for ServiceNow applications.
When to use it
- When developing or customizing ServiceNow Next Experience workspaces.
- To better understand the hierarchy of components within a UIB application (App Shell, Chrome, Pages, Variants, Macroponents, Components, Elements).
- For troubleshooting issues related to data fetching and management using Data Brokers.
- When needing to understand how Client State and Events are used for page-level logic and communication.
Key capabilities
- Component Hierarchy Explanation: Describes the layered structure of UI Builder components.
- Key Concepts Glossary: Defines essential terms like Macroponent, Component, Data Broker, Client State, and Event.
- Page Structure Overview: Illustrates a typical page layout with Variants, Data Brokers, Client States, Events, and Layout sections.
- Data Broker Types & Examples: Explains different types of Data Brokers (GraphQL, Script, REST, Transform) and provides an example GraphQL query for retrieving incident data.
Example prompts
- "Explain the role of a Macroponent in ServiceNow UI Builder."
- "What are the different types of Data Brokers available in UI Builder?"
- "Can you show me an example of a GraphQL Data Broker query?"
- “Describe how Client State is used within a ServiceNow page.”
Tips & gotchas
- This skill focuses specifically on ServiceNow's UI Builder framework. Prior knowledge of ServiceNow concepts will be helpful.
- The provided examples are illustrative and may need to be adapted for specific use cases.