thachvd-kit 1.0.28 → 1.0.30

package/agents/seo-specialist.md

@@ -1,111 +0,0 @@
----
-name: seo-specialist
-description: SEO and GEO (Generative Engine Optimization) expert. Handles SEO audits, Core Web Vitals, E-E-A-T optimization, AI search visibility. Use for SEO improvements, content optimization, or AI citation strategies.
-tools: Read, Grep, Glob, Bash, Write
-model: inherit
-skills: clean-code, seo-fundamentals, geo-fundamentals
----
-
-# SEO Specialist
-
-Expert in SEO and GEO (Generative Engine Optimization) for traditional and AI-powered search engines.
-
-## Core Philosophy
-
-> "Content for humans, structured for machines. Win both Google and ChatGPT."
-
-## Your Mindset
-
-- **User-first**: Content quality over tricks
-- **Dual-target**: SEO + GEO simultaneously
-- **Data-driven**: Measure, test, iterate
-- **Future-proof**: AI search is growing
-
----
-
-## SEO vs GEO
-
-| Aspect | SEO | GEO |
-|--------|-----|-----|
-| Goal | Rank #1 in Google | Be cited in AI responses |
-| Platform | Google, Bing | ChatGPT, Claude, Perplexity |
-| Metrics | Rankings, CTR | Citation rate, appearances |
-| Focus | Keywords, backlinks | Entities, data, credentials |
-
----
-
-## Core Web Vitals Targets
-
-| Metric | Good | Poor |
-|--------|------|------|
-| **LCP** | < 2.5s | > 4.0s |
-| **INP** | < 200ms | > 500ms |
-| **CLS** | < 0.1 | > 0.25 |
-
----
-
-## E-E-A-T Framework
-
-| Principle | How to Demonstrate |
-|-----------|-------------------|
-| **Experience** | First-hand knowledge, real stories |
-| **Expertise** | Credentials, certifications |
-| **Authoritativeness** | Backlinks, mentions, recognition |
-| **Trustworthiness** | HTTPS, transparency, reviews |
-
----
-
-## Technical SEO Checklist
-
-- [ ] XML sitemap submitted
-- [ ] robots.txt configured
-- [ ] Canonical tags correct
-- [ ] HTTPS enabled
-- [ ] Mobile-friendly
-- [ ] Core Web Vitals passing
-- [ ] Schema markup valid
-
-## Content SEO Checklist
-
-- [ ] Title tags optimized (50-60 chars)
-- [ ] Meta descriptions (150-160 chars)
-- [ ] H1-H6 hierarchy correct
-- [ ] Internal linking structure
-- [ ] Image alt texts
-
-## GEO Checklist
-
-- [ ] FAQ sections present
-- [ ] Author credentials visible
-- [ ] Statistics with sources
-- [ ] Clear definitions
-- [ ] Expert quotes attributed
-- [ ] "Last updated" timestamps
-
----
-
-## Content That Gets Cited
-
-| Element | Why AI Cites It |
-|---------|-----------------|
-| Original statistics | Unique data |
-| Expert quotes | Authority |
-| Clear definitions | Extractable |
-| Step-by-step guides | Useful |
-| Comparison tables | Structured |
-
----
-
-## When You Should Be Used
-
-- SEO audits
-- Core Web Vitals optimization
-- E-E-A-T improvement
-- AI search visibility
-- Schema markup implementation
-- Content optimization
-- GEO strategy
-
----
-
-> **Remember:** The best SEO is great content that answers questions clearly and authoritatively.

package/agents/test-engineer.md

@@ -1,158 +0,0 @@
----
-name: test-engineer
-description: Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-skills: clean-code, testing-patterns, tdd-workflow, webapp-testing, code-review-checklist, lint-and-validate
----
-
-# Test Engineer
-
-Expert in test automation, TDD, and comprehensive testing strategies.
-
-## Core Philosophy
-
-> "Find what the developer forgot. Test behavior, not implementation."
-
-## Your Mindset
-
-- **Proactive**: Discover untested paths
-- **Systematic**: Follow testing pyramid
-- **Behavior-focused**: Test what matters to users
-- **Quality-driven**: Coverage is a guide, not a goal
-
----
-
-## Testing Pyramid
-
-```
-        /\          E2E (Few)
-       /  \         Critical user flows
-      /----\
-     /      \       Integration (Some)
-    /--------\      API, DB, services
-   /          \
-  /------------\    Unit (Many)
-                    Functions, logic
-```
-
----
-
-## Framework Selection
-
-| Language | Unit | Integration | E2E |
-|----------|------|-------------|-----|
-| TypeScript | Vitest, Jest | Supertest | Playwright |
-| Python | Pytest | Pytest | Playwright |
-| React | Testing Library | MSW | Playwright |
-
----
-
-## TDD Workflow
-
-```
-🔴 RED    → Write failing test
-🟢 GREEN  → Minimal code to pass
-🔵 REFACTOR → Improve code quality
-```
-
----
-
-## Test Type Selection
-
-| Scenario | Test Type |
-|----------|-----------|
-| Business logic | Unit |
-| API endpoints | Integration |
-| User flows | E2E |
-| Components | Component/Unit |
-
----
-
-## AAA Pattern
-
-| Step | Purpose |
-|------|---------|
-| **Arrange** | Set up test data |
-| **Act** | Execute code |
-| **Assert** | Verify outcome |
-
----
-
-## Coverage Strategy
-
-| Area | Target |
-|------|--------|
-| Critical paths | 100% |
-| Business logic | 80%+ |
-| Utilities | 70%+ |
-| UI layout | As needed |
-
----
-
-## Deep Audit Approach
-
-### Discovery
-
-| Target | Find |
-|--------|------|
-| Routes | Scan app directories |
-| APIs | Grep HTTP methods |
-| Components | Find UI files |
-
-### Systematic Testing
-
-1. Map all endpoints
-2. Verify responses
-3. Cover critical paths
-
----
-
-## Mocking Principles
-
-| Mock | Don't Mock |
-|------|------------|
-| External APIs | Code under test |
-| Database (unit) | Simple deps |
-| Network | Pure functions |
-
----
-
-## Review Checklist
-
-- [ ] Coverage 80%+ on critical paths
-- [ ] AAA pattern followed
-- [ ] Tests are isolated
-- [ ] Descriptive naming
-- [ ] Edge cases covered
-- [ ] External deps mocked
-- [ ] Cleanup after tests
-- [ ] Fast unit tests (<100ms)
-
----
-
-## Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Test implementation | Test behavior |
-| Multiple asserts | One per test |
-| Dependent tests | Independent |
-| Ignore flaky | Fix root cause |
-| Skip cleanup | Always reset |
-
----
-
-## When You Should Be Used
-
-- Writing unit tests
-- TDD implementation
-- E2E test creation
-- Improving coverage
-- Debugging test failures
-- Test infrastructure setup
-- API integration tests
-
----
-
-> **Remember:** Good tests are documentation. They explain what the code should do.

package/kit/PROMPT_RECIPE.md

@@ -1,30 +0,0 @@
-# Prompt Recipes
-
-Use these prompts after `thachvd-kit init` when you want the AI agent to refine project rules.
-
-## Initial Refinement
-
-```text
-Read CLAUDE.md (if using Claude Code), AGENTS.md, and all files under .agent/docs/.
-Scan the current repository.
-Update CLAUDE.md, AGENTS.md, .cursorrules and .agent/docs/project.md, .agent/docs/architecture.md, and .agent/docs/conventions.md with factual project-specific rules.
-Do not implement product code.
-Remove TODO: refine items only when you have real evidence from the codebase.
-```
-
-## Before A Feature
-
-```text
-Read CLAUDE.md (if using Claude Code), AGENTS.md, and .agent/docs/workflow.md.
-Check whether .agent/docs/architecture.md and .agent/docs/conventions.md are accurate for this task.
-If they are stale, update the relevant docs first.
-Then define success criteria, implement the smallest coherent change, and verify.
-```
-
-## After A Task
-
-```text
-Review the files changed in this task.
-If stack, architecture, conventions, commands, or workflow changed, update the relevant .agent/docs/*.md file.
-Summarize verification evidence before claiming done.
-```

package/kit/README.md

@@ -1,30 +0,0 @@
-# thachvd-kit Kit
-
-This kit keeps AI coding behavior consistent across Codex, Antigravity, Claude Code, and Cursor.
-
-## Entry Files
-
-- `AGENTS.md`: shared cross-agent instructions.
-- `CLAUDE.md`: Claude Code entry file that imports `AGENTS.md`.
-- `GEMINI.md`: Antigravity entry file that points to `AGENTS.md`.
-- `.cursorrules`: Cursor entry file that points to `AGENTS.md`.
-
-## Shared Docs
-
-Project-specific knowledge belongs under `.agent/docs/`:
-
-- `project.md`: stack, commands, tools, routing, and scan evidence.
-- `architecture.md`: codebase structure, entry points, and boundaries.
-- `conventions.md`: naming, formatting, testing, API, state, and styling patterns.
-- `workflow.md`: repeatable task flow.
-
-Agents should update these docs when they discover real project facts. Keep root entry files short.
-
-## Local Kit
-
-- `.agent/agents/`: specialist agent guidance.
-- `.agent/skills/`: reusable capability instructions.
-- `.agent/workflows/`: task workflows.
-- `.agent/rules/GEMINI.md`: Antigravity-compatible mirror rules.
-
-Powered by thachvd-kit.

package/prompts/debug.md

@@ -1,11 +0,0 @@
----
-description: Investigate a bug with evidence, root-cause analysis, regression protection, and verification.
-argument-hint: [SYMPTOM]
----
-
-Read and follow `.agent/workflows/debug.md` in the current repository.
-
-Bug or symptom:
-$ARGUMENTS
-
-Use `$systematic-debugging`, the `debugger` agent, and `testing-patterns` when available. Reproduce and isolate the root cause before editing.

package/prompts/release.md

@@ -1,11 +0,0 @@
----
-description: Run the npm release workflow with verification, versioning, tagging, publishing, and registry checks.
-argument-hint: [RELEASE_REQUEST]
----
-
-Read and follow `.agent/workflows/release.md` in the current repository.
-
-Release request:
-$ARGUMENTS
-
-Do not publish until the release gate and `npm run release:verify` pass.

package/prompts/simple.md

@@ -1,11 +0,0 @@
----
-description: Run the fast path for one-file, unambiguous fixes with verification.
-argument-hint: [TASK]
----
-
-Read and follow `.agent/workflows/simple.md` in the current repository.
-
-Request:
-$ARGUMENTS
-
-Use the fast path only when its criteria are met. State `FAST_PATH: simple-fix`, `REASON`, and `SCOPE` before editing. Never skip verification.

package/prompts/spec.md

@@ -1,11 +0,0 @@
----
-description: Define requirements and acceptance criteria before planning or implementation.
-argument-hint: [REQUEST]
----
-
-Read and follow `.agent/workflows/spec.md` in the current repository.
-
-Request:
-$ARGUMENTS
-
-Do not write product code. Stop at the spec gate and wait for human confirmation.

package/prompts/task.md

@@ -1,12 +0,0 @@
----
-description: Route the current request to the smallest safe workflow before editing.
-argument-hint: [TASK]
----
-
-Read and follow `.agent/workflows/task.md` in the current repository.
-
-Route this request before editing:
-
-$ARGUMENTS
-
-Return the required ROUTE, WORKFLOW, SKILLS, AGENTS, GATE, and NEXT fields. Do not edit code while routing.

package/rules/GEMINI.md

@@ -1,45 +0,0 @@
----
-trigger: always_on
----
-
-# GEMINI.md
-
-Antigravity-compatible entry rules for thachvd-kit projects.
-
-## Startup
-
-1. Read `AGENTS.md` at the project root.
-2. Read `.agent/docs/project.md` for stack, commands, and routing.
-3. Read `.agent/docs/workflow.md` before editing.
-4. Read `.agent/docs/architecture.md` and `.agent/docs/conventions.md` before planning non-trivial code changes.
-5. If any `.agent/docs/*.md` file contains `TODO: refine`, update that doc from the real code before product code changes.
-
-## Routing
-
-- Frontend/UI: `.agent/agents/frontend-specialist.md`
-- Backend/API: `.agent/agents/backend-specialist.md`
-- Database/schema: `.agent/agents/database-architect.md`
-- Mobile/desktop: `.agent/agents/mobile-developer.md`
-- DevOps/CI/deploy: `.agent/agents/devops-engineer.md`
-- Debug/RCA: `.agent/agents/debugger.md`
-- Security: `.agent/agents/security-auditor.md`
-- Multi-domain: `.agent/agents/orchestrator.md`
-
-Load only the agent, skill, or workflow files relevant to the current task.
-
-## Execution
-
-- Questions and analysis: answer directly; do not edit code.
-- Simple fix: inspect dependencies, make the smallest change, verify.
-- Feature or refactor: state assumptions, define success criteria, plan, implement, verify.
-- UI work: use relevant frontend design skills before editing.
-- Security or deploy work: run the matching checklist before claiming done.
-
-## Standards
-
-- Respond in the user's language.
-- Keep code, identifiers, and code comments in English.
-- Prefer existing project patterns over new abstractions.
-- Keep changes surgical.
-- Tests or equivalent verification are mandatory.
-- Update `.agent/docs/*` when stack, architecture, workflow, or conventions change.

package/scripts/auto_preview.py

@@ -1,148 +0,0 @@
-#!/usr/bin/env python3
-"""
-Auto Preview - Antigravity Kit
-==============================
-Manages (start/stop/status) the local development server for previewing the application.
-
-Usage:
-    python .agent/scripts/auto_preview.py start [port]
-    python .agent/scripts/auto_preview.py stop
-    python .agent/scripts/auto_preview.py status
-"""
-
-import os
-import sys
-import time
-import json
-import signal
-import argparse
-import subprocess
-from pathlib import Path
-
-AGENT_DIR = Path(".agent")
-PID_FILE = AGENT_DIR / "preview.pid"
-LOG_FILE = AGENT_DIR / "preview.log"
-
-def get_project_root():
-    return Path(".").resolve()
-
-def is_running(pid):
-    try:
-        os.kill(pid, 0)
-        return True
-    except OSError:
-        return False
-
-def get_start_command(root):
-    pkg_file = root / "package.json"
-    if not pkg_file.exists():
-        return None
-    
-    with open(pkg_file, 'r') as f:
-        data = json.load(f)
-    
-    scripts = data.get("scripts", {})
-    if "dev" in scripts:
-        return ["npm", "run", "dev"]
-    elif "start" in scripts:
-        return ["npm", "start"]
-    return None
-
-def start_server(port=3000):
-    if PID_FILE.exists():
-        try:
-            pid = int(PID_FILE.read_text().strip())
-            if is_running(pid):
-                print(f"⚠️  Preview already running (PID: {pid})")
-                return
-        except:
-            pass # Invalid PID file
-
-    root = get_project_root()
-    cmd = get_start_command(root)
-    
-    if not cmd:
-        print("❌ No 'dev' or 'start' script found in package.json")
-        sys.exit(1)
-    
-    # Add port env var if needed (simple heuristic)
-    env = os.environ.copy()
-    env["PORT"] = str(port)
-    
-    print(f"🚀 Starting preview on port {port}...")
-    
-    with open(LOG_FILE, "w") as log:
-        process = subprocess.Popen(
-            cmd,
-            cwd=str(root),
-            stdout=log,
-            stderr=log,
-            env=env,
-            shell=True # Required for npm on windows often, or consistent path handling
-        )
-    
-    PID_FILE.write_text(str(process.pid))
-    print(f"✅ Preview started! (PID: {process.pid})")
-    print(f"   Logs: {LOG_FILE}")
-    print(f"   URL: http://localhost:{port}")
-
-def stop_server():
-    if not PID_FILE.exists():
-        print("ℹ️  No preview server found.")
-        return
-
-    try:
-        pid = int(PID_FILE.read_text().strip())
-        if is_running(pid):
-            # Try gentle kill first
-            os.kill(pid, signal.SIGTERM) if sys.platform != 'win32' else subprocess.call(['taskkill', '/F', '/T', '/PID', str(pid)])
-            print(f"🛑 Preview stopped (PID: {pid})")
-        else:
-            print("ℹ️  Process was not running.")
-    except Exception as e:
-        print(f"❌ Error stopping server: {e}")
-    finally:
-        if PID_FILE.exists():
-            PID_FILE.unlink()
-
-def status_server():
-    running = False
-    pid = None
-    url = "Unknown"
-    
-    if PID_FILE.exists():
-        try:
-            pid = int(PID_FILE.read_text().strip())
-            if is_running(pid):
-                running = True
-                # Heuristic for URL, strictly we should save it
-                url = "http://localhost:3000" 
-        except:
-            pass
-            
-    print("\n=== Preview Status ===")
-    if running:
-        print(f"✅ Status: Running")
-        print(f"🔢 PID: {pid}")
-        print(f"🌐 URL: {url} (Likely)")
-        print(f"📝 Logs: {LOG_FILE}")
-    else:
-        print("⚪ Status: Stopped")
-    print("===================\n")
-
-def main():
-    parser = argparse.ArgumentParser()
-    parser.add_argument("action", choices=["start", "stop", "status"])
-    parser.add_argument("port", nargs="?", default="3000")
-    
-    args = parser.parse_args()
-    
-    if args.action == "start":
-        start_server(int(args.port))
-    elif args.action == "stop":
-        stop_server()
-    elif args.action == "status":
-        status_server()
-
-if __name__ == "__main__":
-    main()