@simplysm/sd-claude 13.0.78 → 13.0.80

package/claude/refs/sd-orm.md

@@ -1,23 +0,0 @@
-# ORM Guidelines
-
-## Table Definition
-
-```typescript
-const User = Table("User")
-  .database("mydb")
-  .columns((c) => ({ id: c.bigint().autoIncrement(), name: c.varchar(100) }))
-  .primaryKey("id");
-```
-
-## SQL Injection Prevention
-
-ORM uses string escaping (not parameter binding). **Always validate user input before ORM queries.**
-
-```typescript
-const userId = Number(req.query.id);
-if (Number.isNaN(userId)) throw new Error("Invalid ID");
-await db
-  .user()
-  .where((u) => [expr.eq(u.id, userId)])
-  .result();
-```

package/claude/refs/sd-service.md

@@ -1,5 +0,0 @@
-# Service Guidelines
-
-- `ServiceServer`: Fastify-based HTTP/WebSocket server
-- `ServiceClient`: WebSocket client, RPC calls
-- `ServiceProtocol`: Message split/merge (300KB chunks when >3MB)

package/claude/refs/sd-simplysm-docs.md

@@ -1,52 +0,0 @@
-# @simplysm Package Documentation
-
-When you need API details, usage examples, or component props for `@simplysm/*` packages,
-read the package's README.md from node_modules.
-
-## How to use
-
-Read the package README directly:
-
-```
-node_modules/@simplysm/{package-name}/README.md
-```
-
-If not found (pnpm hoisting), try:
-
-```
-packages/*/node_modules/@simplysm/{package-name}/README.md
-```
-
-## When to use
-
-**MANDATORY**: Read the relevant README BEFORE any of the following:
-
-- Writing new code that uses `@simplysm/*` APIs
-- Fixing type errors or bugs in code that uses `@simplysm/*` APIs
-- Making assumptions about type mappings (e.g., DB column types → TypeScript types)
-- Refactoring or migrating code that depends on `@simplysm/*` packages
-
-Do NOT guess API behavior or type mappings — always verify from the README first.
-
-## Available Packages
-
-| Package                        | Description                                                     |
-| ------------------------------ | --------------------------------------------------------------- |
-| `core-common`                  | Common utilities, custom types (DateTime, DateOnly, Time, Uuid) |
-| `core-browser`                 | Browser-specific extensions                                     |
-| `core-node`                    | Node.js utilities (filesystem, workers)                         |
-| `orm-common`                   | ORM query builder, table schema definitions                     |
-| `orm-node`                     | DB connectors (MySQL, MSSQL, PostgreSQL)                        |
-| `service-common`               | Service protocol, type definitions                              |
-| `service-client`               | WebSocket client                                                |
-| `service-server`               | Fastify-based HTTP/WebSocket server                             |
-| `solid`                        | SolidJS UI components + Tailwind CSS                            |
-| `excel`                        | Excel (.xlsx) read/write                                        |
-| `storage`                      | FTP/SFTP client                                                 |
-| `sd-cli`                       | Build, lint, typecheck CLI tool                                 |
-| `claude`                       | Claude Code skills/agents (auto-installs via postinstall)       |
-| `eslint-plugin`                | Custom ESLint rules                                             |
-| `capacitor-plugin-auto-update` | Auto update                                                     |
-| `capacitor-plugin-broadcast`   | Broadcast                                                       |
-| `capacitor-plugin-file-system` | File system                                                     |
-| `capacitor-plugin-usb-storage` | USB storage                                                     |

package/claude/refs/sd-solid.md

@@ -1,68 +0,0 @@
-# SolidJS Guidelines
-
-**SolidJS is NOT React!**
-
-## Core Concepts
-
-- Component functions run **once** at mount (not on every state change)
-- Fine-grained reactivity: unchanged signals don't re-evaluate expressions
-- `createMemo`: only for expensive computations used in multiple places
-- **Props destructuring prohibited** → use `props.xxx`
-- Conditionals: `<Show>`, Lists: `<For>`
-- No SSR → browser APIs usable directly
-- Responsive: Mobile UI below 520px
-- Chrome 84+ target
-  - CSS NOT transpiled → no `aspect-ratio`, `inset`, `:is()`, `:where()`
-
-## Props Design
-
-- Props that don't need parameters must accept plain values (`editable={perms().edit}`), not wrapped in functions (`editable={() => perms().edit}`) — use function props only when parameters are needed (callbacks)
-
-## Implementation Rules
-
-- Prefer signals/stores over Provider/Context
-- Check existing patterns before introducing abstractions
-- Before modifying components: always Read the file to check existing props/patterns
-
-## Hook Naming
-
-- `create*`: Reactive hooks wrapping SolidJS primitives
-- `use*`: Hooks depending on Provider Context
-- Others: no hook prefix
-
-## Compound Components
-
-All sub-components via dot notation only (`Parent.Child`).
-
-- Export using `Object.assign` pattern:
-  ```ts
-  export const Select = Object.assign(SelectInnerComponent, {
-    Item: SelectItem,
-    Header: SelectHeader,
-    Action: SelectAction,
-    ItemTemplate: SelectItemTemplate,
-  });
-  ```
-- Do NOT declare a separate type or interface for the compound component (e.g., `SelectComponent`, `TabsComponent`)
-- Do NOT use type assertions on the export (e.g., `as SelectComponent`)
-- Don't export sub-components separately (export parent only)
-- UI elements → compound sub-components, non-rendering config (state, behavior, callbacks) → props
-
-## Tailwind CSS
-
-- `darkMode: "class"`, `aspectRatio` plugin disabled (Chrome 84)
-- Semantic colors: `primary`(blue), `info`(sky), `success`(green), `warning`(amber), `danger`(red), `base`(zinc) → never use `zinc-*` directly
-- Heights: `field`, `field-sm`, `field-lg`
-- z-index: `sidebar`(100), `sidebar-backdrop`(99), `dropdown`(1000)
-- Default `rem`, use `em` for text-relative sizing (e.g., Icon)
-- Use `clsx()` with semantic grouping + `twMerge()` for conflict resolution
-- Before modifying styles: Read existing class patterns of the same component
-- **Class strings inline**: Do not extract class strings into separate variables — write them directly in the JSX return
-- **`*.styles.ts` files**: Tailwind class strings must be wrapped with `clsx()` for IntelliSense support
-
-## Application View Naming (`client-*`)
-
-- `~Sheet` — List view based on DataSheet (e.g., `UserSheet`)
-- `~Detail` — Single record detail/edit view (e.g., `MyInfoDetail`)
-- `~View` — Everything else (e.g., `LoginView`, `MainView`)
-- Directory: `src/views/` (usable as standalone page, embedded component, or modal)

package/claude/refs/sd-workflow.md

@@ -1,25 +0,0 @@
-# Workflow Rules
-
-- **No auto-proceeding after skill completion**: When the user explicitly invokes a skill, report the result and **stop** once the skill finishes. Do not guess the next step and proceed arbitrarily. Wait for explicit user instructions if further work is needed.
-  - **Exception — yolo mode**: When a skill explicitly defines a "yolo mode" that chains multiple skills sequentially (e.g., sd-plan's "Path A: yolo"), auto-proceeding is permitted for the duration of that chain. Each step MUST still be invoked via the Skill tool.
-
-## Problem-Solving Principles
-
-- **Root cause first**: When encountering errors or unexpected behavior, always investigate the root cause before attempting a fix. Do not apply workarounds, hacks, or surface-level patches.
-- **No band-aid fixes**: Avoid techniques like suppressing errors, adding defensive checks to hide symptoms, bypassing validation, or inflating timeout values. These mask the real problem and create technical debt.
-- **Consider refactoring**: If the root cause reveals a design flaw or structural issue, propose a refactoring approach rather than working around it. A proper fix — even if larger in scope — is better than a fragile workaround.
-- **Trace the full chain**: Follow the error or issue through the entire call chain (caller -> callee -> dependencies) to understand why it happens, not just where it happens.
-- **When uncertain, ask**: If the root cause is unclear or the fix requires significant changes, discuss with the user before proceeding. Present findings and options rather than silently applying a quick fix.
-
-## Pre-coding Checklist
-
-- Before creating new files: Glob/Read similar existing files to check structure and patterns
-- Before modifying functions/classes: Read the file to understand existing code style
-- When unsure about API/method usage: Check signatures in source code
-- **Always search the local codebase first.** Do not search the web or external docs until you have confirmed the answer is not in local code.
-- **If confidence is low, ask the user instead of writing code**
-
-## Memory Policy
-
-- **Do NOT use auto memory** (`~/.claude/projects/.../memory/`). It is environment-specific and does not persist across machines.
-- All persistent knowledge belongs in `.claude/rules/` or project docs (committed to git).

package/claude/rules/sd-refs-linker.md

@@ -1,52 +0,0 @@
-# Reference Guide
-
-Before starting work, **Read** the relevant reference files from `.claude/refs/`.
-
-## Version Detection
-
-Determine the major version by the `version` field in `package.json`.
-
-- `12.x.x` → **v12** (< 13)
-- `13.x.x` → **v13** (>= 13)
-
-## Common (all versions)
-
-| When                                             | Read this file                        |
-| ------------------------------------------------ | ------------------------------------- |
-| Writing, modifying, or reviewing code            | `.claude/refs/sd-code-conventions.md` |
-| Working with `.cache/` or Playwright screenshots | `.claude/refs/sd-directories.md`      |
-| Using `@simplysm/*` package APIs                 | `.claude/refs/sd-simplysm-docs.md`    |
-| Debugging, problem-solving, or planning approach | `.claude/refs/sd-workflow.md`         |
-| Using `@simplysm/service-*` packages            | `.claude/refs/sd-service.md`          |
-| Migrating/porting code from another codebase     | `.claude/refs/sd-migration.md`        |
-| Debugging in a project that uses `@simplysm/*` as an external dependency (not the simplysm monorepo itself) | `.claude/refs/sd-library-issue.md` |
-
-## v12 only (< 13)
-
-| When                                   | Read this file               |
-| -------------------------------------- | ---------------------------- |
-| Working on Angular / @simplysm/sd-angular | `.claude/refs/sd-angular.md` |
-| Using `@simplysm/sd-orm-*` packages    | `.claude/refs/sd-orm-v12.md` |
-
-- v12 is **Angular** based (no SolidJS)
-- ORM uses **decorator** pattern (`@Table`, `@Column`)
-- Package names: use `sd-` prefix (`sd-core-common`, `sd-orm-common`, etc.)
-- Package manager: **yarn**
-
-## v13 only (>= 13)
-
-| When                                         | Read this file             |
-| -------------------------------------------- | -------------------------- |
-| Working on SolidJS / @simplysm/solid / Tailwind | `.claude/refs/sd-solid.md` |
-| Using `@simplysm/orm-*` packages             | `.claude/refs/sd-orm.md`   |
-
-- v13 is **SolidJS** based (no Angular)
-- ORM uses **functional builder** pattern (`Table().columns().primaryKey()`)
-- Package names: no prefix (`core-common`, `orm-common`, etc.)
-- Package manager: **pnpm**
-
-## Rules
-
-- Read the reference BEFORE starting the related work (not after)
-- You may read multiple references if the task spans multiple areas
-- If unsure whether a reference applies, read it — the cost of reading is low

package/claude/sd-statusline.js

@@ -1,296 +0,0 @@
-// @ts-check
-import fs from "fs";
-import os from "os";
-import path from "path";
-import { stdin } from "process";
-
-//#region Constants
-
-const STDIN_TIMEOUT_MS = 5000;
-const FETCH_TIMEOUT_MS = 3000;
-const CACHE_TTL_MS = 60_000; // 1 minutes
-const CACHE_PATH = path.join(os.homedir(), ".claude", "usage-api-cache.json");
-
-//#endregion
-
-//#region Stdin
-
-/** @returns {Promise<string>} */
-function readStdin() {
-  return new Promise((resolve) => {
-    let data = "";
-
-    const cleanup = () => {
-      stdin.removeAllListeners("data");
-      stdin.removeAllListeners("end");
-      stdin.removeAllListeners("error");
-    };
-
-    const timeout = setTimeout(() => {
-      cleanup();
-      resolve("");
-    }, STDIN_TIMEOUT_MS);
-
-    stdin.setEncoding("utf8");
-    stdin.on("data", (chunk) => {
-      data += chunk;
-    });
-    stdin.on("end", () => {
-      clearTimeout(timeout);
-      cleanup();
-      resolve(data);
-    });
-    stdin.on("error", () => {
-      clearTimeout(timeout);
-      cleanup();
-      resolve("");
-    });
-  });
-}
-
-//#endregion
-
-//#region OAuth
-
-/** @returns {string | undefined} */
-function getOAuthToken() {
-  try {
-    const configDir = process.env.CLAUDE_CONFIG_DIR ?? path.join(os.homedir(), ".claude");
-    const credentialsPath = path.join(configDir, ".credentials.json");
-    if (!fs.existsSync(credentialsPath)) {
-      return undefined;
-    }
-
-    const content = fs.readFileSync(credentialsPath, "utf-8");
-    const credentials = JSON.parse(content);
-    const oauth = credentials.claudeAiOauth;
-
-    // Check token expiration
-    if (oauth?.expiresAt != null && Date.now() > oauth.expiresAt) {
-      return undefined;
-    }
-
-    return oauth?.accessToken;
-  } catch {
-    return undefined;
-  }
-}
-
-/**
- * Read cached usage data from local file.
- * @returns {{ data: object, timestamp: number } | undefined}
- */
-function readCache() {
-  try {
-    if (!fs.existsSync(CACHE_PATH)) return undefined;
-    const content = fs.readFileSync(CACHE_PATH, "utf-8");
-    return JSON.parse(content);
-  } catch {
-    return undefined;
-  }
-}
-
-/**
- * Write usage data to local cache file.
- * @param {object} data
- */
-function writeCache(data) {
-  try {
-    fs.writeFileSync(CACHE_PATH, JSON.stringify({ data, timestamp: Date.now() }), "utf-8");
-  } catch {
-    // ignore write errors
-  }
-}
-
-/**
- * Fetch Anthropic API usage information using OAuth token, with 1-minute cache.
- * @param {string} token - OAuth access token
- * @param {string} version - Claude Code version
- * @returns {Promise<{
- *   seven_day?: {utilization?: number, resets_at?: string},
- *   daily?: {utilization?: number, resets_at?: string},
- *   five_hour?: {utilization?: number, resets_at?: string},
- *   extra_usage?: {is_enabled?: boolean, monthly_limit?: number | null, used_credits?: number}
- * } | undefined>}
- */
-async function fetchUsage(token, version) {
-  // Return cached data if still valid
-  const cache = readCache();
-  if (cache != null && Date.now() - cache.timestamp < CACHE_TTL_MS) {
-    return cache.data;
-  }
-
-  try {
-    const controller = new AbortController();
-    const timeout = setTimeout(() => controller.abort(), FETCH_TIMEOUT_MS);
-
-    const response = await fetch("https://api.anthropic.com/api/oauth/usage", {
-      headers: {
-        "Authorization": `Bearer ${token}`,
-        "Accept": "application/json",
-        'anthropic-beta': 'oauth-2025-04-20'
-      },
-      signal: controller.signal,
-    });
-
-    clearTimeout(timeout);
-
-    if (!response.ok) {
-      // API failed — update timestamp to prevent retry for TTL duration
-      writeCache(cache?.data ?? {});
-      return undefined;
-    }
-
-    const data = await response.json();
-
-    if (data == null || typeof data !== "object") {
-      writeCache(cache?.data ?? {});
-      return undefined;
-    }
-
-    writeCache(data);
-    return data;
-  } catch {
-    // Network error — update timestamp to prevent retry for TTL duration
-    writeCache(cache?.data ?? {});
-    return undefined;
-  }
-}
-
-//#endregion
-
-//#region Formatting
-
-/**
- * @param {number | undefined} value
- * @returns {string}
- */
-function formatPercent(value) {
-  if (value == null) return "?";
-  return Math.round(value).toString();
-}
-
-/**
- * @param {string | undefined} isoDate
- * @returns {string}
- */
-function formatTimeRemaining(isoDate) {
-  if (isoDate == null) return "";
-  try {
-    const resetTime = new Date(isoDate).getTime();
-    if (Number.isNaN(resetTime)) return "";
-
-    const now = Date.now();
-    const diffMs = resetTime - now;
-
-    if (diffMs <= 0) return "";
-
-    const diffMinutes = Math.floor(diffMs / (1000 * 60));
-    const diffHours = Math.floor(diffMinutes / 60);
-    const days = Math.floor(diffHours / 24);
-    const hours = diffHours % 24;
-    const minutes = diffMinutes % 60;
-
-    if (days > 0) {
-      return `${days}d${hours}h`;
-    }
-    if (hours > 0) {
-      return `${hours}h${minutes}m`;
-    }
-    return `${minutes}m`;
-  } catch {
-    return "";
-  }
-}
-
-//#endregion
-
-//#region Main
-
-/**
- * JSON information received from stdin
- * @typedef {object} StdinInput
- * @property {{display_name?: string}} [model] - Model information
- * @property {{context_window_size?: number, remaining_context_tokens?: number, current_usage?: {input_tokens?: number, output_tokens?: number, cache_creation_input_tokens?: number, cache_read_input_tokens?: number}}} [context_window] - Context window information
- * @property {{tokens_used?: number, tokens_limit?: number}} [weekly_token_usage] - Weekly token usage (fallback)
- * @property {string} [version] - Claude Code version
- */
-
-/**
- * Output Claude Code status bar information.
- * Combine JSON received from stdin with OAuth API response to output
- * model name, context usage, and daily/weekly usage.
- */
-async function main() {
-  const inputStr = await readStdin();
-  /** @type {StdinInput} */
-  let input = {};
-
-  if (inputStr !== "") {
-    try {
-      input = JSON.parse(inputStr);
-    } catch {
-      // Use empty object if JSON parsing fails
-    }
-  }
-
-  // Basic information
-  const modelName = input.model?.display_name ?? "Unknown";
-  const contextSize = input.context_window?.context_window_size ?? 0;
-  const usage = input.context_window?.current_usage;
-  const contextUsed =
-    (usage?.input_tokens ?? 0) +
-    (usage?.output_tokens ?? 0) +
-    (usage?.cache_creation_input_tokens ?? 0) +
-    (usage?.cache_read_input_tokens ?? 0);
-  const contextPercent = contextSize > 0 ? Math.round((contextUsed / contextSize) * 100) : 0;
-
-  // Try fetching usage with OAuth token
-  const token = getOAuthToken();
-  let dailyPercent = "?";
-  let dailyResetTime = "";
-  let weekPercent = "?";
-  let weekResetDay = "";
-  let extraUsage = "";
-
-  if (token != null) {
-    const usageResponse = await fetchUsage(token, input.version ?? "unknown");
-    if (usageResponse != null) {
-      // Use daily or five_hour
-      const dailyData = usageResponse.daily ?? usageResponse.five_hour;
-      dailyPercent = formatPercent(dailyData?.utilization);
-      dailyResetTime = formatTimeRemaining(dailyData?.resets_at);
-      weekPercent = formatPercent(usageResponse.seven_day?.utilization);
-      weekResetDay = formatTimeRemaining(usageResponse.seven_day?.resets_at);
-
-      // Extra usage
-      if (usageResponse.extra_usage?.is_enabled && usageResponse.extra_usage.used_credits != null) {
-        extraUsage = `$${(usageResponse.extra_usage.used_credits / 100).toFixed(2)}`;
-      }
-    }
-  }
-
-  // Fallback: weekly_token_usage
-  if (weekPercent === "?" && input.weekly_token_usage != null) {
-    const used = input.weekly_token_usage.tokens_used ?? 0;
-    const limit = input.weekly_token_usage.tokens_limit ?? 0;
-    if (limit > 0) {
-      weekPercent = Math.round((used / limit) * 100).toString();
-    }
-  }
-
-  // Folder name + git branch
-  const cwd = input.cwd ?? process.cwd();
-  const folderName = path.basename(cwd);
-
-  // Output
-  const dailyStr = dailyResetTime ? `${dailyPercent}%(${dailyResetTime})` : `${dailyPercent}%`;
-  const weekStr = weekResetDay ? `${weekPercent}%(${weekResetDay})` : `${weekPercent}%`;
-  const parts = [folderName, modelName, `${contextPercent}%`, dailyStr, weekStr];
-  if (extraUsage) parts.push(extraUsage);
-  console.log(parts.join(" │ "));
-}
-
-void main();
-
-//#endregion

package/claude/skills/sd-api-name-review/SKILL.md

@@ -1,154 +0,0 @@
----
-name: sd-api-name-review
-description: "Public API naming review (explicit invocation only)"
-model: sonnet
----
-
-# sd-api-name-review
-
-## Overview
-
-Compare a library/module's public API names against industry standards and review internal consistency, producing a standardization report. Uses **sd-explore** to extract the API surface, then dispatches research agents for industry comparison.
-
-**Analysis only — no code modifications.**
-
-## Principles
-
-- **Breaking changes are irrelevant**: Do NOT dismiss findings because renaming would cause a breaking change.
-- **Internal consistency first**: Internal naming consistency takes priority over external standards.
-
-## Usage
-
-- `/sd-api-name-review packages/solid` — full naming review
-- `/sd-api-name-review packages/orm-common` — review specific package
-- `/sd-api-name-review` — if no argument, ask the user for the target path
-
-## Target Selection
-
-- With argument: review source code at the given path
-- Without argument: ask the user for the target path
-
-**Important:** Review ALL source files under the target path. Do not use git status or git diff to limit scope.
-
-## Workflow
-
-### Step 1: Prepare Context
-
-Read these files:
-- `CLAUDE.md` — project overview
-- `.claude/rules/sd-refs-linker.md` — reference guide
-- Target's `package.json` — version (v12/v13)
-
-Based on version and target, read all applicable reference files (e.g., `sd-code-conventions.md`, `sd-solid.md`).
-
-Keep the collected conventions in memory — they will inform the analysis in later steps.
-
-### Step 2: API Extraction (via sd-explore)
-
-Follow the **sd-explore** workflow to extract the target's public API surface.
-
-**sd-explore input:**
-
-- **Target path**: the review target directory
-- **Name**: `api-name-review`
-- **File patterns**: `**/*.ts`, `**/*.tsx` (exclude `node_modules`, `dist`)
-- **Analysis instructions**:
-
-"For each file, extract its public API surface:
-- All exported identifiers (functions, classes, types, constants, etc.)
-- Names and types of user-facing parameters/options/config
-- Naming pattern classification (prefixes, suffixes, verb/adjective/noun usage, abbreviations, etc.)
-
-Output format:
-```
-# API Surface: [directory names]
-
-## Exports
-- `path/to/file.ts` — `exportName`: type (function/class/type/const), signature summary
-
-## Naming Patterns
-- Pattern: description (e.g., 'create-' prefix for factory functions)
-- Examples: list of identifiers using this pattern
-```
-"
-
-### Step 3: Industry Standard Research
-
-Based on Step 2 results:
-
-1. Identify **recurring naming patterns** from the extracted API
-2. Determine the target's domain and tech stack to **select comparable libraries**
-3. Dispatch **parallel agents** to web-search/fetch official docs for each comparable library, investigating naming conventions for the same pattern categories
-
-Each research agent receives:
-
-```
-Research naming conventions in [library name] for these pattern categories:
-[list of patterns from Step 2]
-
-For each pattern, document:
-- What naming convention the library uses
-- Specific examples from the API
-- Any documented rationale for the convention
-
-Write results to: .tmp/api-name-review/research-{library_name}.md
-```
-
-### Step 4: Comparative Analysis & Verification
-
-Cross-compare Step 2 (API surface) and Step 3 (industry research) results.
-
-Classify each naming pattern:
-
-| Priority | Criteria                                               |
-| -------- | ------------------------------------------------------ |
-| **P0**   | Misaligned with majority of surveyed libraries         |
-| **P1**   | Internal inconsistency (same concept, different names) |
-| **P2**   | Better industry term exists (optional)                 |
-| **Keep** | Already aligned with standards                         |
-
-**MANDATORY: Read actual code for EVERY finding.** For each finding, `Read` the file at the referenced location before finalizing. Do NOT rely on explore descriptions alone — verify against the actual code.
-
-Each finding includes: current name, recommended change, rationale (usage patterns per library).
-
-### Step 5: Report & User Confirmation
-
-Present **Keep** items to the user as a summary.
-
-Then present each **P0/P1/P2** finding to the user **one at a time**, ordered by priority (P0 → P1 → P2).
-
-For each finding, explain:
-1. **What the problem is** — the current name and why it's misaligned or inconsistent
-2. **How it could be fixed** — recommended name(s) with rationale from surveyed libraries
-3. **Ask**: address this or skip?
-
-Collect only findings the user confirms. If the user skips all findings, report that and end.
-
-### Step 6: Brainstorm Handoff
-
-Invoke **sd-brainstorm** with all user-confirmed findings as context:
-
-_
-"Design naming changes for the following review findings.
-
-**For each finding, you MUST:**
-1. Review it thoroughly — examine the code, understand the context, assess the real impact
-2. If any aspect is unclear or ambiguous, ask the user (one question at a time, per brainstorm rules)
-3. If a finding has low cost-benefit (adds complexity for marginal gain, pure style preference, scope too small), drop it. After triage, briefly list all dropped findings with one-line reasons (no user confirmation needed).
-4. For findings worth fixing, explore approaches and design solutions
-
-Findings that survive your triage become the design scope. Apply your normal brainstorm process (gap review → approaches → design presentation) to the surviving findings as a group.
-
-<include all confirmed findings with their priority, file:line, current name, recommended name, and rationale>"
-
-sd-brainstorm then owns the full cycle: triage (with user input as needed) → design.
-
-## Common Mistakes
-
-| Mistake | Fix |
-|---------|-----|
-| Using git diff to limit scope | Review ALL source files under target |
-| Skipping context preparation | Always read conventions and refs before analysis |
-| Skipping verification | Always verify findings against actual code |
-| Dismissing findings due to breaking changes | Breaking changes are irrelevant — report the naming issue |
-| Not writing research results to files | Research agents MUST write to disk — prevents context bloat |