Skip to content

chore(dev): add .amplifier/bundles/dev with coupling-diagram and wire-protocol-consistency skills#25

Closed
manojp99 wants to merge 1 commit into
mainfrom
chore/dev-bundle
Closed

chore(dev): add .amplifier/bundles/dev with coupling-diagram and wire-protocol-consistency skills#25
manojp99 wants to merge 1 commit into
mainfrom
chore/dev-bundle

Conversation

@manojp99

Copy link
Copy Markdown
Collaborator

What. Adds a repo-local "dev" bundle at .amplifier/bundles/dev/ for amplifier-agent contributors, with two skills: coupling-diagram (regenerates the L0→L4 cross-layer coupling diagrams, useful for understanding what silently breaks when a module is removed from bundle.md) and wire-protocol-consistency (static linter that runs 8 mechanical checks against the canonical PROTOCOL_VERSION, surfacing drift across the engine, CLI, both wrappers, JSON schemas, conformance fixtures, design docs, and test literals). Also adds a .gitignore entry for .amplifier/digital-twin-universe/ so contributors can commit .amplifier/bundles/ without dragging their personal DTU profile artifacts along.

Why. Two contributor workflows we hit repeatedly while iterating on protocol 0.2.0 and the wrapper alignment work: (1) understanding cross-layer coupling — which wire fields require which modules, and what silently breaks if a module is removed from bundle.md; (2) catching wire-protocol drift at multiple sites (the engine's PROTOCOL_VERSION truth source, both wrapper version constants, argv flag names, TypeScript types vs Python TypedDicts, conformance fixtures, ~30 hardcoded test literals). The wire-protocol-consistency linter shipping in this PR is what surfaced the 2 FAILs and 5 WARNs that became PR #24 (fix(wire): align all sites to protocol 0.2.0). After PR #24's fixes, re-running the linter produced 0 FAIL / 0 WARN — closing the loop on validation. Both skills are repo-local (.amplifier/bundles/dev/skills/) and discoverable via the bundle's tool-skills configuration. Contributors invoke them with /coupling-diagram or /wire-protocol-consistency after running amplifier run --bundle .amplifier/bundles/dev/bundle.md.

How verified. Bundle composition was reference-checked: foundation and dot-graph bundle sources resolve, the explicit tools.tool-skills.config.skills override correctly preserves all three skill sources (foundation curated, dot-graph, local). YAML frontmatter on both SKILL.md files parses cleanly. Both skills were live-tested in the session that produced this PR: coupling-diagram produced 3 DOT diagrams (all reviewer-PASS) and wire-protocol-consistency produced a structured PASS/WARN/FAIL report on 8 categories of drift that directly drove PR #24. After PR #24 merged its fixes, wire-protocol-consistency re-ran clean.

…-protocol-consistency skills

Adds a repo-local "dev" bundle at .amplifier/bundles/dev/ for amplifier-agent
contributors with two skills: coupling-diagram (regenerates L0→L4 cross-layer coupling
diagrams) and wire-protocol-consistency (static linter that checks 8 categories of
protocol drift). Also adds .gitignore entry for .amplifier/digital-twin-universe/
so contributors can commit .amplifier/bundles/ without personal DTU profile artifacts.

Bundle composition: foundation + dot-graph + anthropic-sonnet provider via includes.
Explicit tool-skills override preserves both foundation and dot-graph skill catalogs
alongside local skills. Both skills live-tested and verified.

🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier)

Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
@manojp99 manojp99 closed this Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant