Skip to content

feat(engineering): add archify interactive diagrams - #14

Merged
christso merged 1 commit into
mainfrom
feat/engineering-archify
Nov 10, 2026
Merged

christso merged 1 commit into
mainfrom
feat/engineering-archify

Conversation

@christso

Copy link
Copy Markdown
Contributor

Summary

Engineering plugin users can generate Archify's ten interactive diagram types and one-page explainers through their existing agent. The bundled runtime works after AllAgents copies it into client skill directories, without a dependency installation inside the skill.

The source is tt-a1i/archify at 11b0d603, package version 3.2.0. Upstream instructions and runtime files retain their contents, licenses, attribution, and executable modes. Packaging follows upstream's clean-package exclusions and manifest cleanup; pre-rendered example HTML is omitted. Required viewer assets, validators, schemas, references, locales, and component notices remain included.

The engineering guide documents Node/browser prerequisites, the optional upstream update check, and destination-conflict checks. Existing engineering marketplace entries discover the skill; both native catalogues remain identical.

Validation

  • bun run validate: all five plugins, both native catalogues, and local Markdown references pass.
  • bun test: 58 tests pass, zero failures.
  • Compared all 188 copied upstream files and permission modes; only package.json differs through documented upstream packaging cleanup. The 18 omitted files are development tooling and pre-rendered examples.
  • Temporary relocated package: doctor and demo pass. Architecture finalize --quality showcase --json passes validation, delivery, strict artifact checks, and Chromium browser checks. Explainer finalize --json passes artifact gates with one unchanged upstream scope-length writing warning; its browser gate was not requested.
  • Built current allagentsdev/allagents main at 3ca3efc83f82f4eb7fbe97bf200e869f13362c1c using Bun. Its built CLI installed the local engineering plugin with Archify selected for Codex, Cursor, Claude Code, OpenCode, and Copilot in an isolated project/user-home fixture. All five installed copies passed doctor, with executable modes preserved. The installed Codex copy also passed architecture delivery including Chromium and explainer artifact gates.

Chromium required ARCHIFY_CHROME_NO_SANDBOX=1 in this test environment. Update networking was disabled for smoke checks. No perceptual visual review, upstream full test suite, real user-scope installation, or native-client installation was claimed. First-party files pass git diff --check; preserved upstream files retain existing trailing whitespace.

AllAgents compatibility findings

Compared the built CLI with Archify's installation contract. Clean installations work. Existing AllAgents behavior needs these improvements; this PR documents the preflight requirement and makes no changes to the AllAgents CLI:

Priority Observed gap Improvement
High A fresh project install silently replaced an unmanaged archify/SKILL.md and deleted its personal.txt. Check destination ownership before any write, reject unmanaged conflicts, and preserve unrelated files.
High plugin install --skill archify initially synchronizes all engineering skills. In a separate fixture it deleted an unmanaged github-attention directory even though only Archify was selected. Resolve and validate the skill allowlist before the first synchronization. See current install flow.
Medium skill add https://archify.si --list fails with Git remote requires a repository path; local --from <engineering-path> --list incorrectly attempts a remote fetch. Support website skill discovery, or explain supported GitHub alternatives; route local discovery through the local resolver.
Medium Successful installation reports copying, while installed-package doctor must be run separately for each target. Offer explicit per-target health checks and runtime prerequisite reporting without automatically executing arbitrary package commands.

The conflict fixtures used fictional files under /tmp; no personal installations were changed. The engineering guide requires checking all included skill destinations, including when using --skill.

Review

Independent review covered correctness, repository standards, maintainability, and packaging test coverage. No actionable findings remain.


Compound Engineering

Bundle the upstream Archify skill and runtime with preserved licensing,
supporting resources, and executable modes. Document prerequisites,
provenance, update behavior, and AllAgents destination-conflict checks.
@christso
christso merged commit 0ad4e6b into main Nov 10, 2026
1 check passed
@christso
christso deleted the feat/engineering-archify branch November 10, 2026 07:44
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