Repository navigation
feat(apollo-vertex): add a setup agent skill - #1373
Conversation
|
Apollo Coded App preview deployments are ready.
|
Dependency License Review
License distribution
Excluded packages
|
There was a problem hiding this comment.
🟢 Approval recommended
The localized documentation change has no blocking issues; the dependency reminder is a minor improvement.
1 open finding
What changed in this PR
Adds a copyable setup prompt to the Apollo Vertex docs home page so users can scaffold a solution with their coding agent.
Changes:
- Replaces “Start a solution” with setup instructions and a Copy button.
- Adds copied-state feedback and retains the setup-guide link.
- Directs users to run the interactive skills installer themselves.
| File | Description |
|---|---|
| apps/apollo-vertex/content/docs/_components/home.tsx | Adds the agent prompt and clipboard interaction. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
📊 Coverage + size by packagePer-package bundle size on this PR (no JS/TS source changes detected under
"Coverage" is each package's own |
Storybook visual diff✅ No stories are affected by this PR's changes; nothing to compare. Logs Updated (PT): Oct 16, 2026, 05:21:48 AM |
f7a4a15 to
7ae7630
Compare
7ae7630 to
118003c
Compare
ruudandriessen
changed the title
118003c to
73f3144
Compare
The skill sets up an app to use Apollo Vertex: peer dependencies, the stylesheet import, TanStack Intent with the Vertex skills allowed, and a rule in AGENTS.md that tells agents to follow the Vertex skills when they change UI. Assisted-by: Anthropic:claude-opus-5-5
The home page's "Start a solution" section now has a button that copies a short prompt: install the package, then load and follow the setup skill. Getting started shows the same prompt, drops the uip vss CLI steps and describes the setup skill under agent skills. Assisted-by: Anthropic:claude-opus-5-5
73f3144 to
b91003f
Compare
Getting an agent to set up Apollo Vertex took a long prompt that copied the Getting started page, and
intent installhad to be handed back to the user because it only runs in an interactive terminal. This adds asetupskill to the package, so the prompt only has to install the package and load that skill.The skill has the agent install every peer listed in the installed package's
package.json, including the ones marked optional, since the root entry imports them. It also covers private-registry access for the@uipathpeers, importstailwind.csswith an@sourcefor the app's files, and sets up TanStack Intent. It adds@tanstack/intentas a dev dependency, addsintent.skills: ["@uipath/apollo-vertex"]topackage.jsonsointent installruns without a terminal, and tells the user it allowed those skills and how to change that. Finally, it adds a UI rule toAGENTS.mdand makes sureCLAUDE.mdimports it.On the docs side, the home page's "Start a solution" section has a "Copy prompt for your agent" button, and Getting started shows the same prompt. Getting started drops the
uip vssCLI steps and lists the setup skill under agent skills.The button only works once a release with the
setupskill is on npm. semantic-release publishes it when this merges, so the docs may point at it a few minutes early. If the browser blocks the clipboard, the home page links to the prompt on Getting started instead.I ran the skill end to end in a fresh Vite + React app against a locally packed build of this branch. The prompt loads the skill, and Intent installs with no prompts and lists both skills. The app builds, and
Buttonrenders with the Vertex theme. Without the@uipathpeers the build fails to resolve@uipath/vs-core, which is why the skill installs the optional peers too. I couldn't install the real@uipath/vs-coreand@uipath/proteus-client, since they need private registry access, so I stubbed them for the build.pnpm lint:skillspasses.