docs: Deploy documentation and workflows to GH pages

.claude/settings.json

@@ -0,0 +1,12 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(ls:*)",
+      "Bash(find:*)",
+      "mcp__repsonsible-vibe__whats_next",
+      "mcp__repsonsible-vibe__start_development"
+    ],
+    "deny": ["Bash(curl:*)"]
+  },
+  "env": {}
+}

.github/workflows/deploy-pages.yml

@@ -0,0 +1,65 @@
+name: Deploy VitePress Documentation to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+      - docs
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: npm
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build workflow visualizer
+        run: npm run build:visualizer
+
+      - name: Build VitePress site
+        run: |
+          cd docs
+          npm install
+          npm run build
+          touch .vitepress/dist/.nojekyll
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: docs/.vitepress/dist
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    needs: build
+    runs-on: ubuntu-latest
+    name: Deploy
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -104,6 +104,7 @@ dist
 # vitepress cache directory
 **/.vitepress/cache
 
+
 # Docusaurus cache and generated files
 .docusaurus
 

.mcp.json

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "repsonsible-vibe": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "responsible-vibe-mcp"
+      ],
+      "env": {}
+    }
+  }
+}

.vibe/development-plan-deploy-visualized-workflows.md

@@ -0,0 +1,62 @@
+# Development Plan: responsible-vibe-mcp (deploy-visualized-workflows branch)
+
+*Generated on 2025-07-26 by Vibe Feature MCP*
+*Workflow: minor*
+
+## Goal
+Set up GitHub Pages deployment for the workflow visualizer static site, enabling public access to the interactive workflow state machine visualization tool.
+
+## Explore
+
+### Phase Entrance Criteria:
+- [x] Development workflow has been initiated
+
+### Tasks
+- [x] Analyze current workflow visualizer structure and build process
+- [x] Research GitHub Pages deployment requirements
+- [x] Identify what needs to be configured for static site deployment
+- [x] Design deployment strategy and workflow
+
+### Completed
+- [x] Created development plan file
+- [x] Analyzed workflow visualizer: Vite-based TypeScript app with D3.js, builds to `dist/` folder with static assets
+- [x] Confirmed build process works: `npm run build` generates production-ready static files
+- [x] Researched GitHub Pages: supports static site deployment via GitHub Actions or branch-based deployment
+- [x] Identified deployment strategy: GitHub Actions workflow for automated building and deployment
+
+## Implement
+
+### Phase Entrance Criteria:
+- [x] GitHub Pages deployment requirements are understood
+- [x] Current build process has been analyzed
+- [x] Deployment strategy has been designed (VitePress multi-page site)
+- [x] All necessary configuration steps have been identified
+
+### Tasks
+- [x] Set up VitePress in docs/ directory
+- [x] Convert README.md to VitePress index page
+- [x] Create /workflows page with embedded visualizer
+- [x] Convert workflow visualizer to Vue component
+- [x] Set up VitePress GitHub Actions deployment
+- [x] Test build and deployment process
+
+### Completed
+- [x] Created VitePress documentation site in `docs/` directory
+- [x] Configured VitePress to use existing README.md as index page via rewrites
+- [x] Created `/workflows` page with embedded Vue component for visualizer
+- [x] Built Vue component that wraps existing TypeScript workflow visualizer
+- [x] Set up GitHub Actions workflow for automated deployment to GitHub Pages
+- [x] Successfully tested VitePress build process - generates static site
+
+## Key Decisions
+1. **Site Architecture**: **REVISED** - Use VitePress instead of plain Vite for multi-page documentation site
+2. **Content Structure**: Workflow visualizer as `/visualizer/` page, README as landing page, future docs as additional pages
+3. **Path Strategy**: VitePress file-based routing: `index.md` → `/`, `visualizer.md` → `/visualizer/`
+4. **Migration Approach**: Integrate existing workflow visualizer as Vue component within VitePress
+5. **Deployment Method**: VitePress GitHub Actions workflow with built-in GitHub Pages support
+
+## Notes
+*Additional context and observations*
+
+---
+*This plan is maintained by the LLM. Tool responses provide guidance on which section to focus on and what tasks to work on.*

.vscode/settings.json

@@ -0,0 +1,2 @@
+{
+}

CLAUDE.md

@@ -0,0 +1,72 @@
+
+You are an AI assistant that helps users develop software features.
+You do this by following a structured development process guided by the responsible-vibe-mcp server.
+
+IMPORTANT: Use responsible-vibe-mcp tools after each user message!
+
+Use the start_development() to start a new development.
+
+## Core Workflow
+
+Each tool call will return a JSON formatted response with an "instructions" field in it. Follow these instructions immediately after you received them.
+
+1. **Call whats_next() after each user interaction** to get phase-specific instructions
+2. **Follow the instructions** provided by responsible-vibe-mcp exactly
+3. **Update the plan file** as directed to maintain project memory
+4. **Mark completed tasks** with [x] when instructed
+5. **Provide conversation context** in each whats_next() call
+
+## Development Workflow
+
+The responsible-vibe-mcp server will guide you through development phases specific to the chosen workflow. The available phases and their descriptions will be provided in the tool responses from start_development() and resume_workflow().
+
+## Using whats_next()
+
+After each user interaction, call:
+
+```
+whats_next({
+  context: "Brief description of current situation",
+  user_input: "User's latest message",
+  conversation_summary: "Summary of conversation progress so far",
+  recent_messages: [
+    { role: "assistant", content: "Your recent message" },
+    { role: "user", content: "User's recent response" }
+  ]
+})
+```
+
+## Phase Transitions
+
+You can transition to the next phase when the tasks of the current phase were completed and the entrance criteria for the current phase have been met.
+
+Before suggesting any phase transition:
+- **Check the plan file** for the "Phase Entrance Criteria" section
+- **Evaluate current progress** against the defined criteria
+- **Only suggest transitions** when criteria are clearly met
+- **Be specific** about which criteria have been satisfied
+- **Ask the user** whether he agrees that the current phase is complete.
+
+```
+proceed_to_phase({
+  target_phase: "target_phase_name",  // Use phase names from the current workflow
+  reason: "Why you're transitioning"
+})
+```
+
+## Plan File Management
+
+- Add new tasks as they are identified
+- Mark tasks complete [x] when finished
+- Document important decisions in the Decisions Log
+- Keep the structure clean and readable
+
+## Conversation Context Guidelines
+
+Since responsible-vibe-mcp operates statelessly, provide:
+
+- **conversation_summary**: What the user wants, key decisions, progress
+- **recent_messages**: Last 3-5 relevant exchanges
+- **context**: Current situation and what you're trying to determine
+
+Remember: responsible-vibe-mcp guides the development process but relies on you to provide conversation context and follow its instructions precisely.

docs/.mcp.json

@@ -0,0 +1,10 @@
+{
+  "mcpServers": {
+    "npx": {
+      "type": "stdio",
+      "command": "playwright-mcp",
+      "args": [],
+      "env": {}
+    }
+  }
+}