@rayu-dev/rayu-cli 1.3.436 → 1.3.437

package/dist/rayu.js

@@ -181338,7 +181338,7 @@ function buildKiroPayload(params) {
   }
   if (images.length > 0)
     userMsg.images = images;
-  if (thinking && (userMsg.content !== "" || toolResults.length === 0)) {
+  if (thinking) {
     const prefix = `<thinking_mode>enabled</thinking_mode>
 <max_thinking_length>${thinkingBudget}</max_thinking_length>`;
     userMsg.content = userMsg.content !== "" ? `${prefix}
@@ -461734,7 +461734,7 @@ function SpinnerWithVerbInner({
   const tipsEnabled = settings.spinnerTipsEnabled !== false;
   const showClearTip = tipsEnabled && elapsedSnapshot > 1800000;
   const showBtwTip = tipsEnabled && elapsedSnapshot > 30000 && !getGlobalConfig().btwUseCount;
-  const effectiveTip = contextTipsActive ? undefined : showClearTip && !nextTask ? "Use /clear to start fresh when switching topics and free up context" : showBtwTip && !nextTask ? "Use /btw to ask a quick side question without interrupting Claude's current work" : spinnerTip;
+  const effectiveTip = contextTipsActive ? undefined : showClearTip && !nextTask ? "Use /clear to start fresh when switching topics and free up context" : showBtwTip && !nextTask ? "Use /btw to ask a quick side question without interrupting Rayu's current work" : spinnerTip;
   let budgetText = null;
   if (true) {
     const budget = getCurrentTurnTokenBudget();
@@ -521459,6 +521459,7 @@ function getSimpleDoingTasksSection() {
   ];
   const items = [
     `The user will primarily request you to perform software engineering tasks. These may include solving bugs, adding new functionality, refactoring code, explaining code, and more. When given an unclear or generic instruction, consider it in the context of these software engineering tasks and the current working directory. For example, if the user asks you to change "methodName" to snake case, do not reply with just "method_name", instead find the method in the code and modify the code.`,
+    `Before telling the user a task is done — especially after writing code, fixing a bug, or making any change — you MUST verify it actually works: run the project's build, tests, and linters (use the commands in RAYU.md/AGENTS.md when present), reproduce the original problem to confirm it is resolved, and fix any errors that surface. Do not report success or hand the task back to the user until verification passes, so they don't hit issues when they try it. If you genuinely cannot verify (no test exists or the code can't be run here), say so explicitly rather than implying it works.`,
     `You are highly capable and often allow users to complete ambitious tasks that would otherwise be too complex or take too long. You should defer to user judgement about whether a task is too large to attempt.`,
     ...[],
     `In general, do not propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.`,
@@ -521474,7 +521475,25 @@ function getSimpleDoingTasksSection() {
     `If the user asks for help or wants to give feedback inform them of the following:`,
     userHelpSubitems
   ];
-  return [`# Doing tasks`, ...prependBullets(items)].join(`
+  const minimalismSection = [
+    `## Keep it minimal — reuse before you build`,
+    ``,
+    `Prefer the simplest solution that actually works. Climb this ladder and stop at the first rung that holds:`,
+    `1. Does this need to exist at all? A speculative or "just in case" need is YAGNI — skip it and say so in one line.`,
+    `2. Does the standard library do it? Use it.`,
+    `3. Does a native platform feature cover it? (CSS over JS, a DB constraint over app code, a built-in over a hand-rolled equivalent.)`,
+    `4. Does an already-installed dependency solve it? Use it — never add a new dependency for what a few lines can do.`,
+    `5. Can it be one line? Make it one line.`,
+    `6. Only then write the minimum code that works.`,
+    `Two rungs work → take the higher one and move on. The first simple solution that works is the right one.`,
+    ``,
+    `- Before creating a new component, widget, hook, utility, type, or adding a library: first search the codebase for an existing one and reuse or extend it — do not duplicate or reinvent. Match the patterns, conventions, and libraries already in use.`,
+    `- No unrequested abstractions (no interface with one implementation, no factory for one product, no config for a value that never changes) and no boilerplate or scaffolding "for later". Prefer deletion over addition, boring over clever, and the shortest working diff.`,
+    `- Don't cram everything into one file — split responsibilities into appropriately-scoped, well-named modules so the code stays readable and scales as it grows.`,
+    `- For a complex request, ship the minimal version and flag what you skipped in the same response (e.g. "Did X; Y likely covers it — want the full version?") rather than over-building. When two options are the same size, pick the one that is correct on edge cases — minimal means less code, not a flimsier algorithm.`
+  ].join(`
+`);
+  return [`# Doing tasks`, ...prependBullets(items), ``, minimalismSection].join(`
 `);
 }
 function getActionsSection() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayu-dev/rayu-cli",
-"version": "1.3.436",
+"version": "1.3.437",
   "description": "Rayu-CLI — a multi-provider AI coding CLI",
   "type": "module",
   "bin": {