Skip to content

Latest commit

 

History

History
43 lines (35 loc) · 2.89 KB

VENDORED-SKILLS.md

File metadata and controls

43 lines (35 loc) · 2.89 KB

Vendored design references

Checked 2026-10-19. The three pre-existing reference folders are included in the public Git tree. An earlier statement that they were excluded was stale. All 93 original files match the corresponding upstream Git blobs and working bytes at the revisions below; the local folders and their contents are preserved.

Local folder Pinned upstream source Files Upstream terms
.agents/skills/impeccable Impeccable snapshot, labeled 4.6.0 62 Apache-2.0, original NOTICE
.agents/skills/design-taste-frontend Taste Skill v2 snapshot, retained under its install name 29 MIT
.agents/skills/animate Animate snapshot 2 MIT

The Impeccable snapshot follows its 4.6.0 release; it is not claimed to be the release tag's identical tree. The original import paths and applicability notes remain in .agents/skills/README.md. The Impeccable NOTICE also preserves its platform-design-skills attribution. Original Commit Zero material retains AGPL-3.0; upstream material keeps its own terms.

Verify before using or updating a reference

npm run skills:verify

The offline command compares every source file and retained license/notice with the identity ledger: path, size, SHA-256 and Git blob ID. It rejects missing/changed files, unrecorded files, duplicate entries, outside paths and redirected parents. The full Node gate includes those checks. It downloads and executes nothing. The ledger records a primary-source byte comparison; the offline check verifies local identity against that record. Neither command qualifies a launcher, browser script, downloaded engine or model.

Use the relevant reference as guidance within DESIGN.md and the active task's permissions. The application does not import these tools. In this mission only the applicable written guidance was used; no vendored executable, engine or multi-agent workflow was started. Keep these references optional for installation.

For an intentional update, pin the selected upstream revision, compare every retained file, obtain that revision's original license/notice bytes, and update the ledger with the reviewed files. Run skills:verify, the focused tooling suite and the frozen full/browser gates before publication. A newly passing checksum does not itself establish executable behavior or tool permissions.