thachvd-kit 1.0.15 → 1.0.16

package/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/kit/PROJECT_CONTEXT.template.md

@@ -1,35 +0,0 @@
-# 🗺️ PROJECT CONTEXT - [Project Name]
-
-> Initialize this file at the start of a project to provide the Agent with a Ground Truth.
-
----
-
-## 🎯 Project Objectives
-- Brief description of what the app does and the problem it solves.
-
-## 🛠️ Technology Stack
-- **Frontend/UI:** [e.g., React, Vue, Flutter]
-- **Backend/Core:** [e.g., Rust, Node.js, Python]
-- **State Management:** [e.g., Zustand, Redux, Signals]
-- **Styling:** [e.g., Tailwind CSS, Vanilla CSS]
-
-## 📂 Project Structure
-- `src/[store|state]/`: State management modules.
-- `src/[services|logic]/`: Heavy business logic and I/O.
-- `src/lib/`: Reusable utility functions.
-- [Additional critical directories...]
-
-## 📜 Rules & Constraints
-- **Granularity:** [e.g., Max 250 lines/file] (Mandatory file splitting).
-- **Architecture:** Decouple UI from business logic.
-- **Safety:** [e.g., Use specific patterns for terminal commands or secrets].
-- [Project-specific golden rules...]
-
-## 🚧 Current Status
-- **Current Objective:** [e.g., Implementing Auth flow].
-- **Known Issues:** [e.g., API latency on high load].
-- **Next Milestones:** [e.g., Deployment to staging].
-
----
-
-**Note:** This file is the "Ground Truth". The Agent IS ALLOWED and MANDATED to update this file after every significant task.