Index of every page on this site: llms.txt
All skills
a2ui-project avatar

/a2ui-create-feature-blueprint

@6bf4cc2
by A2UIa2ui-project/a2ui18k stars
1,430
Run it yourself

Provides instructions on how to create a new language-agnostic A2UI Feature Blueprint, ensuring consistency and ease of cross-language implementation.

  • 1 file
  • 2.1 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-create-feature-blueprint

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈45 tokens for metadata: the name and description. ≈473 when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈182 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 in snake_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:

  1. # **[Feature Name] Feature Blueprint**
  2. ## **Requirements**
  3. ## **Detailed Description of Changes**
  4. ## **Links**
  5. ## **Test Cases & Conformance**
  6. ## **Implementation Steps**

Step 4: Validate Blueprint

Run the blueprint validator script:

python3 blueprints/validate_blueprints.py

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 6bf4cc2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
metadata
{
  "internal": true
}

README badge

README badge for a2ui-project/a2ui/a2ui-create-feature-blueprint