@ryuxdsgn/design-intelligence 2.19.1 → 2.19.3

package/dist/intelligence/content.js

@@ -102,10 +102,10 @@ export const RULES = [
             num: 5,
             title: "The product's market first",
             level: "required",
-            do: "Start from how users in the product's own market pay, sign in, write addresses, and read money and dates; check a pattern from another market before reusing it.\n  - Take the market from the brief or the codebase, and ask when it is unclear.\n  - When the brief does not name payment methods (or another market-standard capability), show the market's standard set as unconfirmed capabilities, labeled as proposed in Assumptions, rather than leaving them out: a market's table stakes are not \"for later\" (RX-AS-06). Ask when the set would change the flow.",
+            do: "Start from how users in the product's own market pay, sign in, write addresses, and read money and dates; check a pattern from another market before reusing it.\n  - Take the market from the brief or the codebase, and ask when it is unclear. When you ask, propose no market as your default: RYUX's own examples are Indonesian, the product may not be. If you must proceed without an answer, follow the brief's language and its common currency, and list it under Assumptions.\n  - When the brief does not name payment methods (or another market-standard capability), show the market's standard set as unconfirmed capabilities, labeled as proposed in Assumptions, rather than leaving them out: a market's table stakes are not \"for later\" (RX-AS-06). Ask when the set would change the flow.",
             dont: "Import one market's checkout, currency, language, or tax rules into a product built for another market.",
             why: "Payment, address, and trust habits differ by market (local payment rails, address formats, messaging channels).",
-            basis: "ryux taxonomy of local patterns",
+            basis: "ryux taxonomy of local patterns; wallet-detail benchmark, 2.19.2: 3 of 3 runs proposed Indonesia and IDR as the default for a brief with no market",
             check: "search_screens",
             formerly: ["RX-L-08"],
         },
@@ -1393,10 +1393,10 @@ export const RULES = [
             title: "Sample data is realistic and labeled; placeholders only for what is missing",
             level: "required",
             gate: "hard",
-            do: "Fill mockups with realistic sample content consistent with the brief (names, merchants, amounts in the brief's currency, dates) and list it as sample data in the output. Keep a visible placeholder only for an asset that does not exist yet, such as [LOGO].",
+            do: "Fill mockups with realistic sample content consistent with the brief (names, merchants, amounts in the brief's currency, dates). Names are made up, including merchants, banks, and card networks: a real brand on a sample card or receipt reads as a partnership and list it as sample data in the output. Keep a visible placeholder only for an asset that does not exist yet, such as [LOGO].",
             dont: "Put [REAL DATA], XXX, or lorem text on the canvas where sample data would do, or ship sample data or placeholder copy as final. A sample-data label does not turn a fee, policy, or claim into a fact (RX-PR-02).",
             why: "Bracketed values read as unfinished and hide the layout's real behavior; unlabeled sample data ships by accident.",
-            basis: "ryux anti-slop principle; ryux visual benchmark 2.5, 2026-10-09: [Brand] and XXX read as unfinished",
+            basis: "ryux anti-slop principle; ryux visual benchmark 2.5, 2026-10-09: [Brand] and XXX read as unfinished; wallet-detail benchmark, 2.19.2: 3 of 3 runs showed Visa on a sample card",
             check: "audit_copy C-01",
             formerly: ["RX-C-05"],
         },

package/dist/intelligence/guides.js

@@ -65,7 +65,10 @@ The six stages of the core workflow (SKILL.md), as Design runs them.
    affects the user flow, what the product can do, or whether the content is correct, those
    questions alone, most consequential first, at most three, in one message, before designing.
    A product rule that changes which states or actions the screen has (refunds, fees, what happens
-   on failure) is a major decision. When the prompt and DESIGN.md disagree, the prompt wins for
+   on failure) is a major decision. **Market:** when the prompt, DESIGN.md, and the product docs
+   name no market, ask with no market as the recommended default; RYUX's examples are Indonesian
+   (Rp, id-ID), the product may not be. Without an answer, follow the prompt's language and that
+   language's common currency, as an assumption (RX-PR-05). When the prompt and DESIGN.md disagree, the prompt wins for
    this task; say so. A DESIGN.md written for a different product (another name, domain, or
    audience than this brief) sets no direction for this task: say so, and treat direction as unset.
    **Direction is the user's call:** when neither the prompt nor DESIGN.md sets the UI direction
@@ -281,8 +284,12 @@ workflow (SKILL.md); Frame, Explore, and Evaluate happen in Design.
    used (where components, state, pure logic, and data access live), and the test runner
    (knowledge/frontend.md, knowledge/design-system.md). Reuse before creating.
 2. **Find the design source**: the Design Direction, a Figma or pen.dev design, a DESIGN.md, or an
-   approved mockup; it is the spec. If there is none, run Design's Frame, Explore, and Evaluate
-   first (capabilities/design.md, stages 2-4) instead of inventing one in code.
+   approved mockup; it is the spec. If there is none, run Design's stages 1-4 first
+   (capabilities/design.md) instead of inventing one in code. Stage 1's questions come first even
+   when the request is a quick build or a working prototype: ask the ones whose answers change what
+   gets built (a product rule such as fees, refunds, or what happens on failure; the market, with
+   no default market when nothing names one; the data), at most three, in one message, and wait. A prototype may skip only the choice between
+   directions: build the recommended one and name the alternatives you did not build.
    A screenshot or another product's page is a reference, not the spec, unless the user asks to
    recreate it ("recreate", "match this", "samakan"). Then match it, let QA compare at the same
    viewport, and still leave out another product's brand, logo, and content (RX-AS-11). With no word

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ryuxdsgn/design-intelligence",
-  "version": "2.19.1",
+  "version": "2.19.3",
   "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": {