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

/a2ui-blueprint-navigator

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

Analytical navigation of A2UI Spec-Driven Development module and codebase blueprints.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈28 tokens for metadata: the name and description. ≈634 when used: this file.

Description uses 1.4% 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 ≈112 characters, or 1.4%.

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 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:
    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:
    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.

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-blueprint-navigator