Stacks Documentation
SkillsChangelog
TeamSponsorsPartnersPostcardwareAwesome StacksContributing

Browser

Copy page
Copy page as Markdown for LLMs
View as Markdown
View this page as plain text
Open in ChatGPT
Copy content and open ChatGPT
Open in Claude
Copy content and open Claude
Open in Perplexity
Search with Perplexity AI
On this page 5

stacks-browser · Frontend · model-invoked

The browser-side surface: the useAuth composable, canonical API URL resolution, the Stripe billing helpers, the API fetch client and browser model loading.

When to reach for it

  • The useAuth composable (login, register, logout, token management)
  • Stripe billing utilities (loadCardElement, confirmPayment)
  • The API fetch client
  • Canonical API URL resolution without doubled /api prefixes
  • Browser model loading
  • Auto-imported browser utilities

Covers

@stacksjs/browser.

Inside the skill

The sections an agent reads once the skill loads.

  • Key Paths
  • Authentication Composable (useAuth)
  • API Client (Fetch)
  • Stripe Billing (Browser-Side)
  • Browser Model Loading
  • Browser Query Builder
  • Utility Functions
  • Guards
  • Auto-Initialization
  • Re-exports from Composables
  • Gotchas

Where the code lives

  • Core package: storage/framework/core/browser/src/
  • Auto-imports: storage/framework/browser-auto-imports.json

Using it

This one is model-invoked. Your agent reaches for it on its own when the task matches, and you can also call it by name:

/stacks-browser

Source: stacks-browser/SKILL.md. Shadow it for one project with app/Skills/stacks-browser/SKILL.md, then re-run buddy setup:ai. See Writing your own.