stackblitz-install-auth
/stackblitz-install-auth
Przygotowuje integrację StackBlitz WebContainer lub JavaScript SDK z przypiętymi pakietami, zgodnymi nagłówkami izolacji i właściwą ścieżką uwierzytelniania dla licencji komercyjnej lub pakietów prywatnych.
- Autor
- jeremylongshore ↗
- Repozytorium
- tons-of-skills-marketplace ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Przygotowuje integrację StackBlitz WebContainer lub JavaScript SDK z przypiętymi pakietami, zgodnymi nagłówkami izolacji i właściwą ścieżką uwierzytelniania dla licencji komercyjnej lub pakietów prywatnych.
Wyzwalacze z opisu
Argumenty
/stackblitz-install-auth [project-path] [webcontainer|embed]
Oryginalny opis (EN)
Prepare a StackBlitz WebContainer or JavaScript SDK integration with pinned packages, compatible isolation headers, and the correct commercial or private-package authentication path. Use when adding StackBlitz to an existing web application or reviewing its startup contract. Trigger with "install StackBlitz", "set up WebContainers", or "configure WebContainer auth".
Jak działa
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Authentication
- Workflow
- Approval Boundaries
- Output
- Error Handling
- Examples
Podgląd SKILL.md
--- name: stackblitz-install-auth description: >- Prepare a StackBlitz WebContainer or JavaScript SDK integration with pinned packages, compatible isolation headers, and the correct commercial or private-package authentication path. Use when adding StackBlitz to an existing web application or reviewing its startup contract. Trigger with "install StackBlitz", "set up WebContainers", or "configure WebContainer auth". argument-hint: "[project-path] [webcontainer|embed]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.7.0 author: Jeremy Longshore <jeremy@intentsolutions.io> license: MIT tags: - saas - stackblitz - webcontainers - setup model: inherit effort: medium compatibility: Designed for Claude Code --- # StackBlitz Integration Preflight ## Overview This skill produces a repo-grounded installation and startup plan for either a custom WebContainer application or a StackBlitz SDK embed. It separates ordinary browser startup from commercial API-key configuration and organization-scoped private-package authentication. ## Prerequisites - A named browser application and permission to inspect its package and hosting configuration - A decision between `@webcontainer/api` and `@stackblitz/sdk`, or evidence that both are needed - A licensing decision for production commercial use before release ## Tool Discipline Use `Read`, `Glob`, and `Grep` to inspect package manifests, lockfiles, browser entrypoints, headers, and existing secret bindings. Use `WebFetch` only for current official StackBlitz or WebContainers documentation. Use `Write` or `Edit` only after the evidence pass, and never place API keys or OAuth material in source files. ## Current Contract - Pin the package version selected by the repository's dependency policy; do not install an unreviewed moving tag. - Call `configureAPIKey` before `WebContainer.boot()` when a commercial license supplies an API key. - Call `auth.init` before boot when organization users need private-package access; the user must be logged in, belong to the issuing organization, and authorize the site. - Match the `Cross-Origin-Embedder-Policy` response header to the `coep` boot option. Use HTTPS outside localhost. - A StackBlitz SDK embed is a separate surface and does not require booting a custom WebContainer in the host application. ## Authentication Public prototypes may not need user authentication, but production commercial use requires a licensing review. Treat the WebContainer API key as a secret runtime binding. Treat the auth client ID and scope as configuration, initialize auth during page loading, and handle `need-auth`, `authorized`, and `auth-failed` explicitly. Never infer that ordinary StackBlitz login grants access to private packages. ## Workflow 1. Inspect the framework, package manager, lockfile, client/server boundary, CSP, and current response-header configuration. 2. Choose the minimum package surface and record the installed or proposed pinned version. 3. Decide whether the integration needs a commercial API key, organization auth, neither, or both. 4. Configure consistent COOP/COEP headers and the matching boot option; verify the final HTML response, including cached responses. 5. Add one startup module that orders API-key configuration, auth initialization, and the single boot call correctly. 6. Validate in a supported desktop browser over the same origin and headers intended for deployment. ## Approval Boundaries Default to inspection and a proposed patch. Require explicit authorization before changing production headers, CSP, identity-provider settings, licensed API-key bindings, or deployment configuration. Never create, rotate, expose, or revoke a credential without a separately authorized operational step. ## Output Return the selected integration mode, package/version evidence, licensing and auth decision, header/boot contract, changed or proposed files, verification results, rollout plan, rollback, and unresolved browser or policy risks. ## Error Handling | Condition | Response | |---|---| | API key configured after boot | Stop and move configuration before the first boot call. | | Auth reports `need-auth` | Present the user-authorized flow; do not loop or fabricate authorization. | | `crossOriginIsolated` is false | Inspect actual response headers and cache behavior before changing code. | | Integration mode is unclear | Compare custom runtime requirements with embed-only requirements before installing both SDKs. | ## Examples Given an existing Vite app, identify its lockfile and hosting headers, select a pinned WebContainer API version, document whether commercial licensing applies, and propose a single ordered startup module without reading any secret value. ## Resources - [Official StackBlitz and WebContainers references](references/official-docs.md) - [WebContainer API reference](https://webcontainers.io/api) - [StackBlitz JavaScript SDK](https://developer.stackblitz.com/platform/api/javascript-sdk)
Pliki w paczce (2)
- SKILL.md 5 KB
- references/official-docs.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie stackblitz-install-auth.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 2e7ff7fc8f7e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100stackblitz-common-errors
Diagnozuje błędy startu WebContainer, izolacji, Service Workera, zależności, procesów i podglądu w przeglądarce na podstawie dowodów, zanim zmieni kod lub nagłówki. - 100stackblitz-local-dev-loop
Ustanawia powtarzalną lokalną pętlę rozwoju i testów w przeglądarce dla hosta WebContainer, z asercjami nagłówków izolacji, pojedynczym startem przy HMR i kontrolą sprzątania. - 100customerio-install-auth
Instaluje SDK lub CLI Customer.io i konfiguruje uwierzytelnianie, w tym klucze API, w nowym projekcie. - 100linear-install-auth
Instaluje i konfiguruje uwierzytelnianie SDK i CLI Linear, w tym klucze API, przy nowej integracji w projekcie.