Опишете задачата
Към всички skills

app-builder-sdk

holaboss-ai · Разработка

Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI). The canonical path for vibe-coded apps — integration modules AND dashboard apps both live here.

Оригинален текст · няма потвърден превод на български
Платформи: Не са посочениНиво: Не е посоченоВ индекса: 20.09.2026 г.Обновен в GitHub: 21.08.2026 г.

Теми: agent · agent-harness · agent-os · agentic · ai · ai-agent · ai-agents · artificial-intelligence · claude-code · codex · electron · holaboss · holaos · llm · mcp

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
11 363
Лиценз
NOASSERTION
Последна проверка на записа
20.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add holaboss-ai/holaOS

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

App Builder (SDK)

Use this skill whenever the user wants a new holaOS app. Two shapes both ship through the same SDK; pick the one the request needs:

  1. Integration-only module — Slack, Discord, Notion, Stripe, Linear, anything whose value is "talk to one external service via MCP tools, agent drives, no per-app dashboard". The SDK's default web stub is fine; no src/client/ directory.
  2. Dashboard app — vibe-coded content planners, CRMs, kanban-style trackers, podcast-guest managers, anything where the user expects a workspace pane they can look at and click around in. Has a real shadcn UI authored under src/client/ (TanStack Start). The MCP tools are still there — they're how the agent drives the same data the dashboard surfaces.

The SDK core (5 primitives below) is identical for both shapes. The dashboard shape adds a src/client/ directory; that's the only structural delta.

All supplemental files named in this skill are bundled beside this SKILL.md. Treat those paths as skill-local references that are safe to use in packaged runtimes; do not guess at repo-root paths.

Tooling discipline for this skill

  • In the normal build turn, use surfaced workspace file tools for file work: read / search / find / list for inspection, edit for targeted changes, and write for new files or full rewrites.
  • Do not use bash heredocs for ordinary app file creation or mutation in the build turn. That includes package.json, app.ts, server.ts, app.runtime.yaml, workspace.yaml, and non-src/client/ assets such as game.html.
  • Use bash only for shell-native work such as bun install, starting or probing processes, checking logs, or other commands the surfaced file/runtime tools cannot express directly.
  • The only heredoc exception in this skill is the auto-queued polish pass rule below, and it applies only to apps/<app_id>/src/client/*.tsx and .css files in that separate polish turn.

When NOT to use this skill

  • The user already has a working module app and wants to extend it → modify it in place; don't rewrite as SDK. (The legacy app-builder skill that used to live alongside this one has been removed; all new app work goes through this SDK.)

The 5 primitives

Every SDK app composes exactly these:

Целият SKILL.md в GitHub