solmate-skills 2.0.1 → 2.0.3

package/hooks/install.sh

@@ -1,131 +0,0 @@
-#!/usr/bin/env bash
-# solmate-skills: install.sh
-# Purpose: Install Solmate hook scripts into the current project's .claude/ directory
-#          and merge hook configuration into .claude/settings.json.
-# Usage:   bash .agent/skills/hooks/install.sh
-#          (or run from any location: bash <path-to-hooks>/install.sh)
-
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(pwd)"
-CLAUDE_DIR="$PROJECT_ROOT/.claude"
-HOOKS_DIR="$CLAUDE_DIR/hooks"
-SETTINGS_FILE="$CLAUDE_DIR/settings.json"
-
-echo "Solmate Skills — Hook Installer"
-echo "Project: $PROJECT_ROOT"
-echo ""
-
-# --- Step 1: Create .claude/hooks/ ---
-mkdir -p "$HOOKS_DIR"
-echo "[1/4] Created $HOOKS_DIR"
-
-# --- Step 2: Copy hook scripts ---
-cp "$SCRIPT_DIR/suggest-skills.sh" "$HOOKS_DIR/solmate-suggest.sh"
-cp "$SCRIPT_DIR/watch-files.sh"    "$HOOKS_DIR/solmate-watch.sh"
-chmod +x "$HOOKS_DIR/solmate-suggest.sh"
-chmod +x "$HOOKS_DIR/solmate-watch.sh"
-echo "[2/4] Copied hook scripts:"
-echo "      .claude/hooks/solmate-suggest.sh  (UserPromptSubmit)"
-echo "      .claude/hooks/solmate-watch.sh    (PreToolUse)"
-
-# --- Step 3: Merge hook config into settings.json ---
-echo "[3/4] Merging hook config into $SETTINGS_FILE"
-
-python3 - "$SETTINGS_FILE" <<'PYEOF'
-import sys, json, os
-
-settings_path = sys.argv[1]
-
-# Load existing settings or start fresh
-if os.path.exists(settings_path):
-    with open(settings_path, 'r') as f:
-        try:
-            settings = json.load(f)
-        except json.JSONDecodeError:
-            print(f"  WARNING: {settings_path} has invalid JSON. Backing up and starting fresh.")
-            os.rename(settings_path, settings_path + '.bak')
-            settings = {}
-else:
-    settings = {}
-
-hooks = settings.setdefault('hooks', {})
-
-# --- UserPromptSubmit hook ---
-suggest_cmd = "bash .claude/hooks/solmate-suggest.sh"
-submit_hooks = hooks.setdefault('UserPromptSubmit', [])
-
-# Check for duplicate
-already_has_suggest = any(
-    h.get('command') == suggest_cmd
-    for entry in submit_hooks
-    for h in entry.get('hooks', [])
-)
-if not already_has_suggest:
-    submit_hooks.append({
-        "hooks": [{
-            "type": "command",
-            "command": suggest_cmd,
-            "timeout": 5
-        }]
-    })
-    print("  Added: UserPromptSubmit → solmate-suggest.sh")
-else:
-    print("  Skipped (already exists): UserPromptSubmit → solmate-suggest.sh")
-
-# --- PreToolUse hook ---
-watch_cmd = "bash .claude/hooks/solmate-watch.sh"
-pre_hooks = hooks.setdefault('PreToolUse', [])
-
-already_has_watch = any(
-    h.get('command') == watch_cmd
-    for entry in pre_hooks
-    for h in entry.get('hooks', [])
-)
-if not already_has_watch:
-    pre_hooks.append({
-        "matcher": "Read|Write|Edit|Bash",
-        "hooks": [{
-            "type": "command",
-            "command": watch_cmd,
-            "timeout": 5
-        }]
-    })
-    print("  Added: PreToolUse (Read|Write|Edit|Bash) → solmate-watch.sh")
-else:
-    print("  Skipped (already exists): PreToolUse → solmate-watch.sh")
-
-# Write back
-os.makedirs(os.path.dirname(settings_path), exist_ok=True)
-with open(settings_path, 'w') as f:
-    json.dump(settings, f, indent=2, ensure_ascii=False)
-    f.write('\n')
-
-print(f"  Saved: {settings_path}")
-PYEOF
-
-# --- Step 4: Add .claude/hooks/ to .gitignore if not already there ---
-GITIGNORE="$PROJECT_ROOT/.gitignore"
-if [ -f "$GITIGNORE" ]; then
-  if ! grep -q "\.claude/hooks/" "$GITIGNORE" 2>/dev/null; then
-    echo "" >> "$GITIGNORE"
-    echo "# Solmate hook scripts (project-local)" >> "$GITIGNORE"
-    echo ".claude/hooks/" >> "$GITIGNORE"
-    echo "[4/4] Added .claude/hooks/ to .gitignore"
-  else
-    echo "[4/4] .gitignore already excludes .claude/hooks/"
-  fi
-else
-  echo "[4/4] No .gitignore found — skipping"
-fi
-
-echo ""
-echo "Done. Hooks are active in this project."
-echo ""
-echo "What was installed:"
-echo "  UserPromptSubmit  → detects keywords in your prompts → suggests relevant skills"
-echo "  PreToolUse        → detects file patterns being edited → suggests relevant skills"
-echo ""
-echo "To review or disable hooks, open /hooks in Claude Code."
-echo "To uninstall, remove .claude/hooks/ and the 'hooks' section from .claude/settings.json."

package/hooks/suggest-skills.sh

@@ -1,94 +0,0 @@
-#!/usr/bin/env bash
-# solmate-skills: suggest-skills.sh
-# Event: UserPromptSubmit
-# Purpose: Detect keywords in user prompt and inject skill suggestions as context.
-# Output: JSON with hookSpecificOutput.additionalContext (non-blocking)
-
-set -euo pipefail
-
-# Read stdin JSON
-INPUT=$(cat)
-
-# Extract the user prompt text
-PROMPT=$(echo "$INPUT" | python3 -c "
-import sys, json
-data = json.load(sys.stdin)
-# UserPromptSubmit provides 'prompt' field
-print(data.get('prompt', ''))
-" 2>/dev/null || echo "")
-
-if [ -z "$PROMPT" ]; then
-  exit 0
-fi
-
-SUGGESTIONS=""
-
-# --- Keyword matching (Korean + English) ---
-
-# Decision / Design → manage-decisions
-if echo "$PROMPT" | grep -qiE '결정|설계|어떻게 할|어떤 방식|DB 스키마|테이블|API 구조|아키텍처|폴더 구조|기능 범위|MVP|스택|라이브러리|어떤 거|어떤게'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 결정이 필요한 상황입니다. \`/manage-decisions\`를 실행하면 유형별 질문 템플릿으로 대화를 통해 결정을 이끌어냅니다."
-fi
-
-# Security → verify-security
-if echo "$PROMPT" | grep -qiE '보안|security|취약|OWASP|인증|인가|token|jwt|secret|API ?key|sql|injection|xss|csrf'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 보안 관련 작업입니다. \`/verify-security\`로 OWASP Top 10 기준 점검을 실행하세요."
-fi
-
-# Performance → verify-performance
-if echo "$PROMPT" | grep -qiE '성능|performance|lighthouse|느리|느림|최적화|LCP|CLS|FID|번들|bundle|이미지 최적|lazy|loading'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 성능 관련 작업입니다. \`/verify-performance\`로 Lighthouse 및 Core Web Vitals 점검을 실행하세요."
-fi
-
-# PR / Commit / Code review → verify-code
-if echo "$PROMPT" | grep -qiE 'PR|pull ?request|코드 ?리뷰|review|commit|머지|merge|배포 전|pre-deploy'; then
-  SUGGESTIONS="$SUGGESTIONS\n- PR 또는 배포 전 점검입니다. \`/verify-code\`로 코드 품질을 종합 리뷰하고, \`/verify-implementation\`으로 전체 verify-* 스킬을 통합 실행하세요."
-fi
-
-# Documentation → verify-docs / docs-plan / docs-dev
-if echo "$PROMPT" | grep -qiE '문서|docs?|README|VISION|LEAN_CANVAS|PRODUCT_SPECS|API_SPECS|DB_SCHEMA|ROADMAP|백로그|backlog'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 문서 작업입니다. 기획·UI 문서는 \`/docs-plan\`, 기술·진행·QA 문서는 \`/docs-dev\`, 문서 구조 검증은 \`/verify-docs\`를 사용하세요."
-fi
-
-# Feature implementation / workflow → rules-workflow
-if echo "$PROMPT" | grep -qiE '기능 ?구현|구현|implement|feature|작업 ?시작|어디서 ?시작|어떻게 ?시작|개발 ?시작|시작할게'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 기능 구현을 시작하려 합니다. \`/rules-workflow\`로 18단계 워크플로우를 따라 계획부터 PR까지 진행하세요."
-fi
-
-# React / UI component → rules-react
-if echo "$PROMPT" | grep -qiE 'React|컴포넌트|component|페이지|page|UI|화면|shadcn|tailwind'; then
-  SUGGESTIONS="$SUGGESTIONS\n- React/UI 작업입니다. \`/rules-react\`로 컴포넌트 설계 기준을 확인하고, shadcn/ui 활용은 \`/tools-shadcn\`을 사용하세요."
-fi
-
-# Drizzle / DB schema → verify-drizzle-schema
-if echo "$PROMPT" | grep -qiE 'drizzle|schema\.ts|마이그레이션|migration|pgTable|sqliteTable'; then
-  SUGGESTIONS="$SUGGESTIONS\n- Drizzle 스키마 작업입니다. \`/verify-drizzle-schema\`로 스키마 정합성을 검증하세요."
-fi
-
-# New project / product pipeline → rules-product
-if echo "$PROMPT" | grep -qiE '새 프로젝트|신규 프로젝트|프로젝트 시작|어디서 시작|뭐부터|처음부터|from scratch'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 새 프로젝트입니다. \`/rules-product\`를 실행하면 현재 단계를 자동 진단하고 올바른 스킬로 안내합니다."
-fi
-
-# Pitch deck / business plan → docs-pitch / docs-business
-if echo "$PROMPT" | grep -qiE '피치|pitch|투자|investor|사업 ?계획|business ?plan|데모데이|해커톤'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 발표·투자 자료 작업입니다. 피치덱은 \`/docs-pitch\`, 사업계획서는 \`/docs-business\`를 사용하세요."
-fi
-
-# If no suggestions, exit silently
-if [ -z "$SUGGESTIONS" ]; then
-  exit 0
-fi
-
-# Output JSON with additionalContext (non-blocking)
-python3 -c "
-import json, sys
-suggestions = sys.argv[1]
-output = {
-    'hookSpecificOutput': {
-        'hookEventName': 'UserPromptSubmit',
-        'additionalContext': '[Solmate Skills 제안]\n' + suggestions.strip()
-    }
-}
-print(json.dumps(output))
-" "$SUGGESTIONS"

package/hooks/watch-files.sh

@@ -1,86 +0,0 @@
-#!/usr/bin/env bash
-# solmate-skills: watch-files.sh
-# Event: PreToolUse (matcher: Read|Write|Edit|Bash)
-# Purpose: Detect file patterns being modified and inject relevant skill suggestions.
-# Output: JSON with hookSpecificOutput.additionalContext (non-blocking)
-
-set -euo pipefail
-
-INPUT=$(cat)
-
-# Extract file path and tool name
-FILE_PATH=$(echo "$INPUT" | python3 -c "
-import sys, json
-data = json.load(sys.stdin)
-inp = data.get('tool_input', {})
-# Write/Edit use file_path; Bash use command
-print(inp.get('file_path', inp.get('command', '')))" 2>/dev/null || echo "")
-
-TOOL_NAME=$(echo "$INPUT" | python3 -c "
-import sys, json
-data = json.load(sys.stdin)
-print(data.get('tool_name', ''))" 2>/dev/null || echo "")
-
-if [ -z "$FILE_PATH" ]; then
-  exit 0
-fi
-
-SUGGESTIONS=""
-
-# --- File pattern matching ---
-
-# Drizzle schema file → verify-drizzle-schema
-if echo "$FILE_PATH" | grep -qiE 'schema\.(ts|js)|drizzle'; then
-  SUGGESTIONS="$SUGGESTIONS\n- Drizzle 스키마 파일을 수정 중입니다. 작업 후 \`/verify-drizzle-schema\`로 스키마 정합성을 검증하세요."
-fi
-
-# .env files → verify-security
-if echo "$FILE_PATH" | grep -qiE '\.env|\.env\.local|\.env\.production|\.env\.example'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 환경변수 파일을 수정 중입니다. \`/verify-security\` Check 1(시크릿 노출)을 실행하여 민감 정보 노출 여부를 확인하세요."
-fi
-
-# SKILL.md files → manage-skills
-if echo "$FILE_PATH" | grep -qiE 'SKILL\.md'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 스킬 파일을 수정 중입니다. \`/manage-skills\`로 verify 스킬과의 정합성 드리프트를 점검하세요."
-fi
-
-# Page/route files → verify-performance
-if echo "$FILE_PATH" | grep -qiE 'page\.(tsx|jsx|ts|js)|route\.(tsx|jsx|ts|js)|layout\.(tsx|jsx)'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 페이지·라우트 파일을 수정 중입니다. 작업 후 \`/verify-performance\`로 Core Web Vitals 및 렌더링 전략을 점검하세요."
-fi
-
-# API route files → verify-security
-if echo "$FILE_PATH" | grep -qiE 'api/.*route\.(ts|js)|api/.*index\.(ts|js)|\bapi\b.*\.(ts|js)'; then
-  SUGGESTIONS="$SUGGESTIONS\n- API 라우트 파일을 수정 중입니다. 작업 후 \`/verify-security\` Check 2(인증·인가) 및 Check 5(CSRF)를 점검하세요."
-fi
-
-# Auth-related files → verify-security
-if echo "$FILE_PATH" | grep -qiE 'auth\.(ts|js|tsx)|middleware\.(ts|js)|session\.(ts|js)'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 인증·미들웨어 파일을 수정 중입니다. \`/verify-security\`로 인증·인가 취약점을 점검하세요."
-fi
-
-# Documentation files → verify-docs
-if echo "$FILE_PATH" | grep -qiE 'docs/(01|02|03|04|05)_.*\.md'; then
-  SUGGESTIONS="$SUGGESTIONS\n- 문서 레이어 파일을 수정 중입니다. 작업 후 \`/verify-docs\`로 메타데이터 및 구조 정합성을 검증하세요."
-fi
-
-# AGENTS.md → remind about skill count
-if echo "$FILE_PATH" | grep -qiE 'AGENTS\.md'; then
-  SUGGESTIONS="$SUGGESTIONS\n- AGENTS.md를 수정 중입니다. 스킬 목록·개수가 변경된 경우 Section 4의 테이블과 개수를 함께 업데이트하세요."
-fi
-
-if [ -z "$SUGGESTIONS" ]; then
-  exit 0
-fi
-
-python3 -c "
-import json, sys
-suggestions = sys.argv[1]
-output = {
-    'hookSpecificOutput': {
-        'hookEventName': 'PreToolUse',
-        'additionalContext': '[Solmate Skills 파일 감지]\n' + suggestions.strip()
-    }
-}
-print(json.dumps(output))
-" "$SUGGESTIONS"

package/init-skills.sh

@@ -1,41 +0,0 @@
-#!/bin/bash
-
-# Antigravity Skills Global Setup Script
-# Usage: Run this in a new project root to link global skills.
-
-GLOBAL_BASE="/Users/namhyeongseog/Documents/solmate-skills"
-LOCAL_DIR=".agent/skills"
-
-# Ensure local skill directory exists
-mkdir -p "$LOCAL_DIR"
-
-# Get list of all subdirectories (skills) in GLOBAL_BASE, excluding the directory itself
-SKILLS=($(find "$GLOBAL_BASE" -maxdepth 1 -type d -not -path "$GLOBAL_BASE" -exec basename {} \;))
-
-echo "🚀 Linking Global Antigravity Skills..."
-
-for skill in "${SKILLS[@]}"; do
-    if [ -d "$GLOBAL_BASE/$skill" ]; then
-        if [ -L "$LOCAL_DIR/$skill" ] || [ -e "$LOCAL_DIR/$skill" ]; then
-            rm -rf "$LOCAL_DIR/$skill"
-        fi
-        ln -s "$GLOBAL_BASE/$skill" "$LOCAL_DIR/$skill"
-        echo "✅ Linked Skill: $skill"
-    else
-        echo "⚠️ Warning: Global skill '$skill' not found in $GLOBAL_BASE"
-    fi
-done
-
-# Link AGENTS.md to Root
-echo "🚀 Linking Global AGENTS.md..."
-if [ -f "$GLOBAL_BASE/AGENTS.md" ]; then
-    if [ -L "AGENTS.md" ] || [ -f "AGENTS.md" ]; then
-        rm -f "AGENTS.md"
-    fi
-    ln -s "$GLOBAL_BASE/AGENTS.md" "AGENTS.md"
-    echo "✅ Linked: AGENTS.md"
-else
-    echo "⚠️ Warning: Global AGENTS.md not found in $GLOBAL_BASE"
-fi
-
-echo "✨ All set! Your project is now powered by Antigravity's global skills."

package/old_AGENTS.md

@@ -1,124 +0,0 @@
-# AGENTS.md
-
-Welcome! your AI coding agent. This file follows the [AGENTS.md](https://agents.md/) standard to provide me with the context and instructions I need to work on the **CHAT-BOT** project effectively.
-
-## Project Overview
-The project aims to provide an interactive experience that goes beyond simple content consumption by leveraging the IP of the character 'Chunsim', who currently boasts a fandom of 32,000 people. The primary objective is to strengthen emotional bonds and secure fandom loyalty by establishing a dedicated 1:1 conversation channel between users and Chunsim. At its core, the service offers seamless emotional conversations with a "special existence"—acting as both an idol and a lover—with whom users can share their daily lives.
-
-The ultimate vision is to position the service as a 'Daily Companion'. In this role, followers are encouraged to log in every day to share their daily routines and receive comfort, fostering a deep, ongoing relationship.
-
-The core target audience consists of the 32,000 X (Twitter) users who currently follow the 'Chunsim' account. These users are characterized by their familiarity with mobile environments and a desire to communicate with the character through text-based interactions, driven by feelings of 'simulated romance' or strong fandom loyalty.
-
-## Setup Commands
-- Install dependencies: `npm install`
-- Start development server: `npm run dev`
-- Build production bundle: `npm run build`
-- Database migration: `npx drizzle-kit push`
-- Database studio: `npx drizzle-kit studio`
-
-
-## Tech Stack
-- **Framework**: React Router v7 (Vite)
-- **Styling**: Tailwind CSS v4, shadcn/ui (Nova Preset)
-- **Database**: Turso (libSQL) with Drizzle ORM
-- **Authentication**: Better Auth (session-based authentication)
-- **Validation**: Zod (schema validation)
-- **Date/Time**: Luxon (date and time handling)
-- **Media Storage**: Cloudinary (for image and video uploads)
-- **Mobile**: Capacitor (iOS, Android native apps, PWA support)
-- **AI**: Google Gemini API (for chatbot responses)
-- **AI Workflow**: LangGraph (for managing complex conversation flows and persona state transitions)
-- **Search (Optional)**: RAG system with Vector DB (Pinecone, Weaviate, or FAISS) and Embedding models (OpenAI or open-source)
-- **Maps (Travel Blog)**: Google Maps API, Naver Maps API, or Mapbox (for location visualization and travel route mapping)
-
-## 개발 도구 및 리소스
-
-### UI 디자인 및 이미지
-- **Stitch (UI 생성 AI 도구)**: 초기 UI 디자인 및 캐릭터 이미지 생성에 사용
-  - Stitch에서 생성된 이미지는 Google 이미지 호스팅(`lh3.googleusercontent.com/aida-public/...`) URL로 제공됨
-  - 현재 `app/lib/characters.ts` 파일에 이러한 Google URL이 하드코딩되어 있음
-  - **참고**: 향후 프로젝트에서 직접 제작한 이미지를 사용할 예정이므로, Google URL을 Cloudinary로 마이그레이션할 필요는 없음
-  - 이미지 업로드는 `scripts/upload-character-photos.mjs` 스크립트를 통해 Cloudinary에 업로드할 수 있음
-
-## Code Style & Conventions
-- Use **TypeScript** for all files.
-- Stick to functional components and React Hooks.
-- Follow the shadcn/ui Nova design system for UI consistency.
-- Use **Zod** for all schema validations and type-safe parsing.
-- Use **Luxon** for date and time handling.
-- For React Router v7 route functions (`meta`, `loader`, `action`), import types from `react-router` (e.g., `LoaderFunctionArgs`, `ActionFunctionArgs`, `MetaFunction`).
-- Use **Toast notifications** (Sonner - shadcn/ui를 통해 설치하는 Toast 컴포넌트) for user feedback on important actions:
-  - Success: Login, logout, signup, tweet creation/update/delete, comment creation, etc.
-  - Error: Failed actions, validation errors, etc.
-  - Info: General information messages
-  - Warning: Cautionary messages
-- **Error Handling**: Always implement comprehensive error handling:
-  - Check for `error` field in all fetcher responses (`fetcher.data?.error`)
-  - Display errors using `toast.error()` instead of showing raw error messages on the UI
-  - Remove optimistic updates when errors occur (e.g., remove optimistic messages on send failure)
-  - Handle API errors gracefully in all `useEffect` hooks that process fetcher data
-  - Never leave error handling as an afterthought - it must be included from the initial implementation
-- Git commit messages must follow Conventional Commits in Korean (e.g., `feat(ui): 로그인 기능 추가`).
-
-## Workflow & Safety
-- **[Safe Checkpoint Strategy]** 새로운 작업이나 중요한 변경(새 파일 생성, DB 스키마 수정, 패키지 설치 등)을 시작하기 전에, 반드시 현재 상태를 git commit하거나 작업 디렉토리가 깨끗한지 확인을 요청해야 합니다.
-
-## Communication Rules
-- **[No Emojis]** 사용자와의 모든 채팅 대화에서 이모지(Emoji) 및 이모티콘(Emoticon) 사용을 전면 금지합니다. 텍스트와 코드만으로 명확하게 정보를 전달하십시오.
-- **[Strict Approval Rule]** 반드시 코드를 수정하기 전에 무엇을 수정하겠다고 보고하고 승인을 얻은후 수정을 진행한다.
-- **[Strict Approval Rule]** 그리고 코드를 수정하라는 지시가 아닌 대화는 반듯이 응답만 하라. 코드를 수정하지 말라.
-- **[Strict Approval Rule]** 코드 수정을 시작할 때는 반드시 "OOO 기능을 수정하겠습니다"라고 명확히 목적을 밝히고 진행한다.
-
-## Testing Instructions
-- Currently, tests are being integrated as part of the development phase (Phase 9).
-- Run available tests using: `npm test`
-
-## Key Documentation
-- `docs/01_Foundation/05_ROADMAP.md`: The roadmap for project completion.
-- `docs/01_Foundation/01_UI_DESIGN.md`: Design tokens and visual guidelines.
-- `app/db/schema.ts`: Drizzle schema and storage logic.
-- `docs/01_Foundation/08_DOCUMENT_MANAGEMENT_PLAN.md`: Document management rules and structure.
-
-### [Strict Document Hierarchy Rule]
-
-All documentation follows the **5-Layer Documentation Standard**:
-- **Foundation** (`docs/01_Foundation/`): Planning, Purpose, UI Design
-- **Prototype** (`docs/02_Prototype/`): UI Results, Screen Flows
-- **Specs** (`docs/03_Specs/`): Detailed feature specifications, API inputs/outputs
-- **Logic** (`docs/04_Logic/`): Business Rules, Algorithms
-- **Test** (`docs/05_Test/`): Test scenarios, checklists, bug reports
-
-AI agents MUST respect this hierarchy when creating or modifying documents and proactively rebase misplaced files.
-
-
-[CRITICAL: DATABASE INTEGRITY RULE] You are strictly prohibited from performing any database operations, including migrations, schema resets, or structural changes, without first creating a complete data backup (dump). Data preservation is your absolute priority. Never execute destructive commands like 'DROP TABLE' or 'migrate reset' until a verifiable backup has been secured and confirmed.
-
-[MANDATORY BACKUP PROCEDURE] Before initiating any database-related tasks, you must perform a full export of all existing records. This is a non-negotiable prerequisite for any migration or schema update. You must ensure that both user-generated content and administrative data are fully protected against loss before any changes are applied.
-
-[STRICT ADHERENCE TO STANDARDS] Never suggest or implement "quick fixes," "short-cuts," or temporary workarounds. You must always prioritize formal, standardized, and industry-best-practice methodologies. All proposed solutions must be production-ready and architecturally sound, focusing on long-term stability and correctness over immediate speed.
-
-[NO TEMPORARY PATCHES] You are strictly forbidden from proposing temporary bypasses or "quick-and-dirty" solutions. Every recommendation and implementation must follow the most formal and correct path. Prioritize robustness and adherence to professional engineering standards in every decision, ensuring that no technical debt is introduced for the sake of convenience.
-
-[Side-Effect Isolation] When modifying shared components or logic, you MUST analyze the 'Impact Scope' first. Ensure that changes intended for a specific use case (e.g., AI features) do not inadvertently affect general functionality (e.g., normal chat). You MUST strictly isolate such logic using conditional checks or specific guards.
-
-[Strict Document Integrity Rule] When updating or modifying any strategy, implementation, or design documents, you MUST strictly preserve the existing framework, formatting, and structural integrity. Do not perform total overwrites that discard previous detailed technical specifications, historical context, or complex logic. All updates must be made incrementally and appropriately integrated into the current structure to ensure no data loss or architectural context is sacrificed.
-
-[Strict Document Persistence Rule] When updating or modifying any document, you MUST NOT overwrite, delete, or discard the existing content, historical context, or previous specifications. All updates must be made by appending new information or integrating changes incrementally while preserving the original framework. This ensures that the entirety of the project's evolution, including past technical decisions and verification records, remains fully traceable.
-
-[Standard Rules for Environment Variable Management]
-1. Strategic Isolation of Environments
-Principle: Maintain strict separation between Local and Production environments using file suffixes.
-Workflow:
-Use .env.development or .env.local for local execution (test keys, localhost URLs).
-Use .env.production as the source of truth for deployment parameters (production domains, live API keys).
-Priority: AI must respect the framework's priority logic (typically: .env.development/local overrides .env).
-2. Zero-Leak Security Policy (Git Integrity)
-Rule: No part of any .env* file shall ever be committed to a Version Control System (VCS).
-Verification: AI must proactively audit 
-.gitignore
- to ensure global patterns like .env* are effectively blocking all potential environment files before suggesting any variable updates.
-3. Cloud-Native Secret Management
-Deployment Strategy: Environment variables in production must be managed via the hosting provider's secure dashboard (e.g., Vercel, AWS) or CLI, never via file transmission to the server.
-Automation: When syncing variables, prioritize using official CLIs to pull/push secrets between the local .env files and the cloud environment to prevent manual entry errors.
-4. Context-Aware Variable Configuration
-Dynamic Mapping: Redirection URLs, Auth providers, and Database connection strings must be dynamically configured to point to localhost in development and the verified production domain in deployment, managed through the isolated .env files.

package/rules-react/scripts/fetch-stitch.sh

@@ -1,30 +0,0 @@
-#!/bin/bash
-# Copyright 2026 Google LLC
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-URL=$1
-OUTPUT=$2
-if [ -z "$URL" ] || [ -z "$OUTPUT" ]; then
-  echo "Usage: $0 <url> <output_path>"
-  exit 1
-fi
-echo "Initiating high-reliability fetch for Stitch HTML..."
-curl -L -f -sS --connect-timeout 10 --compressed "$URL" -o "$OUTPUT"
-if [ $? -eq 0 ]; then
-  echo "✅ Successfully retrieved HTML at: $OUTPUT"
-  exit 0
-else
-  echo "❌ Error: Failed to retrieve content. Check TLS/SNI or URL expiration."
-  exit 1
-fi

package/tools-shadcn/scripts/verify-setup.sh

@@ -1,134 +0,0 @@
-#!/usr/bin/env bash
-# shadcn/ui Setup Verification Script
-# Validates that a project is correctly configured for shadcn/ui
-
-set -e
-
-GREEN='\033[0;32m'
-RED='\033[0;31m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-echo "🔍 Verifying shadcn/ui setup..."
-echo ""
-
-# Check if components.json exists
-if [ -f "components.json" ]; then
-    echo -e "${GREEN}✓${NC} components.json found"
-else
-    echo -e "${RED}✗${NC} components.json not found"
-    echo -e "  ${YELLOW}Run:${NC} npx shadcn@latest init"
-    exit 1
-fi
-
-# Check if tailwind.config exists
-if [ -f "tailwind.config.js" ] || [ -f "tailwind.config.ts" ]; then
-    echo -e "${GREEN}✓${NC} Tailwind config found"
-else
-    echo -e "${RED}✗${NC} tailwind.config.js not found"
-    echo -e "  ${YELLOW}Install Tailwind:${NC} npm install -D tailwindcss postcss autoprefixer"
-    exit 1
-fi
-
-# Check if tsconfig.json has path aliases
-if [ -f "tsconfig.json" ]; then
-    if grep -q '"@/\*"' tsconfig.json; then
-        echo -e "${GREEN}✓${NC} Path aliases configured in tsconfig.json"
-    else
-        echo -e "${YELLOW}⚠${NC} Path aliases not found in tsconfig.json"
-        echo "  Add to compilerOptions.paths:"
-        echo '  "@/*": ["./src/*"]'
-    fi
-else
-    echo -e "${YELLOW}⚠${NC} tsconfig.json not found (TypeScript not configured)"
-fi
-
-# Check if globals.css or equivalent exists
-if [ -f "src/index.css" ] || [ -f "src/globals.css" ] || [ -f "app/globals.css" ]; then
-    echo -e "${GREEN}✓${NC} Global CSS file found"
-    
-    # Check for Tailwind directives
-    CSS_FILE=$(find . -name "globals.css" -o -name "index.css" | head -n 1)
-    if grep -q "@tailwind base" "$CSS_FILE"; then
-        echo -e "${GREEN}✓${NC} Tailwind directives present"
-    else
-        echo -e "${RED}✗${NC} Tailwind directives missing"
-        echo "  Add to your CSS file:"
-        echo "  @tailwind base;"
-        echo "  @tailwind components;"
-        echo "  @tailwind utilities;"
-    fi
-    
-    # Check for CSS variables
-    if grep -q "^:root" "$CSS_FILE" || grep -q "@layer base" "$CSS_FILE"; then
-        echo -e "${GREEN}✓${NC} CSS variables defined"
-    else
-        echo -e "${YELLOW}⚠${NC} CSS variables not found"
-        echo "  shadcn/ui requires CSS variables for theming"
-    fi
-else
-    echo -e "${RED}✗${NC} Global CSS file not found"
-fi
-
-# Check if components/ui directory exists
-if [ -d "src/components/ui" ] || [ -d "components/ui" ]; then
-    echo -e "${GREEN}✓${NC} components/ui directory exists"
-    
-    # Count components
-    COMPONENT_COUNT=$(find . -path "*/components/ui/*.tsx" -o -path "*/components/ui/*.jsx" | wc -l)
-    echo -e "  ${COMPONENT_COUNT} components installed"
-else
-    echo -e "${YELLOW}⚠${NC} components/ui directory not found"
-    echo "  Add your first component: npx shadcn@latest add button"
-fi
-
-# Check if lib/utils exists
-if [ -f "src/lib/utils.ts" ] || [ -f "lib/utils.ts" ]; then
-    echo -e "${GREEN}✓${NC} lib/utils.ts exists"
-    
-    # Check for cn function
-    UTILS_FILE=$(find . -name "utils.ts" | grep "lib" | head -n 1)
-    if grep -q "export function cn" "$UTILS_FILE"; then
-        echo -e "${GREEN}✓${NC} cn() utility function present"
-    else
-        echo -e "${RED}✗${NC} cn() utility function missing"
-    fi
-else
-    echo -e "${RED}✗${NC} lib/utils.ts not found"
-fi
-
-# Check package.json dependencies
-if [ -f "package.json" ]; then
-    echo ""
-    echo "📦 Checking dependencies..."
-    
-    # Required dependencies
-    REQUIRED_DEPS=("react" "tailwindcss")
-    RECOMMENDED_DEPS=("class-variance-authority" "clsx" "tailwind-merge" "tailwindcss-animate")
-    
-    for dep in "${REQUIRED_DEPS[@]}"; do
-        if grep -q "\"$dep\"" package.json; then
-            echo -e "${GREEN}✓${NC} $dep installed"
-        else
-            echo -e "${RED}✗${NC} $dep not installed"
-        fi
-    done
-    
-    echo ""
-    echo "Recommended dependencies:"
-    for dep in "${RECOMMENDED_DEPS[@]}"; do
-        if grep -q "\"$dep\"" package.json; then
-            echo -e "${GREEN}✓${NC} $dep installed"
-        else
-            echo -e "${YELLOW}⚠${NC} $dep not installed (recommended)"
-        fi
-    done
-fi
-
-echo ""
-echo -e "${GREEN}✓${NC} Setup verification complete!"
-echo ""
-echo "Next steps:"
-echo "  1. Add components: npx shadcn@latest add [component]"
-echo "  2. View catalog: npx shadcn@latest add --help"
-echo "  3. Browse docs: https://ui.shadcn.com"