plcode-windows-x64 2.1.0

package/.plcode/skill/experimental/architecture-diagram/SKILL.md

@@ -0,0 +1,378 @@
+---
+name: architecture-diagram
+description: Generate professional, dark-themed SVG architecture and infrastructure diagrams as standalone HTML files. Use this skill when the user asks to create system architecture diagrams, cloud infrastructure maps, microservice topologies, database schemas, deployment diagrams, or any technical infrastructure visualization. Produces a single self-contained HTML file with inline SVG that opens in any browser with no dependencies.
+category: design
+---
+
+# Architecture Diagram Skill
+
+Generate professional, dark-themed technical architecture diagrams as standalone HTML files with inline SVG graphics. No external tools, no API keys, no rendering libraries — write the HTML file and the user opens it in a browser.
+
+Based on [Cocoon AI's architecture-diagram-generator](https://github.com/Cocoon-AI/architecture-diagram-generator) (MIT).
+
+## Scope
+
+**Best suited for:**
+
+- Software system architecture (frontend / backend / database layers)
+- Cloud infrastructure (VPC, regions, subnets, managed services)
+- Microservice / service-mesh topology
+- Database + API maps, deployment diagrams
+- CI/CD pipeline visualization
+- Network topology and security boundaries
+- Anything with a tech-infra subject that fits a dark, grid-backed aesthetic
+
+**Not suited for:**
+
+- Scientific diagrams (physics, chemistry, biology)
+- Physical objects, floor plans, anatomy
+- Hand-drawn whiteboard sketches
+- Animated explainers or interactive dashboards
+- UML class diagrams (use a dedicated UML tool)
+
+## Workflow
+
+1. User describes their system architecture (components, connections, technologies)
+2. Plan the layout: identify component groups, layers, and connection flows
+3. Generate the HTML file following the design system below
+4. Save to a `.html` file in the project directory (e.g., `./architecture-diagram.html`)
+5. Tell the user to open it in any browser — it works offline, zero dependencies
+
+### Output Location
+
+Save diagrams to a user-specified path, or default to the current working directory:
+
+```
+./[descriptive-name]-architecture.html
+```
+
+## Design System & Visual Language
+
+### Color Palette (Semantic Mapping)
+
+Use specific `rgba` fills and hex strokes to categorize components by type:
+
+| Component Type  | Fill (rgba)               | Stroke (Hex)            |
+| :-------------- | :------------------------ | :---------------------- |
+| **Frontend**    | `rgba(8, 51, 68, 0.4)`    | `#22d3ee` (cyan-400)    |
+| **Backend**     | `rgba(6, 78, 59, 0.4)`    | `#34d399` (emerald-400) |
+| **Database**    | `rgba(76, 29, 149, 0.4)`  | `#a78bfa` (violet-400)  |
+| **AWS/Cloud**   | `rgba(120, 53, 15, 0.3)`  | `#fbbf24` (amber-400)   |
+| **Security**    | `rgba(136, 19, 55, 0.4)`  | `#fb7185` (rose-400)    |
+| **Message Bus** | `rgba(251, 146, 60, 0.3)` | `#fb923c` (orange-400)  |
+| **External**    | `rgba(30, 41, 59, 0.5)`   | `#94a3b8` (slate-400)   |
+
+### Typography & Background
+
+- **Font:** JetBrains Mono (Monospace), loaded from Google Fonts
+- **Sizes:** 12px (component names), 9px (sublabels), 8px (annotations), 7px (tiny labels)
+- **Background:** Slate-950 (`#020617`) with a subtle 40px grid pattern
+
+```svg
+<!-- Background Grid Pattern -->
+<pattern id="grid" width="40" height="40" patternUnits="userSpaceOnUse">
+  <path d="M 40 0 L 0 0 0 40" fill="none" stroke="#1e293b" stroke-width="0.5"/>
+</pattern>
+```
+
+## Technical Implementation Details
+
+### Component Rendering
+
+Components are rounded rectangles (`rx="6"`) with 1.5px strokes. Use a **double-rect masking technique** to prevent arrows from bleeding through semi-transparent fills:
+
+1. Draw an opaque background rect filled with `#0f172a`
+2. Draw the semi-transparent styled rect on top
+
+Example component:
+
+```svg
+<!-- Opaque mask -->
+<rect x="100" y="80" width="160" height="60" rx="6" fill="#0f172a"/>
+<!-- Styled rect -->
+<rect x="100" y="80" width="160" height="60" rx="6"
+      fill="rgba(6, 78, 59, 0.4)" stroke="#34d399" stroke-width="1.5"/>
+<!-- Label -->
+<text x="180" y="105" text-anchor="middle" fill="#34d399"
+      font-size="12" font-family="'JetBrains Mono', monospace">API Server</text>
+<text x="180" y="120" text-anchor="middle" fill="#94a3b8"
+      font-size="9" font-family="'JetBrains Mono', monospace">Node.js / Express</text>
+```
+
+### Connection Rules
+
+- **Z-Order:** Draw arrows FIRST in the SVG (after the grid background) so they render behind component boxes
+- **Arrowheads:** Define via SVG `<marker>` elements in `<defs>`
+- **Standard connections:** Solid lines with matching component color
+- **Security flows:** Dashed lines in rose color (`#fb7185`, `stroke-dasharray="4,4"`)
+- **Async/event flows:** Dashed lines in orange (`#fb923c`, `stroke-dasharray="6,3"`)
+
+Arrowhead marker definition:
+
+```svg
+<defs>
+  <marker id="arrow-emerald" viewBox="0 0 10 10" refX="9" refY="5"
+          markerWidth="6" markerHeight="6" orient="auto-start-reverse">
+    <path d="M 0 0 L 10 5 L 0 10 z" fill="#34d399"/>
+  </marker>
+</defs>
+```
+
+### Boundary Boxes
+
+- **Security Groups:** Dashed border (`stroke-dasharray="4,4"`), rose color, `rx="8"`
+- **Region/Zone boundaries:** Large dashed border (`stroke-dasharray="8,4"`), amber color, `rx="12"`
+- **Logical groupings:** Dotted border (`stroke-dasharray="2,4"`), slate color, `rx="6"`
+
+### Spacing & Layout Logic
+
+- **Standard component height:** 60px (simple services); 80–120px (large components with details)
+- **Minimum vertical gap:** 40px between components
+- **Minimum horizontal gap:** 30px between components
+- **Message buses / event streams:** Place IN the gap between services, not overlapping
+- **Legend placement:** CRITICAL — must be placed outside all boundary boxes. Calculate the lowest Y-coordinate of all boundaries and place the legend at least 20px below it.
+
+## HTML Document Structure
+
+The generated HTML file has four sections:
+
+### 1. Header
+
+Title with a pulsing status dot and subtitle describing the system.
+
+### 2. Main SVG Diagram
+
+The architecture diagram in an SVG element, contained within a rounded border card. The SVG should use a `viewBox` for responsive scaling.
+
+### 3. Summary Cards
+
+A grid of 2–4 cards below the diagram summarizing key architectural details:
+
+- **Components** — list of major services and their roles
+- **Data Flow** — how data moves through the system
+- **Key Technologies** — tech stack overview
+- **Notes** — design decisions, scaling considerations
+
+### 4. Footer
+
+Minimal metadata line (generation date, project name).
+
+### Card Pattern
+
+```html
+<div class="card">
+  <div class="card-header">
+    <div class="card-dot cyan"></div>
+    <h3>Components</h3>
+  </div>
+  <ul>
+    <li>• API Gateway — request routing & auth</li>
+    <li>• User Service — authentication & profiles</li>
+  </ul>
+</div>
+```
+
+## CSS Essentials
+
+The HTML file must include these core styles inline in a `<style>` block:
+
+```css
+@import url("https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;700&display=swap");
+
+* {
+  margin: 0;
+  padding: 0;
+  box-sizing: border-box;
+}
+
+body {
+  background: #020617;
+  color: #e2e8f0;
+  font-family: "JetBrains Mono", monospace;
+  padding: 2rem;
+  min-height: 100vh;
+}
+
+.container {
+  max-width: 1200px;
+  margin: 0 auto;
+}
+
+.header {
+  text-align: center;
+  margin-bottom: 2rem;
+}
+.header h1 {
+  font-size: 1.5rem;
+  color: #f1f5f9;
+}
+.header p {
+  font-size: 0.75rem;
+  color: #64748b;
+  margin-top: 0.5rem;
+}
+
+.diagram-card {
+  border: 1px solid #1e293b;
+  border-radius: 12px;
+  padding: 1.5rem;
+  background: #0f172a;
+  margin-bottom: 2rem;
+}
+
+.diagram-card svg {
+  width: 100%;
+  height: auto;
+}
+
+.cards-grid {
+  display: grid;
+  grid-template-columns: repeat(auto-fit, minmax(280px, 1fr));
+  gap: 1rem;
+  margin-bottom: 2rem;
+}
+
+.card {
+  background: #0f172a;
+  border: 1px solid #1e293b;
+  border-radius: 8px;
+  padding: 1.25rem;
+}
+
+.card-header {
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+  margin-bottom: 0.75rem;
+}
+
+.card-dot {
+  width: 8px;
+  height: 8px;
+  border-radius: 50%;
+  animation: pulse 2s infinite;
+}
+
+.card-dot.cyan {
+  background: #22d3ee;
+}
+.card-dot.emerald {
+  background: #34d399;
+}
+.card-dot.violet {
+  background: #a78bfa;
+}
+.card-dot.amber {
+  background: #fbbf24;
+}
+
+.card h3 {
+  font-size: 0.85rem;
+  color: #f1f5f9;
+}
+.card ul {
+  list-style: none;
+}
+.card li {
+  font-size: 0.7rem;
+  color: #94a3b8;
+  padding: 0.2rem 0;
+}
+
+.footer {
+  text-align: center;
+  font-size: 0.65rem;
+  color: #475569;
+  padding-top: 1rem;
+  border-top: 1px solid #1e293b;
+}
+
+@keyframes pulse {
+  0%,
+  100% {
+    opacity: 1;
+  }
+  50% {
+    opacity: 0.4;
+  }
+}
+```
+
+## Output Requirements
+
+- **Single file:** One self-contained `.html` file
+- **No external dependencies:** All CSS and SVG inline (exception: Google Fonts import)
+- **No JavaScript:** Pure CSS for animations (pulsing dots, etc.)
+- **Responsive:** SVG uses `viewBox` so it scales in any browser window
+- **Browser compatibility:** Must render correctly in Chrome, Firefox, Safari, Edge
+
+## Layout Planning Tips
+
+Before writing SVG, sketch the layout mentally:
+
+1. **Identify layers** — external users/clients at top, frontend layer, backend layer, data layer at bottom
+2. **Group related services** — wrap with boundary boxes (security groups, regions)
+3. **Route connections** — prefer straight vertical/horizontal lines; use one bend for non-adjacent connections; avoid crossing lines where possible
+4. **Calculate coordinates** — start with a grid: X positions at 100, 300, 500, 700... and Y positions at 80, 200, 320, 440...
+5. **Size the viewBox** — add 40px padding around all content; set `viewBox="0 0 [width] [height]"`
+
+## Example Minimal Diagram Structure
+
+```html
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>System Architecture</title>
+    <style>
+      /* ... full CSS from above ... */
+    </style>
+  </head>
+  <body>
+    <div class="container">
+      <div class="header">
+        <h1>
+          <span class="card-dot cyan" style="display:inline-block;vertical-align:middle;margin-right:8px;"></span>System
+          Architecture
+        </h1>
+        <p>High-level overview of service topology</p>
+      </div>
+      <div class="diagram-card">
+        <svg viewBox="0 0 800 600" xmlns="http://www.w3.org/2000/svg">
+          <defs>
+            <pattern id="grid" width="40" height="40" patternUnits="userSpaceOnUse">
+              <path d="M 40 0 L 0 0 0 40" fill="none" stroke="#1e293b" stroke-width="0.5" />
+            </pattern>
+            <!-- arrowhead markers here -->
+          </defs>
+          <rect width="800" height="600" fill="#020617" />
+          <rect width="800" height="600" fill="url(#grid)" />
+          <!-- arrows drawn first (behind components) -->
+          <!-- boundary boxes -->
+          <!-- components on top -->
+          <!-- legend last, below all boundaries -->
+        </svg>
+      </div>
+      <div class="cards-grid">
+        <!-- summary cards -->
+      </div>
+      <div class="footer">
+        <p>Generated with PLCODE · architecture-diagram skill</p>
+      </div>
+    </div>
+  </body>
+</html>
+```
+
+## Checklist Before Saving
+
+- [ ] All components use the double-rect masking technique
+- [ ] Arrows are drawn before (behind) component rects in SVG order
+- [ ] Legend is placed below all boundary boxes
+- [ ] Message buses sit in gaps, not overlapping components
+- [ ] viewBox dimensions encompass all content with padding
+- [ ] All text uses JetBrains Mono font-family
+- [ ] Color coding matches the semantic palette table
+- [ ] File is self-contained (no external CSS/JS, only Google Fonts import)
+- [ ] No JavaScript — animations are CSS-only

package/.plcode/skill/experimental/artifacts-builder/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/.plcode/skill/experimental/artifacts-builder/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: web-artifacts-builder
+description: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
+category: design
+license: Complete terms in LICENSE.txt
+---
+
+# Web Artifacts Builder
+
+To build powerful frontend claude.ai artifacts, follow these steps:
+
+1. Initialize the frontend repo using `scripts/init-artifact.sh`
+2. Develop your artifact by editing the generated code
+3. Bundle all code into a single HTML file using `scripts/bundle-artifact.sh`
+4. Display artifact to user
+5. (Optional) Test the artifact
+
+**Stack**: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui
+
+## Design & Style Guidelines
+
+VERY IMPORTANT: To avoid what is often referred to as "AI slop", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.
+
+## Quick Start
+
+### Step 1: Initialize Project
+
+Run the initialization script to create a new React project:
+
+```bash
+bash scripts/init-artifact.sh <project-name>
+cd <project-name>
+```
+
+This creates a fully configured project with:
+
+- ✅ React + TypeScript (via Vite)
+- ✅ Tailwind CSS 3.4.1 with shadcn/ui theming system
+- ✅ Path aliases (`@/`) configured
+- ✅ 40+ shadcn/ui components pre-installed
+- ✅ All Radix UI dependencies included
+- ✅ Parcel configured for bundling (via .parcelrc)
+- ✅ Node 18+ compatibility (auto-detects and pins Vite version)
+
+### Step 2: Develop Your Artifact
+
+To build the artifact, edit the generated files. See **Common Development Tasks** below for guidance.
+
+### Step 3: Bundle to Single HTML File
+
+To bundle the React app into a single HTML artifact:
+
+```bash
+bash scripts/bundle-artifact.sh
+```
+
+This creates `bundle.html` - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact.
+
+**Requirements**: Your project must have an `index.html` in the root directory.
+
+**What the script does**:
+
+- Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)
+- Creates `.parcelrc` config with path alias support
+- Builds with Parcel (no source maps)
+- Inlines all assets into single HTML using html-inline
+
+### Step 4: Share Artifact with User
+
+Finally, share the bundled HTML file in conversation with the user so they can view it as an artifact.
+
+### Step 5: Testing/Visualizing the Artifact (Optional)
+
+Note: This is a completely optional step. Only perform if necessary or requested.
+
+To test/visualize the artifact, use available tools (including other Skills or built-in tools like Playwright or Puppeteer). In general, avoid testing the artifact upfront as it adds latency between the request and when the finished artifact can be seen. Test later, after presenting the artifact, if requested or if issues arise.
+
+## Reference
+
+- **shadcn/ui components**: https://ui.shadcn.com/docs/components