beth-copilot 1.0.0

package/templates/.github/skills/vercel-react-best-practices/rules/server-serialization.md

@@ -0,0 +1,38 @@
+---
+title: Minimize Serialization at RSC Boundaries
+impact: HIGH
+impactDescription: reduces data transfer size
+tags: server, rsc, serialization, props
+---
+
+## Minimize Serialization at RSC Boundaries
+
+The React Server/Client boundary serializes all object properties into strings and embeds them in the HTML response and subsequent RSC requests. This serialized data directly impacts page weight and load time, so **size matters a lot**. Only pass fields that the client actually uses.
+
+**Incorrect (serializes all 50 fields):**
+
+```tsx
+async function Page() {
+  const user = await fetchUser()  // 50 fields
+  return <Profile user={user} />
+}
+
+'use client'
+function Profile({ user }: { user: User }) {
+  return <div>{user.name}</div>  // uses 1 field
+}
+```
+
+**Correct (serializes only 1 field):**
+
+```tsx
+async function Page() {
+  const user = await fetchUser()
+  return <Profile name={user.name} />
+}
+
+'use client'
+function Profile({ name }: { name: string }) {
+  return <div>{name}</div>
+}
+```

package/templates/.github/skills/web-design-guidelines/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: web-design-guidelines
+description: Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
+metadata:
+  author: vercel
+  version: "1.0.0"
+  argument-hint: <file-or-pattern>
+---
+
+# Web Interface Guidelines
+
+Review files for compliance with Web Interface Guidelines.
+
+## How It Works
+
+1. Fetch the latest guidelines from the source URL below
+2. Read the specified files (or prompt user for files/pattern)
+3. Check against all rules in the fetched guidelines
+4. Output findings in the terse `file:line` format
+
+## Guidelines Source
+
+Fetch fresh guidelines before each review:
+
+```
+https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
+```
+
+Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
+
+## Usage
+
+When a user provides a file or pattern argument:
+1. Fetch guidelines from the source URL above
+2. Read the specified files
+3. Apply all rules from the fetched guidelines
+4. Output findings using the format specified in the guidelines
+
+If no files specified, ask the user which files to review.

package/templates/AGENTS.md

@@ -0,0 +1,70 @@
+# Agent Instructions
+
+This project uses [Backlog.md](https://github.com/MrLesk/Backlog.md) for issue tracking.
+
+## Quick Setup
+
+```bash
+# Install (choose one)
+bun i -g backlog.md
+npm i -g backlog.md
+brew install backlog-md
+
+# Initialize in your project
+backlog init "Project Name"
+
+# Shell completion (optional)
+backlog completion install
+```
+
+## Quick Reference
+
+```bash
+# Create a task
+backlog task create "Task title" -d "Description"
+
+# List tasks
+backlog task list --plain
+
+# View Kanban board (TUI)
+backlog board
+
+# Web UI
+backlog browser
+
+# Configure settings
+backlog config
+```
+
+## Workflow
+
+1. Check available work: `backlog task list`
+2. Claim work: `backlog task edit <id> --status "In Progress"`
+3. Do the work
+4. Complete: `backlog task edit <id> --status "Done"`
+5. Commit and push
+
+## Landing the Plane (Session Completion)
+
+**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
+
+**MANDATORY WORKFLOW:**
+
+1. **Update Backlog.md** - Move completed tasks, add new items for follow-up work
+2. **Run quality gates** (if code changed) - Tests, linters, builds
+3. **PUSH TO REMOTE** - This is MANDATORY:
+   ```bash
+   git add -A
+   git commit -m "description of work"
+   git pull --rebase
+   git push
+   git status  # MUST show "up to date with origin"
+   ```
+4. **Verify** - All changes committed AND pushed
+5. **Hand off** - Provide context for next session
+
+**CRITICAL RULES:**
+- Work is NOT complete until `git push` succeeds
+- NEVER stop before pushing - that leaves work stranded locally
+- NEVER say "ready to push when you are" - YOU must push
+- If push fails, resolve and retry until it succeeds

package/templates/Backlog.md

@@ -0,0 +1,80 @@
+# Backlog
+
+> *"I don't have time to explain things twice. Read this."*
+
+Last updated: <!-- Update this date when making changes -->
+
+---
+
+## Completed
+
+| Task | Notes |
+|------|-------|
+| Initial setup | Beth agent system installed |
+
+---
+
+## In Progress
+
+*Nothing currently in progress.*
+
+---
+
+## Backlog (Prioritized)
+
+### High Priority (P1)
+
+- [ ] **Your first task** — Describe what needs to be done
+
+### Medium Priority (P2)
+
+- [ ] **Future work** — Things to do later
+
+### Low Priority (P3)
+
+- [ ] **Nice to have** — When you have time
+
+---
+
+## Decisions
+
+| Decision | Rationale | Date |
+|----------|-----------|------|
+| Use Beth orchestrator | Coordinated multi-agent workflows | Today |
+
+---
+
+## Status Summary
+
+**For Leadership:**
+
+Project initialized with Beth agent system.
+
+**What's Working:**
+
+- Beth agent (orchestrator) — Ready
+- Full agent roster — Ready
+- All skills — Loaded
+
+**What's Coming:**
+
+- Your roadmap here
+
+**Blockers:** None.
+
+---
+
+## How We Track Work
+
+This file is the single source of truth. When you start work:
+
+1. Move the task to **In Progress**
+2. Do the work
+3. Move to **Completed** when done
+4. Commit changes
+
+No external tools. No databases. Just this markdown file.
+
+---
+
+*"Now you know what's happening. Questions? I'll answer them. Complaints? Keep them to yourself."*

package/templates/mcp.json.example

@@ -0,0 +1,9 @@
+{
+  "$schema": "https://code.visualstudio.com/docs/copilot/chat/mcp-servers",
+  "servers": {
+    "shadcn": {
+      "command": "npx",
+      "args": ["shadcn@latest", "mcp"]
+    }
+  }
+}