Skip to content

armgit / dbx

Public Imported from GitHub
0

25 MB lightweight cross-platform database client for 100+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 100+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP。

3.2 KB
Raw Blame
import type { UserSkillMeta } from "@/types/userSkills";

/** A selected skill rendered as a chip, whether or not it is still discoverable. */
export interface SelectedSkillChip {
  id: string;
  name: string;
  description: string;
  source: "custom" | "default";
  /** True when the catalog no longer lists this id (deleted, or its root went away). */
  unavailable: boolean;
  /**
   * True once this conversation has had the skill loaded — by the model through
   * `use_skill`, or by the user forcing the load (prd 09-30 Req 13). A persistent
   * per-conversation signal, never a per-turn one.
   */
  loaded: boolean;
}

/**
 * The backend mints ids as `<root>-<digest>` (`c-` custom root, `d-` default
 * root). Deriving the source from that prefix instead of from the catalog keeps
 * a selected skill labeled and removable after it disappears from discovery.
 */
export function userSkillSourceOfId(id: string): "custom" | "default" {
  return id.startsWith("c-") ? "custom" : "default";
}

/**
 * Every selected id keeps a chip: a skill that vanished from discovery would
 * otherwise lose its only remove affordance and block every later send. The
 * fallback label is the opaque id, paired with `unavailable` for styling.
 *
 * `loadedIds` is the conversation's loaded set; an omitted one leaves every chip
 * in its default state, which is what a caller with no conversation state wants.
 */
export function buildSelectedSkillChips(ids: readonly string[], lookup: (id: string) => UserSkillMeta | undefined, loadedIds: Iterable<string> = []): SelectedSkillChip[] {
  const loaded = new Set(loadedIds);
  return ids.map((id) => {
    const meta = lookup(id);
    return {
      id,
      name: meta?.name ?? id,
      description: meta?.description ?? "",
      source: userSkillSourceOfId(id),
      unavailable: !meta,
      loaded: loaded.has(id),
    };
  });
}

/**
 * Display names appearing more than once inside one source/root.
 *
 * Skill discovery is flat (`<root>/<dir>/SKILL.md`, `crates/dbx-core/src/skills.rs`),
 * so every entry in a root already has its own directory — a collision inside one
 * root is therefore always two directories declaring the same frontmatter `name`.
 * The model addresses skills by name + source (ADR Decision 6), so `use_skill`
 * can only answer "ambiguous" for these; `source` cannot separate two entries of
 * the same root. The badge in the selector exists to tell the user that, because
 * only changing one of the two frontmatter `name` values can resolve it — the
 * collision key is that field, not the directory name, so renaming a folder
 * changes nothing. The same name in *different* roots is normal and is not
 * reported here.
 */
export function duplicateSkillNames(skills: readonly UserSkillMeta[]): Set<string> {
  const seen = new Set<string>();
  const duplicates = new Set<string>();
  for (const skill of skills) {
    if (seen.has(skill.name)) duplicates.add(skill.name);
    else seen.add(skill.name);
  }
  return duplicates;
}

/** Order-preserving removal, shared by the chip close button and the failure banner. */
export function removeSkillIds(ids: readonly string[], removed: Iterable<string>): string[] {
  const dropped = new Set(removed);
  return ids.filter((id) => !dropped.has(id));
}