Skip to content
Skills Library
Programming · Building & coding

stackblitz-core-workflow-b

/stackblitz-core-workflow-b

Design and implement a StackBlitz JavaScript SDK embed with an explicit project source, load strategy, UI options, persistence expectations, and responsive fallback. Use when documentation, training, or product pages need an interactive code example without owning a custom WebContainer runtime. Trigger with "embed StackBlitz", "StackBlitz SDK project", or "interactive code example".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design and implement a StackBlitz JavaScript SDK embed with an explicit project source, load strategy, UI options, persistence expectations, and responsive fallback. Use when documentation, training, or product pages need an interactive code example without owning a custom WebContainer runtime. Trigger with "embed StackBlitz", "StackBlitz SDK project", or "interactive code example".

Triggers from the description

embed StackBlitzStackBlitz SDK projectinteractive code example

Arguments

/stackblitz-core-workflow-b [project-path] [project-id|github-path|inline]
Original author description

Design and implement a StackBlitz JavaScript SDK embed with an explicit project source, load strategy, UI options, persistence expectations, and responsive fallback. Use when documentation, training, or product pages need an interactive code example without owning a custom WebContainer runtime. Trigger with "embed StackBlitz", "StackBlitz SDK project", or "interactive code example".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Workflow
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 65 lines, 529 words
SKILL.md preview
---
name: stackblitz-core-workflow-b
description: >-
  Design and implement a StackBlitz JavaScript SDK embed with an explicit project source, load strategy, UI options, persistence expectations, and responsive fallback. Use when documentation, training, or product pages need an interactive code example without owning a custom WebContainer runtime. Trigger with "embed StackBlitz", "StackBlitz SDK project", or "interactive code example".
argument-hint: "[project-path] [project-id|github-path|inline]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.7.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- stackblitz
- embedding
- documentation
model: inherit
effort: medium
compatibility: Designed for Claude Code
---
# StackBlitz Embed Integration

## Overview

This skill selects and implements the supported SDK method for an existing StackBlitz project, a public GitHub path, or an inline project. It treats the embed as third-party executable content with explicit loading, persistence, accessibility, and browser-support boundaries.

## Prerequisites

- A named host page and the source of the project to embed
- Confirmation that source code is public and safe to send to or execute through StackBlitz
- A static fallback and intended responsive behavior

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect the host component, content source, CSP, existing third-party scripts, and responsive patterns. Use `WebFetch` only for current official StackBlitz documentation. Use `Write` or `Edit` after the embed source and trust boundary are confirmed.

## Current Contract

- Use `embedProjectId` for an existing StackBlitz project, `embedGithubProject` for a public GitHub repository/path, and `embedProject` for a generated inline project.
- Inline projects live in browser memory unless a user forks them into a StackBlitz account; do not promise automatic persistence.
- Use current `EmbedOptions`; do not depend on deprecated `forceEmbedLayout` behavior.
- `clickToLoad` is a useful consent/performance boundary for expensive or numerous embeds.
- Treat the returned VM instance as an integration capability with an explicit owner and disposal path.
- WebContainer-based embeds have stricter browser constraints than static code fallbacks.

## Authentication

Do not embed private repositories, secrets, licensed source, or authenticated application state through a public project method. If enterprise origin or private access is required, stop and obtain the documented organization configuration and security approval.

## Workflow

1. Inspect the host page, choose the authoritative project source, and classify its sensitivity.
2. Select one SDK method and a pinned SDK version from the repository lockfile.
3. Define height, view, theme, `openFile`, and `clickToLoad` from the user journey; avoid deprecated options.
4. Add a titled container, loading state, error state, and accessible static link or code fallback.
5. Reconcile CSP, privacy disclosure, responsive layout, and browser support with the site owner.
6. Test initial load, user-triggered load, failure, keyboard flow, narrow viewport, and navigation cleanup.

## Approval Boundaries

Require explicit authorization before adding a third-party executable embed, changing CSP, loading private code, selecting an enterprise origin, or adding analytics. Show the data/source flow and fallback before deployment.

## Output

Return the selected source and SDK method, package/version evidence, embed options, trust and persistence semantics, accessibility/fallback behavior, tests run, changed files, rollout, and rollback.

## Error Handling

| Condition | Response |
|---|---|
| GitHub project cannot load | Verify the public repository, branch/tag/commit, and optional subfolder path. |
| Inline work disappears | Explain browser-memory semantics and offer an explicit fork/export path. |
| Embed breaks narrow layouts | Use a responsive container and preserve the static fallback. |
| Host CSP blocks the embed | Propose the narrow official origins; never disable CSP wholesale. |

## Examples

Given a public tutorial repository pinned to a commit, add a click-to-load embed opening the relevant file and provide a normal GitHub link plus static code sample when the runtime cannot load.

## Resources

- [Official StackBlitz and WebContainers references](references/official-docs.md)
- [StackBlitz JavaScript SDK](https://developer.stackblitz.com/platform/api/javascript-sdk)
- [SDK options reference](https://developer.stackblitz.com/platform/api/javascript-sdk-options)
Files in this package (2)
  • SKILL.md 5 KB
  • references/official-docs.md 1 KB

Versions

The database has no other skills named stackblitz-core-workflow-b.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 7e056dee8169 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100stackblitz-install-auth
    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.…
  • 100stackblitz-common-errors
    Diagnose WebContainer startup, isolation, Service Worker, dependency, process, preview, and browser failures from evidence before changing code or headers. Use when a StackBlitz runtime or embed fails, hangs, or behaves differently across browsers. Trigger with "StackBlitz…
  • 100bolt
    Bolt (bolt.new, by StackBlitz) is an AI app builder that turns a text prompt into a working web or mobile app, with built-in database, hosting and domains. Use when asked to prototype an app from a prompt in Bolt, write better Bolt prompts, plan with Plan Mode, spend fewer…
  • 100aws-sdk-js-v3-usage
    AWS SDK for JavaScript v3 development patterns. Use when writing JavaScript or TypeScript code that uses AWS services via @aws-sdk/* packages (aws-sdk-js-v3), or when asked about schemas, runtime validation, serialization, or code generation in the context of the JS/TS AWS SDK.
  • 100output-dev-code-style
    Code style conventions for Output SDK workflow projects. Use when writing or reviewing any TypeScript/JavaScript code. Discovers the project's own linting rules first; falls back to Output SDK conventions when no linter is configured.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.