start-vibing 4.1.0 → 4.1.2

package/template/.claude/skills/composition-patterns/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: vercel-composition-patterns
+description:
+  React composition patterns that scale. Use when refactoring components with
+  boolean prop proliferation, building flexible component libraries, or
+  designing reusable APIs. Triggers on tasks involving compound components,
+  render props, context providers, or component architecture. Includes React 19
+  API changes.
+license: MIT
+metadata:
+  author: vercel
+  version: '1.0.0'
+---
+
+# React Composition Patterns
+
+Composition patterns for building flexible, maintainable React components. Avoid
+boolean prop proliferation by using compound components, lifting state, and
+composing internals. These patterns make codebases easier for both humans and AI
+agents to work with as they scale.
+
+## When to Apply
+
+Reference these guidelines when:
+
+- Refactoring components with many boolean props
+- Building reusable component libraries
+- Designing flexible component APIs
+- Reviewing component architecture
+- Working with compound components or context providers
+
+## Rule Categories by Priority
+
+| Priority | Category                | Impact | Prefix          |
+| -------- | ----------------------- | ------ | --------------- |
+| 1        | Component Architecture  | HIGH   | `architecture-` |
+| 2        | State Management        | MEDIUM | `state-`        |
+| 3        | Implementation Patterns | MEDIUM | `patterns-`     |
+| 4        | React 19 APIs           | MEDIUM | `react19-`      |
+
+## Quick Reference
+
+### 1. Component Architecture (HIGH)
+
+- `architecture-avoid-boolean-props` - Don't add boolean props to customize
+  behavior; use composition
+- `architecture-compound-components` - Structure complex components with shared
+  context
+
+### 2. State Management (MEDIUM)
+
+- `state-decouple-implementation` - Provider is the only place that knows how
+  state is managed
+- `state-context-interface` - Define generic interface with state, actions, meta
+  for dependency injection
+- `state-lift-state` - Move state into provider components for sibling access
+
+### 3. Implementation Patterns (MEDIUM)
+
+- `patterns-explicit-variants` - Create explicit variant components instead of
+  boolean modes
+- `patterns-children-over-render-props` - Use children for composition instead
+  of renderX props
+
+### 4. React 19 APIs (MEDIUM)
+
+> **⚠️ React 19+ only.** Skip this section if using React 18 or earlier.
+
+- `react19-no-forwardref` - Don't use `forwardRef`; use `use()` instead of `useContext()`
+
+## How to Use
+
+Read individual rule files for detailed explanations and code examples:
+
+```
+rules/architecture-avoid-boolean-props.md
+rules/state-context-interface.md
+```
+
+Each rule file contains:
+
+- Brief explanation of why it matters
+- Incorrect code example with explanation
+- Correct code example with explanation
+- Additional context and references
+
+## Full Compiled Document
+
+For the complete guide with all rules expanded: `AGENTS.md`

package/template/.claude/skills/docs-tracker/SKILL.md

@@ -0,0 +1,239 @@
+---
+name: docs-tracker
+description: "ALWAYS invoke AFTER implementation completes. Detects modified files via git diff, creates/updates docs. Do NOT skip — documentation is mandatory for all changes."
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# Docs Tracker - Automatic Documentation System
+
+## Purpose
+
+This skill automates documentation maintenance:
+
+- **Detects** modified files via git diff
+- **Compares** with existing documentation
+- **Creates** docs for new files
+- **Updates** docs for modified files
+- **Removes** docs for deleted files
+- **Generates** automatic changelog
+
+---
+
+## Execution Flow
+
+```
+1. DETECT CHANGES → git diff --name-status
+        ↓
+2. CLASSIFY CHANGES → A=Added, M=Modified, D=Deleted
+        ↓
+3. CHECK EXISTING DOCS → docs/, codebase-knowledge/domains/
+        ↓
+4. EXECUTE ACTIONS → Create, update, or remove docs
+```
+
+---
+
+## Detection Commands
+
+### Changes Since Last Commit
+
+```bash
+git diff --name-status HEAD~1
+```
+
+### Changes vs Main
+
+```bash
+git diff --name-status main..HEAD
+```
+
+### Added Files
+
+```bash
+git diff --name-status main..HEAD | grep "^A"
+```
+
+### Modified Files
+
+```bash
+git diff --name-status main..HEAD | grep "^M"
+```
+
+### Deleted Files
+
+```bash
+git diff --name-status main..HEAD | grep "^D"
+```
+
+### Detailed File Diff
+
+```bash
+git diff main..HEAD -- path/to/file.ts
+```
+
+---
+
+## File → Doc Mapping
+
+| File Type             | Related Documentation                         |
+| --------------------- | --------------------------------------------- |
+| `server/routers/*.ts` | `codebase-knowledge/domains/[domain].md`      |
+| `server/models/*.ts`  | `codebase-knowledge/domains/[domain].md`      |
+| `app/**/page.tsx`     | `docs/flows/[feature].md`                     |
+| `components/**/*.tsx` | `docs/components/[component].md` (if complex) |
+| `lib/**/*.ts`         | `docs/utils/[lib].md` (if exported)           |
+
+---
+
+## Update Rules
+
+### CREATE Doc When:
+
+- [ ] New file in `server/routers/` → Update domain
+- [ ] New file in `server/models/` → Update domain
+- [ ] New page in `app/` → Create flow doc if complex
+- [ ] New complex component → Consider doc
+
+### UPDATE Doc When:
+
+- [ ] tRPC procedure changed signature
+- [ ] Model changed schema
+- [ ] Page changed main flow
+- [ ] Connections between domains changed
+
+### REMOVE Doc When:
+
+- [ ] File was deleted
+- [ ] Feature was completely removed
+- [ ] Component was discontinued
+
+---
+
+## Changelog Template
+
+```markdown
+## [Unreleased] - YYYY-MM-DD
+
+### Added
+
+- New feature X in `path/to/file.ts`
+- New component Y
+
+### Changed
+
+- Changed behavior of Z
+- Refactored module W
+
+### Fixed
+
+- Fixed bug in A
+- Resolved issue #123
+
+### Removed
+
+- Removed obsolete feature B
+
+### Docs Updated
+
+- Updated `codebase-knowledge/domains/[domain].md`
+- Created `docs/flows/[feature].md`
+```
+
+---
+
+## Pre-Commit Checklist
+
+### 1. Detect Changes
+
+```bash
+git diff --name-status --cached
+```
+
+### 2. For Each Modified File
+
+- [ ] Which domain does it belong to?
+- [ ] Is domain updated in `codebase-knowledge/domains/`?
+- [ ] Has flow doc in `docs/flows/`? Needs update?
+- [ ] Commit hash will be added to domain?
+
+### 3. For Added Files
+
+- [ ] Which domain? Add to file list
+- [ ] Needs own doc or just update domain?
+- [ ] Connections with other domains?
+
+### 4. For Deleted Files
+
+- [ ] Remove from `codebase-knowledge/domains/`
+- [ ] Remove flow doc if exists
+- [ ] Update connections in related domains
+
+---
+
+## Integration with Codebase-Knowledge
+
+### Update Domain After Change
+
+```markdown
+## Domain Update: [name]
+
+### Changes Detected
+
+| File         | Status   | Description    |
+| ------------ | -------- | -------------- |
+| path/file.ts | Modified | [what changed] |
+
+### Required Updates in domains/[domain].md
+
+- [ ] Update "Last Update" with date and commit
+- [ ] Add/remove files from list
+- [ ] Update "Recent Commits"
+- [ ] Check "Connections" if integration changed
+- [ ] Update "Attention Points" if applicable
+```
+
+---
+
+## Output Format
+
+```markdown
+## DOCS TRACKER - Report
+
+### Changes Detected
+
+- **Added:** X files
+- **Modified:** Y files
+- **Deleted:** Z files
+
+### Docs That Need Update
+
+| Doc              | Type   | Action | Priority |
+| ---------------- | ------ | ------ | -------- |
+| domains/auth.md  | domain | update | HIGH     |
+| flows/feature.md | flow   | create | MEDIUM   |
+
+### Actions Executed
+
+- [x] Updated `domains/auth.md` with commit abc123
+- [x] Created `flows/new-feature.md`
+- [x] Removed `flows/obsolete.md`
+
+### Changelog Generated
+
+[changelog preview]
+```
+
+---
+
+## Critical Rules
+
+1. **ALWAYS run before commit** - Outdated docs are technical debt
+2. **NEVER ignore new files** - Every file deserves documentation
+3. **KEEP changelog updated** - Facilitates releases
+4. **SYNC with codebase-knowledge** - It's the source of truth
+
+---
+
+## Version
+
+- **v2.0.0** - Generic template

package/template/.claude/skills/mcp-builder/SKILL.md

@@ -0,0 +1,236 @@
+---
+name: mcp-builder
+description: Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
+license: Complete terms in LICENSE.txt
+---
+
+# MCP Server Development Guide
+
+## Overview
+
+Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.
+
+---
+
+# Process
+
+## 🚀 High-Level Workflow
+
+Creating a high-quality MCP server involves four main phases:
+
+### Phase 1: Deep Research and Planning
+
+#### 1.1 Understand Modern MCP Design
+
+**API Coverage vs. Workflow Tools:**
+Balance comprehensive API endpoint coverage with specialized workflow tools. Workflow tools can be more convenient for specific tasks, while comprehensive coverage gives agents flexibility to compose operations. Performance varies by client—some clients benefit from code execution that combines basic tools, while others work better with higher-level workflows. When uncertain, prioritize comprehensive API coverage.
+
+**Tool Naming and Discoverability:**
+Clear, descriptive tool names help agents find the right tools quickly. Use consistent prefixes (e.g., `github_create_issue`, `github_list_repos`) and action-oriented naming.
+
+**Context Management:**
+Agents benefit from concise tool descriptions and the ability to filter/paginate results. Design tools that return focused, relevant data. Some clients support code execution which can help agents filter and process data efficiently.
+
+**Actionable Error Messages:**
+Error messages should guide agents toward solutions with specific suggestions and next steps.
+
+#### 1.2 Study MCP Protocol Documentation
+
+**Navigate the MCP specification:**
+
+Start with the sitemap to find relevant pages: `https://modelcontextprotocol.io/sitemap.xml`
+
+Then fetch specific pages with `.md` suffix for markdown format (e.g., `https://modelcontextprotocol.io/specification/draft.md`).
+
+Key pages to review:
+- Specification overview and architecture
+- Transport mechanisms (streamable HTTP, stdio)
+- Tool, resource, and prompt definitions
+
+#### 1.3 Study Framework Documentation
+
+**Recommended stack:**
+- **Language**: TypeScript (high-quality SDK support and good compatibility in many execution environments e.g. MCPB. Plus AI models are good at generating TypeScript code, benefiting from its broad usage, static typing and good linting tools)
+- **Transport**: Streamable HTTP for remote servers, using stateless JSON (simpler to scale and maintain, as opposed to stateful sessions and streaming responses). stdio for local servers.
+
+**Load framework documentation:**
+
+- **MCP Best Practices**: [📋 View Best Practices](./reference/mcp_best_practices.md) - Core guidelines
+
+**For TypeScript (recommended):**
+- **TypeScript SDK**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`
+- [⚡ TypeScript Guide](./reference/node_mcp_server.md) - TypeScript patterns and examples
+
+**For Python:**
+- **Python SDK**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`
+- [🐍 Python Guide](./reference/python_mcp_server.md) - Python patterns and examples
+
+#### 1.4 Plan Your Implementation
+
+**Understand the API:**
+Review the service's API documentation to identify key endpoints, authentication requirements, and data models. Use web search and WebFetch as needed.
+
+**Tool Selection:**
+Prioritize comprehensive API coverage. List endpoints to implement, starting with the most common operations.
+
+---
+
+### Phase 2: Implementation
+
+#### 2.1 Set Up Project Structure
+
+See language-specific guides for project setup:
+- [⚡ TypeScript Guide](./reference/node_mcp_server.md) - Project structure, package.json, tsconfig.json
+- [🐍 Python Guide](./reference/python_mcp_server.md) - Module organization, dependencies
+
+#### 2.2 Implement Core Infrastructure
+
+Create shared utilities:
+- API client with authentication
+- Error handling helpers
+- Response formatting (JSON/Markdown)
+- Pagination support
+
+#### 2.3 Implement Tools
+
+For each tool:
+
+**Input Schema:**
+- Use Zod (TypeScript) or Pydantic (Python)
+- Include constraints and clear descriptions
+- Add examples in field descriptions
+
+**Output Schema:**
+- Define `outputSchema` where possible for structured data
+- Use `structuredContent` in tool responses (TypeScript SDK feature)
+- Helps clients understand and process tool outputs
+
+**Tool Description:**
+- Concise summary of functionality
+- Parameter descriptions
+- Return type schema
+
+**Implementation:**
+- Async/await for I/O operations
+- Proper error handling with actionable messages
+- Support pagination where applicable
+- Return both text content and structured data when using modern SDKs
+
+**Annotations:**
+- `readOnlyHint`: true/false
+- `destructiveHint`: true/false
+- `idempotentHint`: true/false
+- `openWorldHint`: true/false
+
+---
+
+### Phase 3: Review and Test
+
+#### 3.1 Code Quality
+
+Review for:
+- No duplicated code (DRY principle)
+- Consistent error handling
+- Full type coverage
+- Clear tool descriptions
+
+#### 3.2 Build and Test
+
+**TypeScript:**
+- Run `npm run build` to verify compilation
+- Test with MCP Inspector: `npx @modelcontextprotocol/inspector`
+
+**Python:**
+- Verify syntax: `python -m py_compile your_server.py`
+- Test with MCP Inspector
+
+See language-specific guides for detailed testing approaches and quality checklists.
+
+---
+
+### Phase 4: Create Evaluations
+
+After implementing your MCP server, create comprehensive evaluations to test its effectiveness.
+
+**Load [✅ Evaluation Guide](./reference/evaluation.md) for complete evaluation guidelines.**
+
+#### 4.1 Understand Evaluation Purpose
+
+Use evaluations to test whether LLMs can effectively use your MCP server to answer realistic, complex questions.
+
+#### 4.2 Create 10 Evaluation Questions
+
+To create effective evaluations, follow the process outlined in the evaluation guide:
+
+1. **Tool Inspection**: List available tools and understand their capabilities
+2. **Content Exploration**: Use READ-ONLY operations to explore available data
+3. **Question Generation**: Create 10 complex, realistic questions
+4. **Answer Verification**: Solve each question yourself to verify answers
+
+#### 4.3 Evaluation Requirements
+
+Ensure each question is:
+- **Independent**: Not dependent on other questions
+- **Read-only**: Only non-destructive operations required
+- **Complex**: Requiring multiple tool calls and deep exploration
+- **Realistic**: Based on real use cases humans would care about
+- **Verifiable**: Single, clear answer that can be verified by string comparison
+- **Stable**: Answer won't change over time
+
+#### 4.4 Output Format
+
+Create an XML file with this structure:
+
+```xml
+<evaluation>
+  <qa_pair>
+    <question>Find discussions about AI model launches with animal codenames. One model needed a specific safety designation that uses the format ASL-X. What number X was being determined for the model named after a spotted wild cat?</question>
+    <answer>3</answer>
+  </qa_pair>
+<!-- More qa_pairs... -->
+</evaluation>
+```
+
+---
+
+# Reference Files
+
+## 📚 Documentation Library
+
+Load these resources as needed during development:
+
+### Core MCP Documentation (Load First)
+- **MCP Protocol**: Start with sitemap at `https://modelcontextprotocol.io/sitemap.xml`, then fetch specific pages with `.md` suffix
+- [📋 MCP Best Practices](./reference/mcp_best_practices.md) - Universal MCP guidelines including:
+  - Server and tool naming conventions
+  - Response format guidelines (JSON vs Markdown)
+  - Pagination best practices
+  - Transport selection (streamable HTTP vs stdio)
+  - Security and error handling standards
+
+### SDK Documentation (Load During Phase 1/2)
+- **Python SDK**: Fetch from `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`
+- **TypeScript SDK**: Fetch from `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`
+
+### Language-Specific Implementation Guides (Load During Phase 2)
+- [🐍 Python Implementation Guide](./reference/python_mcp_server.md) - Complete Python/FastMCP guide with:
+  - Server initialization patterns
+  - Pydantic model examples
+  - Tool registration with `@mcp.tool`
+  - Complete working examples
+  - Quality checklist
+
+- [⚡ TypeScript Implementation Guide](./reference/node_mcp_server.md) - Complete TypeScript guide with:
+  - Project structure
+  - Zod schema patterns
+  - Tool registration with `server.registerTool`
+  - Complete working examples
+  - Quality checklist
+
+### Evaluation Guide (Load During Phase 4)
+- [✅ Evaluation Guide](./reference/evaluation.md) - Complete evaluation creation guide with:
+  - Question creation guidelines
+  - Answer verification strategies
+  - XML format specifications
+  - Example questions and answers
+  - Running an evaluation with the provided scripts

package/template/.claude/skills/quality-gate/scripts/check-all.sh

@@ -0,0 +1,83 @@
+#!/bin/bash
+# Quality Gate - Run All Checks
+# Usage: bash .claude/skills/quality-gate/scripts/check-all.sh
+
+set -e
+
+echo "========================================"
+echo "        QUALITY GATE - ALL CHECKS"
+echo "========================================"
+echo ""
+
+# Colors
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m' # No Color
+
+FAILED=0
+
+# 1. TypeCheck
+echo "1/5 Running TypeCheck..."
+if bun run typecheck 2>&1; then
+    echo -e "${GREEN}✓ TypeCheck passed${NC}"
+else
+    echo -e "${RED}✗ TypeCheck failed${NC}"
+    FAILED=1
+fi
+echo ""
+
+# 2. Lint
+echo "2/5 Running Lint..."
+if bun run lint 2>&1; then
+    echo -e "${GREEN}✓ Lint passed${NC}"
+else
+    echo -e "${RED}✗ Lint failed${NC}"
+    FAILED=1
+fi
+echo ""
+
+# 3. Unit Tests
+echo "3/5 Running Unit Tests..."
+if bun run test 2>&1; then
+    echo -e "${GREEN}✓ Unit tests passed${NC}"
+else
+    echo -e "${RED}✗ Unit tests failed${NC}"
+    FAILED=1
+fi
+echo ""
+
+# 4. E2E Tests (optional - check if exists)
+echo "4/5 Running E2E Tests..."
+if [ -f "playwright.config.ts" ]; then
+    if bun run test:e2e 2>&1; then
+        echo -e "${GREEN}✓ E2E tests passed${NC}"
+    else
+        echo -e "${YELLOW}⚠ E2E tests failed (non-blocking)${NC}"
+    fi
+else
+    echo -e "${YELLOW}⚠ E2E tests skipped (no playwright config)${NC}"
+fi
+echo ""
+
+# 5. Build
+echo "5/5 Running Build..."
+if bun run build 2>&1; then
+    echo -e "${GREEN}✓ Build passed${NC}"
+else
+    echo -e "${RED}✗ Build failed${NC}"
+    FAILED=1
+fi
+echo ""
+
+# Summary
+echo "========================================"
+echo "                SUMMARY"
+echo "========================================"
+if [ $FAILED -eq 0 ]; then
+    echo -e "${GREEN}All quality gates passed!${NC}"
+    exit 0
+else
+    echo -e "${RED}Some quality gates failed!${NC}"
+    exit 1
+fi