Community registry / standalone packages

Built on Archify.
Shared by everyone.

Community packages are standalone works that wrap the Archify CLI — skill packs, recipe libraries, brand kits, locales, and wrappers. Nothing here is a plugin: no third-party code ever runs inside the renderer.

Submit your package ↗
2packages listed
from the registry
2package types
in the catalog
PASSmetadata validated
deterministically
Submitted by PR · maintained by their authors

The catalog.

Every entry is a metadata file in the Archify repository, merged by PR and revalidated on every change. Listing is not endorsement — evidence links speak for each package.

02 archify-hermes Skill pack

Hermes Agent integration: lets Hermes author Archify JSON IR and render through the Archify CLI — no code loaded into Archify.

tt-a1i archify >=3.0.0 <4.0.0 IR v1 · v2
View source ↗ Plugin contract tests ↗
No packages match this filter.
Join the registry

A pull request is the submission.

01Publish your package in your own repoYOU
02Add one metadata file under community/packages/YOU
03Validate with check-community-packages.mjsPASS
04Open a PR targeting dev — publication follows main deploymentPASS
submit locallyzero dependencies
# from your fork, track upstream dev
$ git fetch upstream dev
$ git switch -c community/my-pack upstream/dev

# add community/packages/my-pack.json
# validate from the repository root
$ node scripts/check-community-packages.mjs

# open PR to dev → review
# promote to main → deploy → public catalog
Read the submission guide ↗