This skill provides precise analytical methods and recipes for discovering blueprints, inspecting commit-hash compliance, and mapping language-agnostic specifications to physical directories in the monorepo.

1. Understanding Blueprints Layout

Spec-Driven Development (SDD) in A2UI confines all specifications and compliance files inside blueprints/:

Module Blueprints (blueprints/modules/): Language-agnostic authorities specifying core architecture, APIs, types, and expected behaviors (e.g. a2ui_core.blueprint.md).
Feature Blueprints (blueprints/features/): Standalone optional feature specifications (features/<name>.blueprint.md) and merged required features (features/archived/<name>.blueprint.md).
Codebase Blueprints (blueprints/codebases/<relative_codebase_path>/codebase.blueprint.md): Local metadata trackers documenting codebase compliance with a specific git commit hash of its associated Module Blueprint (module_blueprint_commit).

2. Commit-Hash Module Compliance

Rather than checking against a list of required feature names, a codebase's compliance status is tracked by the git commit hash of its associated Module Blueprint (module_blueprint_commit).

When a feature is merged into a Module Blueprint (blueprints/modules/<module>.blueprint.md), the file's git commit hash advances.
Codebase blueprints verify and update compliance by checking diffs against module_blueprint_commit.

3. Navigator Recipes

Recipe A: Check if a Codebase is Up to Date with its Module Blueprint

Open the codebase blueprint at blueprints/codebases/<relative_path>/codebase.blueprint.md.
Inspect module_blueprint_commit in the YAML frontmatter.

Retrieve the latest commit hash of the associated module blueprint:

git log -n 1 --pretty=format:%H blueprints/modules/<associated_module>.blueprint.md

If module_blueprint_commit matches the latest commit hash, the codebase is up to date.

If they differ, inspect the exact specification diff that needs to be implemented:

git diff <module_blueprint_commit>..HEAD blueprints/modules/<associated_module>.blueprint.md

Recipe B: Find the Module Blueprint for a Particular Codebase

Locate the codebase blueprint at blueprints/codebases/<relative_path>/codebase.blueprint.md.
Look up associated_module in the frontmatter.
Open blueprints/modules/<associated_module>.blueprint.md.

Más de este repositorio

mismo repositorio

a2ui-issue-triage

a2ui-project/a2ui

Automates the triage of GitHub issues in the A2UI repository. Helps the oncall engineer by fetching untriaged issues, generating AI-suggested priorities, assignees, and responses, launching a local review dashboard, and bulk-applying approved decisions to GitHub. Use when tasked with triaging new GitHub issues or managing the repository backlog.

2026-07-1015.7k

a2ui-implement-new-sdks-for-client-language

a2ui-project/a2ui

Step-by-step phased instructions for building new A2UI Core SDKs, Framework Adapters, and Inference SDKs from scratch in any client language.

2026-07-0815.7k

a2ui-blueprint-maintenance

a2ui-project/a2ui

Manage the evolution, merging, archiving, and cleanup of specifications and blueprints across the workspace.

2026-07-0815.7k

a2ui-create-feature-blueprint

a2ui-project/a2ui

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

2026-07-0815.7k

a2ui-implement-feature-from-blueprint

a2ui-project/a2ui

Provides instructions on implementing feature specs or module blueprint commit diffs in a specific codebase.

2026-07-0815.7k

natural-writing

a2ui-project/a2ui

Contains well-defined rules for creating natural, accurate, and readable writing. Use this skill whenever authoring longer text, including reports, PR or CL descriptions, READMEs, system designs, analysis documents, or general documentation.

2026-06-2615.7k

A2UI Blueprint Navigator Skill

1. Understanding Blueprints Layout

Spec-Driven Development (SDD) in A2UI confines all specifications and compliance files inside blueprints/:

Module Blueprints (blueprints/modules/): Language-agnostic authorities specifying core architecture, APIs, types, and expected behaviors (e.g. a2ui_core.blueprint.md).

Feature Blueprints (blueprints/features/): Standalone optional feature specifications (features/<name>.blueprint.md) and merged required features (features/archived/<name>.blueprint.md).

Codebase Blueprints (blueprints/codebases/<relative_codebase_path>/codebase.blueprint.md): Local metadata trackers documenting codebase compliance with a specific git commit hash of its associated Module Blueprint (module_blueprint_commit).

2. Commit-Hash Module Compliance

Rather than checking against a list of required feature names, a codebase's compliance status is tracked by the git commit hash of its associated Module Blueprint (module_blueprint_commit).

When a feature is merged into a Module Blueprint (blueprints/modules/<module>.blueprint.md), the file's git commit hash advances.

Codebase blueprints verify and update compliance by checking diffs against module_blueprint_commit.

3. Navigator Recipes

Recipe A: Check if a Codebase is Up to Date with its Module Blueprint

Open the codebase blueprint at blueprints/codebases/<relative_path>/codebase.blueprint.md.

Inspect module_blueprint_commit in the YAML frontmatter.

Retrieve the latest commit hash of the associated module blueprint:

git log -n 1 --pretty=format:%H blueprints/modules/<associated_module>.blueprint.md

If module_blueprint_commit matches the latest commit hash, the codebase is up to date.

If they differ, inspect the exact specification diff that needs to be implemented:

git diff <module_blueprint_commit>..HEAD blueprints/modules/<associated_module>.blueprint.md

Recipe B: Find the Module Blueprint for a Particular Codebase

Locate the codebase blueprint at blueprints/codebases/<relative_path>/codebase.blueprint.md.

Look up associated_module in the frontmatter.

Open blueprints/modules/<associated_module>.blueprint.md.