---
name: a2ui-blueprint-navigator
description: Analytical navigation of A2UI Spec-Driven Development module and codebase blueprints.
metadata:
  internal: true
title: a2ui-blueprint-navigator
canonical_url: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-blueprint-navigator
last_updated: 2026-11-12T06:16:11.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install a2ui-project/a2ui/a2ui-blueprint-navigator`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/a2ui-blueprint-navigator`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/a2ui-project/a2ui/a2ui-blueprint-navigator) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/a2ui-blueprint-navigator`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/a2ui-blueprint-navigator --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/a2ui-blueprint-navigator --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# A2UI Blueprint Navigator Skill

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/`:

1. **Module Blueprints** (`blueprints/modules/`): Language-agnostic authorities specifying core architecture, APIs, types, and expected behaviors (e.g. `a2ui_core.blueprint.md`).
2. **Feature Blueprints** (`blueprints/features/`): Standalone optional feature specifications (`features/<name>.blueprint.md`) and merged required features (`features/archived/<name>.blueprint.md`).
3. **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**

1. Open the codebase blueprint at `blueprints/codebases/<relative_path>/codebase.blueprint.md`.
2. Inspect `module_blueprint_commit` in the YAML frontmatter.
3. Retrieve the latest commit hash of the associated module blueprint:
   ```bash
   git log -n 1 --pretty=format:%H blueprints/modules/<associated_module>.blueprint.md
   ```
4. If `module_blueprint_commit` matches the latest commit hash, the codebase is up to date.
5. If they differ, inspect the exact specification diff that needs to be implemented:
   ```bash
   git diff <module_blueprint_commit>..HEAD blueprints/modules/<associated_module>.blueprint.md
   ```

### **Recipe B: Find the Module Blueprint for a Particular Codebase**

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