@mindstudio-ai/remy 0.1.30 → 0.1.31
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/headless.js
CHANGED
|
@@ -2579,7 +2579,7 @@ var DESIGN_REFERENCE_PROMPT = fs14.readFileSync(resolvePath("prompts/tool-prompt
|
|
|
2579
2579
|
var DESIGN_EXPERT_TOOLS = [
|
|
2580
2580
|
{
|
|
2581
2581
|
name: "searchGoogle",
|
|
2582
|
-
description:
|
|
2582
|
+
description: 'Search Google for web results. Reserch modern design trends in industries or verticals, "best [domain] apps 2026", ui patterns, etc. Prioritize authoritative sources like Figma and other design leaders, avoid random blog spam. Pick one or more URLs from the results and then use `fetchUrl` to get their text content.',
|
|
2583
2583
|
inputSchema: {
|
|
2584
2584
|
type: "object",
|
|
2585
2585
|
properties: {
|
|
@@ -2593,7 +2593,7 @@ var DESIGN_EXPERT_TOOLS = [
|
|
|
2593
2593
|
},
|
|
2594
2594
|
{
|
|
2595
2595
|
name: "fetchUrl",
|
|
2596
|
-
description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use
|
|
2596
|
+
description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use when reading sites from search results or specific things the user wants to incorporate.",
|
|
2597
2597
|
inputSchema: {
|
|
2598
2598
|
type: "object",
|
|
2599
2599
|
properties: {
|
package/dist/index.js
CHANGED
|
@@ -2700,7 +2700,7 @@ var init_tools2 = __esm({
|
|
|
2700
2700
|
DESIGN_EXPERT_TOOLS = [
|
|
2701
2701
|
{
|
|
2702
2702
|
name: "searchGoogle",
|
|
2703
|
-
description:
|
|
2703
|
+
description: 'Search Google for web results. Reserch modern design trends in industries or verticals, "best [domain] apps 2026", ui patterns, etc. Prioritize authoritative sources like Figma and other design leaders, avoid random blog spam. Pick one or more URLs from the results and then use `fetchUrl` to get their text content.',
|
|
2704
2704
|
inputSchema: {
|
|
2705
2705
|
type: "object",
|
|
2706
2706
|
properties: {
|
|
@@ -2714,7 +2714,7 @@ var init_tools2 = __esm({
|
|
|
2714
2714
|
},
|
|
2715
2715
|
{
|
|
2716
2716
|
name: "fetchUrl",
|
|
2717
|
-
description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use
|
|
2717
|
+
description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use when reading sites from search results or specific things the user wants to incorporate.",
|
|
2718
2718
|
inputSchema: {
|
|
2719
2719
|
type: "object",
|
|
2720
2720
|
properties: {
|
|
@@ -4,6 +4,8 @@
|
|
|
4
4
|
- Use `screenshot` to see the current state of the app preview. This is your primary tool for visual review. Use `fullPage: true` to see the entire page at once. Remember, the screenshot analysis is not overly precise - for example, it cannot reliably identify specific fonts by name — it can only describe what letterforms look like.
|
|
5
5
|
- Use `runBrowserTest` only to verify specific computed values that a screenshot can't tell you: exact font-family names, hex colors, pixel measurements, border-radius, box-shadow, transforms. Keep requests focused — ask it to check specific properties on specific elements, not to take screenshots or scroll around.
|
|
6
6
|
- **screenshot vs runBrowserTest**: Screenshot to *see* the page. Browser test to *measure* specific CSS values. Never use the browser agent for tasks your screenshot tool can handle, or vice versa.
|
|
7
|
+
Use `searchGoogle` for research: modern design trends in industries or verticals, "best [domain] apps 2026", ui patterns, etc. Prioritize authoritative sources like Figma and other design leaders, avoid random blog spam. Pick one or more URLs and use `fetchUrl` to get their text content to read and inform your inspiration.
|
|
8
|
+
- Use `fetchUrl` when you need to get the text content of a site.
|
|
7
9
|
- Use `searchGoogle` and `fetchUrl` only when the user references something specific: a particular website to match, a brand to look up, a company whose identity you need to research. You already have curated fonts, inspiration references, and strong internal knowledge — don't search the web for generic inspiration or "best X apps." The web is for specific lookups, not creative direction.
|
|
8
10
|
- When proposing multiple options, make them genuinely different directions (dark + bold vs. light + editorial) rather than minor variations.
|
|
9
11
|
- When multiple tool calls are independent, make them all in a single turn. Searching for three different products, or fetching two reference sites: batch them instead of doing one per turn.
|