npm - antigravity-ide - Versions diffs - 4.2.1 → 4.3.3 - Mend

antigravity-ide 4.2.1 → 4.3.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (359) hide show

package/.agent/workflows/test.md CHANGED Viewed

@@ -1,144 +1,47 @@
 ---
-description: Sợ bug khi sửa code? Viết test tự động.
+description: Sợ bug khi sửa code? Viết test tự động theo chuẩn TDD Master.
 ---
-# /test - Test Generation and Execution
+# /test - TDD & Verification Suite
 $ARGUMENTS
 ---
-## Purpose
+## 🟢 PHASE 1: Code Analysis & Edge Case Mapping
+**Agent**: `test-engineer`
+**Mission**: Map the "Search Space" of potential bugs.
+- **Action**: Identify all public functions, API routes, and logic branches.
+- **Discovery**: Generate a "Gherkin" style list of test scenarios (Given/When/Then).
-This command generates tests, runs existing tests, or checks test coverage.
+## 🟡 PHASE 2: Test Architecture & Mocking
+**Agent**: `test-engineer`
+**Mission**: Build the testing base.
+- **Action**: Configure mocks for DB, External APIs, and system clock.
+- **Artifact**: Write a Test Plan in the `implementation_plan.md`.
----
-## Sub-commands
-```
-/test                - Run all tests
-/test [file/feature] - Generate tests for specific target
-/test coverage       - Show test coverage report
-/test watch          - Run tests in watch mode
-```
----
-## Behavior
-### Generate Tests
-When asked to test a file or feature:
-1. **Analyze the code**
-   - Identify functions and methods
-   - Find edge cases
-   - Detect dependencies to mock
+## 🔵 PHASE 3: Execution (The RED-GREEN Loop)
+**Agent**: `qa-automation-engineer`
+**Mission**: Automate the verification.
+- **Action**: Write and run unit, integration, and E2E tests.
+- **Audit**: Every test must fail at least once (verify the test is valid).
-2. **Generate test cases**
-   - Happy path tests
-   - Error cases
-   - Edge cases
-   - Integration tests (if needed)
-3. **Write tests**
-   - Use project's test framework (Jest, Vitest, etc.)
-   - Follow existing test patterns
-   - Mock external dependencies
+## 🔴 PHASE 4: Coverage & Quality Sign-off
+**Agent**: `quality-inspector`
+**Mission**: Verify the safety net.
+- **Action**: Check code coverage metrics.
+- **Artifact**: Report Pass/Fail stats in the final `walkthrough.md`.
 ---
-## Output Format
-### For Test Generation
-```markdown
-## 🧪 Tests: [Target]
-### Test Plan
-| Test Case | Type | Coverage |
-|-----------|------|----------|
-| Should create user | Unit | Happy path |
-| Should reject invalid email | Unit | Validation |
-| Should handle db error | Unit | Error case |
-### Generated Tests
-`tests/[file].test.ts`
-[Code block with tests]
+## Patterns of Excellence:
+- **One Assertion**: Each test tests one thing.
+- **Fast Feedback**: Unit tests should run in <1s.
+- **Hermeticity**: Tests must not share state or depend on network.
 ---
-Run with: `npm test`
-```
-### For Test Execution
-```
-🧪 Running tests...
-✅ auth.test.ts (5 passed)
-✅ user.test.ts (8 passed)
-❌ order.test.ts (2 passed, 1 failed)
-Failed:
-  ✗ should calculate total with discount
-    Expected: 90
-    Received: 100
-Total: 15 tests (14 passed, 1 failed)
-```
----
-## Examples
-```
-/test src/services/auth.service.ts
-/test user registration flow
-/test coverage
-/test fix failed tests
-```
----
-## Test Patterns
-### Unit Test Structure
-```typescript
-describe('AuthService', () => {
-  describe('login', () => {
-    it('should return token for valid credentials', async () => {
-      // Arrange
-      const credentials = { email: 'test@test.com', password: 'pass123' };
-      // Act
-      const result = await authService.login(credentials);
-      // Assert
-      expect(result.token).toBeDefined();
-    });
-    it('should throw for invalid password', async () => {
-      // Arrange
-      const credentials = { email: 'test@test.com', password: 'wrong' };
-      // Act & Assert
-      await expect(authService.login(credentials)).rejects.toThrow('Invalid credentials');
-    });
-  });
-});
-```
----
-## Key Principles
-- **Test behavior not implementation**
-- **One assertion per test** (when practical)
-- **Descriptive test names**
-- **Arrange-Act-Assert pattern**
-- **Mock external dependencies**
+## Examples:
+- `/test auth service`
+- `/test coverage src/utils`
+- `/test fix failed tests`

package/.agent/workflows/ui-ux-pro-max.md CHANGED Viewed

@@ -1,293 +1,34 @@
 ---
-description: Muốn giao diện đẹp (Linear/Magic UI)? Bấm vào đây.
+description: Thiết kế giao diện Visuals Premium với phong cách hiện đại
 ---
+# /ui-ux-pro-max - Premium UI Generator
-# ui-ux-pro-max
+> **Chế độ**: Premium Visuals (Modern Aesthetic)
+> **Yêu cầu BẮT BUỘC**: Clean, Minimalist, High Contrast.
-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.
+## 🎨 Design Standard
-## Prerequisites
+Mọi giao diện được tạo bởi workflow này phải tuân thủ chuẩn "Pro Max":
-Check if Python is installed:
+1.  **Typography**:
+    -   Sử dụng Font phương tây hiện đại (Inter, Roboto, Poppins).
+    -   Heading đậm, Body thanh thoát.
+2.  **Color Palette**:
+    -   Sử dụng màu Gradient tinh tế.
+    -   Tránh màu quá chói (Neon) trừ khi là điểm nhấn (Accent).
+3.  **Layout**:
+    -   Sử dụng Grid/Flexbox chuẩn.
+    -   Whitespace rộng rãi (Breathable design).
+4.  **Micro-interactions**:
+    -   Hover effects mượt mà (transition: 0.3s).
+    -   Button có active state rõ ràng.
-```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 .agent/.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 .agent/.shared/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 .agent/.shared/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 .agent/.shared/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
-### Step 3: Supplement with Detailed Searches (as needed)
-After getting the design system, use domain searches to get additional details:
-```bash
-python3 .agent/.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 .agent/.shared/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`
-, `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 .agent/.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 .agent/.shared/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
-# Get alternative typography options if needed
-python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
-```
-### Step 4: Stack Guidelines
-```bash
-python3 .agent/.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 .agent/.shared/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
-# Markdown - best for documentation
-python3 .agent/.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 |
+## 🛠️ Quy trình thực hiện
+1. **Analyze**: Hiểu rõ user persona.
+2. **Structure**: HTML5 Semantic (Header, Main, Section, Footer).
+3. **Style**: CSS Variables cho màu sắc, spacing.
+4. **Resposive**: Mobile-first approach.
 ---
-## 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
+**Note**: Focus on Usability and Elegance.

package/LICENSE CHANGED Viewed

@@ -17,25 +17,39 @@ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 ================================================================================
-ACKNOWLEDGEMENTS & REFERENCES
+UNIVERSAL ACKNOWLEDGEMENTS & REFERENCES
 ================================================================================
-This project is maintained by Dokhacgiakhoa.
-It incorporates concepts and references from the following open source projects:
+This project is authored and maintained by Dokhacgiakhoa.
+Antigravity IDE (Enhanced Edition) draws significant inspiration and inherits
+open-source knowledge from the following masters and repositories:
-1. Antigravity Kit (Ref: Structure)
-   - Original Author: VUDOVN
+1. Antigravity Kit (Core Reference)
+   - Original Author: vudovn
    - Link: https://github.com/vudovn/antigravity-kit
-2. Antigravity Awesome Skills (Ref: Skill Data)
+2. Antigravity Awesome Skills (Skill Metadata Reference)
    - Original Author: sickn33
    - Link: https://github.com/sickn33/antigravity-awesome-skills
-3. UI/UX Pro Max (Ref: Design Standards)
+3. UI/UX Pro Max (Design Philosophy Reference)
    - Original Author: sickn33
    - Link: https://github.com/sickn33/ui-ux-pro-max
-*Note: The original authors listed above are credited for their antecedent work but are not involved in the maintenance of this derived repository.*
+4. Model Context Protocol (MCP) standards
+   - Authors: Anthropic & Ecosystem Contributors
+   - Link: https://modelcontextprotocol.io/
+5. High-Performance Web Standards
+   - Inspiration: Vercel Engineering & Anthony Fu (antfu)
+6. Strategic Knowledge Extraction
+   - Inspiration: Fabric Patterns (danielmiessler)
+*Note: All trademarks and copyrights belong to their respective owners.
+The references above reflect research-level inspiration and antecedent
+contributions. These parties are not involved in the management of this repository.*