@opendash-ai/cli 0.1.0-beta.1 → 0.1.0-beta.3

package/src/skill/builtin/.bundle/self-extend/reference/tui-api.md

@@ -1,258 +0,0 @@
-# TUI Plugin API Reference
-
-## File Format
-
-```tsx
-import type { TuiPlugin } from "@mimo-ai/plugin/tui"
-
-export const tui: TuiPlugin = async (api, options, meta) => {
-  // api — the full TUI plugin API
-  // options — plugin options from config (if any)
-  // meta — plugin metadata (id, source, version, etc.)
-}
-```
-
-File extension should be `.tsx` (JSX support for UI components).
-
-## TuiPluginApi
-
-### api.command
-
-Register commands in the command palette (Ctrl+K / Cmd+K).
-
-```ts
-const unregister = api.command.register(() => [
-  {
-    title: "Deploy to Staging",        // Display name
-    value: "deploy-staging",           // Unique id
-    description: "Run staging deploy", // Optional subtitle
-    category: "Deploy",                // Optional grouping
-    keybind: "ctrl+shift+d",           // Optional shortcut
-    suggested: true,                   // Pin to top
-    hidden: false,                     // Show/hide
-    enabled: true,                     // Greyed out if false
-    onSelect: () => { /* action */ },
-  },
-])
-
-api.command.trigger("deploy-staging")  // Programmatic trigger
-api.command.show()                     // Open palette
-```
-
-### api.route
-
-Register full-screen views (pages).
-
-```tsx
-api.route.register([
-  {
-    name: "my-dashboard",
-    render: (input) => (
-      <div>
-        <h1>Dashboard</h1>
-        <p>Params: {JSON.stringify(input.params)}</p>
-      </div>
-    ),
-  },
-])
-
-api.route.navigate("my-dashboard", { filter: "active" })
-api.route.current  // { name: "session", params: { sessionID: "..." } }
-```
-
-### api.slots
-
-Inject content into predefined UI slots.
-
-```tsx
-api.slots.register({
-  slots: {
-    sidebar_footer: (props) => (
-      <div>Session: {props.session_id}</div>
-    ),
-    home_bottom: () => (
-      <div>Custom widget here</div>
-    ),
-  },
-})
-```
-
-#### Available Slots
-
-| Slot Name | Props | Where |
-|-----------|-------|-------|
-| `app` | `{}` | Root wrapper |
-| `home_logo` | `{}` | Home screen logo |
-| `home_prompt` | `{ workspace_id?, ref? }` | Home input |
-| `home_prompt_right` | `{ workspace_id? }` | Right of home input |
-| `home_bottom` | `{}` | Below home content |
-| `home_footer` | `{}` | Home footer bar |
-| `session_prompt` | `{ session_id, visible?, disabled?, on_submit?, ref? }` | Session input |
-| `session_prompt_right` | `{ session_id }` | Right of session input |
-| `sidebar_title` | `{ session_id, title, share_url? }` | Sidebar header |
-| `sidebar_content` | `{ session_id }` | Sidebar body |
-| `sidebar_footer` | `{ session_id }` | Sidebar footer |
-
-### api.ui
-
-Built-in dialog components and toast notifications.
-
-```tsx
-// Toast notification
-api.ui.toast({
-  variant: "success",  // "info" | "success" | "warning" | "error"
-  title: "Done",
-  message: "Deployment complete",
-  duration: 3000,
-})
-
-// Dialog stack
-api.ui.dialog.replace(() => (
-  <api.ui.DialogConfirm
-    title="Confirm"
-    message="Are you sure?"
-    onConfirm={() => api.ui.dialog.clear()}
-    onCancel={() => api.ui.dialog.clear()}
-  />
-))
-
-// Available dialog components:
-// api.ui.Dialog — generic dialog wrapper
-// api.ui.DialogAlert — alert with OK button
-// api.ui.DialogConfirm — confirm with OK/Cancel
-// api.ui.DialogPrompt — text input dialog
-// api.ui.DialogSelect — list selection dialog
-```
-
-### api.state
-
-Read-only access to application state.
-
-```ts
-api.state.config                        // Current config
-api.state.provider                      // Available providers
-api.state.path.directory                // Project directory
-api.state.path.worktree                 // Git worktree
-api.state.vcs?.branch                   // Current branch
-
-api.state.session.count()               // Number of sessions
-api.state.session.messages(sessionID)   // Messages in session
-api.state.session.status(sessionID)     // Session status
-api.state.session.diff(sessionID)       // Changed files
-api.state.session.todo(sessionID)       // Todo items
-api.state.session.task(sessionID)       // Tasks
-
-api.state.lsp()                         // LSP server status
-api.state.mcp()                         // MCP server status
-```
-
-### api.theme
-
-Theme access and management.
-
-```ts
-api.theme.current           // All current theme colors (RGBA)
-api.theme.selected          // Theme name
-api.theme.mode()            // "dark" | "light"
-api.theme.set("monokai")   // Switch theme
-api.theme.has("monokai")   // Check if installed
-await api.theme.install("./themes/custom.json")  // Install from file
-```
-
-### api.keybind
-
-Keyboard shortcut utilities.
-
-```ts
-api.keybind.match("submit", event)   // Check if key matches binding
-api.keybind.print("submit")          // Human-readable "Ctrl+Enter"
-const keys = api.keybind.create(
-  { submit: "ctrl+enter", cancel: "escape" },
-  overrides,
-)
-```
-
-### api.client
-
-SDK client for server communication.
-
-```ts
-// The full @mimo-ai/sdk client — same as what plugins get on server side
-const sessions = await api.client.session.list()
-const messages = await api.client.session.messages(sessionID)
-```
-
-### api.event
-
-Subscribe to server-side events (SSE).
-
-```ts
-const unsub = api.event.on("session.updated", (event) => {
-  console.log("Session changed:", event.properties)
-})
-```
-
-### api.kv
-
-Persistent key-value storage (survives restarts).
-
-```ts
-api.kv.set("my-plugin.lastRun", Date.now())
-const last = api.kv.get<number>("my-plugin.lastRun", 0)
-```
-
-### api.lifecycle
-
-Plugin lifecycle management.
-
-```ts
-api.lifecycle.signal  // AbortSignal — fired when plugin is deactivated
-api.lifecycle.onDispose(() => {
-  // Cleanup: close connections, remove listeners, etc.
-})
-```
-
-## Complete Example
-
-```tsx
-import type { TuiPlugin } from "@mimo-ai/plugin/tui"
-
-export const tui: TuiPlugin = async (api) => {
-  // Register a command
-  api.command.register(() => [
-    {
-      title: "Show Project Stats",
-      value: "project-stats",
-      category: "Info",
-      onSelect: () => {
-        api.ui.toast({
-          variant: "info",
-          message: `Sessions: ${api.state.session.count()}, Branch: ${api.state.vcs?.branch ?? "unknown"}`,
-        })
-      },
-    },
-  ])
-
-  // Add sidebar footer content
-  api.slots.register({
-    slots: {
-      sidebar_footer: (props) => {
-        const status = api.state.session.status(props.session_id)
-        return <div>{status ?? "idle"}</div>
-      },
-    },
-  })
-
-  // Cleanup on deactivate
-  api.lifecycle.onDispose(() => {
-    console.log("Plugin deactivated")
-  })
-}
-```
-
-## Constraints
-
-- TUI plugins need a restart to take effect (they run in a separate thread from the server)
-- Use `.tsx` extension for JSX support
-- Components use Solid.js JSX (NOT React) — no useState/useEffect, use signals
-- Keep plugins lightweight — they run in the main rendering thread

package/src/skill/builtin/bundle.macro.ts

@@ -1,30 +0,0 @@
-import fs from "fs"
-import path from "path"
-
-function walkDir(base: string, rel: string, out: Record<string, string>) {
-  const fullPath = rel ? path.join(base, rel) : base
-  for (const entry of fs.readdirSync(fullPath, { withFileTypes: true })) {
-    const relPath = rel ? `${rel}/${entry.name}` : entry.name
-    if (entry.isDirectory()) {
-      walkDir(base, relPath, out)
-    } else {
-      out[relPath] = fs.readFileSync(path.join(fullPath, entry.name), "utf8")
-    }
-  }
-}
-
-export function loadBuiltinBundle(): Record<string, Record<string, string>> {
-  const dir = path.resolve(import.meta.dir, ".bundle")
-  const result: Record<string, Record<string, string>> = {}
-
-  for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
-    if (!entry.isDirectory()) continue
-    const files: Record<string, string> = {}
-    walkDir(path.join(dir, entry.name), "", files)
-    if (Object.keys(files).length > 0) {
-      result[entry.name] = files
-    }
-  }
-
-  return result
-}

package/src/skill/builtin/extract.ts

@@ -1,41 +0,0 @@
-import path from "path"
-import { Effect } from "effect"
-import { AppFileSystem } from "@opendash-ai/shared/filesystem"
-import { Path as GlobalPath } from "@/global"
-import { InstallationLocal, InstallationVersion } from "@/installation/version"
-import { Log } from "@/util"
-import { loadBuiltinBundle } from "./bundle.macro" with { type: "macro" }
-import { loadBuiltinBundle as loadBuiltinBundleDev } from "./bundle.macro"
-
-function safeLoadBuiltinBundle() {
-  try {
-    return loadBuiltinBundle()
-  } catch(e) {
-    if (e instanceof ReferenceError) {
-      return loadBuiltinBundleDev()
-    }
-    throw e
-  }
-}
-const BUILTIN_BUNDLE = safeLoadBuiltinBundle()
-
-const log = Log.create({ service: "skill.builtin" })
-
-export const extractBuiltinBundle = Effect.fn("Skill.extractBuiltinBundle")(function* (
-  fsys: AppFileSystem.Interface,
-) {
-  const root = path.join(GlobalPath.data, "builtin_skills", InstallationVersion)
-  const marker = path.join(root, ".extracted")
-
-  if (!InstallationLocal && (yield* fsys.existsSafe(marker))) return root
-
-  for (const [skillName, files] of Object.entries(BUILTIN_BUNDLE)) {
-    const skillDir = path.join(root, "skills", skillName)
-    for (const [relPath, content] of Object.entries(files)) {
-      yield* fsys.writeWithDirs(path.join(skillDir, relPath), content)
-    }
-  }
-  yield* fsys.writeWithDirs(marker, InstallationVersion)
-  log.info("extracted builtin skills", { root })
-  return root
-})

package/src/skill/compose/.bundle/ask/SKILL.md

@@ -1,58 +0,0 @@
----
-name: compose:ask
-hidden: true
-description: "Use whenever you need a decision, clarification, or approval from the user — covers how to ask with the question tool, and how to resolve the decision yourself when no user is available (question tool absent, or a [Never-Ask] response)"
----
-
-# Asking the User
-
-## The Rule
-
-Every time you need the user to decide, clarify, or approve something, route it through the `question` tool. **Never** stop the loop with a natural-language question ("Does this look right?", "Should I proceed?", "Which would you prefer?"). A natural-language question ends your turn without finishing the task; a `question` tool call does not.
-
-This means: **the loop only ends when the task is actually complete** — never because you paused to ask in prose.
-
-## How to Ask
-
-- **Structured options** — when the decision has known choices, list them as `options` (each with a short `label` and a `description`).
-- **Open-ended** — when you can't enumerate good options, pass **empty `options`**. An empty options list renders as a free-text prompt: the user types whatever they want. So anything you'd normally ask in prose can be asked through `question` instead.
-- **One question per concern** — don't bundle unrelated decisions; ask them as separate questions (or separate calls).
-- **Don't repeat the question in prose** — the tool already renders it. Just call the tool.
-
-```
-question({
-  questions: [{
-    question: "Which auth strategy should I use?",
-    header: "Auth",
-    options: [
-      { label: "Session cookies", description: "Server-side sessions, simplest" },
-      { label: "JWT", description: "Stateless, good for multiple services" },
-    ],
-  }],
-})
-```
-
-## When No User Is Available
-
-There are two situations where you won't get a human answer. **The decision behavior is identical in both** — you pick the best option for unattended/headless execution yourself and keep going. They differ only in *whether the question tool is reached this turn*:
-
-1. **Question tool absent** (e.g. `run`/eval, where `question` is denied) — the tool isn't in your list. You never call it; decide and proceed directly.
-2. **`[Never-Ask]` response** (never-ask is on) — you *do* call `question`, but instead of a user answer the tool returns a `[Never-Ask]` directive. Re-pick from the options you proposed, **explicitly state your choice and reasoning in your response text**, and continue.
-
-### How to decide autonomously
-
-The best option for a human is often **not** the best option for headless execution. Re-evaluate your own options through this lens:
-
-- Prefer **text-only** over visual/interactive paths (e.g. don't launch a GUI companion, don't open a browser — produce the same content as text).
-- Prefer **non-interactive** over anything needing the user present.
-- Prefer the **minimal-scope** path — don't expand the work to cover speculative edge cases just because no one is gating it.
-- When approval is the only thing being requested, treat it as **granted** and proceed to implementation.
-- **Exception — destructive, irreversible actions** (deleting a branch/commits, dropping data, force-pushing) never auto-approve. When you can't get explicit confirmation, choose the non-destructive path (keep things as-is) and continue with the rest of the task.
-
-### Only this turn — keep asking later
-
-Autonomous resolution applies **only to the current question**. Do **not** infer "I should stop using the question tool from now on." never-ask can be turned off at any moment, and the question tool may reappear — at the next decision point, ask normally again. The user may have returned.
-
-## Why this skill exists
-
-This is the single source of truth for asking and autonomous fallback. Other compose skills reference it at their decision points instead of repeating fallback text, so the rules stay consistent and the prompts stay small.

package/src/skill/compose/.bundle/brainstorm/SKILL.md

@@ -1,200 +0,0 @@
----
-name: compose:brainstorm
-hidden: true
-description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
----
-
-# Brainstorming Ideas Into Designs
-
-Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
-
-Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
-
-<HARD-GATE>
-Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.
-
-**Autonomous override:** When no user is available to approve, this HARD-GATE does not apply: skip design presentation and approval, proceed directly to implementation, treating every approval gate as auto-approved.
-</HARD-GATE>
-
-## Anti-Pattern: "This Is Too Simple To Need A Design"
-
-Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
-
-**Autonomous override:** When no user is available, skip this anti-pattern guidance — proceed directly to exploring context and implementing; do not present a design for approval.
-
-## Checklist
-
-You MUST create a task for each of these items and complete them in order:
-
-**Autonomous mode (no user available):** Skip steps 2–8. Only do: explore project context (step 1) → implement directly (invoke compose:plan or compose:execute). Do NOT present a design, ask questions, write a spec, or wait for approval.
-
-1. **Explore project context** — check files, docs, recent commits
-2. **Offer visual companion** (if topic will involve visual questions) — this is its own message, not combined with a clarifying question. See the Visual Companion section below.
-3. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
-4. **Propose 2-3 approaches** — with trade-offs and your recommendation
-5. **Present design** — in sections scaled to their complexity, get user approval after each section
-6. **Write design doc** (optional, multi-step features only) — save to the `specs/` directory given in the `<compose_docs_dir>` block of your prompt, as `YYYY-MM-DD-<topic>-design.md`, and commit. For single-step fixes or small changes, keep the design in conversation context only.
-7. **Spec self-review** (if doc written) — quick inline check for placeholders, contradictions, ambiguity, scope (see below)
-8. **User reviews written spec** (if doc written) — ask user to review the spec file before proceeding
-9. **Transition to implementation** — invoke compose:plan to create implementation plan
-
-## Process Flow
-
-- **Explore project context**
-- **Visual questions ahead?** — Yes → offer Visual Companion (own message, no other content)
-- **Ask clarifying questions**
-- **Propose 2-3 approaches**
-- **Present design sections**
-- **User approves design?** — No → revise, back to present design sections
-- **Write design doc**
-- **Spec self-review** (fix inline)
-- **User reviews spec?** — Changes requested → back to write design doc / Approved → **invoke compose:plan**
-
-**The terminal state is invoking compose:plan.** Do NOT invoke frontend-design, mcp-builder, or any other implementation skill. The ONLY skill you invoke after brainstorming is compose:plan.
-
-## The Process
-
-**Understanding the idea:**
-
-- Check out the current project state first (files, docs, recent commits)
-- Before asking detailed questions, assess scope: if the request describes multiple independent subsystems (e.g., "build a platform with chat, file storage, billing, and analytics"), flag this immediately. Don't spend questions refining details of a project that needs to be decomposed first.
-- If the project is too large for a single spec, help the user decompose into sub-projects: what are the independent pieces, how do they relate, what order should they be built? Then brainstorm the first sub-project through the normal design flow. Each sub-project gets its own spec → plan → implementation cycle.
-- For appropriately-scoped projects, ask questions one at a time to refine the idea
-- When the question has a known set of likely answers, use `compose:ask` with those answers as options
-- For open-ended questions, use `compose:ask` with 2-3 suggested answers as options — the user can always type their own answer
-- If no user is available, make reasonable assumptions from project context and proceed
-- Only one question per tool call — if a topic needs more exploration, break it into multiple questions
-- Focus on understanding: purpose, constraints, success criteria
-
-**Exploring approaches:**
-
-- Propose 2-3 different approaches with trade-offs
-- Present options conversationally with your recommendation and reasoning
-- Lead with your recommended option and explain why
-
-**Presenting the design:**
-
-- Once you believe you understand what you're building, present the design
-- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced
-- After presenting each section, use `compose:ask`:
-  - header: `Design Review`
-  - question: `Does this <section-name> look right?`
-  - options:
-    - label: `Looks good`, description: `Approve and continue`
-    - label: `Needs changes`, description: `I have feedback`
-
-  If no user is available, treat as approved and continue.
-- Cover: architecture, components, data flow, error handling, testing
-- Be ready to go back and clarify if something doesn't make sense
-
-**Design for isolation and clarity:**
-
-- Break the system into smaller units that each have one clear purpose, communicate through well-defined interfaces, and can be understood and tested independently
-- For each unit, you should be able to answer: what does it do, how do you use it, and what does it depend on?
-- Can someone understand what a unit does without reading its internals? Can you change the internals without breaking consumers? If not, the boundaries need work.
-- Smaller, well-bounded units are also easier for you to work with - you reason better about code you can hold in context at once, and your edits are more reliable when files are focused. When a file grows large, that's often a signal that it's doing too much.
-
-**Working in existing codebases:**
-
-- Explore the current structure before proposing changes. Follow existing patterns.
-- Where existing code has problems that affect the work (e.g., a file that's grown too large, unclear boundaries, tangled responsibilities), include targeted improvements as part of the design - the way a good developer improves code they're working in.
-- Don't propose unrelated refactoring. Stay focused on what serves the current goal.
-
-## After the Design
-
-**Documentation (optional, multi-step features only):**
-
-For features with multiple tasks or significant architectural decisions:
-- Write the validated design (spec) to the `specs/` directory given in `<compose_docs_dir>`, as `YYYY-MM-DD-<topic>-design.md`
-  - (User preferences for spec location override this default)
-- Use elements-of-style:writing-clearly-and-concisely skill if available
-- Commit the design document to git
-
-For single bug fixes or small changes, skip the written spec — the design presented in conversation is sufficient.
-
-**Spec Self-Review (if doc written):**
-After writing the spec document, look at it with fresh eyes:
-
-1. **Placeholder scan:** Any "TBD", "TODO", incomplete sections, or vague requirements? Fix them.
-2. **Internal consistency:** Do any sections contradict each other? Does the architecture match the feature descriptions?
-3. **Scope check:** Is this focused enough for a single implementation plan, or does it need decomposition?
-4. **Ambiguity check:** Could any requirement be interpreted two different ways? If so, pick one and make it explicit.
-
-Fix any issues inline. No need to re-review — just fix and move on.
-
-**User Review Gate (if doc written):**
-After spec self-review passes, use `compose:ask`:
-- header: `Spec Review`
-- question: `Spec written and committed to <path>. Ready to proceed?`
-- options:
-  - label: `Approved`, description: `Proceed to compose:plan`
-  - label: `Changes needed`, description: `I have revisions`
-
-If no user is available, treat as approved and invoke compose:plan.
-
-If "Changes needed" or custom feedback, apply changes and re-run spec review. Only proceed on approval.
-
-**Implementation:**
-
-- Invoke compose:plan to create a detailed implementation plan
-- Do NOT invoke any other skill. compose:plan is the next step.
-
-## Spec Section Anchors
-
-When writing the spec, give every `##` section heading a stable anchor ID so downstream plan tasks and reviewers can reference exact spec locations. Put the ID at the start of the heading text:
-
-```markdown
-## [S1] Problem
-## [S2] Solution overview
-## [S3] Coverage gate behavior
-```
-
-Rules:
-
-- **ID format** is `S` followed by a number (`[S1]`, `[S2]`, `[S3]`, ...), unique within the spec — no two sections share an ID, and no section is left without one.
-- **Number sections in document order** when first authoring the spec (top section is `[S1]`, the next is `[S2]`, and so on).
-- **The ID is stable.** If a heading is later reworded, keep its existing ID and do NOT renumber the other sections. Downstream `covers:` references and review verdicts depend on these IDs not drifting — renumbering would silently break every reference that points at them.
-
-These anchors are the index the plan and reviewers use to trace each task and each review verdict back to the exact spec section it serves.
-
-## Key Principles
-
-- **One question at a time** - Don't overwhelm with multiple questions
-- **Multiple choice preferred** - Easier to answer than open-ended when possible
-- **YAGNI ruthlessly** - Remove unnecessary features from all designs
-- **Explore alternatives** - Always propose 2-3 approaches before settling
-- **Incremental validation** - Present design, get approval before moving on
-- **Be flexible** - Go back and clarify when something doesn't make sense
-
-## Visual Companion
-
-A browser-based companion for showing mockups, diagrams, and visual options during brainstorming. Available as a tool — not a mode. Accepting the companion means it's available for questions that benefit from visual treatment; it does NOT mean every question goes through the browser.
-
-**Offering the companion:** When you anticipate visual content (mockups, layouts, diagrams):
-
-1. **Check memory** for a `visual-companion` preference in the `compose-preferences` memory file. If found, honor it.
-
-2. **If no saved preference,** offer consent using `compose:ask` (this MUST be its own message — do not combine with other content):
-   - header: `Visual Companion`
-   - question: `Some upcoming questions may benefit from browser-based mockups and diagrams. This feature is token-intensive and requires opening a local URL.`
-   - options:
-     - label: `Yes, always`, description: `Enable visuals for this and future sessions`
-     - label: `No, never`, description: `Skip visuals for this and future sessions`
-     - label: `Yes, this time`, description: `Enable visuals for this session only`
-     - label: `No, this time`, description: `Skip visuals for this session only`
-
-   If no user is available, skip the visual companion and use text-only.
-
-3. **If "Yes, always" or "No, never":** Save to the `compose-preferences` memory file.
-
-If declined, proceed with text-only brainstorming.
-
-**Per-question decision:** Even after the user accepts, decide FOR EACH QUESTION whether to use the browser or the terminal. The test: **would the user understand this better by seeing it than reading it?**
-
-- **Use the browser** for content that IS visual — mockups, wireframes, layout comparisons, architecture diagrams, side-by-side visual designs
-- **Use the terminal** for content that is text — requirements questions, conceptual choices, tradeoff lists, A/B/C/D text options, scope decisions
-
-A question about a UI topic is not automatically a visual question. "What does personality mean in this context?" is a conceptual question — use the terminal. "Which wizard layout works better?" is a visual question — use the browser.
-
-If they agree to the companion, read the detailed guide before proceeding:
-`<compose:brainstorm>/visual-companion.md`