A2ui Create Feature Blueprint
Developmenta2ui-create-feature-blueprintA2ui Create Feature Blueprint is an Agent Skill for development published in the a2ui-project/a2ui repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Provides instructions on how to create a new language-agnostic A2UI Feature Blueprint, ensuring consistency and ease of cross-language implementation.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/a2ui-project/a2ui/blob/HEAD/blueprints/skills/a2ui-create-feature-blueprint/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/a2ui-create-feature-blueprint, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
A2UI Create Feature Blueprint Skill
This skill provides step-by-step instructions on how to design, format, and check in a new A2UI Feature Blueprint inside blueprints/features/ to specify behavioral or protocol changes before implementation.
1. Design Principles for Feature Blueprints
- Language Agnosticism: Keep the blueprint completely free of language-specific or framework-specific terminology.
- Generic Protocol Alignment: Reference specific messages, schemas, or JSON pointers as the primary mechanism for interaction.
- Portability: Design the feature so that it can be implemented cleanly across targeted SDK languages.
2. Step-by-Step Creation Recipe
Step 1: File Naming & Location
- Target Path:
blueprints/features/<feature_name>.blueprint.md<feature_name>must be insnake_case(e.g.dynamic_theming.blueprint.md).- Do NOT prefix filenames with a date.
- Initial Status: All newly created feature blueprints in
blueprints/features/start as optional (unmerged).
Step 2: Define YAML Frontmatter
Every feature blueprint must start with a YAML block containing:
---
feature_name: feature_name # Must match the filename's snake_case name exactly
module_blueprints:
- a2ui_core # One or more valid module blueprint names affected
dependencies: [] # Optional list of prerequisite feature names
date_added: 2026-07-07 # Date initially authored (YYYY-MM-DD)
---
Step 3: Structure Content
Implement canonical Markdown sections:
# **[Feature Name] Feature Blueprint**## **Requirements**## **Detailed Description of Changes**## **Links**## **Test Cases & Conformance**## **Implementation Steps**
Step 4: Validate Blueprint
Run the blueprint validator script:
python3 blueprints/validate_blueprints.py