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

/a2ui-implement-feature-from-blueprint

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

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

  • 1 file
  • 2.3 KB
  • Updated last week
  • GitHub
Use this Skill: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-implement-feature-from-blueprint

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈37 tokens for metadata: the name and description. ≈534 when used: this file.

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

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 Implement Feature from Blueprint Skill

This skill provides step-by-step instructions on implementing feature specifications and updating codebase module compliance commit hashes.


1. Implementation Workflow

Step 1: Check Codebase Status & Context

  • Open the target codebase's blueprint at blueprints/codebases/<relative_path>/codebase.blueprint.md.
  • Identify the target associated_module and module_blueprint_commit.
  • Check if the codebase needs to catch up to the latest Module Blueprint commit:
    git diff <module_blueprint_commit>..HEAD blueprints/modules/<associated_module>.blueprint.md
  • If implementing an optional feature blueprint from blueprints/features/<feature_name>.blueprint.md, check its dependencies list first.
  • Verify that terms used in code, documentation and blueprints are consistent with the glossary. If you find deviations, suggest fixes. If you see an important term is used in documentation and/or API, but is missing from the glossary, suggest an update for the glossary.

Step 2: Execute Implementation & Conformance Tests

  • Implement required code changes in the target codebase directory (<relative_path>).
  • Run local unit and conformance tests specified by test_command in codebase.blueprint.md.

Step 3: Update Codebase Blueprint Compliance

  • Open blueprints/codebases/<relative_path>/codebase.blueprint.md.
  • If you brought the codebase up to date with the latest Module Blueprint commit, update module_blueprint_commit to the current commit hash:
    git log -n 1 --pretty=format:%H -- blueprints/modules/<associated_module>.blueprint.md
  • If you implemented or updated an optional feature from blueprints/features/, record its latest 40-character commit hash under implemented_features:
    git log -n 1 --pretty=format:%H -- blueprints/features/<feature_name>.blueprint.md

Step 4: Validate Blueprints

Verify blueprint consistency across the monorepo:

python3 blueprints/validate_blueprints.py

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 last week
metadata
{
  "internal": true
}

README badge

README badge for a2ui-project/a2ui/a2ui-implement-feature-from-blueprint