Agents ​

How coding agents (and humans pasting into agents) should load Sometic context without inventing a visual UI kit.

For full-app pasteable scaffolds (SaaS, auth e2e, AI workspace, and more), use App scaffolds (also linked from the home hero). This page covers surface Copy Prompt buttons and llms.txt.

Copy Prompt ​

Surface docs expose a Copy Prompt button (dashed outline). Each button copies a pro integration brief for that area: product framing, Wave A path gate, architecture, App Shell spine, shared API truth, module wiring recipe, acceptance criteria, and docs links.

These briefs are module-focused (not full product novels). For a complete SaaS/auth/marketplace build, use an App scaffolds prompt instead.

SurfacePagePrompt file
EcosystemHome (Copy prompt CTA)ecosystem.txt
App ShellApp Shellapp-shell.txt
AuthAuthenticationauth.txt
HTTPHTTPhttp.txt
HeadHead / SEOhead.txt
QueryQueryquery.txt
FormsFormsforms.txt
StoresStoresstores.txt
ThemingThemingtheming.txt
FoundationPrimitivesfoundation.txt
ComponentsComponentscomponents.txt

Paste the prompt into your agent, answer A / B / C / D1 / D2 when asked, then follow the linked docs. Prompt sources are composed from apps/docs/.vitepress/prompts/shared/ + bodies/ via pnpm prompts:compose.

llms.txt ​

  • Curated index: /llms.txt (also linked in site head as rel="alternate")
  • Full consumer export: /llms-full.txt (regenerated via python scripts/generate-llms-full.py)
  • Short pointer file: /ai.txt

Prefer llms.txt for routing; use llms-full.txt for offline / IDE ingestion.

Package graph (mental model) ​

text
Adapters (@sometic/react, vue, elements, …)
    → Composition (@sometic/app-shell)
        → Features (forms, auth, http, query, theme, head, dom, …)
            → Foundation (core, events, store, styling, accessibility, …)
  • App Shell composes System packages behind one session epoch and dispose().
  • Query caches server data; store holds client/UI state; do not mix.
  • HTTP owns transport and 401 refresh; auth owns session; query refetches after re-auth.
  • Prefer subpath imports (@sometic/react/query, @sometic/react/button).
  • Custom elements use the sometic-* prefix.
  • Publishable packages are font-agnostic; brand fonts are docs and demo surfaces only.

Start paths ​

  1. Architecture: layers and guarantees
  2. What’s included: honest inventory
  3. Comparison: when not to use Sometic
  4. System hubs: App Shell, Auth, HTTP, Query, Forms, Stores, Head