thachvd-kit 1.0.29 → 1.0.31

package/.agent/skills/webapp-testing/SKILL.md

@@ -1,187 +0,0 @@
----
-name: webapp-testing
-description: Web application testing principles. E2E, Playwright, deep audit strategies.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# Web App Testing
-
-> Discover and test everything. Leave no route untested.
-
-## 🔧 Runtime Scripts
-
-**Execute these for automated browser testing:**
-
-| Script | Purpose | Usage |
-|--------|---------|-------|
-| `scripts/playwright_runner.py` | Basic browser test | `python scripts/playwright_runner.py https://example.com` |
-| | With screenshot | `python scripts/playwright_runner.py <url> --screenshot` |
-| | Accessibility check | `python scripts/playwright_runner.py <url> --a11y` |
-
-**Requires:** `pip install playwright && playwright install chromium`
-
----
-
-## 1. Deep Audit Approach
-
-### Discovery First
-
-| Target | How to Find |
-|--------|-------------|
-| Routes | Scan app/, pages/, router files |
-| API endpoints | Grep for HTTP methods |
-| Components | Find component directories |
-| Features | Read documentation |
-
-### Systematic Testing
-
-1. **Map** - List all routes/APIs
-2. **Scan** - Verify they respond
-3. **Test** - Cover critical paths
-
----
-
-## 2. Testing Pyramid for Web
-
-```
-        /\          E2E (Few)
-       /  \         Critical user flows
-      /----\
-     /      \       Integration (Some)
-    /--------\      API, data flow
-   /          \
-  /------------\    Component (Many)
-                    Individual UI pieces
-```
-
----
-
-## 3. E2E Test Principles
-
-### What to Test
-
-| Priority | Tests |
-|----------|-------|
-| 1 | Happy path user flows |
-| 2 | Authentication flows |
-| 3 | Critical business actions |
-| 4 | Error handling |
-
-### E2E Best Practices
-
-| Practice | Why |
-|----------|-----|
-| Use data-testid | Stable selectors |
-| Wait for elements | Avoid flaky tests |
-| Clean state | Independent tests |
-| Avoid implementation details | Test user behavior |
-
----
-
-## 4. Playwright Principles
-
-### Core Concepts
-
-| Concept | Use |
-|---------|-----|
-| Page Object Model | Encapsulate page logic |
-| Fixtures | Reusable test setup |
-| Assertions | Built-in auto-wait |
-| Trace Viewer | Debug failures |
-
-### Configuration
-
-| Setting | Recommendation |
-|---------|----------------|
-| Retries | 2 on CI |
-| Trace | on-first-retry |
-| Screenshots | on-failure |
-| Video | retain-on-failure |
-
----
-
-## 5. Visual Testing
-
-### When to Use
-
-| Scenario | Value |
-|----------|-------|
-| Design system | High |
-| Marketing pages | High |
-| Component library | Medium |
-| Dynamic content | Lower |
-
-### Strategy
-
-- Baseline screenshots
-- Compare on changes
-- Review visual diffs
-- Update intentional changes
-
----
-
-## 6. API Testing Principles
-
-### Coverage Areas
-
-| Area | Tests |
-|------|-------|
-| Status codes | 200, 400, 404, 500 |
-| Response shape | Matches schema |
-| Error messages | User-friendly |
-| Edge cases | Empty, large, special chars |
-
----
-
-## 7. Test Organization
-
-### File Structure
-
-```
-tests/
-├── e2e/           # Full user flows
-├── integration/   # API, data
-├── component/     # UI units
-└── fixtures/      # Shared data
-```
-
-### Naming Convention
-
-| Pattern | Example |
-|---------|---------|
-| Feature-based | `login.spec.ts` |
-| Descriptive | `user-can-checkout.spec.ts` |
-
----
-
-## 8. CI Integration
-
-### Pipeline Steps
-
-1. Install dependencies
-2. Install browsers
-3. Run tests
-4. Upload artifacts (traces, screenshots)
-
-### Parallelization
-
-| Strategy | Use |
-|----------|-----|
-| Per file | Playwright default |
-| Sharding | Large suites |
-| Workers | Multiple browsers |
-
----
-
-## 9. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Test implementation | Test behavior |
-| Hardcode waits | Use auto-wait |
-| Skip cleanup | Isolate tests |
-| Ignore flaky tests | Fix root cause |
-
----
-
-> **Remember:** E2E tests are expensive. Use them for critical paths only.

package/.agent/skills/webapp-testing/scripts/playwright_runner.py

@@ -1,173 +0,0 @@
-#!/usr/bin/env python3
-"""
-Skill: webapp-testing
-Script: playwright_runner.py
-Purpose: Run basic Playwright browser tests
-Usage: python playwright_runner.py <url> [--screenshot]
-Output: JSON with page info, health status, and optional screenshot path
-Note: Requires playwright (pip install playwright && playwright install chromium)
-Screenshots: Saved to system temp directory (auto-cleaned by OS)
-"""
-import sys
-import json
-import os
-import tempfile
-from datetime import datetime
-
-# Fix Windows console encoding for Unicode output
-try:
-    sys.stdout.reconfigure(encoding='utf-8', errors='replace')
-    sys.stderr.reconfigure(encoding='utf-8', errors='replace')
-except AttributeError:
-    pass  # Python < 3.7
-
-try:
-    from playwright.sync_api import sync_playwright
-    PLAYWRIGHT_AVAILABLE = True
-except ImportError:
-    PLAYWRIGHT_AVAILABLE = False
-
-
-def run_basic_test(url: str, take_screenshot: bool = False) -> dict:
-    """Run basic browser test on URL."""
-    if not PLAYWRIGHT_AVAILABLE:
-        return {
-            "error": "Playwright not installed",
-            "fix": "pip install playwright && playwright install chromium"
-        }
-    
-    result = {
-        "url": url,
-        "timestamp": datetime.now().isoformat(),
-        "status": "pending"
-    }
-    
-    try:
-        with sync_playwright() as p:
-            browser = p.chromium.launch(headless=True)
-            context = browser.new_context(
-                viewport={"width": 1280, "height": 720},
-                user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36"
-            )
-            page = context.new_page()
-            
-            # Navigate
-            response = page.goto(url, wait_until="networkidle", timeout=30000)
-            
-            # Basic info
-            result["page"] = {
-                "title": page.title(),
-                "url": page.url,
-                "status_code": response.status if response else None
-            }
-            
-            # Health checks
-            result["health"] = {
-                "loaded": response.ok if response else False,
-                "has_title": bool(page.title()),
-                "has_h1": page.locator("h1").count() > 0,
-                "has_links": page.locator("a").count() > 0,
-                "has_images": page.locator("img").count() > 0
-            }
-            
-            # Console errors
-            console_errors = []
-            page.on("console", lambda msg: console_errors.append(msg.text) if msg.type == "error" else None)
-            
-            # Performance metrics
-            result["performance"] = {
-                "dom_content_loaded": page.evaluate("window.performance.timing.domContentLoadedEventEnd - window.performance.timing.navigationStart"),
-                "load_complete": page.evaluate("window.performance.timing.loadEventEnd - window.performance.timing.navigationStart")
-            }
-            
-            # Screenshot - uses system temp directory (cross-platform, auto-cleaned)
-            if take_screenshot:
-                # Cross-platform: Windows=%TEMP%, Linux/macOS=/tmp
-                screenshot_dir = os.path.join(tempfile.gettempdir(), "maestro_screenshots")
-                os.makedirs(screenshot_dir, exist_ok=True)
-                screenshot_path = os.path.join(screenshot_dir, f"screenshot_{datetime.now().strftime('%Y%m%d_%H%M%S')}.png")
-                page.screenshot(path=screenshot_path, full_page=True)
-                result["screenshot"] = screenshot_path
-                result["screenshot_note"] = "Saved to temp directory (auto-cleaned by OS)"
-            
-            # Element counts
-            result["elements"] = {
-                "links": page.locator("a").count(),
-                "buttons": page.locator("button").count(),
-                "inputs": page.locator("input").count(),
-                "images": page.locator("img").count(),
-                "forms": page.locator("form").count()
-            }
-            
-            browser.close()
-            
-            result["status"] = "success" if result["health"]["loaded"] else "failed"
-            result["summary"] = "[OK] Page loaded successfully" if result["status"] == "success" else "[X] Page failed to load"
-            
-    except Exception as e:
-        result["status"] = "error"
-        result["error"] = str(e)
-        result["summary"] = f"[X] Error: {str(e)[:100]}"
-    
-    return result
-
-
-def run_accessibility_check(url: str) -> dict:
-    """Run basic accessibility check."""
-    if not PLAYWRIGHT_AVAILABLE:
-        return {"error": "Playwright not installed"}
-    
-    result = {"url": url, "accessibility": {}}
-    
-    try:
-        with sync_playwright() as p:
-            browser = p.chromium.launch(headless=True)
-            page = browser.new_page()
-            page.goto(url, wait_until="networkidle", timeout=30000)
-            
-            # Basic a11y checks
-            result["accessibility"] = {
-                "images_with_alt": page.locator("img[alt]").count(),
-                "images_without_alt": page.locator("img:not([alt])").count(),
-                "buttons_with_label": page.locator("button[aria-label], button:has-text('')").count(),
-                "links_with_text": page.locator("a:has-text('')").count(),
-                "form_labels": page.locator("label").count(),
-                "headings": {
-                    "h1": page.locator("h1").count(),
-                    "h2": page.locator("h2").count(),
-                    "h3": page.locator("h3").count()
-                }
-            }
-            
-            browser.close()
-            result["status"] = "success"
-            
-    except Exception as e:
-        result["status"] = "error"
-        result["error"] = str(e)
-    
-    return result
-
-
-if __name__ == "__main__":
-    if len(sys.argv) < 2:
-        print(json.dumps({
-            "error": "Usage: python playwright_runner.py <url> [--screenshot] [--a11y]",
-            "examples": [
-                "python playwright_runner.py https://example.com",
-                "python playwright_runner.py https://example.com --screenshot",
-                "python playwright_runner.py https://example.com --a11y"
-            ]
-        }, indent=2))
-        sys.exit(1)
-    
-    url = sys.argv[1]
-    take_screenshot = "--screenshot" in sys.argv
-    check_a11y = "--a11y" in sys.argv
-    
-    if check_a11y:
-        result = run_accessibility_check(url)
-    else:
-        result = run_basic_test(url, take_screenshot)
-    
-    print(json.dumps(result, indent=2))

package/.agent/skills/writing-skills/SKILL.md

@@ -1,170 +0,0 @@
----
-name: writing-skills
-description: Use when creating a new skill or improving an existing one — follows best practices for SKILL.md structure, Claude Search Optimization, token efficiency, anti-rationalization tables, and skill testing methodology
-allowed-tools: Read, Write, Edit
----
-
-# Writing Skills
-
-## What is a Skill?
-
-A skill is a reusable instruction set that activates when an AI detects a relevant context. It lives in a folder with a `SKILL.md` file and works across Codex, Antigravity, Claude, and Cursor.
-
-## Skill Types
-
-| Type | Purpose | Example | Anti-Rationalization Required? |
-|------|---------|---------|----|
-| **Technique** | How-to guide | `tdd-workflow` | Optional |
-| **Pattern** | Mental model | `clean-code` | Optional |
-| **Reference** | Documentation | `api-patterns` | No |
-| **Discipline** | Rules/enforcement | `verification-before-completion` | **Mandatory** |
-
-## Directory Structure
-
-```
-skill-name/
-├── SKILL.md          # Required: metadata + instructions
-├── scripts/          # Optional: runnable scripts
-└── references/       # Optional: templates, docs
-```
-
-## SKILL.md Structure
-
-```markdown
----
-name: skill-name
-description: [Trigger description — when to use this skill]
-allowed-tools: [Bash, Read, Edit, Write, ...]
----
-
-# Skill Title
-
-## Overview
-Brief summary + core principle
-
-## When to Use
-- Specific trigger scenarios
-
-## [Main Content]
-...
-
-## Anti-Rationalization  ← REQUIRED for Discipline/Technique skills
-| Excuse | Correct Response |
-|--------|-----------------|
-| "Just this once" | No exceptions. Apply the rule. |
-
-## Exit Criteria  ← REQUIRED for Technique/Discipline skills
-- [ ] Specific, verifiable condition 1
-- [ ] Specific, verifiable condition 2
-```
-
-## Claude Search Optimization (CSO)
-
-The `description` field is how the AI decides whether to load your skill. Make it trigger correctly:
-
-### 1. Rich Description
-
-```yaml
-# ❌ Vague
-description: For code review
-
-# ✅ Specific with triggers
-description: Use when completing tasks, implementing major features, or before merging — pre-review checklist, evidence-before-claims workflow
-```
-
-### 2. Keyword Coverage
-
-Include synonyms, trigger phrases, and common user requests in description.
-
-### 3. Token Efficiency (Critical)
-
-- Use tables instead of prose for comparisons
-- Use code blocks for commands
-- Use flowcharts/diagrams for processes
-- Avoid narrative explanations — use structured data
-
-### 4. Cross-Referencing
-
-Use `Pairs with:` and `Integration:` sections to link related skills.
-
-## Anti-Rationalization Tables (Key Concept)
-
-The most powerful feature of a discipline skill. A table that blocks the AI's most common excuses for skipping a rule.
-
-### Why They Matter
-
-AI agents (like humans) tend to rationalize shortcuts under pressure. An Anti-Rationalization table names each excuse explicitly and provides the correct response, making it impossible to skip without consciously overriding the rule.
-
-### Format
-
-```markdown
-## Anti-Rationalization
-
-| Excuse | Reality / Correct Response |
-|--------|---------------------------|
-| "It's a small change" | Size doesn't reduce the need. Apply the rule. |
-| "I'm confident it works" | Confidence ≠ evidence. Run verification. |
-| "Just this once" | No exceptions — "just this once" is how standards die. |
-| "The last run passed" | Stale results. Run fresh verification now. |
-```
-
-### What Makes a Good Entry
-
-- **Excuse column**: Real phrases AI uses to justify skipping. Be specific.
-- **Reality column**: The direct counter. Short, imperative, no hedging.
-- Cover at least 4–6 common excuses for discipline skills.
-
-## Exit Criteria
-
-Every Technique or Discipline skill must end with a verifiable checklist the AI can check off before declaring the task done.
-
-```markdown
-## Exit Criteria
-
-Before claiming this task is complete:
-- [ ] [Verifiable condition 1]
-- [ ] [Verifiable condition 2]
-- [ ] [Verifiable condition 3]
-```
-
-**Rules for Exit Criteria:**
-- Each item must be binary (done or not done) — no vague "looks good" items
-- Must be something that can be checked programmatically or by inspection
-- Failing any item = task is NOT complete
-
-## Anti-Patterns to Avoid
-
-| ❌ Anti-Pattern | ✅ Fix |
-|----------------|-------|
-| Narrative prose everywhere | Tables, bullet lists, code blocks |
-| Discipline skill with no Anti-Rationalization | Add the table — it's mandatory |
-| Technique skill with no Exit Criteria | Add verifiable checklist |
-| Vague description | Specific triggers and use cases |
-| Generic labels ("Step 1", "Step 2") | Descriptive labels ("Verify baseline", "Run tests") |
-| Code examples in flowchart labels | Flowcharts for flow, code blocks for code |
-
-## Skill Creation Checklist
-
-- [ ] Description field triggers correctly (test: "would AI load this for X?")
-- [ ] Core principle stated in Overview
-- [ ] Content uses tables/code blocks, not prose paragraphs
-- [ ] Token-efficient (no redundant explanations)
-- [ ] **Anti-Rationalization section included** (Discipline/Technique skills — mandatory)
-- [ ] **Exit Criteria section included** (Discipline/Technique skills — mandatory)
-- [ ] Integration section lists related skills
-- [ ] Tested: create a scenario where this skill should fire, verify it does
-
-## Testing Skills
-
-For **discipline skills** (rules): Create scenario where rule should fire, verify AI follows it AND rejects the rationalizations in the Anti-Rationalization table.
-For **technique skills** (how-to): Apply skill to a real task, verify output quality and that Exit Criteria are met.
-For **reference skills** (docs): Query for specific info, verify correct answer.
-
-## The Bottom Line
-
-A skill is good when:
-1. It fires when it should (good description/CSO)
-2. It improves output quality noticeably
-3. It's token-efficient (doesn't waste context)
-4. It has no ambiguous loopholes (Anti-Rationalization table closes them)
-5. It's verifiable (Exit Criteria defines "done")

package/.agent/workflows/brainstorm.md

@@ -1,113 +0,0 @@
----
-description: Structured brainstorming for projects and features. Explores multiple options before implementation.
----
-
-# /brainstorm - Structured Idea Exploration
-
-$ARGUMENTS
-
----
-
-## Purpose
-
-This command activates BRAINSTORM mode for structured idea exploration. Use when you need to explore options before committing to an implementation.
-
----
-
-## Behavior
-
-When `/brainstorm` is triggered:
-
-1. **Understand the goal**
-   - What problem are we solving?
-   - Who is the user?
-   - What constraints exist?
-
-2. **Generate options**
-   - Provide at least 3 different approaches
-   - Each with pros and cons
-   - Consider unconventional solutions
-
-3. **Compare and recommend**
-   - Summarize tradeoffs
-   - Give a recommendation with reasoning
-
----
-
-## Output Format
-
-```markdown
-## 🧠 Brainstorm: [Topic]
-
-### Context
-[Brief problem statement]
-
----
-
-### Option A: [Name]
-[Description]
-
-✅ **Pros:**
-- [benefit 1]
-- [benefit 2]
-
-❌ **Cons:**
-- [drawback 1]
-
-📊 **Effort:** Low | Medium | High
-
----
-
-### Option B: [Name]
-[Description]
-
-✅ **Pros:**
-- [benefit 1]
-
-❌ **Cons:**
-- [drawback 1]
-- [drawback 2]
-
-📊 **Effort:** Low | Medium | High
-
----
-
-### Option C: [Name]
-[Description]
-
-✅ **Pros:**
-- [benefit 1]
-
-❌ **Cons:**
-- [drawback 1]
-
-📊 **Effort:** Low | Medium | High
-
----
-
-## 💡 Recommendation
-
-**Option [X]** because [reasoning].
-
-What direction would you like to explore?
-```
-
----
-
-## Examples
-
-```
-/brainstorm authentication system
-/brainstorm state management for complex form
-/brainstorm database schema for social app
-/brainstorm caching strategy
-```
-
----
-
-## Key Principles
-
-- **No code** - this is about ideas, not implementation
-- **Visual when helpful** - use diagrams for architecture
-- **Honest tradeoffs** - don't hide complexity
-- **Defer to user** - present options, let them decide

package/.agent/workflows/create.md

@@ -1,59 +0,0 @@
----
-description: Create new application command. Triggers App Builder skill and starts interactive dialogue with user.
----
-
-# /create - Create Application
-
-$ARGUMENTS
-
----
-
-## Task
-
-This command starts a new application creation process.
-
-### Steps:
-
-1. **Request Analysis**
-   - Understand what the user wants
-   - If information is missing, use `conversation-manager` skill to ask
-
-2. **Project Planning**
-   - Use `project-planner` agent for task breakdown
-   - Determine tech stack
-   - Plan file structure
-   - Create plan file and proceed to building
-
-3. **Application Building (After Approval)**
-   - Orchestrate with `app-builder` skill
-   - Coordinate expert agents:
-     - `database-architect` → Schema
-     - `backend-specialist` → API
-     - `frontend-specialist` → UI
-
-4. **Preview**
-   - Start with `auto_preview.py` when complete
-   - Present URL to user
-
----
-
-## Usage Examples
-
-```
-/create blog site
-/create e-commerce app with product listing and cart
-/create todo app
-/create Instagram clone
-/create crm system with customer management
-```
-
----
-
-## Before Starting
-
-If request is unclear, ask these questions:
-- What type of application?
-- What are the basic features?
-- Who will use it?
-
-Use defaults, add details later.