agents-templated 1.2.3 → 1.2.6

package/README.md

@@ -122,7 +122,6 @@ your-project/
 ├── agent-docs/                      # 📚 Comprehensive documentation
 │   ├── AGENTS.md                   # AI assistant guide
 │   ├── ARCHITECTURE.md             # Project architecture & tech stack
-│   ├── AGENTS.MD                   # Agent delegation patterns
 │   └── README.md                   # Human-readable setup guide
 │
 ├── agents/                          # 🤖 AI Agent rules and skills
@@ -134,8 +133,9 @@ your-project/
 │   │   ├── database.mdc           # Database patterns
 │   │   └── style.mdc              # Code style guidelines
 │   └── skills/
-│       ├── web-design-guidelines/ # UI/UX patterns
-│       └── find-skills/           # Skill discovery
+│       ├── find-skills/           # Skill discovery helper
+│       ├── README.md              # Guide for creating custom skills
+│       └── [your-custom-skills]/  # Your project-specific skills
 │
 ├── .github/
 │   └── copilot-instructions.md    # GitHub Copilot config
@@ -224,15 +224,49 @@ Open your AI assistant and it will automatically load the appropriate config:
 - **Claude**: Reads `CLAUDE.md`
 - **Gemini**: Reads `GEMINI.md`
 
-### 3. Read the Documentation
+### 3. Create Custom Skills (Optional)
+
+Extend your AI agents with domain-specific skills for your project:
+
+```bash
+# View the skills guide
+cat agents/skills/README.md
+```
+
+Create a new skill folder in `agents/skills/`:
+
+```markdown
+agents/skills/my-custom-skill/SKILL.md
+---
+name: my-custom-skill
+description: Custom patterns for my project domain
+---
+
+# My Custom Skill
+
+Use this skill when working with [your domain].
+
+## Recommended Patterns
+
+- Pattern 1: Description
+- Pattern 2: Description
+
+## Example
+
+Code and examples...
+```
+
+Skills define *how to execute specific tasks*, complementing rules that define *how to behave*. See [agents/skills/README.md](agents/skills/README.md) for detailed guidance.
+
+### 4. Read the Documentation
 
 - **[AGENTS.md](AGENTS.md)** – AI assistant guide
 - **[agent-docs/ARCHITECTURE.md](agent-docs/ARCHITECTURE.md)** – Project architecture & tech stack guidance
-- **[AGENTS.md](AGENTS.md)** – AI assistant guide
+- **[agents/skills/README.md](agents/skills/README.md)** – Custom skills guide
 - **[agents/rules/security.mdc](agents/rules/security.mdc)** – Security patterns (CRITICAL)
 - **[agents/rules/testing.mdc](agents/rules/testing.mdc)** – Testing strategy
 
-### 4. Start Building
+### 5. Start Building
 
 Tell your AI assistant what to build:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agents-templated",
-  "version": "1.2.3",
+  "version": "1.2.6",
   "description": "Technology-agnostic development template with multi-AI agent support (Cursor, Copilot, VSCode, Gemini), security-first patterns, and comprehensive testing guidelines",
   "main": "index.js",
   "bin": {

package/templates/.github/copilot-instructions.md

@@ -4,9 +4,9 @@ This project follows enterprise-grade, technology-agnostic development patterns.
 
 ## Quick Start
 
-- **AI Guide**: See `agent-docs/AI_INSTRUCTIONS.md` for comprehensive instructions
+- **AI Guide**: See `AGENTS.md` for comprehensive instructions
 - **Architecture**: See `agent-docs/ARCHITECTURE.md` for project guidelines
-- **Agent Patterns**: See `agent-docs/AGENTS.md` for delegation patterns
+- **Custom Skills**: See `agents/skills/` directory for domain-specific extensions
 - **Detailed Rules**: See `agents/rules/*.mdc` files
 
 ## Always Apply

package/templates/AGENTS.MD

@@ -6,6 +6,7 @@ This project follows enterprise-grade, technology-agnostic development patterns.
 
 - **`AGENTS.md`** - This file! AI instructions for working with AI assistants
 - **`agent-docs/ARCHITECTURE.md`** - Overall project guidelines, architecture principles, and technology stack selection
+- **`agents/skills/`** - Custom skills for domain-specific tasks in your project
 
 ## Detailed Rules (Reference When Relevant)
 
@@ -23,10 +24,11 @@ When implementing features, always check the relevant rule file:
 
 When implementing any feature:
 
-1. **Reference `agent-docs/ARCHITECTURE.md`** for overall architecture and technology stack guidance
-2. **Apply relevant rules** from `agents/rules/*.mdc` files based on the task
-3. **Always apply security patterns** from `agents/rules/security.mdc`
-4. **Always apply testing patterns** from `agents/rules/testing.mdc`
+1. **Check for custom skills**: Review `agents/skills/` for domain-specific guidance
+2. **Reference `agent-docs/ARCHITECTURE.md`** for overall architecture and technology stack guidance
+3. **Apply relevant rules** from `agents/rules/*.mdc` files based on the task
+4. **Always apply security patterns** from `agents/rules/security.mdc`
+5. **Always apply testing patterns** from `agents/rules/testing.mdc`
 
 ## Critical Rules (Always Apply)
 

package/templates/CLAUDE.md

@@ -6,7 +6,7 @@ This project uses enterprise-grade, technology-agnostic development patterns for
 
 - **AI Guide**: See `AGENTS.md` for comprehensive instructions
 - **Architecture**: See `agent-docs/ARCHITECTURE.md` for project guidelines
-- **AI Guide**: See `AGENTS.md` for AI assistant patterns
+- **Custom Skills**: See `agents/skills/` directory for domain-specific extensions
 - **Detailed Rules**: See `agents/rules/*.mdc` files
 
 ## Always Apply

package/templates/GEMINI.md

@@ -10,9 +10,9 @@ This project uses enterprise-grade, technology-agnostic development patterns for
 
 - **AI Guide**: See `AGENTS.md` for comprehensive instructions
 - **Architecture**: See `agent-docs/ARCHITECTURE.md` for project guidelines
-- **AI Guide**: See `AGENTS.md` for AI assistant patterns
+- **Custom Skills**: See `agents/skills/` directory for domain-specific extensions
 - **Detailed Rules**: See `agents/rules/*.mdc` files
-- **Available Skills**: See `agents/skills/` directory
+- **Available Skills**: Check `agents/skills/` for project-specific skills
 
 ## Core Development Patterns
 

package/templates/README.md

@@ -118,7 +118,6 @@ your-project/
 ├── agent-docs/                      # 📚 Comprehensive documentation
 │   ├── AGENTS.md                   # AI assistant guide
 │   ├── ARCHITECTURE.md             # Project architecture & tech stack
-│   ├── AGENTS.MD                   # Agent delegation patterns
 │   └── README.md                   # Human-readable setup guide
 │
 ├── agents/                          # 🤖 AI Agent rules and skills
@@ -130,8 +129,9 @@ your-project/
 │   │   ├── database.mdc           # Database patterns
 │   │   └── style.mdc              # Code style guidelines
 │   └── skills/
-│       ├── web-design-guidelines/ # UI/UX patterns
-│       └── find-skills/           # Skill discovery
+│       ├── find-skills/           # Skill discovery helper
+│       ├── README.md              # Guide for creating custom skills
+│       └── [your-custom-skills]/  # Your project-specific skills
 │
 ├── .github/
 │   └── copilot-instructions.md    # GitHub Copilot config
@@ -220,15 +220,49 @@ Open your AI assistant and it will automatically load the appropriate config:
 - **Claude**: Reads `CLAUDE.md`
 - **Gemini**: Reads `GEMINI.md`
 
-### 3. Read the Documentation
+### 3. Create Custom Skills (Optional)
+
+Extend your AI agents with domain-specific skills for your project:
+
+```bash
+# View the skills guide
+cat agents/skills/README.md
+```
+
+Create a new skill folder in `agents/skills/`:
+
+```markdown
+agents/skills/my-custom-skill/SKILL.md
+---
+name: my-custom-skill
+description: Custom patterns for my project domain
+---
+
+# My Custom Skill
+
+Use this skill when working with [your domain].
+
+## Recommended Patterns
+
+- Pattern 1: Description
+- Pattern 2: Description
+
+## Example
+
+Code and examples...
+```
+
+Skills define *how to execute specific tasks*, complementing rules that define *how to behave*. See [agents/skills/README.md](agents/skills/README.md) for detailed guidance.
+
+### 4. Read the Documentation
 
 - **[AGENTS.md](AGENTS.md)** – AI assistant guide
 - **[agent-docs/ARCHITECTURE.md](agent-docs/ARCHITECTURE.md)** – Project architecture & tech stack guidance
-- **[AGENTS.md](AGENTS.md)** – Working with AI assistants guide
+- **[agents/skills/README.md](agents/skills/README.md)** – Custom skills guide
 - **[agents/rules/security.mdc](agents/rules/security.mdc)** – Security patterns (CRITICAL)
 - **[agents/rules/testing.mdc](agents/rules/testing.mdc)** – Testing strategy
 
-### 4. Start Building
+### 5. Start Building
 
 Tell your AI assistant what to build:
 

package/templates/agent-docs/README.md

@@ -36,16 +36,43 @@ agents-templated list
 
 ## Rules and Skills
 
-- **Rules** (`agents/rules/*.mdc`): Markdown files with YAML frontmatter (`description`, `globs`, `alwaysApply`). AI agents use them to know when to apply each rule. Adapt the content to your stack.
-- **Skills** (`agents/skills/*/SKILL.md`): Extend agent capabilities (e.g. find-skills, web-design-guidelines). Each has a name, description, and when to use.
+- **Rules** (`agents/rules/*.mdc`): Define *how to behave* - patterns, principles, and standards for your team
+- **Skills** (`agents/skills/*/SKILL.md`): Define *how to execute specific tasks* - domain-specific workflows and specialized knowledge
+
+### Using Skills in Your AI Assistants
+
+Skills can be referenced in all AI configuration files:
+
+**In `.cursorrules` (Cursor IDE):**
+```
+When the user asks about [domain], use the [skill-name] skill from agents/skills/
+```
+
+**In `CLAUDE.md` (Claude):**
+```
+
+When working on [domain-specific task], reference the [skill-name] skill in agents/skills/[skill-name]/SKILL.md
+```
+
+**In `GEMINI.md` (Google Gemini):**
+```
+When working on [domain-specific task], reference the [skill-name] skill in agents/skills/[skill-name]/SKILL.md
+```
+
+**In `.github/copilot-instructions.md` (GitHub Copilot):**
+```
+When helping with [domain-specific task], reference the [skill-name] skill from agents/skills/[skill-name]/SKILL.md
+```
+
+All AI assistants support skill references. Create custom skills in `agents/skills/` to extend capabilities across your entire team.
 
 ## Getting Started
 
 1. Review AGENTS.md for AI assistance guidance
 2. Review ARCHITECTURE.md for overall project guidelines
-3. Review AGENTS.MD for agent patterns
-4. Adapt the rules to your specific technology stack
-5. Configure your AI assistant (Cursor, Copilot, Claude, Gemini)
+3. Adapt the rules to your specific technology stack
+4. Create custom skills in `agents/skills/` for your domain
+5. Configure your AI assistants (Cursor, Copilot, Claude, Gemini) to reference your skills
 
 ## Documentation
 

package/templates/agents/skills/README.md

@@ -0,0 +1,172 @@
+# Agent Skills
+
+This directory contains custom skills for your AI agents. Skills extend agent capabilities with specialized knowledge, workflows, and tools for specific domains.
+
+## What is a Skill?
+
+A **skill** is a reusable module that:
+- Defines domain-specific knowledge or workflows
+- Extends agent capabilities for specialized tasks
+- Can be shared across your project or published for others
+
+**Rules** define *how to behave*; **Skills** define *how to execute specific tasks*.
+
+## Getting Started
+
+### Finding Existing Skills
+
+Use the built-in `find-skills` skill to discover skills from the open ecosystem:
+
+```bash
+npx skills find [query]
+```
+
+Examples:
+- `npx skills find react testing`
+- `npx skills find deployment`
+- `npx skills find accessibility`
+
+Browse more at: https://skills.sh/
+
+### Creating a Custom Skill
+
+To create a new skill for your specific domain:
+
+1. **Create a new folder** in this directory:
+   ```
+   agents/skills/my-custom-skill/
+   ```
+
+2. **Create a SKILL.md file** with metadata and instructions:
+   ```markdown
+   ---
+   name: my-custom-skill
+   description: Brief description of what this skill does
+   ---
+
+   # My Custom Skill
+
+   Instructions and examples for using this skill...
+   ```
+
+3. **Reference it** in your agent documentation or `.cursorrules`
+
+### Skill Structure
+
+```
+agents/skills/
+├── find-skills/
+│   └── SKILL.md              # Meta-skill for discovering skills
+├── my-custom-skill/
+│   └── SKILL.md              # Your custom skill
+└── README.md                 # This file
+```
+
+## Best Practices
+
+1. **Keep skills focused** - Each skill should handle one domain or workflow
+2. **Document clearly** - Include examples and use cases in SKILL.md
+3. **Name descriptively** - Use kebab-case names that reflect the skill's purpose
+4. **Version your skills** - Include version info in the metadata
+5. **Test before sharing** - Ensure skills work as documented
+
+## Common Skill Categories
+
+Consider creating skills for:
+
+| Category        | Use Case                                 |
+| --------------- | ---------------------------------------- |
+| Web Development | Framework-specific patterns and guidelines |
+| Testing         | Testing strategies and examples          |
+| DevOps          | Deployment, CI/CD, infrastructure        |
+| Documentation   | Doc generation, README templates         |
+| Code Quality    | Code review, refactoring patterns        |
+| Design          | UI/UX, accessibility, design systems    |
+| Productivity    | Workflows, automation, git patterns      |
+
+## Using Skills in Your Project
+
+Skills can be referenced in all your AI assistant configuration files:
+
+### Cursor IDE (`.cursorrules`)
+```
+When the user asks about [domain], use the [skill-name] skill from agents/skills/[skill-name]/SKILL.md
+```
+
+### Claude (`CLAUDE.md`)
+```markdown
+## When Working on [Domain]
+
+Reference the [skill-name] skill in `agents/skills/[skill-name]/SKILL.md` for patterns and guidance.
+```
+
+### Google Gemini (`GEMINI.md`)
+```markdown
+## When Working on [Domain]
+
+Reference the [skill-name] skill in `agents/skills/[skill-name]/SKILL.md` for patterns and guidance.
+```
+
+### GitHub Copilot (`.github/copilot-instructions.md`)
+```markdown
+When helping with [domain-specific task], reference the [skill-name] skill from `agents/skills/[skill-name]/SKILL.md`
+```
+
+### Documentation (`AGENTS.md`)
+```markdown
+- When working with [domain], see the [skill-name] skill in `agents/skills/[skill-name]/SKILL.md`
+```
+
+**All AI assistants support skill references.** Keep your team aligned by linking to skill files across your configuration files.
+
+3. **Share with your team**:
+   - Commit to version control
+   - Document installation in your README
+
+## Example: Creating a Fastapi Skill
+
+```markdown
+---
+name: fastapi-patterns
+description: FastAPI development patterns and best practices for your projects
+---
+
+# FastAPI Patterns
+
+Use this skill when working with FastAPI projects.
+
+## Recommended Patterns
+
+### Request Validation
+- Use Pydantic models for all request bodies
+- Validate query parameters with proper typing
+
+### Error Handling
+- Return meaningful HTTP status codes
+- Document error responses in OpenAPI
+
+### Testing
+- Use TestClient for API testing
+- Mock external dependencies
+
+## Project Structure
+
+```
+src/
+├── api/
+│   ├── v1/
+│   │   ├── users/
+│   │   └── posts/
+│   └── dependencies.py
+├── models/
+├── schemas/
+├── database/
+└── main.py
+```
+```
+
+## Resources
+
+- [Skills Documentation](https://skills.sh/)
+- [Creating Skills Guide](https://skills.sh/docs/creating-skills)
+- [Browse Popular Skills](https://skills.sh/explore)

package/templates/agents/skills/ui-ux-pro-max/SKILL.md

@@ -0,0 +1,386 @@
+---
+name: ui-ux-pro-max
+description: "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples."
+---
+
+# UI/UX Pro Max - Design Intelligence
+
+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.
+
+## When to Apply
+
+Reference these guidelines when:
+- Designing new UI components or pages
+- Choosing color palettes and typography
+- Reviewing code for UX issues
+- Building landing pages or dashboards
+- Implementing accessibility requirements
+
+## Rule Categories by Priority
+
+| Priority | Category | Impact | Domain |
+|----------|----------|--------|--------|
+| 1 | Accessibility | CRITICAL | `ux` |
+| 2 | Touch & Interaction | CRITICAL | `ux` |
+| 3 | Performance | HIGH | `ux` |
+| 4 | Layout & Responsive | HIGH | `ux` |
+| 5 | Typography & Color | MEDIUM | `typography`, `color` |
+| 6 | Animation | MEDIUM | `ux` |
+| 7 | Style Selection | MEDIUM | `style`, `product` |
+| 8 | Charts & Data | LOW | `chart` |
+
+## Quick Reference
+
+### 1. Accessibility (CRITICAL)
+
+- `color-contrast` - Minimum 4.5:1 ratio for normal text
+- `focus-states` - Visible focus rings on interactive elements
+- `alt-text` - Descriptive alt text for meaningful images
+- `aria-labels` - aria-label for icon-only buttons
+- `keyboard-nav` - Tab order matches visual order
+- `form-labels` - Use label with for attribute
+
+### 2. Touch & Interaction (CRITICAL)
+
+- `touch-target-size` - Minimum 44x44px touch targets
+- `hover-vs-tap` - Use click/tap for primary interactions
+- `loading-buttons` - Disable button during async operations
+- `error-feedback` - Clear error messages near problem
+- `cursor-pointer` - Add cursor-pointer to clickable elements
+
+### 3. Performance (HIGH)
+
+- `image-optimization` - Use WebP, srcset, lazy loading
+- `reduced-motion` - Check prefers-reduced-motion
+- `content-jumping` - Reserve space for async content
+
+### 4. Layout & Responsive (HIGH)
+
+- `viewport-meta` - width=device-width initial-scale=1
+- `readable-font-size` - Minimum 16px body text on mobile
+- `horizontal-scroll` - Ensure content fits viewport width
+- `z-index-management` - Define z-index scale (10, 20, 30, 50)
+
+### 5. Typography & Color (MEDIUM)
+
+- `line-height` - Use 1.5-1.75 for body text
+- `line-length` - Limit to 65-75 characters per line
+- `font-pairing` - Match heading/body font personalities
+
+### 6. Animation (MEDIUM)
+
+- `duration-timing` - Use 150-300ms for micro-interactions
+- `transform-performance` - Use transform/opacity, not width/height
+- `loading-states` - Skeleton screens or spinners
+
+### 7. Style Selection (MEDIUM)
+
+- `style-match` - Match style to product type
+- `consistency` - Use same style across all pages
+- `no-emoji-icons` - Use SVG icons, not emojis
+
+### 8. Charts & Data (LOW)
+
+- `chart-type` - Match chart type to data type
+- `color-guidance` - Use accessible color palettes
+- `data-table` - Provide table alternative for accessibility
+
+## How to Use
+
+Search specific domains using the CLI tool below.
+
+---
+
+## 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 Skill
+
+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 skills/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 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
+```
+
+### Step 2b: Persist Design System (Master + Overrides Pattern)
+
+To save the design system for **hierarchical retrieval across sessions**, add `--persist`:
+
+```bash
+python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
+```
+
+This creates:
+- `design-system/MASTER.md` — Global Source of Truth with all design rules
+- `design-system/pages/` — Folder for page-specific overrides
+
+**With page-specific override:**
+```bash
+python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
+```
+
+This also creates:
+- `design-system/pages/dashboard.md` — Page-specific deviations from Master
+
+**How hierarchical retrieval works:**
+1. When building a specific page (e.g., "Checkout"), first check `design-system/pages/checkout.md`
+2. If the page file exists, its rules **override** the Master file
+3. If not, use `design-system/MASTER.md` exclusively
+
+**Context-aware retrieval prompt:**
+```
+I am building the [Page Name] page. Please read design-system/MASTER.md.
+Also check if design-system/pages/[page-name].md exists.
+If the page file exists, prioritize its rules.
+If not, use the Master rules exclusively.
+Now, generate the code...
+```
+
+### Step 3: Supplement with Detailed Searches (as needed)
+
+After getting the design system, use domain searches to get additional details:
+
+```bash
+python3 skills/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 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
+```
+
+Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`, `react-native`, `flutter`, `shadcn`, `jetpack-compose`
+
+---
+
+## 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 skills/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 skills/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
+
+# Get alternative typography options if needed
+python3 skills/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
+```
+
+### Step 4: Stack Guidelines
+
+```bash
+python3 skills/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 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
+
+# Markdown - best for documentation
+python3 skills/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/templates/agents/skills/web-design-guidelines/SKILL.md

@@ -1,39 +0,0 @@
----
-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.