add-addons-existing-app
Apply integrations to existing projects with tanstack add, including add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Apply integrations to existing projects with tanstack add, including add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions.
Build and iterate custom add-ons/templates with tanstack add-on init, add-on compile, add-on dev, and tanstack create --dev-watch, including sync loop preconditions, watch-path validation, and project metadata constraints.
Build a single C++ file. Use when a single .cc file needs to be compiled to check for errors.
Combines all git commits for a change into a single commit and pushes it to gerrit. Use when you push to gerrit.
Create Atomico web components using the `c()` function. Triggers when the user needs to create a new custom element, define reactive props, attach styles, or register a component with `customElements.define`. Do NOT trigger for React, Vue, or Angular component creation. Atomico components are functional web components that return JSX with a mandatory `<host>` root element.
Use the css tagged template literal and adoptedStyleSheets for styling Atomico components. Triggers when the user needs to style web components, use CSS custom properties, create themeable components, or understand how Atomico manages stylesheets. Do NOT trigger for external CSS frameworks unless combined with Atomico's css utility.
Use usePromise, useAsync, useSuspense, and useAbortController hooks for asynchronous data fetching and loading state management. Triggers when the user needs to fetch data, handle loading/error/fulfilled states, implement suspense boundaries, or abort in-flight requests in Atomico components.
Use core Atomico hooks: useState, useMemo, useCallback, useRef, useHost, useUpdate, useId, useHook. Triggers when the user needs local state management, memoization, DOM references, or access to the host element in Atomico components. Do NOT trigger for React hooks — Atomico hooks have the same API but run in a web component context with different lifecycle semantics.