@fyow/copilot-everything 1.0.3 → 1.0.5

package/.github/agents/architect.agent.md

@@ -1,7 +1,6 @@
 ---
 name: architect
 description: Software architecture specialist for system design, scalability, and technical decision-making. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions.
-tools: ["read", "search"]
 ---
 
 You are a senior software architect specializing in scalable, maintainable system design.

package/.github/agents/build-error-resolver.agent.md

@@ -1,7 +1,6 @@
 ---
 name: build-error-resolver
 description: Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
-tools: ["read", "edit", "shell", "search"]
 ---
 
 # Build Error Resolver

package/.github/agents/code-reviewer.agent.md

@@ -1,7 +1,6 @@
 ---
 name: code-reviewer
 description: Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
-tools: ["read", "search", "shell"]
 ---
 
 You are a senior code reviewer ensuring high standards of code quality and security.

package/.github/agents/doc-updater.agent.md

@@ -1,7 +1,6 @@
 ---
 name: doc-updater
 description: Documentation and codemap specialist. Use PROACTIVELY for updating codemaps and documentation. Runs /update-codemaps and /update-docs, generates docs/CODEMAPS/*, updates READMEs and guides.
-tools: ["read", "edit", "shell", "search"]
 ---
 
 # Documentation & Codemap Specialist

package/.github/agents/e2e-runner.agent.md

@@ -1,7 +1,6 @@
 ---
 name: e2e-runner
 description: End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
-tools: ["read", "edit", "shell", "search"]
 ---
 
 # E2E Test Runner

package/.github/agents/planner.agent.md

@@ -1,7 +1,6 @@
 ---
 name: planner
 description: Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.
-tools: ["read", "search"]
 ---
 
 You are an expert planning specialist focused on creating comprehensive, actionable implementation plans.

package/.github/agents/refactor-cleaner.agent.md

@@ -1,7 +1,6 @@
 ---
 name: refactor-cleaner
 description: Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
-tools: ["read", "edit", "shell", "search"]
 ---
 
 # Refactor & Dead Code Cleaner

package/.github/agents/security-reviewer.agent.md

@@ -1,7 +1,6 @@
 ---
 name: security-reviewer
 description: Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
-tools: ["read", "edit", "shell", "search"]
 ---
 
 # Security Reviewer

package/.github/agents/tdd-guide.agent.md

@@ -1,7 +1,6 @@
 ---
 name: tdd-guide
 description: Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
-tools: ["read", "edit", "shell", "search"]
 ---
 
 You are a Test-Driven Development (TDD) specialist who ensures all code is developed test-first with comprehensive coverage.

package/.github/prompts/architect.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: architect
+---

package/.github/prompts/build-error-resolver.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: build-error-resolver
+---

package/.github/prompts/code-reviewer.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: code-reviewer
+---

package/.github/prompts/doc-updater.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: doc-updater
+---

package/.github/prompts/e2e-runner.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: e2e-runner
+---

package/.github/prompts/git.commit.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: git.commit
+---

package/.github/prompts/planner.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: planner
+---

package/.github/prompts/refactor-cleaner.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: refactor-cleaner
+---

package/.github/prompts/tdd-guide.prompt.md

@@ -0,0 +1,3 @@
+---
+agent: tdd-guide
+---

package/.github/prompts/ui-ux-pro-max.prompt.md

@@ -0,0 +1,263 @@
+# ui-ux-pro-max
+
+Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 9 technology stacks. Searchable database with priority-based recommendations.
+
+## Prerequisites
+
+Check if Python is installed:
+
+```bash
+python3 --version || python --version
+```
+
+If Python is not installed, install it based on user's OS:
+
+**macOS:**
+```bash
+brew install python3
+```
+
+**Ubuntu/Debian:**
+```bash
+sudo apt update && sudo apt install python3
+```
+
+**Windows:**
+```powershell
+winget install Python.Python.3.12
+```
+
+---
+
+## How to Use This Workflow
+
+When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow:
+
+### Step 1: Analyze User Requirements
+
+Extract key information from user request:
+- **Product type**: SaaS, e-commerce, portfolio, dashboard, landing page, etc.
+- **Style keywords**: minimal, playful, professional, elegant, dark mode, etc.
+- **Industry**: healthcare, fintech, gaming, education, etc.
+- **Stack**: React, Vue, Next.js, or default to `html-tailwind`
+
+### Step 2: Generate Design System (REQUIRED)
+
+**Always start with `--design-system`** to get comprehensive recommendations with reasoning:
+
+```bash
+python3 .shared/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
+```
+
+This command:
+1. Searches 5 domains in parallel (product, style, color, landing, typography)
+2. Applies reasoning rules from `ui-reasoning.csv` to select best matches
+3. Returns complete design system: pattern, style, colors, typography, effects
+4. Includes anti-patterns to avoid
+
+**Example:**
+```bash
+python3 .shared/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
+```
+
+### Step 3: Supplement with Detailed Searches (as needed)
+
+After getting the design system, use domain searches to get additional details:
+
+```bash
+python3 .shared/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
+```
+
+**When to use detailed searches:**
+
+| Need | Domain | Example |
+|------|--------|---------|
+| More style options | `style` | `--domain style "glassmorphism dark"` |
+| Chart recommendations | `chart` | `--domain chart "real-time dashboard"` |
+| UX best practices | `ux` | `--domain ux "animation accessibility"` |
+| Alternative fonts | `typography` | `--domain typography "elegant luxury"` |
+| Landing structure | `landing` | `--domain landing "hero social-proof"` |
+
+### Step 4: Stack Guidelines (Default: html-tailwind)
+
+Get implementation-specific best practices. If user doesn't specify a stack, **default to `html-tailwind`**.
+
+```bash
+python3 .shared/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
+```
+
+Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`, `react-native`, `flutter`,`jetpack-compose`, `shadcn`
+
+---
+
+## Search Reference
+
+### Available Domains
+
+| Domain | Use For | Example Keywords |
+|--------|---------|------------------|
+| `product` | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |
+| `style` | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |
+| `typography` | Font pairings, Google Fonts | elegant, playful, professional, modern |
+| `color` | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |
+| `landing` | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |
+| `chart` | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |
+| `ux` | Best practices, anti-patterns | animation, accessibility, z-index, loading |
+| `react` | React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache |
+| `web` | Web interface guidelines | aria, focus, keyboard, semantic, virtualize |
+| `prompt` | AI prompts, CSS keywords | (style name) |
+
+### Available Stacks
+
+| Stack | Focus |
+|-------|-------|
+| `html-tailwind` | Tailwind utilities, responsive, a11y (DEFAULT) |
+| `react` | State, hooks, performance, patterns |
+| `nextjs` | SSR, routing, images, API routes |
+| `vue` | Composition API, Pinia, Vue Router |
+| `svelte` | Runes, stores, SvelteKit |
+| `swiftui` | Views, State, Navigation, Animation |
+| `react-native` | Components, Navigation, Lists |
+| `flutter` | Widgets, State, Layout, Theming |
+| `shadcn` | shadcn/ui components, theming, forms, patterns |
+| `jetpack-compose` | Composables, Modifiers, State Hoisting, Recomposition |
+
+---
+
+## Example Workflow
+
+**User request:** "Làm landing page cho dịch vụ chăm sóc da chuyên nghiệp"
+
+### Step 1: Analyze Requirements
+- Product type: Beauty/Spa service
+- Style keywords: elegant, professional, soft
+- Industry: Beauty/Wellness
+- Stack: html-tailwind (default)
+
+### Step 2: Generate Design System (REQUIRED)
+
+```bash
+python3 .shared/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
+```
+
+**Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
+
+### Step 3: Supplement with Detailed Searches (as needed)
+
+```bash
+# Get UX guidelines for animation and accessibility
+python3 .shared/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
+
+# Get alternative typography options if needed
+python3 .shared/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
+```
+
+### Step 4: Stack Guidelines
+
+```bash
+python3 .shared/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
+```
+
+**Then:** Synthesize design system + detailed searches and implement the design.
+
+---
+
+## Output Formats
+
+The `--design-system` flag supports two output formats:
+
+```bash
+# ASCII box (default) - best for terminal display
+python3 .shared/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
+
+# Markdown - best for documentation
+python3 .shared/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
+```
+
+---
+
+## Tips for Better Results
+
+1. **Be specific with keywords** - "healthcare SaaS dashboard" > "app"
+2. **Search multiple times** - Different keywords reveal different insights
+3. **Combine domains** - Style + Typography + Color = Complete design system
+4. **Always check UX** - Search "animation", "z-index", "accessibility" for common issues
+5. **Use stack flag** - Get implementation-specific best practices
+6. **Iterate** - If first search doesn't match, try different keywords
+
+---
+
+## Common Rules for Professional UI
+
+These are frequently overlooked issues that make UI look unprofessional:
+
+### Icons & Visual Elements
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **No emoji icons** | Use SVG icons (Heroicons, Lucide, Simple Icons) | Use emojis like 🎨 🚀 ⚙️ as UI icons |
+| **Stable hover states** | Use color/opacity transitions on hover | Use scale transforms that shift layout |
+| **Correct brand logos** | Research official SVG from Simple Icons | Guess or use incorrect logo paths |
+| **Consistent icon sizing** | Use fixed viewBox (24x24) with w-6 h-6 | Mix different icon sizes randomly |
+
+### Interaction & Cursor
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **Cursor pointer** | Add `cursor-pointer` to all clickable/hoverable cards | Leave default cursor on interactive elements |
+| **Hover feedback** | Provide visual feedback (color, shadow, border) | No indication element is interactive |
+| **Smooth transitions** | Use `transition-colors duration-200` | Instant state changes or too slow (>500ms) |
+
+### Light/Dark Mode Contrast
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **Glass card light mode** | Use `bg-white/80` or higher opacity | Use `bg-white/10` (too transparent) |
+| **Text contrast light** | Use `#0F172A` (slate-900) for text | Use `#94A3B8` (slate-400) for body text |
+| **Muted text light** | Use `#475569` (slate-600) minimum | Use gray-400 or lighter |
+| **Border visibility** | Use `border-gray-200` in light mode | Use `border-white/10` (invisible) |
+
+### Layout & Spacing
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **Floating navbar** | Add `top-4 left-4 right-4` spacing | Stick navbar to `top-0 left-0 right-0` |
+| **Content padding** | Account for fixed navbar height | Let content hide behind fixed elements |
+| **Consistent max-width** | Use same `max-w-6xl` or `max-w-7xl` | Mix different container widths |
+
+---
+
+## Pre-Delivery Checklist
+
+Before delivering UI code, verify these items:
+
+### Visual Quality
+- [ ] No emojis used as icons (use SVG instead)
+- [ ] All icons from consistent icon set (Heroicons/Lucide)
+- [ ] Brand logos are correct (verified from Simple Icons)
+- [ ] Hover states don't cause layout shift
+- [ ] Use theme colors directly (bg-primary) not var() wrapper
+
+### Interaction
+- [ ] All clickable elements have `cursor-pointer`
+- [ ] Hover states provide clear visual feedback
+- [ ] Transitions are smooth (150-300ms)
+- [ ] Focus states visible for keyboard navigation
+
+### Light/Dark Mode
+- [ ] Light mode text has sufficient contrast (4.5:1 minimum)
+- [ ] Glass/transparent elements visible in light mode
+- [ ] Borders visible in both modes
+- [ ] Test both modes before delivery
+
+### Layout
+- [ ] Floating elements have proper spacing from edges
+- [ ] No content hidden behind fixed navbars
+- [ ] Responsive at 375px, 768px, 1024px, 1440px
+- [ ] No horizontal scroll on mobile
+
+### Accessibility
+- [ ] All images have alt text
+- [ ] Form inputs have labels
+- [ ] Color is not the only indicator
+- [ ] `prefers-reduced-motion` respected

package/.github/skills/tdd-workflow/SKILL.md

@@ -7,6 +7,17 @@ description: Use this skill when writing new features, fixing bugs, or refactori
 
 This skill ensures all code development follows TDD principles with comprehensive test coverage.
 
+> **Note for GitHub Copilot Chat Users**: This skill provides TDD workflow guidance. The AI assistant will use the available VS Code tools (file reading, editing, terminal execution) automatically. You don't need to manually invoke any tools - just follow the TDD steps below and the assistant will use the appropriate tools.
+
+## Available Capabilities
+
+When working with GitHub Copilot Chat in VS Code, the following capabilities are available:
+
+- **Reading files**: View source code and test files
+- **Creating/Editing files**: Write test files and implementation code
+- **Running commands**: Execute test commands, coverage reports
+- **Searching code**: Find existing tests, patterns, implementations
+
 ## When to Activate
 
 - Writing new features or functionality

package/.github/skills/verification-loop/SKILL.md

@@ -1,6 +1,8 @@
 # Verification Loop Skill
 
-A comprehensive verification system for Claude Code sessions.
+A comprehensive verification system for code development sessions.
+
+> **Note for GitHub Copilot Chat Users**: This skill provides verification workflow guidance. The AI assistant will use the available VS Code tools automatically to run commands, read files, and search code. No manual tool invocation is required.
 
 ## When to Use
 

package/README.md

@@ -144,10 +144,25 @@ your-project/
 
 ## Compatibility
 
-- **GitHub Copilot CLI** ✅
-- **Claude Code** ✅ (uses same .github/ structure)
-- **VS Code Copilot** ✅
-- **Node.js** >= 18.0.0
+| Platform | Support Level | Notes |
+|----------|--------------|-------|
+| **GitHub Copilot CLI** | ✅ Full | All features (agents, skills, hooks, instructions) |
+| **Claude Code** | ✅ Full | Uses same .github/ structure |
+| **VS Code Copilot Chat** | ⚠️ Partial | Instructions only; agents/hooks not supported |
+| **Node.js** | >= 18.0.0 | Required for CLI |
+
+### Using in VS Code Copilot Chat
+
+VS Code Copilot Chat has different tool capabilities than Copilot CLI:
+
+1. **Custom agents** (`.agent.md`) are **not supported** in VS Code
+2. **Hooks** are **not supported** in VS Code
+3. **Instructions** are loaded automatically ✅
+4. **Skills** can be referenced manually by:
+   - Attaching the skill file to your chat
+   - Saying: "Follow the workflow in `.github/skills/tdd-workflow/SKILL.md`"
+
+VS Code uses its own built-in tools (`read_file`, `run_in_terminal`, etc.) which work automatically.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fyow/copilot-everything",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "description": "Everything you need for GitHub Copilot CLI - agents, skills, instructions, and hooks configurations",
   "main": "src/index.js",
   "bin": {

package/src/commands/init.js

@@ -149,6 +149,15 @@ function init(flags = {}) {
     totalSkipped += instructionsResult.skipped;
     totalErrors.push(...instructionsResult.errors);
 
+    // Prompts (for "/" invocation)
+    const promptsSrc = path.join(githubSrc, 'prompts');
+    const promptsDest = path.join(githubDest, 'prompts');
+    const promptsResult = copyDir(promptsSrc, promptsDest, options);
+    console.log(`   ✅ Prompts: ${promptsResult.copied} copied, ${promptsResult.skipped} skipped`);
+    totalCopied += promptsResult.copied;
+    totalSkipped += promptsResult.skipped;
+    totalErrors.push(...promptsResult.errors);
+
     // Hooks
     if (!skipHooks) {
       const hooksSrc = path.join(githubSrc, 'hooks');