An AI agent skill for generating valid Amplience Content Type JSON schemas.
Follows the agentskills.io standard.
Once installed, the skill automatically activates whenever you ask your AI assistant to create, generate, or design an Amplience Content Type or schema. It produces ready-to-register .json schema files with:
- Correct
$schemaand$idstructure - Amplience Core type references (
image-link,video-link,content-link,content-reference,localized-value) - Rich UI hints (
ui:component) for the Amplience Content Form editor — tabs, grids, fieldsets, color pickers, sliders, markdown editors, and more - Content palettes (
oneOfarrays) for multi-variant editorial slots if/then/elseconditionals for dynamic field visibility- Traits (
sortable,filterable,hierarchy) - Reusable partial schemas via
$refto avoid duplication across types
The skill checks for existing schemas in your workspace first, so generated output aligns with your naming conventions, $id host, and existing partials.
Download the .skill file and upload it at https://claude.ai/customize/skills.
Copy the skill folder (containing SKILL.md and any references/) into .claude/skills/ in your project. See the Claude Code skills docs for details.
Copy the skill folder (containing SKILL.md and any references/) into one of:
- Project-level:
.github/skills/,.claude/skills/, or.agents/skills/in your repository - Personal (all projects):
~/.copilot/skills/or~/.agents/skills/
See the GitHub Copilot agent skills docs for details.
Copy the skill folder into your .codex/skills/ directory. See the Codex skills docs for details.
Copy the skill folder into your .gemini/skills/ directory. See the Gemini CLI skills docs for details.
Create an Amplience Content Type schema for a hero banner with a title, subtitle, background image, and a CTA button.
Generate a reusable SEO partial schema and reference it from a Page schema.
Add a content palette to the existing page schema with rich text, image, and banner variants.
Each run produces one or more .json files containing pure JSON — no markdown, no prose. Files are named in kebab-case after the schema's $id suffix (e.g. hero-banner.json).
Pair this skill with figma-context-for-schema-generation to generate schemas directly from a Figma component.