thachvd-kit 1.0.17 → 1.0.19

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.
@@ -1,30 +1,30 @@
1
- # Prompt Recipes
2
-
3
- Use these prompts after `thachvd-kit init` when you want the AI agent to refine project rules.
4
-
5
- ## Initial Refinement
6
-
7
- ```text
8
- Read AGENTS.md and all files under .agent/docs/.
9
- Scan the current repository.
10
- Update .agent/docs/project.md, .agent/docs/architecture.md, and .agent/docs/conventions.md with factual project-specific rules.
11
- Do not implement product code.
12
- Remove TODO: refine items only when you have real evidence from the codebase.
13
- ```
14
-
15
- ## Before A Feature
16
-
17
- ```text
18
- Read AGENTS.md and .agent/docs/workflow.md.
19
- Check whether .agent/docs/architecture.md and .agent/docs/conventions.md are accurate for this task.
20
- If they are stale, update the relevant docs first.
21
- Then define success criteria, implement the smallest coherent change, and verify.
22
- ```
23
-
24
- ## After A Task
25
-
26
- ```text
27
- Review the files changed in this task.
28
- If stack, architecture, conventions, commands, or workflow changed, update the relevant .agent/docs/*.md file.
29
- Summarize verification evidence before claiming done.
30
- ```
1
+ # Prompt Recipes
2
+
3
+ Use these prompts after `thachvd-kit init` when you want the AI agent to refine project rules.
4
+
5
+ ## Initial Refinement
6
+
7
+ ```text
8
+ Read AGENTS.md and all files under .agent/docs/.
9
+ Scan the current repository.
10
+ Update .agent/docs/project.md, .agent/docs/architecture.md, and .agent/docs/conventions.md with factual project-specific rules.
11
+ Do not implement product code.
12
+ Remove TODO: refine items only when you have real evidence from the codebase.
13
+ ```
14
+
15
+ ## Before A Feature
16
+
17
+ ```text
18
+ Read AGENTS.md and .agent/docs/workflow.md.
19
+ Check whether .agent/docs/architecture.md and .agent/docs/conventions.md are accurate for this task.
20
+ If they are stale, update the relevant docs first.
21
+ Then define success criteria, implement the smallest coherent change, and verify.
22
+ ```
23
+
24
+ ## After A Task
25
+
26
+ ```text
27
+ Review the files changed in this task.
28
+ If stack, architecture, conventions, commands, or workflow changed, update the relevant .agent/docs/*.md file.
29
+ Summarize verification evidence before claiming done.
30
+ ```
package/kit/README.md CHANGED
@@ -1,29 +1,29 @@
1
- # thachvd-kit Kit
2
-
3
- This kit keeps AI coding behavior consistent across Codex, Antigravity, and Claude Code.
4
-
5
- ## Entry Files
6
-
7
- - `AGENTS.md`: shared cross-agent instructions.
8
- - `CLAUDE.md`: Claude Code entry file that imports `AGENTS.md`.
9
- - `GEMINI.md`: Antigravity entry file that points to `AGENTS.md`.
10
-
11
- ## Shared Docs
12
-
13
- Project-specific knowledge belongs under `.agent/docs/`:
14
-
15
- - `project.md`: stack, commands, tools, routing, and scan evidence.
16
- - `architecture.md`: codebase structure, entry points, and boundaries.
17
- - `conventions.md`: naming, formatting, testing, API, state, and styling patterns.
18
- - `workflow.md`: repeatable task flow.
19
-
20
- Agents should update these docs when they discover real project facts. Keep root entry files short.
21
-
22
- ## Local Kit
23
-
24
- - `.agent/agents/`: specialist agent guidance.
25
- - `.agent/skills/`: reusable capability instructions.
26
- - `.agent/workflows/`: task workflows.
27
- - `.agent/rules/GEMINI.md`: Antigravity-compatible mirror rules.
28
-
29
- Powered by thachvd-kit.
1
+ # thachvd-kit Kit
2
+
3
+ This kit keeps AI coding behavior consistent across Codex, Antigravity, and Claude Code.
4
+
5
+ ## Entry Files
6
+
7
+ - `AGENTS.md`: shared cross-agent instructions.
8
+ - `CLAUDE.md`: Claude Code entry file that imports `AGENTS.md`.
9
+ - `GEMINI.md`: Antigravity entry file that points to `AGENTS.md`.
10
+
11
+ ## Shared Docs
12
+
13
+ Project-specific knowledge belongs under `.agent/docs/`:
14
+
15
+ - `project.md`: stack, commands, tools, routing, and scan evidence.
16
+ - `architecture.md`: codebase structure, entry points, and boundaries.
17
+ - `conventions.md`: naming, formatting, testing, API, state, and styling patterns.
18
+ - `workflow.md`: repeatable task flow.
19
+
20
+ Agents should update these docs when they discover real project facts. Keep root entry files short.
21
+
22
+ ## Local Kit
23
+
24
+ - `.agent/agents/`: specialist agent guidance.
25
+ - `.agent/skills/`: reusable capability instructions.
26
+ - `.agent/workflows/`: task workflows.
27
+ - `.agent/rules/GEMINI.md`: Antigravity-compatible mirror rules.
28
+
29
+ Powered by thachvd-kit.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "thachvd-kit",
3
- "version": "1.0.17",
3
+ "version": "1.0.19",
4
4
  "description": "Cross-agent project rules bootstrap kit for Codex, Antigravity, and Claude Code",
5
5
  "bin": {
6
6
  "thachvd-kit": "./bin/cli.js"
package/rules/GEMINI.md CHANGED
@@ -1,45 +1,45 @@
1
- ---
2
- trigger: always_on
3
- ---
4
-
5
- # GEMINI.md
6
-
7
- Antigravity-compatible entry rules for thachvd-kit projects.
8
-
9
- ## Startup
10
-
11
- 1. Read `AGENTS.md` at the project root.
12
- 2. Read `.agent/docs/project.md` for stack, commands, and routing.
13
- 3. Read `.agent/docs/workflow.md` before editing.
14
- 4. Read `.agent/docs/architecture.md` and `.agent/docs/conventions.md` before planning non-trivial code changes.
15
- 5. If any `.agent/docs/*.md` file contains `TODO: refine`, update that doc from the real code before product code changes.
16
-
17
- ## Routing
18
-
19
- - Frontend/UI: `.agent/agents/frontend-specialist.md`
20
- - Backend/API: `.agent/agents/backend-specialist.md`
21
- - Database/schema: `.agent/agents/database-architect.md`
22
- - Mobile/desktop: `.agent/agents/mobile-developer.md`
23
- - DevOps/CI/deploy: `.agent/agents/devops-engineer.md`
24
- - Debug/RCA: `.agent/agents/debugger.md`
25
- - Security: `.agent/agents/security-auditor.md`
26
- - Multi-domain: `.agent/agents/orchestrator.md`
27
-
28
- Load only the agent, skill, or workflow files relevant to the current task.
29
-
30
- ## Execution
31
-
32
- - Questions and analysis: answer directly; do not edit code.
33
- - Simple fix: inspect dependencies, make the smallest change, verify.
34
- - Feature or refactor: state assumptions, define success criteria, plan, implement, verify.
35
- - UI work: use relevant frontend design skills before editing.
36
- - Security or deploy work: run the matching checklist before claiming done.
37
-
38
- ## Standards
39
-
40
- - Respond in the user's language.
41
- - Keep code, identifiers, and code comments in English.
42
- - Prefer existing project patterns over new abstractions.
43
- - Keep changes surgical.
44
- - Tests or equivalent verification are mandatory.
45
- - Update `.agent/docs/*` when stack, architecture, workflow, or conventions change.
1
+ ---
2
+ trigger: always_on
3
+ ---
4
+
5
+ # GEMINI.md
6
+
7
+ Antigravity-compatible entry rules for thachvd-kit projects.
8
+
9
+ ## Startup
10
+
11
+ 1. Read `AGENTS.md` at the project root.
12
+ 2. Read `.agent/docs/project.md` for stack, commands, and routing.
13
+ 3. Read `.agent/docs/workflow.md` before editing.
14
+ 4. Read `.agent/docs/architecture.md` and `.agent/docs/conventions.md` before planning non-trivial code changes.
15
+ 5. If any `.agent/docs/*.md` file contains `TODO: refine`, update that doc from the real code before product code changes.
16
+
17
+ ## Routing
18
+
19
+ - Frontend/UI: `.agent/agents/frontend-specialist.md`
20
+ - Backend/API: `.agent/agents/backend-specialist.md`
21
+ - Database/schema: `.agent/agents/database-architect.md`
22
+ - Mobile/desktop: `.agent/agents/mobile-developer.md`
23
+ - DevOps/CI/deploy: `.agent/agents/devops-engineer.md`
24
+ - Debug/RCA: `.agent/agents/debugger.md`
25
+ - Security: `.agent/agents/security-auditor.md`
26
+ - Multi-domain: `.agent/agents/orchestrator.md`
27
+
28
+ Load only the agent, skill, or workflow files relevant to the current task.
29
+
30
+ ## Execution
31
+
32
+ - Questions and analysis: answer directly; do not edit code.
33
+ - Simple fix: inspect dependencies, make the smallest change, verify.
34
+ - Feature or refactor: state assumptions, define success criteria, plan, implement, verify.
35
+ - UI work: use relevant frontend design skills before editing.
36
+ - Security or deploy work: run the matching checklist before claiming done.
37
+
38
+ ## Standards
39
+
40
+ - Respond in the user's language.
41
+ - Keep code, identifiers, and code comments in English.
42
+ - Prefer existing project patterns over new abstractions.
43
+ - Keep changes surgical.
44
+ - Tests or equivalent verification are mandatory.
45
+ - Update `.agent/docs/*` when stack, architecture, workflow, or conventions change.
@@ -1,25 +1,25 @@
1
- ---
2
- name: desktop-design
3
- 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.
4
- allowed-tools: Read, Write, Edit, Glob, Grep, Bash
5
- ---
6
-
7
- # Desktop Design
8
-
9
- This skill covers desktop-first product thinking where `mobile-design` is the wrong default.
10
-
11
- Use it for Tauri and other desktop-oriented apps with window management, keyboard shortcuts, dense layouts, or multi-panel workflows.
12
-
13
- ## Guidance
14
-
15
- - Design for pointer + keyboard, not touch-first.
16
- - Use information density deliberately; desktop screens can support richer sidebars and multi-column layouts.
17
- - Respect platform conventions for menus, shortcuts, dialogs, file pickers, and drag/drop.
18
- - Assume resizing, multiple windows, and long-running sessions are normal.
19
- - Pair with `rust-pro` for Tauri backend/native concerns and `frontend-design` for UI execution.
20
-
21
- ## Related Skills
22
-
23
- - `mobile-design` for touch-first mobile products
24
- - `frontend-design` for visual and interaction design
25
- - `rust-pro` for Rust and Tauri implementation details
1
+ ---
2
+ name: desktop-design
3
+ 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.
4
+ allowed-tools: Read, Write, Edit, Glob, Grep, Bash
5
+ ---
6
+
7
+ # Desktop Design
8
+
9
+ This skill covers desktop-first product thinking where `mobile-design` is the wrong default.
10
+
11
+ Use it for Tauri and other desktop-oriented apps with window management, keyboard shortcuts, dense layouts, or multi-panel workflows.
12
+
13
+ ## Guidance
14
+
15
+ - Design for pointer + keyboard, not touch-first.
16
+ - Use information density deliberately; desktop screens can support richer sidebars and multi-column layouts.
17
+ - Respect platform conventions for menus, shortcuts, dialogs, file pickers, and drag/drop.
18
+ - Assume resizing, multiple windows, and long-running sessions are normal.
19
+ - Pair with `rust-pro` for Tauri backend/native concerns and `frontend-design` for UI execution.
20
+
21
+ ## Related Skills
22
+
23
+ - `mobile-design` for touch-first mobile products
24
+ - `frontend-design` for visual and interaction design
25
+ - `rust-pro` for Rust and Tauri implementation details
@@ -1,42 +1,42 @@
1
- ---
2
- name: project-onboarding
3
- description: Scan the repository and refine `.agent/docs/*` so all supported AI tools share accurate project rules.
4
- ---
5
-
6
- # Project Onboarding
7
-
8
- 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.
9
-
10
- ## Goal
11
-
12
- Create or update the shared project docs used by Codex, Antigravity, and Claude Code:
13
-
14
- - `.agent/docs/project.md`
15
- - `.agent/docs/architecture.md`
16
- - `.agent/docs/conventions.md`
17
- - `.agent/docs/workflow.md`
18
-
19
- Do not create a legacy root context file.
20
-
21
- ## Process
22
-
23
- 1. Read `AGENTS.md`.
24
- 2. Inspect repository structure, package/build config, test config, entry points, and representative source files.
25
- 3. Update `.agent/docs/project.md` with stack, app root, commands, test/lint tooling, and routing.
26
- 4. Update `.agent/docs/architecture.md` with major directories, entry points, boundaries, and important decisions.
27
- 5. Update `.agent/docs/conventions.md` with real naming, formatting, API, state, styling, and testing patterns.
28
- 6. Update `.agent/docs/workflow.md` only when the repository needs project-specific workflow steps.
29
-
30
- ## Rules
31
-
32
- - Keep docs concise and factual.
33
- - Mark unknowns as `TODO: refine` only when the codebase does not provide evidence.
34
- - Do not implement product code during onboarding.
35
- - Do not overwrite unrelated user-maintained notes.
36
-
37
- ## Completion Checklist
38
-
39
- - [ ] `.agent/docs/project.md` reflects actual stack and commands.
40
- - [ ] `.agent/docs/architecture.md` maps the current codebase.
41
- - [ ] `.agent/docs/conventions.md` captures observed patterns.
42
- - [ ] `.agent/docs/workflow.md` has the task flow agents should follow.
1
+ ---
2
+ name: project-onboarding
3
+ description: Scan the repository and refine `.agent/docs/*` so all supported AI tools share accurate project rules.
4
+ ---
5
+
6
+ # Project Onboarding
7
+
8
+ 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.
9
+
10
+ ## Goal
11
+
12
+ Create or update the shared project docs used by Codex, Antigravity, and Claude Code:
13
+
14
+ - `.agent/docs/project.md`
15
+ - `.agent/docs/architecture.md`
16
+ - `.agent/docs/conventions.md`
17
+ - `.agent/docs/workflow.md`
18
+
19
+ Do not create a legacy root context file.
20
+
21
+ ## Process
22
+
23
+ 1. Read `AGENTS.md`.
24
+ 2. Inspect repository structure, package/build config, test config, entry points, and representative source files.
25
+ 3. Update `.agent/docs/project.md` with stack, app root, commands, test/lint tooling, and routing.
26
+ 4. Update `.agent/docs/architecture.md` with major directories, entry points, boundaries, and important decisions.
27
+ 5. Update `.agent/docs/conventions.md` with real naming, formatting, API, state, styling, and testing patterns.
28
+ 6. Update `.agent/docs/workflow.md` only when the repository needs project-specific workflow steps.
29
+
30
+ ## Rules
31
+
32
+ - Keep docs concise and factual.
33
+ - Mark unknowns as `TODO: refine` only when the codebase does not provide evidence.
34
+ - Do not implement product code during onboarding.
35
+ - Do not overwrite unrelated user-maintained notes.
36
+
37
+ ## Completion Checklist
38
+
39
+ - [ ] `.agent/docs/project.md` reflects actual stack and commands.
40
+ - [ ] `.agent/docs/architecture.md` maps the current codebase.
41
+ - [ ] `.agent/docs/conventions.md` captures observed patterns.
42
+ - [ ] `.agent/docs/workflow.md` has the task flow agents should follow.
@@ -1,25 +1,25 @@
1
- ---
2
- name: react-frontend
3
- 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.
4
- allowed-tools: Read, Write, Edit, Glob, Grep, Bash
5
- ---
6
-
7
- # React Frontend
8
-
9
- This skill is the React-first counterpart to `nextjs-react-expert`.
10
-
11
- Use it when the project uses React without needing Next.js-specific assumptions such as SSR, App Router, or server components.
12
-
13
- ## Guidance
14
-
15
- - Prefer the existing project architecture over introducing a new pattern.
16
- - Keep state ownership shallow and explicit.
17
- - Separate presentational UI from data-fetching and side effects when it improves maintainability.
18
- - Optimize rendering only after confirming an actual bottleneck.
19
- - Pair with `frontend-design` for UI/UX decisions.
20
-
21
- ## Related Skills
22
-
23
- - `nextjs-react-expert` for Next.js-specific performance and routing concerns
24
- - `frontend-design` for layout, visual hierarchy, and responsive design
25
- - `clean-code` for naming, file boundaries, and readability
1
+ ---
2
+ name: react-frontend
3
+ 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.
4
+ allowed-tools: Read, Write, Edit, Glob, Grep, Bash
5
+ ---
6
+
7
+ # React Frontend
8
+
9
+ This skill is the React-first counterpart to `nextjs-react-expert`.
10
+
11
+ Use it when the project uses React without needing Next.js-specific assumptions such as SSR, App Router, or server components.
12
+
13
+ ## Guidance
14
+
15
+ - Prefer the existing project architecture over introducing a new pattern.
16
+ - Keep state ownership shallow and explicit.
17
+ - Separate presentational UI from data-fetching and side effects when it improves maintainability.
18
+ - Optimize rendering only after confirming an actual bottleneck.
19
+ - Pair with `frontend-design` for UI/UX decisions.
20
+
21
+ ## Related Skills
22
+
23
+ - `nextjs-react-expert` for Next.js-specific performance and routing concerns
24
+ - `frontend-design` for layout, visual hierarchy, and responsive design
25
+ - `clean-code` for naming, file boundaries, and readability