thachvd-kit 1.0.29 → 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/commands/forge-debug.md

@@ -1,12 +0,0 @@
----
-description: Investigate and fix a bug with evidence-first root-cause analysis.
-argument-hint: [SYMPTOM]
----
-
-# Forge Debug
-
-Symptom:
-
-$ARGUMENTS
-
-Read `.agent/workflows/debug.md`, use `$systematic-debugging`, the `debugger` agent, and `testing-patterns` when available. Reproduce the symptom, inspect the relevant code path with codegraph/MCP, form and test hypotheses, identify the root cause, add regression protection when practical, make the smallest fix, and verify it. Do not patch by guesswork and do not stop by asking the member to invoke another command.

package/commands/forge-fast.md

@@ -1,22 +0,0 @@
----
-description: Execute a trivial, unambiguous change with focused verification.
-argument-hint: [REQUEST]
----
-
-# Forge Fast Path
-
-Request:
-
-$ARGUMENTS
-
-Use this path only for one obvious file or tiny local change with no behavior, API, schema, security, CI, dependency, workflow, or release contract change.
-
-Before editing, state exactly:
-
-```text
-FAST_PATH: simple-fix
-REASON: [why Spec, Plan, and feature Review are not needed]
-SCOPE: [file or narrow area]
-```
-
-Inspect the target, make the smallest change, run focused verification, and report evidence. If the scope expands, stop and internally re-route through the appropriate Forge workflow. Never skip inspection or verification.

package/commands/forge-release.md

@@ -1,12 +0,0 @@
----
-description: Verify, version, publish, and verify the thachvd-kit npm release.
-argument-hint: [RELEASE_REQUEST]
----
-
-# Forge Release
-
-Release request:
-
-$ARGUMENTS
-
-Read `.agent/workflows/release.md` and run the release gate. Confirm the working tree, review status, version, npm authentication, verification output, and package contents before publishing. Never use the fast path. Do not run `npm publish` until the release gate is satisfied and the human has confirmed the final version and publish action. After publishing, verify the registry version and the installed package output.

package/commands/forge-research.md

@@ -1,24 +0,0 @@
----
-description: Research the codebase, technical topic, or domain without editing product code.
-argument-hint: [QUESTION]
----
-
-# Forge Research
-
-Research question:
-
-$ARGUMENTS
-
-Do not edit product code. First classify the research as codebase, external technical, or domain research. For codebase research, use codegraph/MCP first. For external research, use authoritative current sources only when needed and cite them. Return exactly:
-
-```text
-RESEARCH_STATUS: complete | blocked
-QUESTION: [what was investigated]
-ASSUMPTIONS: [explicit assumptions]
-FINDINGS: [evidence-based findings]
-SOURCES: [file paths, symbols, MCP evidence, or URLs]
-RISKS: [known risks and unknowns]
-OPTIONS: [possible approaches and tradeoffs]
-RECOMMENDATION: [recommended direction]
-OPEN_QUESTIONS: [unresolved questions]
-```

package/commands/forge-review.md

@@ -1,12 +0,0 @@
----
-description: Review a change across correctness, simplicity, architecture, security, and performance.
-argument-hint: [SCOPE]
----
-
-# Forge Review
-
-Review scope:
-
-$ARGUMENTS
-
-Read `.agent/workflows/review.md` and inspect the relevant diff, task, and verification evidence. Review all five axes. Report findings first, ordered by severity, using `BLOCKING`, `SUGGESTION`, `NIT`, or `QUESTION`. Do not edit code during review unless the member explicitly asks for fixes after the findings.

package/commands/forge-task.md

@@ -1,37 +0,0 @@
----
-description: Route a request and continue the selected Forge workflow in this turn.
-argument-hint: [REQUEST]
----
-
-# Forge Task Orchestrator
-
-The request supplied with this command is:
-
-$ARGUMENTS
-
-Read `AGENTS.md`, `.agent/docs/project.md`, and `.agent/docs/workflow.md` before editing.
-
-Classify the request internally as `question`, `fast`, `feature`, `bug`, `research`, `review`, `release`, or `multi-domain`. Then continue the selected workflow in this same turn. Do not stop after printing a `NEXT` command and do not ask the member to invoke another Forge command for ordinary routing.
-
-Use this compact status header when useful:
-
-```text
-REQUEST: [original request]
-ROUTE: [route]
-WORKFLOW: [exact workflow file]
-SKILLS: [matching skills]
-AGENTS: [matching agents]
-GATE: fast-path | standard | human-approval
-ACTION: [what you are doing now]
-```
-
-Rules:
-
-- Questions and analysis: answer directly with no edits.
-- Trivial one-file changes: apply the `forge-fast` protocol, including focused verification.
-- Bugs or unknown failures: reproduce, isolate root cause, add regression protection, fix, and verify.
-- Research: use codegraph/MCP first for repository questions, use authoritative external sources when needed, and do not edit code.
-- Features and refactors: follow spec -> plan -> approval -> implement -> test -> review. Stop only at the documented human approval gate.
-- Reviews: run the five-axis review and report findings first.
-- Releases: follow `.agent/workflows/release.md`; never use the fast path.
-- If the request is empty or unsafe to classify, ask one concise clarification question.

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.