@ryuxdsgn/design-intelligence 2.13.7 → 2.13.8

package/dist/cli/index.js

@@ -167,16 +167,22 @@ async function runInstall(flags) {
     }
     if (nonInteractive)
         return;
+    let answers = {};
     if (!scope.global) {
         const s = await p.confirm({ message: "Set up project context now? Every question can be skipped.", initialValue: true });
         if (p.isCancel(s))
             return cancel();
-        if (s && !(await setupInteractive(scope.root)))
-            return cancel();
-        if (!s)
+        if (s) {
+            const a = await setupInteractive(scope.root);
+            if (!a)
+                return cancel();
+            answers = a;
+        }
+        else
             p.log.info(`Set it up later with: ${CLI_CMD} setup`);
     }
-    p.outro(`RYUX is ready. Try: ${pc.cyan('"Design a transaction detail page for our app."')}`);
+    p.note(suggestionsText(answers), "Try");
+    p.outro("RYUX is ready.");
 }
 async function runUpdate(flags) {
     const scope = scopeOf(flags);
@@ -578,11 +584,40 @@ async function setupInteractive(root) {
     p.log.info("Teach RYUX about this project. Every question can be skipped: blanks stay unknown, and RYUX asks when they matter.");
     const answers = await askContext(root);
     if (!answers)
-        return false;
+        return null;
     const body = await writeContext(root, answers);
     p.log.success(`${CONTEXT_FILE} updated · ${filledCount(body)} of ${ASKED_FIELDS.length} setup fields filled`);
-    return true;
+    return answers;
+}
+/** Curated, per product kind (setup's Product answer): a typical screen and flow to name in example prompts. */
+const SUGGESTED = {
+    "Online store": { screen: "the checkout page", flow: "our checkout flow" },
+    "Payments or finance": { screen: "the transaction detail screen", flow: "our send-money flow" },
+    "Marketplace": { screen: "the seller's new listing form", flow: "our listing flow" },
+    "Booking or scheduling": { screen: "the date and time slot picker", flow: "our booking flow" },
+    "SaaS or dashboard": { screen: "the billing settings page", flow: "our onboarding flow" },
+    "Content or media": { screen: "the article reading page", flow: "our sign-up flow" },
+    "Internal tool": { screen: "the orders table with filters", flow: "our approval flow" },
+};
+/** Three concrete prompts, one per entry point, from the setup answers; the README examples when there are none. */
+function promptSuggestions(answers) {
+    const kind = Object.keys(SUGGESTED).find((k) => (answers["Product"] ?? "").startsWith(k));
+    if (!kind) {
+        return [
+            "Design the transaction detail screen for our wallet, in pen.dev.",
+            "Critique our pricing page at https://example.com/pricing.",
+            "Analyze this checkout screen (screenshot attached).",
+        ];
+    }
+    const { screen, flow } = SUGGESTED[kind];
+    const changing = /existing flow|redesign/i.test(answers["Current work"] ?? "");
+    return [
+        `Design ${screen} for our app.`,
+        `Critique ${flow} and tell us what to fix first.`,
+        changing ? `Analyze ${flow} before we change it (screenshots attached).` : `QA the build of ${screen} against the design.`,
+    ];
 }
+const suggestionsText = (answers) => [...promptSuggestions(answers).map((s) => `"${s}"`), "", "RYUX may ask up to three questions first."].join("\n");
 async function runSetup(flags) {
     if (flags.global) {
         console.error(`setup is per project. Run it inside the project folder: ${CLI_CMD} setup`);
@@ -599,6 +634,7 @@ async function runSetup(flags) {
     if (Object.keys(fromFlags).length) {
         const body = await writeContext(root, fromFlags);
         console.log(`${pc.green("✓ ")}${CONTEXT_FILE} updated · ${filledCount(body)} of ${ASKED_FIELDS.length} setup fields filled`);
+        console.log(`\nTry:\n${suggestionsText(fromFlags).split("\n").map((l) => (l ? `  ${l}` : "")).join("\n")}`);
         return;
     }
     if (!process.stdin.isTTY) {
@@ -609,8 +645,10 @@ async function runSetup(flags) {
     }
     p.intro(pc.bgCyan(pc.black(" RYUX setup ")));
     p.log.message(KEY_LEGEND);
-    if (!(await setupInteractive(root)))
+    const answers = await setupInteractive(root);
+    if (!answers)
         return cancel();
+    p.note(suggestionsText(answers), "Try");
     p.outro(`RYUX is ready. Next: ${CLI_CMD} check`);
 }
 async function runInit(flags) {

package/dist/intelligence/content.js

@@ -130,6 +130,19 @@ export const RULES = [
             basis: "ryux evidence principle",
             check: "review",
         },
+        {
+            num: 11,
+            title: "An AI feature has a written standard for its output",
+            level: "contextual",
+            when: "the product shows content generated by AI: an answer, a summary, a draft, a recommendation",
+            do: "Before designing it, write what good and bad output look like, per kind of response:\n  - Sort the responses the feature gives (a short answer, an open explanation, a list, a draft, a refusal) and write pass criteria for each kind, concrete enough for a reviewer to check: \"answers the question in the first sentence; at most two related details\", not \"not too verbose\".\n  - Design the states generated output brings: a long and a short answer, no answer or a refusal, an answer that is wrong, slow generation, and a failed request (RX-EC-01).\n  - Hand the criteria to the team as the feature's test: real inputs checked against them before launch, and again after every model or prompt change.",
+            dont: "Design an AI feature around one ideal sample answer, judge its output by feel, or leave out the states where the output is wrong, empty, or slow.",
+            why: "Generated output cannot be specified exactly, so the design is only as good as its definition of good; a screen built around one perfect answer breaks on the next one.",
+            basis: "NNGroup design critique in the AI era (criteria per response type; judge, evaluate, iterate; watch for regressions); RX-EC-01",
+            notWhen: "AI that works behind the scenes and shows users no generated content",
+            tradeoff: "criteria per response type take time before the first screen and need real inputs to write well",
+            check: "review: a criteria list per response type, and the wrong, empty, slow, and failed states in the design",
+        },
     ]),
     ...skill("ux", [
         {
@@ -1508,6 +1521,7 @@ export const ACTIVATION = [
     { task: "Checkout or payment", skills: ["product", "interaction", "forms", "content", "edge-cases", "ui", "anti-slop"] },
     { task: "Data-heavy view (list, table, dashboard)", skills: ["ux", "edge-cases", "responsive", "design-system", "frontend", "ui", "anti-slop"] },
     { task: "Frontend logic or utilities (formatting, state, data shown to users)", skills: ["frontend", "content", "edge-cases"] },
+    { task: "AI feature (generated answers, summaries, drafts)", skills: ["product", "ux", "content", "edge-cases", "anti-slop"] },
     { task: "Copy only (UI text, chat, announcements)", skills: ["content", "anti-slop"] },
     { task: "Visual refinement", skills: ["ui", "design-system", "visual-qa", "anti-slop"] },
 ];

package/dist/intelligence/guides.js

@@ -11,8 +11,8 @@ generator, an anti-slop framework, a design system, or a prompt library.
 \`\`\`
 Understand → Frame → Explore → Evaluate and select → Build and critique → Verify and deliver → done
 \`\`\``;
-export const CORE_CAPABILITIES = `Tell RYUX what you are doing; RYUX decides what it needs to know. Pick the entry point, read its
-file, then only the knowledge modules the task needs (task table below); paths are relative to this skill's folder.
+export const CORE_CAPABILITIES = `Tell RYUX what you are doing; RYUX decides what it needs to know (no task named: offer three concrete tasks for this project as choices,
+from DESIGN.md and the repo's screens). Pick the entry point, read its file, then only the knowledge modules the task needs (task table below); paths are relative to this skill's folder.
 
 | Entry point | When | Read |
 | --- | --- | --- |
@@ -25,9 +25,8 @@ file, then only the knowledge modules the task needs (task table below); paths a
 Knowledge modules (\`knowledge/\`): product, ux, interaction, forms, edge-cases, content, ui,
 design-system, accessibility, responsive, frontend, and anti-slop. Evidence comes from the brief, the
 project, product data, standards, and the ryux MCP when connected; none is required. Every entry point ends at the quality gates: the Hard
-Gates below and the Delivery Gate, with anti-slop as the last check, never the starting point.
-
-Keep them apart: Analyze says what exists, Design what to do, Critique if it is right, QA if it matches.`;
+Gates below and the Delivery Gate, with anti-slop as the last check, never the starting point. Keep them apart:
+Analyze says what exists, Design what to do, Critique if it is right, QA if it matches.`;
 export const CORE_PRINCIPLE = `Novelty is not a goal; a recognisable brand layer is: familiar structure, distinct surface.
 Optimize for clarity, usability, consistency, product fit, accessibility, and intentional decisions.
 Understand the context first; keep observed facts apart from assumptions; prefer evidence over
@@ -44,7 +43,7 @@ export const CORE_WORKFLOW = `One workflow, six stages; each entry point runs th
 3. **Explore**: on a new or complex surface, two or three alternatives that differ in hypothesis and
    structure, not paint; reference screens through the ryux MCP when connected. A small change skips it.
 4. **Evaluate and select**: rate the alternatives against the Frame criteria with evidence
-   (RX-PR-09, RX-PR-10); the user picks; write the Decision Receipt.
+   (RX-PR-09, RX-PR-10); the user picks from options (capabilities/design.md); write the Decision Receipt.
 5. **Build and critique**: design or implement the choice, render, inspect, and fix; Reconsider an
    unchosen alternative when a finding contradicts the choice, and say why.
 6. **Verify and deliver**: Hard Gates, the Delivery Gate, honest claims, and a user test plan (RX-UX-12).
@@ -73,7 +72,11 @@ The six stages of the core workflow (SKILL.md), as Design runs them.
    (character, or brand colour and type) or the motion direction, ask for it in that message (it
    counts toward the three) instead of choosing it yourself. **No DESIGN.md and no product docs is the
    case where these questions matter most, never a reason to skip them:** ask, then wait for the
-   answer before designing. Complete context means no questions. Never ask what the prompt, DESIGN.md, or the
+   answer before designing. Complete context means no questions.
+   **Ask as choices.** When you ask, or the user picks (stage 4, Reconsider), use the agent's
+   question or choice tool if it has one: two to four options per question, the recommended one
+   first and labeled, and room for the user's own answer. Without such a tool, write numbered
+   options with the recommendation first, so the user can answer with a number. Never ask what the prompt, DESIGN.md, or the
    product docs already answer. For the rest, make the smallest reasonable assumption, write it
    down, and continue (RX-PR-01, RX-PR-02).
    **Record direction answers.** When the user answers a UI or motion direction question, write the
@@ -116,7 +119,8 @@ The six stages of the core workflow (SKILL.md), as Design runs them.
    - A small change, or a screen inside a fixed design system, skips Explore: say so and continue.
 4. **Evaluate and select.** Rate each alternative against the Frame criteria, Strong, Adequate, or
    Weak with one reason each, rate the evidence (RX-PR-10), and recommend one with a Decision Receipt.
-   "It looks better" is not a reason. Then stop and let the user choose. Build only the chosen one
+   "It looks better" is not a reason. Then stop and let the user choose, with the alternatives as
+   options and your recommendation first (stage 1, "Ask as choices"). Build only the chosen one
    into the full design (states, widths, Visual Brief, RX-UI-10), write the Design Direction
    below, and mark the others on the canvas as not chosen. When the user has already said to pick for
    them, continue with the recommendation and say so.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ryuxdsgn/design-intelligence",
-  "version": "2.13.7",
+  "version": "2.13.8",
   "description": "RYUX: design intelligence for AI agents and designers. One skill, five entry points: Analyze, Design, Build, Critique, and QA, for Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Cline, Copilot, and more.",
   "type": "module",
   "bin": {