From 3241b35ed6dd3137113ec4024f6037682ecf055c Mon Sep 17 00:00:00 2001 From: David Balderston Date: Fri, 9 Oct 2026 21:57:10 -0700 Subject: [PATCH] Ship the kickoff interview with the skill The skill sent agents to the project's DECORATOR.md for the kickoff interview, which exists only once the kit is installed. Publish rules/60-getting-started.md as references/getting-started.md, like the accessibility and security rules, and point the skill there. A new test holds every exported reference page to the whole rule: no pointer to DECORATOR.md, no leftover on-demand marker, and the interview's questions present. Part of #12. --- CHANGELOG.md | 6 ++ library/tritonai/ucsd-decorator/SKILL.md | 4 +- .../references/getting-started.md | 99 +++++++++++++++++++ scripts/lib/rules.mjs | 1 + skills/ucsd-decorator/SKILL.md | 4 +- .../references/getting-started.md | 99 +++++++++++++++++++ test/rules.test.mjs | 21 +++- 7 files changed, 229 insertions(+), 5 deletions(-) create mode 100644 library/tritonai/ucsd-decorator/references/getting-started.md create mode 100644 skills/ucsd-decorator/references/getting-started.md diff --git a/CHANGELOG.md b/CHANGELOG.md index ea5bcb9..c552f46 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,12 @@ ### Added +- **The kickoff interview ships with the skill.** `rules/60-getting-started.md` + is now also published as `skills/ucsd-decorator/references/getting-started.md`, + like the accessibility and security rules. The skill pointed at the + project's `DECORATOR.md` for the six questions, which exists only once the + kit is installed, so "help me get started" had nothing to ask without it. A + test holds every exported reference page to the whole rule. See #12. - **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 diff --git a/library/tritonai/ucsd-decorator/SKILL.md b/library/tritonai/ucsd-decorator/SKILL.md index 4dbe4c9..16cbfc1 100644 --- a/library/tritonai/ucsd-decorator/SKILL.md +++ b/library/tritonai/ucsd-decorator/SKILL.md @@ -175,8 +175,7 @@ template, never from recall. When a developer asks to get started — "help me get started", "where do I begin", "start a new project" — run the kickoff interview before writing any -markup. Its full text is "Getting started — the kickoff interview" in the -project's `DECORATOR.md`, compiled from the kit's `rules/60-getting-started.md`. +markup. Its full text is in `references/getting-started.md`. Ask its six questions in one message, recommend a layout and modules with links to the Decorator Kit Developer Guide at `https://developer.ucsd.edu/design/decorator/user-guide/`, let the developer @@ -482,6 +481,7 @@ the source file to restore from. Use it; do not guess. table written from live pages; where it disagrees with the references above, prefer them - `references/component-inventory.md` — kitchen sink, widgets, modules +- `references/getting-started.md` — the kickoff interview and build brief - `references/accessibility.md` — full WCAG 2.1 AA rule set - `references/security.md` — full IS-3 / PPM 135-3 rule set - `references/distribution.md` — how Decorator is published, and what a consuming project should depend on diff --git a/library/tritonai/ucsd-decorator/references/getting-started.md b/library/tritonai/ucsd-decorator/references/getting-started.md new file mode 100644 index 0000000..f0c377f --- /dev/null +++ b/library/tritonai/ucsd-decorator/references/getting-started.md @@ -0,0 +1,99 @@ + + +# Getting started — the kickoff interview + +When a developer asks to get started — "help me get started", "where do I +begin", "start a new project", "what should I build this with" — do not start +writing markup. Run this interview first. Skip it when the request already +answers its questions — a named template, a page name, and the pieces to build — +and ask only what is missing. + +The interview exists for developers who know what the app has to do but not +what it should look like: their answers pick the layout, modules, and patterns, +so the first iteration is already close to the goal and stays on brand. + +## The visual guide + +Every recommendation links a card in the Decorator Kit Developer Guide, so the +developer can see it before agreeing to it. Base URL: +`https://developer.ucsd.edu/design/decorator/user-guide/`. The anchors below +are relative to it — write them out as full links. + +## Round 1 — ask all six at once + +Ask in one message, as a numbered list with lettered options, so the developer +can reply "1b, 2 students checking waitlists, 3b…". If your environment has a +structured multiple-choice tool, you may use it instead. Always allow a +free-text answer. + +1. **What are you building?** (a) a department or information site + (b) a request, intake, or multi-step application form (c) a dashboard or + status board (d) a directory, search, or records admin tool (e) a knowledge + base or help articles (f) something else — describe it in a sentence. +2. **Who uses it, and what is the one thing they must be able to do?** For + example: "students — check whether they got off a waitlist." +3. **Which campus area?** (a) advising (b) enrollment and courses (c) research + (d) housing (e) IT services (f) facilities and energy (g) library (h) HR + (i) other or none. +4. **How will it be built and hosted?** (a) static HTML (b) a JavaScript + framework such as React or Vue (c) server-rendered templates (d) Cascade CMS + (e) not sure. The Decorator is Bootstrap 3 and jQuery whatever language the + app is written in; this decides where the canvas lives, not the look. +5. **What data does it touch?** (a) public information only (b) it needs campus + sign-in (c) student records, personal, or health data (d) not sure. +6. **Site name**, and a short form of it for phones — a word or an acronym. + +## Round 2 — recommend, link, and let the developer choose + +Map the answers with these tables. Link every card you recommend. + +| Building | Suggested layout | Guide cards | +|---|---|---| +| (a) information site | `homepage.html` for the landing page, `two-column.html` for inner pages | `index.html#r-dept`, `#lay-home`, `#modules`, `#m-tiles`, `#m-news`, `#m-events` | +| (b) request or application | `two-column.html` or `blank-slate.html` | `index.html#r-form`, `#c-forms`, `#w-wiz`, `app-patterns.html#pat-shell`, `#shell-steps` | +| (c) dashboard | `blank-slate.html` | `index.html#r-dash`, `app-patterns.html#dash-workflow`, `#shell-dashboard`, `#blk-kpi`, `#blk-status`, `#blk-filter` | +| (d) directory, search, admin | `blank-slate.html` or `two-column.html` | `index.html#r-dir`, `#w-dt`, `#c-tables`, `app-patterns.html#shell-search`, `#shell-admin`, `#shell-record` | +| (e) knowledge base | `two-column.html` | `index.html#r-kb`, `#c-drawer`, `#c-crumbs` | + +| Campus area | Dashboard example to borrow from | +|---|---| +| advising · enrollment · research · housing | `app-patterns.html#dash-advising` · `#dash-enroll` · `#dash-research` · `#dash-housing` | +| IT · facilities · library · HR | `app-patterns.html#dash-its` · `#dash-energy` · `#dash-library` · `#dash-hr` | + +- **Build (b) or (c):** the canvas is still `main#main-content`. If the + project uses a component library, it goes in `canvas-components/` — link + `app-patterns.html#brand-layer`. **(d) Cascade:** content goes into the + page's canvas region only. **(e):** recommend static HTML. +- **Data (b), (c), or (d):** say that the security rules apply from the first + commit — campus SSO, no real records in placeholder content, nothing + sensitive in URLs or logs. + +**Recommend a layout, but do not choose it.** Link all four layout cards — +`index.html#lay-blank`, `#lay-two`, `#lay-three`, `#lay-home` — say which one +you suggest and why in one sentence, and wait for the developer to pick. The +template-selection rule still holds: the choice is theirs. + +## Write the brief before building + +Once the layout is chosen, save `BRIEF.md` at the project root and show it: + +```markdown +# Build brief — () + +- **Building:** · **For:** · **Must do:** +- **Layout:**