thachvd-kit 1.0.15 → 1.0.17

package/.agent/agents/frontend-specialist.md

@@ -3,7 +3,7 @@ name: frontend-specialist
 description: Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: clean-code, react-frontend, nextjs-react-expert, web-design-guidelines, tailwind-patterns, frontend-design, lint-and-validate
+skills: clean-code, react-frontend, nextjs-react-expert, web-design-guidelines, tailwind-patterns, frontend-design, lint-and-validate
 ---
 
 # Senior Frontend Architect
@@ -575,7 +575,7 @@ After editing any file:
 
 ---
 
-> **Note:** This agent loads relevant skills (`react-frontend`, `nextjs-react-expert`, etc.) for detailed guidance. Apply behavioral principles from those skills rather than copying patterns.
+> **Note:** This agent loads relevant skills (`react-frontend`, `nextjs-react-expert`, etc.) for detailed guidance. Apply behavioral principles from those skills rather than copying patterns.
 
 ---
 

package/.agent/agents/mobile-developer.md

@@ -1,14 +1,14 @@
 ---
-name: mobile-developer
-description: Expert in React Native, Flutter, and Tauri-style app development. Use for cross-platform mobile or desktop apps, native features, and platform-specific UI patterns. Triggers on mobile, desktop, tauri, react native, flutter, ios, android, app store, expo.
+name: mobile-developer
+description: Expert in React Native, Flutter, and Tauri-style app development. Use for cross-platform mobile or desktop apps, native features, and platform-specific UI patterns. Triggers on mobile, desktop, tauri, react native, flutter, ios, android, app store, expo.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: clean-code, mobile-design, desktop-design
+skills: clean-code, mobile-design, desktop-design
 ---
 
 # Mobile Developer
 
-Expert app developer specializing in React Native, Flutter, and Tauri-style cross-platform development.
+Expert app developer specializing in React Native, Flutter, and Tauri-style cross-platform development.
 
 ## Your Philosophy
 

package/.agent/docs/architecture.md

@@ -0,0 +1,22 @@
+# Architecture Notes
+
+## Current Map
+
+- `bin/cli.js`: Main Node.js CLI. Handles scan detection, prompts, file generation, and `.agent/` copy.
+- `.agent/`: Installed kit content copied into target projects.
+- `agents/`, `skills/`, `workflows/`, `rules/`: Source mirrors for kit content.
+- `kit/`: Human-facing kit docs and prompt recipes.
+- `scripts/`: Helper scripts used by generated workflows.
+
+## Output Model
+
+`thachvd-kit init` creates thin root entry files and puts project-specific knowledge in `.agent/docs/`:
+
+- `AGENTS.md`: shared instructions for Codex, Antigravity, and Claude Code.
+- `CLAUDE.md`: imports `AGENTS.md` for Claude Code.
+- `GEMINI.md`: Antigravity entry that points to `AGENTS.md`.
+- `.agent/docs/*.md`: stack, architecture, conventions, and workflow.
+
+## Maintenance Rule
+
+Keep root entry files short. Add project-specific details to `.agent/docs/*` and reusable behavior to `.agent/skills/*` or `.agent/workflows/*`.

package/.agent/docs/conventions.md

@@ -0,0 +1,21 @@
+# Coding Conventions
+
+## JavaScript CLI
+
+- Keep CLI behavior in `bin/cli.js` unless a helper becomes clearly reusable.
+- Prefer simple filesystem APIs from Node.js standard library.
+- Keep generated Markdown ASCII-only unless the target file already requires non-ASCII.
+- Avoid adding dependencies for small formatting or path operations.
+
+## Docs And Rules
+
+- Root `AGENTS.md`, `CLAUDE.md`, and `GEMINI.md` should stay concise.
+- Put scan-specific or project-specific detail in `.agent/docs/`.
+- Keep `.agent/rules/GEMINI.md` and `rules/GEMINI.md` aligned.
+- Keep mirrored source folders and `.agent/` content aligned when changing kit assets.
+
+## Verification
+
+- Syntax-check `bin/cli.js` after edits.
+- Run `npm test`.
+- Run `npm pack --dry-run` for package output changes.

package/.agent/docs/project.md

@@ -0,0 +1,40 @@
+# Project Rules
+
+Generated by thachvd-kit.
+
+## Summary
+
+- Name: thachvd-kit
+- Description: Project rules bootstrap kit for Codex, Antigravity, and Claude Code.
+- Type: CLI package
+- App root: `.`
+
+## Stack
+
+- Language: JavaScript
+- Runtime: Node.js
+- Package manager: npm
+- CLI entry: `bin/cli.js`
+- Published package files: `.agent`, `agents`, `bin`, `kit`, `rules`, `scripts`, `skills`, `workflows`, `README.md`, `LICENSE`
+
+## Commands
+
+- Install: `npm install`
+- Test: `npm test`
+- Package dry run: `npm pack --dry-run`
+- Publish: `npm publish`
+
+## Agent Routing
+
+| Task Type | Agent | Primary Skills |
+|-----------|-------|----------------|
+| CLI behavior | `backend-specialist` | `nodejs-best-practices`, `clean-code` |
+| Docs/rules | `documentation-writer` | `documentation-templates` |
+| Workflow design | `project-planner` | `plan-writing`, `executing-plans` |
+| Security/release | `security-auditor` / `devops-engineer` | `vulnerability-scanner`, `deployment-procedures` |
+
+## Verification
+
+- Run `node --check bin/cli.js` after CLI edits.
+- Run `npm test` before claiming code changes are complete.
+- Run `npm pack --dry-run` before release-oriented changes.

package/.agent/docs/workflow.md

@@ -0,0 +1,24 @@
+# Agent Workflow
+
+## Before Every Task
+
+1. Read `AGENTS.md`.
+2. Read `.agent/docs/project.md`.
+3. Classify the request.
+4. Load only the relevant agent, skill, or workflow docs.
+
+## Implementation Flow
+
+1. State assumptions and success criteria when the task is not trivial.
+2. Inspect dependent files before editing.
+3. Make the smallest coherent change.
+4. Add or update focused tests when behavior changes.
+5. Run verification.
+6. Summarize changed files and verification evidence.
+
+## Release Flow
+
+1. Update package metadata when changing publish behavior.
+2. Run `npm test`.
+3. Run `npm pack --dry-run`.
+4. Review tarball contents before publish.

package/.agent/rules/GEMINI.md

@@ -2,206 +2,44 @@
 trigger: always_on
 ---
 
-# GEMINI.md — Universal Agent Kit
+# GEMINI.md
 
-> Cross-platform agent protocol. Works with: Antigravity · Claude Code · Codex · OpenCode
+Antigravity-compatible entry rules for thachvd-kit projects.
 
----
-
-## MANDATORY FIRST ACTION
-
-**At session start — before anything else:**
-
-```
-1. Read AGENTS.md (at project root) → load stack, agents, constraints
-2. If missing → ask user to run: thachvd-kit init --scan
-3. Confirm: "Context loaded: [Project Name] | Stack: [Stack] | Ready."
-```
-
-> All routing decisions below depend on AGENTS.md.
-> Without it, ask user to run: `thachvd-kit init --scan`
-
----
-
-## STEP 1 — CLASSIFY REQUEST
-
-| Type | Triggers | Action |
-|------|----------|--------|
-| **QUESTION** | "what", "how", "explain", "why" | Direct answer |
-| **SURVEY** | "analyze", "list", "overview", "check" | Analysis only, no code |
-| **SIMPLE FIX** | "fix", "add", "change" (single file) | Inline edit |
-| **BUILD** | "build", "create", "implement", "refactor" | Agent + `{task-slug}.md` |
-| **DESIGN/UI** | "design", "UI", "page", "dashboard" | Agent + `{task-slug}.md` |
-
----
-
-## STEP 2 — AUTO-SELECT AGENT
-
-**Protocol:**
-1. Read `## Project Overview` from AGENTS.md → detect language and frameworks
-2. Match to agent table below
-3. Announce before responding:
-
-```
-🤖 Applying knowledge of `@[agent-name]`...
-```
-
-### Agent Routing Table
-
-| Domain | Agent | Skills to Load |
-|--------|-------|---------------|
-| Web frontend (any framework) | `frontend-specialist` | `frontend-design` + framework skill from AGENTS.md |
-| Backend API (any language) | `backend-specialist` | language skill + `api-design` |
-| Database / Schema | `database-architect` | `database-design` |
-| Mobile / Desktop (Tauri, RN, Flutter) | `mobile-developer` | platform skill from AGENTS.md |
-| DevOps / Cloud / CI | `devops-engineer` | `docker-patterns`, `deployment-procedures` |
-| Security audit | `security-auditor` | `vulnerability-scanner` |
-| Debug / RCA | `debugger` | `systematic-debugging` |
-| Planning / Discovery | `project-planner` | `brainstorming`, `plan-writing` |
-| Multi-domain | `orchestrator` | `dispatching-parallel-agents` |
-
-**Framework-specific skill mapping** (reference AGENTS.md stack):
-
-| Framework/Language | Load Skill |
-|-------------------|-----------|
-| Vue | `frontend-design` (+ Vue-specific if available) |
-| React | `react-frontend` |
-| Next.js | `nextjs-react-expert` |
-| Laravel | `laravel-patterns` + `laravel-security` |
-| Node.js | `nodejs-best-practices` |
-| Python | `python-patterns` |
-| Go | `golang-patterns` |
-| Rust | `rust-pro` |
-| Tauri | `desktop-design` + `rust-pro` |
-| Docker | `docker-patterns` |
-
-> If stack not in mapping → use agent's general skill set + `clean-code`.
-
-**MANDATORY checklist before any code:**
-- [ ] Agent identified from AGENTS.md stack?
-- [ ] Agent `.md` file read/recalled?
-- [ ] Announcement `🤖 Applying knowledge of @[agent]...` written?
-
-> 🔴 Code without announcement = **PROTOCOL VIOLATION**
-
----
-
-## STEP 3 — SOCRATIC GATE
-
-**Trigger: BUILD or DESIGN/UI requests only**
-
-| Scenario | Action |
-|----------|--------|
-| New feature / greenfield | Ask **3 questions**: Purpose · Users · Must-have vs Nice-to-have |
-| Code edit / bug fix | Confirm scope + 1 impact question |
-| Vague request | Ask Purpose + Constraints |
-| User gave full spec | **Proceed immediately** |
-| User says "proceed" / "just do it" | **DO IT — no more questions** |
-
-**Rules:**
-- Max 3 questions at once
-- Never ask edge case questions after user already answered
-- Reference `@[skills/brainstorming]` for question format
+## Startup
 
----
-
-## UNIVERSAL RULES (Always Active)
-
-### Language
-- Respond in user's language (auto-detect from prompt)
-- Code comments/variables always in English
-
-### Code Quality
-- `@[skills/clean-code]` applies to ALL code, ALL languages
-- Tests mandatory: Unit > Integration > E2E
-- `@[skills/verification-before-completion]` before claiming "done"
-
-### File Changes
-- Identify dependent files before modifying
-- Update ALL affected files together
-
----
+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.
 
-## EXECUTION WORKFLOW
+## Routing
 
-**BUILD tasks — 7-step flow:**
+- 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`
 
-```
-1. brainstorming           → Clarify (Socratic Gate)
-2. plan-writing            → Create {task-slug}.md
-3. using-git-worktrees     → Isolated workspace
-4. subagent-driven-development → Implement + 2-stage review
-5. requesting-code-review  → After each major task
-6. verification-before-completion → Before claiming done
-7. finishing-a-development-branch → Merge / PR / keep
-```
-
-**SIMPLE FIX:** Skip to step 4, no worktree needed.
-
----
-
-## MODE BEHAVIOR
-
-| Mode | Behavior |
-|------|----------|
-| **plan** | Analysis → Planning → Architecture → NO CODE until confirmed |
-| **ask** | Questions and analysis only |
-| **edit** | Execute. Multi-file → create `{task-slug}.md`. Single-file → proceed. |
-
----
+Load only the agent, skill, or workflow files relevant to the current task.
 
-## FINAL CHECK
-
-**Trigger:** "final check", "deploy check", "kiểm tra cuối", "done?"
-
-```bash
-python scripts/checklist.py .
-```
-
-Priority: Security → Lint → Tests → UX → SEO
-
----
-
-## PATHS
-
-```
-agents/     → agents/{agent}.md
-skills/     → skills/{skill}/SKILL.md
-workflows/  → workflows/{command}.md
-scripts/    → scripts/init.py, checklist.py, verify_all.py
-```
-
----
-
-## QUICK SKILL REFERENCE
-
-| Need | Skill |
-|------|-------|
-| Clean code (any lang) | `clean-code` |
-| Plan a task | `plan-writing` → `executing-plans` |
-| Parallel agents | `dispatching-parallel-agents` |
-| Code review | `requesting-code-review` / `receiving-code-review` |
-| Git isolation | `using-git-worktrees` |
-| Agent-based dev | `subagent-driven-development` |
-| Verify done | `verification-before-completion` |
-| Finish branch | `finishing-a-development-branch` |
-| Write new skill | `writing-skills` |
-| API design | `api-design` |
-| Docker | `docker-patterns` |
-| Laravel | `laravel-patterns`, `laravel-security`, `laravel-tdd` |
-| Go | `golang-patterns`, `golang-testing` |
-| Debugging | `systematic-debugging` |
-| Security | `vulnerability-scanner` |
-
----
+## Execution
 
-## CROSS-PLATFORM NOTES
+- 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.
 
-| Platform | Rules File | Skills Dir | Workflows |
-|----------|-----------|-----------|-----------| 
-| **Antigravity** | `rules/GEMINI.md` (this file) | `skills/` | `workflows/` |
-| **Claude Code** | `CLAUDE.md` at project root | `.agent/skills/` | `.agent/workflows/` |
-| **Codex / OpenCode** | `AGENTS.md` at project root | `.agent/skills/` | `.agent/workflows/` |
-| **Cursor** | `.cursorrules` or `.agent/rules/GEMINI.md` | `.agent/skills/` | `.agent/workflows/` |
+## Standards
 
-> Run `thachvd-kit init --scan` to generate AGENTS.md and copy the `.agent/` folder automatically.
+- 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/.agent/skills/desktop-design/SKILL.md

@@ -1,25 +1,25 @@
----
-name: desktop-design
-description: Desktop and cross-platform app design guidance for Tauri and similar desktop shells. Use when building desktop-first interfaces, windowed workflows, keyboard-heavy UX, or cross-platform desktop UI behavior.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# Desktop Design
-
-This skill covers desktop-first product thinking where `mobile-design` is the wrong default.
-
-Use it for Tauri and other desktop-oriented apps with window management, keyboard shortcuts, dense layouts, or multi-panel workflows.
-
-## Guidance
-
-- Design for pointer + keyboard, not touch-first.
-- Use information density deliberately; desktop screens can support richer sidebars and multi-column layouts.
-- Respect platform conventions for menus, shortcuts, dialogs, file pickers, and drag/drop.
-- Assume resizing, multiple windows, and long-running sessions are normal.
-- Pair with `rust-pro` for Tauri backend/native concerns and `frontend-design` for UI execution.
-
-## Related Skills
-
-- `mobile-design` for touch-first mobile products
-- `frontend-design` for visual and interaction design
-- `rust-pro` for Rust and Tauri implementation details
+---
+name: desktop-design
+description: Desktop and cross-platform app design guidance for Tauri and similar desktop shells. Use when building desktop-first interfaces, windowed workflows, keyboard-heavy UX, or cross-platform desktop UI behavior.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+---
+
+# Desktop Design
+
+This skill covers desktop-first product thinking where `mobile-design` is the wrong default.
+
+Use it for Tauri and other desktop-oriented apps with window management, keyboard shortcuts, dense layouts, or multi-panel workflows.
+
+## Guidance
+
+- Design for pointer + keyboard, not touch-first.
+- Use information density deliberately; desktop screens can support richer sidebars and multi-column layouts.
+- Respect platform conventions for menus, shortcuts, dialogs, file pickers, and drag/drop.
+- Assume resizing, multiple windows, and long-running sessions are normal.
+- Pair with `rust-pro` for Tauri backend/native concerns and `frontend-design` for UI execution.
+
+## Related Skills
+
+- `mobile-design` for touch-first mobile products
+- `frontend-design` for visual and interaction design
+- `rust-pro` for Rust and Tauri implementation details

package/.agent/skills/project-onboarding/SKILL.md

@@ -1,62 +1,42 @@
----
-name: project-onboarding
-description: Skill for project reconnaissance and Ground Truth establishment. Automatically scans project structure, tech stack, and logic to create or update PROJECT_CONTEXT.md.
-allowed-tools: list_dir, grep_search, find_by_name, view_file, write_to_file
----
-
-# Project Onboarding Skill
-
-> Establish a Ground Truth map for any project before writing code.
-
----
-
-## 🎯 Objectives
-- **Reconnaissance:** Understand the directory structure, technology stack, and core business logic.
-- **Ground Truth:** Create `PROJECT_CONTEXT.md` to serve as the project's primary reference.
-- **Continuity:** Ensure all future sessions have a map to follow.
-
----
-
-## 📑 Process
-
-1. **Scan Filesystem:**
-   - Run `list_dir` on root.
-   - Run `find_by_name` for configuration files (`package.json`, `tsconfig.json`, `tailwind.config.js`, etc.).
-2. **Identify Tech Stack:**
-   - Detect frameworks (React, Next.js, Vite, etc.).
-   - Detect database/storage (SQL, NoSQL, client-side DB).
-   - Detect styling and UI libraries.
-3. **Analyze Structure:**
-   - Identify where pages, components, logic, and state management live.
-4. **Identify Core Logic:**
-   - `grep` for main keywords (e.g., patient, pharmacy, etc.) to find business rules.
-5. **Create/Update Map:**
-   - Generate `PROJECT_CONTEXT.md` in root using the `PROJECT_CONTEXT.template.md` as a guide.
-
----
-
-## ✅ Onboarding Checklist
-
-Before completing onboarding:
-
-- [ ] **Scanned root directory?**
-- [ ] **Identified Frontend/Backend stack?**
-- [ ] **Mapped primary folder structure?**
-- [ ] **Found core business logic entry points?**
-- [ ] **Created/Updated PROJECT_CONTEXT.md?**
-- [ ] **Stated: "Ground Truth identified/established. Ready to proceed."?**
-
----
-
-## ❌ Anti-Patterns
-
-**DON'T:**
-- Skip onboarding for "simple" fixes.
-- Assume structure based on generic templates.
-- Start writing code before `PROJECT_CONTEXT.md` exists.
-- Leave the context file empty or vague.
-
-**DO:**
-- Perform deep directory analysis.
-- Read core configuration files.
-- Document any project-specific constraints found in existing code.
+---
+name: project-onboarding
+description: Scan the repository and refine `.agent/docs/*` so all supported AI tools share accurate project rules.
+---
+
+# Project Onboarding
+
+Use this skill when a project has just run `thachvd-kit init`, when `.agent/docs/*` contains `TODO: refine`, or when the stack/architecture has changed.
+
+## Goal
+
+Create or update the shared project docs used by Codex, Antigravity, and Claude Code:
+
+- `.agent/docs/project.md`
+- `.agent/docs/architecture.md`
+- `.agent/docs/conventions.md`
+- `.agent/docs/workflow.md`
+
+Do not create a legacy root context file.
+
+## Process
+
+1. Read `AGENTS.md`.
+2. Inspect repository structure, package/build config, test config, entry points, and representative source files.
+3. Update `.agent/docs/project.md` with stack, app root, commands, test/lint tooling, and routing.
+4. Update `.agent/docs/architecture.md` with major directories, entry points, boundaries, and important decisions.
+5. Update `.agent/docs/conventions.md` with real naming, formatting, API, state, styling, and testing patterns.
+6. Update `.agent/docs/workflow.md` only when the repository needs project-specific workflow steps.
+
+## Rules
+
+- Keep docs concise and factual.
+- Mark unknowns as `TODO: refine` only when the codebase does not provide evidence.
+- Do not implement product code during onboarding.
+- Do not overwrite unrelated user-maintained notes.
+
+## Completion Checklist
+
+- [ ] `.agent/docs/project.md` reflects actual stack and commands.
+- [ ] `.agent/docs/architecture.md` maps the current codebase.
+- [ ] `.agent/docs/conventions.md` captures observed patterns.
+- [ ] `.agent/docs/workflow.md` has the task flow agents should follow.

package/.agent/skills/react-frontend/SKILL.md

@@ -1,25 +1,25 @@
----
-name: react-frontend
-description: React-focused frontend guidance for component architecture, state flow, rendering boundaries, and maintainable UI systems. Use for plain React apps that are not specifically Next.js-first.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# React Frontend
-
-This skill is the React-first counterpart to `nextjs-react-expert`.
-
-Use it when the project uses React without needing Next.js-specific assumptions such as SSR, App Router, or server components.
-
-## Guidance
-
-- Prefer the existing project architecture over introducing a new pattern.
-- Keep state ownership shallow and explicit.
-- Separate presentational UI from data-fetching and side effects when it improves maintainability.
-- Optimize rendering only after confirming an actual bottleneck.
-- Pair with `frontend-design` for UI/UX decisions.
-
-## Related Skills
-
-- `nextjs-react-expert` for Next.js-specific performance and routing concerns
-- `frontend-design` for layout, visual hierarchy, and responsive design
-- `clean-code` for naming, file boundaries, and readability
+---
+name: react-frontend
+description: React-focused frontend guidance for component architecture, state flow, rendering boundaries, and maintainable UI systems. Use for plain React apps that are not specifically Next.js-first.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+---
+
+# React Frontend
+
+This skill is the React-first counterpart to `nextjs-react-expert`.
+
+Use it when the project uses React without needing Next.js-specific assumptions such as SSR, App Router, or server components.
+
+## Guidance
+
+- Prefer the existing project architecture over introducing a new pattern.
+- Keep state ownership shallow and explicit.
+- Separate presentational UI from data-fetching and side effects when it improves maintainability.
+- Optimize rendering only after confirming an actual bottleneck.
+- Pair with `frontend-design` for UI/UX decisions.
+
+## Related Skills
+
+- `nextjs-react-expert` for Next.js-specific performance and routing concerns
+- `frontend-design` for layout, visual hierarchy, and responsive design
+- `clean-code` for naming, file boundaries, and readability

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 thachvd
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-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.
+MIT License
+
+Copyright (c) 2026 thachvd
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+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.