build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore synchronization, or diagnosing an existing TinyBase application.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 5177
- Лиценз
- MIT
- Последна проверка на записа
- 21.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add tinyplex/tinybaseСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Build With TinyBase
Prefer a current generated application over reconstructing TinyBase setup from memory. Preserve persistence and synchronization lifecycle ordering, and verify the behavior the user actually needs.
Read The References
Do not recall TinyBase API details from memory. Read the reference covering the task before writing code:
| Reference | Read it when |
|---|---|
| references/architecture.md | Choosing between Store and MergeableStore, a persistence backend, a synchronization approach, or UI bindings |
| references/import-paths.md | Importing anything outside the tinybase root, or checking which Persisters accept a MergeableStore |
| references/lifecycle.md | Creating, starting, reconnecting, or destroying a Persister or Synchronizer, or setting WebSocket paths and channel Ids |
| references/durable-objects.md | Building or debugging a Cloudflare Durable Object sync server |
Select The Architecture
Read references/architecture.md when choosing between Store and MergeableStore, persistence backends, synchronization, or UI bindings.
Confirm that TinyBase fits the task:
- Keep the active application dataset in a JavaScript runtime.
- Use TinyBase for reactive tabular or key-value data, local-first behavior, persistence, synchronization, or framework bindings.
- Do not present TinyBase as a hosted database service.
- Pair it with another database or service when the authoritative dataset is unbounded, primarily queried on a server, or requires managed backend facilities.
Scaffold A New Application
Inspect the installed generator contract first:
npm create tinybase@latest -- --list-options
Translate the user's requirements into explicit values. Generate unattended projects with every applicable option and always disable automatic installation and server startup: