スキル wiki-vitepress
📦

wiki-vitepress

低リスク ⚡ スクリプトを含む

Build VitePress Sites from Wiki Markdown

Transform generated wiki Markdown files into a polished, browsable VitePress static site. Includes dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production-ready build output.

対応: Claude Codex Code(CC)
🥉 72 ブロンズ
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「wiki-vitepress」を使用しています。 Generate VitePress site from wiki pages

期待される結果:

Created wiki-site/ directory with .vitepress/config.mts (dark theme, Mermaid configured), custom.css (Mermaid dark styles), theme/index.ts (click-to-zoom setup), and 12 wiki pages. Site builds successfully to .vitepress/dist/.

「wiki-vitepress」を使用しています。 Configure Mermaid diagrams for dark mode

期待される結果:

Applied three-layer dark mode fix: 1) themeVariables in config.mts with custom colors, 2) CSS overrides targeting .mermaid SVG elements, 3) JavaScript polling in theme/index.ts to replace inline styles. All diagrams render correctly in dark mode.

セキュリティ監査

低リスク
v1 • 2/25/2026

Static analyzer detected 69 patterns but 68 are false positives from Markdown documentation (code fences mistaken for shell execution, crypto references in comments). One legitimate concern: innerHTML assignment at line 112 uses self-generated content (low risk). Safe to publish with documentation warning.

1
スキャンされたファイル
154
解析された行数
2
検出結果
1
総監査数
低リスクの問題 (1)
innerHTML Usage
innerHTML assignment at line 112 sets modal content from el.outerHTML. While content is self-generated (not user input), innerHTML is generally discouraged due to potential XSS risks if content source changes.

リスク要因

⚡ スクリプトを含む (1)
監査者: claude

品質スコア

38
アーキテクチャ
100
保守性
87
コンテンツ
50
コミュニティ
88
セキュリティ
91
仕様準拠

作れるもの

Technical Documentation Site

Build a professional documentation site from wiki Markdown files with dark theme and interactive diagrams.

Knowledge Base Export

Convert internal wiki content into a browsable static site for team knowledge sharing.

Open Source Project Docs

Generate polished documentation sites with Mermaid diagrams for GitHub repositories.

これらのプロンプトを試す

Basic VitePress Setup
Create a VitePress site structure in wiki-site/ with dark theme config and copy all generated .md wiki files into the project.
Configure Mermaid Dark Mode
Set up the VitePress config with Mermaid plugin and configure dark theme variables for mermaid.themeVariables including primaryColor, nodeBorder, and background colors.
Add Click-to-Zoom for Diagrams
Implement click-to-zoom functionality for Mermaid diagrams by wrapping .mermaid containers with event listeners that open fullscreen modals on click.
Build Production Site
Run post-processing to fix Markdown syntax issues, then build the VitePress site with npm run docs:build and output the dist folder.

ベストプラクティス

  • Use setup() with onMounted for DOM manipulation, not enhanceApp() which runs during SSR
  • Apply polling for Mermaid SVG elements since they render asynchronously
  • Ensure all wiki pages have YAML frontmatter with title and description

回避

  • Do not use isCustomElement compiler option for bare generic parameters - causes crashes
  • Avoid relying solely on CSS for Mermaid dark mode - inline styles require JavaScript replacement
  • Do not attempt DOM access during SSR phase - document is undefined

よくある質問

Why do Mermaid diagrams not render in dark mode?
Mermaid applies inline styles with high specificity. You need the three-layer fix: themeVariables in config, CSS overrides with !important, and JavaScript to replace inline styles on rendered SVGs.
Why use setup() instead of enhanceApp() for DOM manipulation?
enhanceApp() runs during server-side rendering where document does not exist. setup() with onMounted only executes in the browser where DOM is available.
How do I enable click-to-zoom for diagrams?
Add event listeners to .mermaid elements that create a fullscreen modal div containing the SVG when clicked. The modal should close when clicked and use scale transform for zoom effect.
What Markdown syntax issues need fixing before build?
Replace br/ with br for Vue compatibility, wrap bare T generic parameters in backticks outside code fences, and ensure every page has YAML frontmatter with title and description.
Where does the built site output go?
The production build outputs to wiki-site/.vitepress/dist/ directory after running npm run docs:build.
Can I use this with light mode instead of dark mode?
Yes, change appearance to 'dark-mode' in config.mts and adjust the Mermaid theme variables and CSS colors for light backgrounds and dark text.

開発者の詳細

ファイル構成

📄 SKILL.md