diff --git a/CHANGELOG.md b/CHANGELOG.md index cfe2624..ea5bcb9 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,16 @@ # Changelog +## Unreleased + +### Added + +- **A `ucsd-decorator-kit` skill for the TritonAI Skills Library.** A short + pointer at `library/tritonai/ucsd-decorator-kit/` that tells an agent with no + kit installed how to get it: `npx ucsd-decorator-kit@latest init` in an empty + directory, `npx ucsd-decorator-kit@latest add --with-decorator` in an + existing project, then follow the generated rule files. It holds no rules + itself. + ## 2.5.0 ### Changed diff --git a/README.md b/README.md index 8d1ca42..3a8af4f 100644 --- a/README.md +++ b/README.md @@ -349,6 +349,7 @@ channels, alongside the Claude Code plugin and the generated IDE rule files. ``` library/tritonai/ucsd-decorator/SKILL.md + references/ (published from skills/) library/tritonai/ucsd-branding/SKILL.md retirement pointer +library/tritonai/ucsd-decorator-kit/SKILL.md install pointer (library only) ``` `library/tritonai/ucsd-decorator/` is a **published copy** of @@ -360,6 +361,13 @@ duplicate is the same failure mode this kit exists to prevent. rather than deleted, so anyone already invoking that slug is told where it went instead of silently loading guidance that routes agents into rendered chrome. +`ucsd-decorator-kit` is the TritonAI entry point for a project that does not +have the kit yet. It carries no rules: it names this repository and the two +install commands — `init` for an empty directory, `add --with-decorator` for an +existing project — and tells the agent to follow the rule files those write. It +lives only in `library/`, because a project that has the kit no longer needs +it. + Validate before publishing: ```bash diff --git a/library/tritonai/ucsd-decorator-kit/SKILL.md b/library/tritonai/ucsd-decorator-kit/SKILL.md new file mode 100644 index 0000000..1339f89 --- /dev/null +++ b/library/tritonai/ucsd-decorator-kit/SKILL.md @@ -0,0 +1,50 @@ +--- +name: ucsd-decorator-kit +description: Install the UC San Diego Decorator Kit before building a UC San Diego web page on the Decorator 5 design system. Use when someone wants to start a new ucsd.edu site, page, or app, or to add the Decorator to a project that does not have the kit yet (no decorator-kit.json at the project root). This skill only installs the kit; the kit's generated rule files, not this skill, govern the work after that. +--- + +# UC San Diego Decorator Kit — get started + +This skill is a pointer, not the rules. The Decorator Kit exists because a skill +file on its own is not enough to keep an agent from damaging the shared +campus page shell. The kit installs the real Decorator source, the rules in the +format your tool reads, and a check that catches shell damage. Install it first, +then follow what it installs. + +Source: + +## Install + +Requires Node 22 or later. + +**New, empty directory:** + +```bash +npx ucsd-decorator-kit@latest init +``` + +**Existing project** (`init` refuses a directory that already has files in it): + +```bash +npx ucsd-decorator-kit@latest add --with-decorator +``` + +`add` writes the rule files and the skill and leaves the rest of the project +alone. `--with-decorator` also installs `ucsd-decorator-v5`, the Decorator +source the rules tell you to read markup from; without it there is nothing on +disk to read. + +If you can run shell commands, run the one that fits. If you cannot, give the +person the command and wait for them to run it. + +## After it installs + +1. Read the rule file it wrote at the project root — `CLAUDE.md`, `AGENTS.md`, + or your tool's equivalent — and follow it. It overrides anything here. +2. Do not write Decorator markup from memory or from this skill. The rules name + where to read it from on disk. +3. If the person is not sure what to build, they can say "help me get started" + and the installed rules run a short interview first. + +If the project already has `decorator-kit.json` at its root, the kit is +installed: skip this skill and follow the rule files.