A2ui Blueprint Navigator
Developmenta2ui-blueprint-navigatorA2ui Blueprint Navigator 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.
Analytical navigation of A2UI Spec-Driven Development module and codebase blueprints.
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-blueprint-navigator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/a2ui-blueprint-navigator, 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 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/:
- 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_commitin 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_commitmatches 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_modulein the frontmatter. - Open
blueprints/modules/<associated_module>.blueprint.md.