@xopcai/xopc 0.0.103 → 0.0.104

package/skills/creative/theme-factory/SKILL-zh.md

@@ -1,59 +0,0 @@
----
-name: theme-factory
-description: 用于为制品应用主题样式的工具包。这些制品可以是幻灯片、文档、报告、HTML 落地页等。有 10 个预设主题（包含颜色/字体）可应用于已创建的任何制品，也可以即时生成新主题。
-license: 完整条款见 LICENSE.txt
----
-
-# Theme Factory Skill（主题工厂技能）
-
-本技能提供一组精心策划的专业字体和颜色主题，每个主题都包含精心挑选的调色板和字体搭配。选择主题后，可将其应用于任何制品。
-
-## 目的
-
-将一致、专业的样式应用于演示幻灯片。每个主题包括：
-- 包含十六进制颜色代码的协调调色板
-- 标题和正文文字的互补字体搭配
-- 适合不同上下文和受众的独特视觉风格
-
-## 使用说明
-
-要将样式应用于幻灯片或其他制品：
-
-1. **展示主题预览**：展示 `theme-showcase.pdf` 文件，让用户直观查看所有可用主题。不要对其进行任何修改；仅展示文件供查看。
-2. **询问用户选择**：询问用户要为幻灯片应用哪个主题
-3. **等待选择**：获得关于选定主题的明确确认
-4. **应用主题**：一旦选定了主题，将选定主题的颜色和字体应用到幻灯片/制品中
-
-## 可用主题
-
-以下 10 个主题可供使用，每个主题在 `theme-showcase.pdf` 中有展示：
-
-1. **海洋深处（Ocean Depths）** - 专业且平静的海洋主题
-2. **日落大道（Sunset Boulevard）** - 温暖而充满活力的日落色彩
-3. **森林冠层（Forest Canopy）** - 自然质朴的大地色调
-4. **现代极简（Modern Minimalist）** - 干净现代的灰度风格
-5. **黄金时刻（Golden Hour）** - 丰富温暖的秋日调色板
-6. **北极冰霜（Arctic Frost）** - 凉爽清新的冬季主题
-7. **沙漠玫瑰（Desert Rose）** - 柔和精致的灰粉色系
-8. **科技革新（Tech Innovation）** - 大胆现代的科技审美
-9. **植物花园（Botanical Garden）** - 清新自然的园艺色彩
-10. **午夜星系（Midnight Galaxy）** - 戏剧性的宇宙深色系
-
-## 主题详情
-
-每个主题在 `themes/` 目录中有完整定义，包括：
-- 包含十六进制颜色代码的协调调色板
-- 标题和正文文字的互补字体搭配
-- 适合不同上下文和受众的独特视觉风格
-
-## 应用流程
-
-选定偏好的主题后：
-1. 从 `themes/` 目录读取对应的主题文件
-2. 在整个幻灯片中一致地应用指定的颜色和字体
-3. 确保适当的对比度和可读性
-4. 在所有幻灯片中保持主题的视觉风格
-
-## 创建自己的主题
-
-在没有现有主题适合某个制品的情况下，创建自定义主题。根据提供的输入，生成一个类似上述主题的新主题。给主题起一个类似的名称，描述该字体/颜色组合所代表的风格。使用提供的任何基本描述来选择适当的颜色/字体。生成主题后，展示给用户审阅和确认。之后，按照上述方法应用主题。

package/skills/creative/web-artifacts-builder/LICENSE.txt

@@ -1,202 +0,0 @@
-
-                                 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 2026 Anthropic, PBC.
-
-   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/skills/creative/web-artifacts-builder/SKILL-zh.md

@@ -1,74 +0,0 @@
----
-name: web-artifacts-builder
-description: 使用现代前端 Web 技术（React、Tailwind CSS、shadcn/ui）创建精密的、多组件的 claude.ai HTML 制品。用于需要状态管理、路由或 shadcn/ui 组件的复杂制品——不适用于简单的单文件 HTML/JSX 制品。
-license: 完整条款见 LICENSE.txt
----
-
-# Web Artifacts Builder（Web 制品构建器）
-
-要构建功能强大的前端 claude.ai 制品，按照以下步骤：
-1. 使用 `scripts/init-artifact.sh` 初始化前端仓库
-2. 通过编辑生成的代码开发你的制品
-3. 使用 `scripts/bundle-artifact.sh` 将所有代码打包到单个 HTML 文件中
-4. 向用户展示制品
-5. （可选）测试制品
-
-**技术栈**：React 18 + TypeScript + Vite + Parcel（打包）+ Tailwind CSS + shadcn/ui
-
-## 设计与样式指南
-
-非常重要：为避免常说的"AI 同质化"设计，避免过度使用居中布局、紫色渐变、统一圆角和 Inter 字体。
-
-## 快速开始
-
-### 第 1 步：初始化项目
-
-运行初始化脚本创建新的 React 项目：
-```bash
-bash scripts/init-artifact.sh <project-name>
-cd <project-name>
-```
-
-这会创建一个完全配置好的项目，包含：
-- ✅ React + TypeScript（通过 Vite）
-- ✅ Tailwind CSS 3.4.1 及 shadcn/ui 主题系统
-- ✅ 配置好的路径别名（`@/`）
-- ✅ 预安装了 40+ 个 shadcn/ui 组件
-- ✅ 包含所有 Radix UI 依赖
-- ✅ Parcel 配置好用于打包（通过 .parcelrc）
-- ✅ Node 18+ 兼容性（自动检测并锁定 Vite 版本）
-
-### 第 2 步：开发你的制品
-
-要构建制品，编辑生成的文件。参考下方"常见开发任务"的指导。
-
-### 第 3 步：打包到单个 HTML 文件
-
-要将 React 应用打包为单个 HTML 制品：
-```bash
-bash scripts/bundle-artifact.sh
-```
-
-这会创建 `bundle.html`——一个自包含的制品，包含所有内联的 JavaScript、CSS 和依赖。此文件可直接在 Claude 对话中作为制品分享。
-
-**要求**：你的项目根目录必须有一个 `index.html` 文件。
-
-**脚本作用**：
-- 安装打包依赖（parcel、@parcel/config-default、parcel-resolver-tspaths、html-inline）
-- 创建带路径别名支持的 `.parcelrc` 配置
-- 使用 Parcel 构建（无 source map）
-- 使用 html-inline 将所有资源内联到单个 HTML 中
-
-### 第 4 步：与用户分享制品
-
-最后，在对话中与用户分享打包好的 HTML 文件，以便他们作为制品查看。
-
-### 第 5 步：测试/可视化制品（可选）
-
-注意：这是完全可选的步骤。仅在必要或请求时执行。
-
-要测试/可视化制品，使用可用工具（包括其他技能或内置工具如 Playwright 或 Puppeteer）。通常，避免提前测试制品，因为这会在请求和用户看到完成的制品之间增加延迟。在展示制品后，如果请求或出现问题再进行测试。
-
-## 参考
-
-- **shadcn/ui 组件**：https://ui.shadcn.com/docs/components

package/skills/creative/web-artifacts-builder/SKILL.md

@@ -1,74 +0,0 @@
----
-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.
-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

package/skills/creative/web-artifacts-builder/scripts/bundle-artifact.sh

@@ -1,54 +0,0 @@
-#!/bin/bash
-set -e
-
-echo "📦 Bundling React app to single HTML artifact..."
-
-# Check if we're in a project directory
-if [ ! -f "package.json" ]; then
-  echo "❌ Error: No package.json found. Run this script from your project root."
-  exit 1
-fi
-
-# Check if index.html exists
-if [ ! -f "index.html" ]; then
-  echo "❌ Error: No index.html found in project root."
-  echo "   This script requires an index.html entry point."
-  exit 1
-fi
-
-# Install bundling dependencies
-echo "📦 Installing bundling dependencies..."
-pnpm add -D parcel @parcel/config-default parcel-resolver-tspaths html-inline
-
-# Create Parcel config with tspaths resolver
-if [ ! -f ".parcelrc" ]; then
-  echo "🔧 Creating Parcel configuration with path alias support..."
-  cat > .parcelrc << 'EOF'
-{
-  "extends": "@parcel/config-default",
-  "resolvers": ["parcel-resolver-tspaths", "..."]
-}
-EOF
-fi
-
-# Clean previous build
-echo "🧹 Cleaning previous build..."
-rm -rf dist bundle.html
-
-# Build with Parcel
-echo "🔨 Building with Parcel..."
-pnpm exec parcel build index.html --dist-dir dist --no-source-maps
-
-# Inline everything into single HTML
-echo "🎯 Inlining all assets into single HTML file..."
-pnpm exec html-inline dist/index.html > bundle.html
-
-# Get file size
-FILE_SIZE=$(du -h bundle.html | cut -f1)
-
-echo ""
-echo "✅ Bundle complete!"
-echo "📄 Output: bundle.html ($FILE_SIZE)"
-echo ""
-echo "You can now use this single HTML file as an artifact in Claude conversations."
-echo "To test locally: open bundle.html in your browser"