# Apexlang Inventory

Provides an overview of APEX application components, APEXlang syntax, and application...

- Repository: https://github.com/oracle/skills (909 stars)
- Category: Engineering
- License: UPL-1.0
- Last updated: 2026-10-09
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add oracle/skills --skill apexlang-inventory -g -a claude-code -y`
Codex: `npx skills add oracle/skills --skill apexlang-inventory -g -a codex -y`
Cursor: `npx skills add oracle/skills --skill apexlang-inventory -g -a cursor -y`
Gemini CLI: `npx skills add oracle/skills --skill apexlang-inventory -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add oracle/skills`

## Description

Provides an overview of APEX application components, APEXlang syntax, and application file layout, with links to detailed component properties and examples. Use this catalog to select, compose, generate, and edit APEX applications with APEXlang.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# APEXLang Component Catalog

Use this hierarchy to locate APEXlang component references under assets/ and then read the matching component document before authoring.

APEX Version: 26.1.0

Reference context: subscribed central-theme app 8842.261; central-theme reference versions 8842.261.

# Introduction
This catalog is a routing index for APEX application components. Use the hierarchy to locate the detailed references under `assets/`. A referenced component document with a `filePath` bullet represents a component declared in its own APEX application file.

# Authoring Guide

Use this sequence when creating or editing an APEXlang application:

1. Start with the application layout and create `application.apx` with an `app` component.
2. Select a component from this catalog and open its linked document under `assets/`.
3. Use the document's `componentType` and `identifierRequired` bullets to write the component declaration. Use the documented `filePath` only when the component is the root of its own `.apx` file.
4. Add the documented properties using their group names. A `(direct group)` is flattened into the component; other groups use `{ ... }`. Complex properties use `property: { ... }`, arrays use `property: [ ... ]`, and nested components use `componentType identifier ( ... )`.
5. Follow the catalog hierarchy for containment. Select `plugin-variants/<plugin-name>` or `template-component/<name>` only after checking the parent or ancestor selector and its applicability condition.
6. Validate the completed application before deploying it.

Every property, array value, group member, and nested component member must be on its own physical line. Use APEXlang-visible enum values and component references, not internal metadata or display labels.

Use the component document as the source of truth for authoring:

The rest: https://github.com/oracle/skills/blob/HEAD/apex/apexlang/26.1/apexlang-inventory/SKILL.md