Find and pull any UI component
What it does
Find the right UI component, chart, block or template for a need across hundreds of design sources, check that its licence allows the person's use, pull its code from the source itself, and adapt it into the person's own project or their Trillion look with the credit kept. The person's own AI does every step; search by meaning happens by that AI turning the need into several word searches.
What it needs
{"type":"object","required":["need","into"],"properties":{"need":{"type":"string","minLength":5,"description":"What the person needs, in their words, for example a pricing table with a monthly and yearly switch"},"into":{"type":"string","minLength":3,"description":"Where it goes: a project folder and its framework (for example React with Tailwind), or 'my Trillion look'"},"use":{"type":"string","minLength":3,"description":"How it will be used: in something sold, internal only, or personal. Decid
Steps
1. Turn the need into at least three different word searches (the component's common names, synonyms, the job it does). Run each with search_shared_library on dataset design-components, filtered by framework or kind when that helps, and look up each candidate's source in dataset design-sources. Keep the best candidates with their entry id, source, licence and item address. Prefer can_ship entries when the use is in something sold. · 2. Open the chosen candidate's licence where the code lives (its repository LICENSE file, the registry's terms, or the site's licence page) at the exact version you will pull. The catalogue's licence field is a lead, never the proof. Say whether it fits the person's use and what credit it asks for. If it does not fit, go back to the next candidate. · 3. Pull the code the way the source says (its how_to_pull: a registry command, a CLI, its MCP, or the repository files) at an exact version or commit. Never retype it from a screenshot and never take it from a copy that is not the source. · 4. Fit it into what already exists: the project's own components, design tokens, fonts and colours, or the person's Trillion look. Reuse a part that already does the job instead of adding a second one. Keep the credit line and the licence text beside the adapted files. Run the project's checks or tests. · 5. Show the component working in the person's project or Trillion at phone and desktop widths with a picture or recording, and keep the adoption as a row in the person's own list of components they use (name, source, licence, where it is used), so the next search knows it is already in use.