// Keeps apollo-wind up to date in a designer's prototype repo and ensures it is correctly configured. Use when the user wants to sync apollo-wind, update components, set up apollo-wind in their project, or at the start of any prototyping session to ensure they are on the latest version.
Use when fixing npm/pnpm security vulnerabilities, Dependabot alerts, or audit failures
Use when creating or reviewing GitHub Actions workflows in this repo. Applies all security patterns established during the apollo-ui hardening session — permissions, action pinning, checkout safety, install patterns, secrets handling, fork protection, Turbo caching, artifacts, and minimumReleaseAge.
Applies UiPath UX writing guidelines to UI copy — labels, buttons, errors, modals, empty states, and all microcopy. Use when writing or reviewing UI text, copy, or content for UiPath products.
Migrate an apollo-react canvas component from Emotion styled-components to apollo-wind Tailwind classes following the BaseNode reference migration patterns
Use when cutting a maintenance/support branch for an older major version of an apollo-ui package (e.g. apollo-react v3, v4, v5). Orchestrates branch creation, pushes it bare, then opens a PR with workspace dep locking, release config, and lockfile regeneration. Confirms commit messages and git actions with the user before executing them.
Sets up and launches the Apollo Wind Storybook from scratch. Use when the user wants to run Apollo Wind, start Storybook, set up the apollo-ui repo, or says something like "get apollo running", "set up apollo", or "start apollo storybook".
| name | apollo-repo-sync |
| description | Keeps apollo-wind up to date in a designer's prototype repo and ensures it is correctly configured. Use when the user wants to sync apollo-wind, update components, set up apollo-wind in their project, or at the start of any prototyping session to ensure they are on the latest version. |
Keeps @uipath/apollo-wind correctly configured and up to date in the user's prototype project. Run this at the start of each session or any time the user wants to pull in the latest components, styles, and templates.
Run this phase only if @uipath/apollo-wind is not yet in the project.
pnpm add @uipath/apollo-wind
Or with npm:
npm install @uipath/apollo-wind
Add this to the project's root CSS file (e.g. src/index.css or src/globals.css):
@import "@uipath/apollo-wind/styles";
In the root component (e.g. App.tsx or layout.tsx), apply the theme class:
<div className="future-dark min-h-screen bg-background text-foreground">
{/* your app */}
</div>
Use future-light for the light theme. Tell the user they can switch themes by changing this class — no other changes needed.
Let the user know apollo-wind is installed and the theme is active. Tell them:
Apollo Wind is configured. Components are available from
@uipath/apollo-wind/componentsand thefuture-darktheme is active on your root element.
Run this phase every time to ensure the project is on the latest version.
pnpm list @uipath/apollo-wind
npm show @uipath/apollo-wind version
Compare the two. If they match, skip to the success message.
pnpm update @uipath/apollo-wind
Or with npm:
npm update @uipath/apollo-wind
pnpm build
Or if there is a dev server already running, restart it so new components and styles are picked up.
Tell the user what changed:
Apollo Wind has been updated to vX.X.X. New components, styles, and templates are now available. You can start prototyping.
If already on the latest version:
Apollo Wind is up to date (vX.X.X). No changes needed.
After syncing, components are available at:
import { Button } from '@uipath/apollo-wind/components';
import { Card, CardContent } from '@uipath/apollo-wind/components';
import { DataTable } from '@uipath/apollo-wind/components';
For theming tokens and utilities:
import { cn } from '@uipath/apollo-wind/lib';
@uipath/apollo-wind not found on npm registry
The package may not yet be published. Ask the user to check back or use the local monorepo setup via apollo-install instead.
Styles not applying after update The CSS import may be missing. Re-check Phase 1b and ensure the import is at the top of the root CSS file.
Components not resolving after update
Re-run pnpm build or restart the dev server to pick up the updated package.