---
name: a2ui-blueprint-compliance
description: Verification of platform codebase blueprint compliance against the latest module blueprints.
metadata:
  internal: true
title: a2ui-blueprint-compliance
canonical_url: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-blueprint-compliance
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.
>
> Supporting files, fetch one when the Skill refers to it: [scripts/check_compliance.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-blueprint-compliance/scripts/check_compliance.py), [scripts/test_check_compliance.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-blueprint-compliance/scripts/test_check_compliance.py).
>
> If the user asked to install this Skill, run `npx skilld install a2ui-project/a2ui/a2ui-blueprint-compliance`. 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-compliance`, 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-compliance) 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-compliance`. 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-compliance --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/a2ui-blueprint-compliance --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 Compliance Check Skill

This skill guides you through the process of auditing the repository's codebase blueprints to verify that they are synchronized with the latest module specifications, and posting a weekly report issue.

---

## **Instructions**

> [!IMPORTANT]
> All codebase auditing must be performed using static/structural inspection (e.g. reading file contents, grep searching symbols, checking git logs, or static lints). Do not run package/dependency installations (like `yarn install`, `pip install`, `pub get`), compile code, or execute dynamic test suites.

1. **Run Check Compliance Script**:
   - Run the compliance checker script to generate the baseline status of the repository:
     ```bash
     python3 blueprints/skills/a2ui-blueprint-compliance/scripts/check_compliance.py
     ```
   - This script automatically discovers codebase blueprints, parses their pinned commits, compares them against module blueprints git logs, and formats the baseline Markdown report structure.

2. **Audit Each Codebase (Manual Verification)**:
   - For each codebase, perform the following static code analysis tasks:
     - **Step 2.1: Audit Actual Implementation vs. Module Blueprint**:
       - Analyze the specifications, required interfaces, and behavior described in the module blueprint (located at `blueprints/modules/<associated_module>.blueprint.md`).
       - Inspect the source code in the codebase directory (`<codebase_path>`) to verify if the required specifications are implemented.
       - Identify any features, interfaces, or protocol requirements specified in the module blueprint (including those introduced in the missing commits listed in the script's output report) that are **not** currently implemented in the code.

   - **Step 2.2: Audit Claimed Features (`implemented_features`)**:
     - For each feature key and pinned commit hash in the codebase blueprint's `implemented_features` mapping (`{feature_name: <commit_sha>}`):
       - Verify that the pinned commit matches the latest commit on `blueprints/features/<feature_name>.blueprint.md` (or inspect `git diff <pinned_sha>..HEAD -- blueprints/features/<feature_name>.blueprint.md`).
       - Search the codebase (code files, symbols, tests, or documentation) to verify if the feature is actually implemented.
       - If it is not found or is incomplete, flag it as a discrepancy (e.g. "Claimed as implemented, but missing or incomplete in code").

   - **Step 2.3: Identify Implemented Optional Features**:
     - Inspect the codebase for any implemented optional features (either from the `blueprints/features/` folder, or from codebase-specific extensions).
     - Verify if they are correctly documented in the codebase blueprint's `implemented_features`.
     - Compile a list of verified implemented optional features.

3. **Format the Report**:
   - Build a Markdown report with a summary table listing:
     - Codebase Path
     - Associated Module
     - Status (Up to Date, Out of Date, Not Baselined, Error)
     - Commits Behind
     - Pinned Commit
     - Latest Commit
   - For each codebase, include a detailed section listing:
     - **Missing Required Features**: Features/specifications in the module blueprint (or in newer commits to it) that are missing from the implementation code.
     - **Feature Claims Verification / Discrepancies**:
       - Features listed in `implemented_features` that are missing or incomplete in the code.
       - Implemented features that are missing from the `implemented_features` frontmatter list.
     - **Implemented Optional Features**: A list of optional features verified as implemented in the code.
     - **Missing Commits / Spec Diffs**: The list of git commits since the pinned hash.
   - Return this Markdown report as your final response.
