---
name: vendored-assets
description: Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
title: vendored-assets
canonical_url: https://skilld.dev/gh/pingdotgg/t3code/vendored-assets
last_updated: 2026-11-12T14:20:12.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [browser-assets.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/vendored-assets/browser-assets.md).
>
> If the user asked to install this Skill, run `npx skilld install pingdotgg/t3code/vendored-assets`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/vendored-assets`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/pingdotgg/t3code/vendored-assets) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/vendored-assets`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/vendored-assets --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/vendored-assets --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

Treat upstream artifacts as supply-chain inputs. Change their generator or
documented import source, then regenerate; generated output is review evidence,
not an editing surface.

## Workflow

1. **Trace ownership.** Identify the artifact, generator or exact import
   procedure, upstream source/version, license, consumers, tests, and shipped
   package or bundle. Search by asset and upstream project name to find current
   packaging scripts, generated artifacts, consumers, and history.
   Continue when every input and consumer is accounted for.
2. **Pin provenance.** Resolve moving URLs, tags, branches, and omitted versions
   to an immutable release or artifact. Record project, version, path or URL,
   and digest in the generator or maintenance header. Omit a digest only when
   another enforced immutable source is recorded.
   Continue when a future run cannot silently select different bytes.
3. **Clear the license gate.** Verify release metadata, license files, bundled
   notices, and the license trail retained in the distributed form.
   Continue when every distributed artifact has a verified retained license trail.
4. **Regenerate.** Improve the generator or import reference first. Recover an
   exact procedure for generatorless assets; add a deterministic script only
   for recurring updates. Record a one-off procedure beside the artifact. A
   clean rerun must produce no diff.
5. **Audit the complete diff.** Account for behavior, URLs and runtime fetches,
   source maps, notices, encoding, format changes, and additions or removals.
   For browser assets, also read [browser-assets.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/vendored-assets/browser-assets.md).
   Continue when every change is attributable and suspicious content is resolved
   or reported.
6. **Clear test and size gates.** Record byte sizes before and after, use
   focused consumer tests, and compare bundle size or composition when shipped
   JavaScript, CSS, or registry output changes materially. Compare that output
   against the pre-update revision rather than measuring only current size.
   Continue when focused checks pass and every non-trivial size delta is explained.
7. **Close release impact.** Apply root changeset routing for consumer-visible
   behavior, browser support, wire data, or meaningful shipped-size changes.
   Generated sections owned by barrels, AI docs, or migration tooling remain
   with the owners named in root instructions.

The task is complete when every input and consumer is accounted for, provenance
and licenses are immutable and retained, regeneration is deterministic, every
output change and non-trivial size delta is explained, focused checks pass or
are reported as not runnable, and release impact is recorded.
