OpenSkillIndex← back to search
claude-codedevelopment

Full-stack-skills stitch-vue-bootstrap-components

Convert Stitch designs into modular Vite + Vue 3 + BootstrapVue/BootstrapVueNext components. Use when the user mentions Bootstrap or BootstrapVue conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Bootstrap utilities, enforces Vue SFC structure with Bootstrap components (b-container, b-row, b-col, b-button, b-card).

install
source · Clone the upstream repo
git clone https://github.com/partme-ai/full-stack-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/partme-ai/full-stack-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/stitch-skills/stitch-vue-bootstrap-components" ~/.claude/skills/partme-ai-full-stack-skills-stitch-vue-bootstrap-components && rm -rf "$T"
manifest: skills/stitch-skills/stitch-vue-bootstrap-components/SKILL.md
tags
#stitch-conversion#vue-3#bootstrapvue#component-generation#frontend#design-to-code
source content

Stitch to Vue 3 + Bootstrap Components

Constraint: Only use this skill when the user explicitly mentions "Stitch" and converting Stitch screens to Vue 3 + Bootstrap (Vite, .vue SFC, BootstrapVue Vue 3 or BootstrapVueNext).

You are a frontend engineer turning Stitch designs into clean, modular Vue 3 + Bootstrap code. Use Stitch MCP (or stitch-mcp-get-screen) to retrieve screen metadata and HTML; use scripts and resources in this skill for reliable fetch and quality checks. Target stack: Vue 3 + BootstrapVue Vue.js 3 Support (@vue/compat) or BootstrapVueNext (Bootstrap 5 + Vue 3).

Prerequisites

  • Stitch MCP Server (https://stitch.withgoogle.com/docs/mcp/guide/)
  • Node.js and npm (for Vite/Vue 3 project)
  • Stitch project and screen IDs — two ways: (1) From a Stitch design URL: parse projectId (path) and screenId (
    node-id
    query). (2) When no URL or when browsing: use stitch-mcp-list-projects and stitch-mcp-list-screens to discover and obtain IDs.

Official Documentation

Retrieval and Networking

  1. Discover Stitch MCP prefix: Run 
    list_tools
    to find the prefix (e.g. 
    mcp_stitch__stitch:
    ).
  2. Fetch screen metadata: Call 
    [prefix]:get_screen
    with 
    projectId
    and 
    screenId
    (numeric IDs) to get design JSON, 
    htmlCode.downloadUrl
    , 
    screenshot.downloadUrl
    , dimensions, deviceType.
  3. High-reliability HTML download: AI fetch tools can fail on Google Cloud Storage URLs. Use Bash to run the skill script: 
    bash scripts/fetch-stitch.sh "<htmlCode.downloadUrl>" "temp/source.html"
    Ensure the URL is quoted.
  4. Visual reference: Use 
    screenshot.downloadUrl
    to confirm layout and details.

Architectural Rules

  • Modular components: Split the design into separate .vue files; avoid one giant SFC.
  • Logic isolation: Put event handlers and composables in 
    src/composables/
    or within script setup.
  • Data decoupling: Move static text, image URLs, and lists into 
    src/data/mockData.js
    (or .ts).
  • Bootstrap components only (use framework components when available): Use b-card for cards, b-alert for tips; do not use div.card or custom .card-header/.tips-text. Use 
    <b-container>
    , 
    <b-row>
    , 
    <b-col>
    , 
    <b-button>
    , etc. per references/contract.md; do not use raw 
    <button class="btn">
    or 
    <div class="card">
    when b-* applies.
  • Project-specific: Omit third-party license headers from generated components.

Execution Steps

  1. Environment: If the project has no 
    node_modules
    , run 
    npm install
    .
  2. Data layer: Create 
    src/data/mockData.js
    from the design content.
  3. Component drafting: Use 
    resources/component-template.vue
    as base; replace placeholder with real component name and Bootstrap Vue tags per contract.
  4. Wiring: Update the app entry (e.g. 
    App.vue
    or router) to render the new components.
  5. Quality check: Verify against 
    resources/architecture-checklist.md
    ; run 
    npm run dev
    to confirm visually.

Integration with This Repo

  • Get screen: Use stitch-mcp-get-screen with projectId and screenId. Obtain IDs either by parsing a Stitch design URL or by using stitch-mcp-list-projects and stitch-mcp-list-screens when no URL or when the user needs to browse/select.
  • Design spec: If Stitch was generated with stitch-ui-design-spec-bootstrap constraints, map to Vue SFC and Bootstrap Vue components. If converting from Stitch HTML (e.g. get_screen htmlCode), use references/tailwind-to-bootstrap.md for Tailwind utility → Bootstrap utilities/components, then references/contract.md for component API.
  • Design system: If the project has DESIGN.md (from stitch-design-md), align colors and spacing with that system when mapping to Bootstrap tokens.

Troubleshooting

  • Fetch errors: Quote the URL in the bash command; ensure 
    scripts/fetch-stitch.sh
    is executable.
  • Component mapping: Follow references/contract.md for layout (
    b-container
    /
    b-row
    /
    b-col
    ), buttons (
    b-button
    ), forms (
    b-form-group
    , 
    b-form-input
    ), cards (
    b-card
    ).

Example: Stitch HTML to Bootstrap Vue SFC

Stitch HTML with Tailwind card:

<div class="bg-white rounded-lg shadow p-4"><h2 class="text-lg font-bold">Title</h2><button class="bg-blue-500 text-white px-4 py-2 rounded">Action</button></div>

Converted Bootstrap Vue component:

<template>
  <b-card title="Title">
    <b-button variant="primary">Action</b-button>
  </b-card>
</template>

Key mapping: 

div.rounded-lg.shadow
becomes 
<b-card>
, raw 
<button>
becomes 
<b-button variant="primary">
, Tailwind colors map to Bootstrap variants.

References