profclaw 2.0.0 → 2.3.0

package/skills/deploy-vercel/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: deploy-vercel
+description: |
+  Deploy applications to Vercel. Handles project setup, environment variables,
+  and deployment. Returns the live URL after deploy.
+user-invocable: true
+metadata:
+  profclaw:
+    emoji: "▲"
+    category: deployment
+    requires:
+      bins: ["vercel"]
+---
+
+# Deploy to Vercel
+
+Deploy web applications to Vercel for instant production URLs.
+
+## When to Use
+- User asks to "deploy to Vercel" or "put this online"
+- User wants a live URL for a web app
+- Project is Next.js, React, Vite, or static HTML
+
+## Workflow
+
+### 1. Check Vercel CLI
+```bash
+exec command:"vercel --version"
+```
+If not installed: `exec command:"npm install -g vercel"`
+
+### 2. Check Auth
+```bash
+exec command:"vercel whoami"
+```
+If not authenticated: tell the user to run `vercel login`
+
+### 3. Deploy
+```bash
+exec command:"vercel --yes"
+```
+The `--yes` flag skips prompts and uses defaults.
+
+For production deploy:
+```bash
+exec command:"vercel --prod --yes"
+```
+
+### 4. Extract URL
+The deploy output contains the URL. Parse it:
+- Preview: `https://project-xxx.vercel.app`
+- Production: `https://project.vercel.app`
+
+### 5. Set Environment Variables (if needed)
+```bash
+exec command:"vercel env add DATABASE_URL production"
+```
+
+## Frameworks Auto-Detected
+Vercel auto-detects: Next.js, Nuxt, Remix, SvelteKit, Astro, Vite, CRA
+
+## After Deploy
+Tell the user:
+1. The live URL
+2. How to view in dashboard: `vercel inspect <url>`
+3. How to redeploy: `vercel --prod`
+4. How to set env vars: `vercel env add KEY`

package/skills/docker-deploy/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: docker-deploy
+description: |
+  Build, deploy, and manage applications with Docker. Handles Dockerfile generation,
+  image building, container management, and docker-compose workflows. Use when the user
+  wants to deploy, containerize, or run services locally.
+user-invocable: true
+metadata:
+  profclaw:
+    emoji: "🐳"
+    category: deployment
+    requires:
+      bins: ["docker"]
+---
+
+# Docker Deploy
+
+You help users build, deploy, and manage applications using Docker.
+
+## When to Use
+- User asks to "deploy", "run", "containerize", or "dockerize" an app
+- User wants to start a service locally
+- User mentions Docker, containers, or docker-compose
+
+## Workflow
+
+### 1. Analyze the Project
+First, understand what we're deploying:
+```
+project_info       # Detect language, framework, scripts
+read_file package.json   # Or requirements.txt, go.mod, Cargo.toml
+search_files "Dockerfile"  # Check if Dockerfile exists
+search_files "docker-compose"  # Check for compose file
+```
+
+### 2. Generate Dockerfile (if missing)
+Based on project type, generate an appropriate Dockerfile:
+
+**Node.js/TypeScript:**
+```dockerfile
+FROM node:22-slim AS build
+WORKDIR /app
+COPY package*.json pnpm-lock.yaml* ./
+RUN corepack enable && pnpm install --frozen-lockfile
+COPY . .
+RUN pnpm build
+
+FROM node:22-slim
+WORKDIR /app
+COPY --from=build /app/dist ./dist
+COPY --from=build /app/node_modules ./node_modules
+COPY --from=build /app/package.json ./
+EXPOSE 3000
+CMD ["node", "dist/server.js"]
+```
+
+**Python:**
+```dockerfile
+FROM python:3.12-slim
+WORKDIR /app
+COPY requirements.txt .
+RUN pip install --no-cache-dir -r requirements.txt
+COPY . .
+EXPOSE 8000
+CMD ["python", "-m", "uvicorn", "main:app", "--host", "0.0.0.0"]
+```
+
+**Static site:**
+```dockerfile
+FROM nginx:alpine
+COPY dist/ /usr/share/nginx/html/
+EXPOSE 80
+```
+
+### 3. Build the Image
+```bash
+exec command:"docker build -t {{app_name}} ."
+```
+
+### 4. Run the Container
+```bash
+exec command:"docker run -d --name {{app_name}} -p {{host_port}}:{{container_port}} {{app_name}}"
+```
+
+### 5. Verify and Return URL
+```bash
+exec command:"docker ps --filter name={{app_name}} --format '{{.Status}} {{.Ports}}'"
+```
+
+The URL will be: `http://localhost:{{host_port}}`
+
+For verification:
+```bash
+exec command:"curl -s -o /dev/null -w '%{http_code}' http://localhost:{{host_port}}"
+```
+
+## Docker Compose
+
+For multi-service apps:
+
+### Generate docker-compose.yml
+```yaml
+services:
+  app:
+    build: .
+    ports:
+      - "3000:3000"
+    environment:
+      - DATABASE_URL=postgres://postgres:postgres@db:5432/app
+    depends_on:
+      - db
+  db:
+    image: postgres:16-alpine
+    environment:
+      POSTGRES_PASSWORD: postgres
+    volumes:
+      - pgdata:/var/lib/postgresql/data
+
+volumes:
+  pgdata:
+```
+
+### Run with Compose
+```bash
+exec command:"docker compose up -d --build"
+exec command:"docker compose ps"
+exec command:"docker compose logs --tail 20"
+```
+
+## Management Commands
+
+| Action | Command |
+|--------|---------|
+| List containers | `docker ps -a` |
+| View logs | `docker logs {{name}} --tail 50` |
+| Stop | `docker stop {{name}}` |
+| Remove | `docker rm -f {{name}}` |
+| Restart | `docker restart {{name}}` |
+| Shell into | `docker exec -it {{name}} sh` |
+| Rebuild | `docker compose up -d --build` |
+
+## Port Selection
+- Avoid common ports: 3000 (profClaw), 5432 (postgres), 6379 (redis)
+- Use 8080, 8081, 8082 for web apps
+- Check availability: `exec command:"lsof -i :8080 || echo 'port free'"`
+
+## Troubleshooting
+- Build fails? Check: `docker build --no-cache -t {{name}} .`
+- Container exits? Check: `docker logs {{name}}`
+- Port in use? Try: `docker run -p 0:{{port}} {{name}}` (random host port)
+- Out of space? Run: `docker system prune -f`
+
+## After Deploy
+Always tell the user:
+1. The container name
+2. The URL (http://localhost:PORT)
+3. How to view logs: `docker logs {{name}}`
+4. How to stop: `docker stop {{name}}`

package/skills/full-stack-builder/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: full-stack-builder
+description: |
+  Build complete applications from a description. Creates project structure,
+  writes code, installs dependencies, runs tests, and optionally deploys.
+  The end-to-end "build me an app" skill.
+user-invocable: true
+metadata:
+  profclaw:
+    emoji: "🏗️"
+    category: coding
+---
+
+# Full Stack Builder
+
+Build complete applications from natural language descriptions.
+
+## When to Use
+- "Build me a..." / "Create an app that..." / "Make a website for..."
+- User describes functionality and wants a working app
+- Starting from scratch or adding major features
+
+## Workflow
+
+### Phase 1: Plan
+1. Understand the requirements (ask clarifying questions if vague)
+2. Choose the stack:
+   - **Static site**: HTML + CSS + JS (or Astro/Vite)
+   - **React app**: Vite + React + TypeScript
+   - **Full-stack**: Next.js or Hono backend + React frontend
+   - **API only**: Hono or Express + TypeScript
+   - **Python**: FastAPI or Flask
+3. Plan the file structure
+
+### Phase 2: Scaffold
+1. Create project directory
+2. Initialize package.json / pyproject.toml
+3. Create configuration files (tsconfig, vite.config, etc.)
+4. Install dependencies
+
+```bash
+exec command:"mkdir -p {{project_name}}"
+exec command:"cd {{project_name}} && pnpm init"
+exec command:"cd {{project_name}} && pnpm add {{deps}}"
+```
+
+### Phase 3: Build
+1. Write source files (components, routes, styles)
+2. Write tests
+3. Create README.md
+
+Use `write_file` for new files, `edit_file` for modifications.
+
+### Phase 4: Verify
+```bash
+typecheck         # Check types
+lint              # Check code quality
+test_run          # Run tests
+build             # Build for production
+```
+
+Fix any issues found, then re-verify.
+
+### Phase 5: Deploy (if requested)
+Based on project type:
+- **Static**: Docker (nginx) or Vercel/Cloudflare Pages
+- **Node.js**: Docker or Vercel/Fly.io
+- **API**: Docker or Cloudflare Workers
+
+After deploy, return the live URL.
+
+### Phase 6: Git (if requested)
+```bash
+exec command:"cd {{project}} && git init && git add -A && git commit -m 'feat: initial setup'"
+create_pr title:"Initial app setup" body:"Created {{project}} with {{stack}}"
+```
+
+## Output
+Always provide:
+1. Summary of what was built
+2. File structure overview
+3. How to run locally: `pnpm dev` or `docker compose up`
+4. How to deploy (if not already deployed)
+5. Live URL (if deployed)
+
+## Best Practices
+- Always use TypeScript for JS projects
+- Include a .gitignore
+- Add basic error handling
+- Include at least one test
+- Add a README with setup instructions
+- Use environment variables for secrets (never hardcode)