@dianzhong/create-harness-app 0.1.2 → 0.1.4

package/dist/index.mjs

@@ -329,6 +329,10 @@ async function overlay(projectRoot, config) {
   if (config.harness !== "none") {
     await overlayHarness(projectRoot, config.harness);
     merge(config.harness === "full" ? HARNESS_FULL_PKG : HARNESS_MINIMAL_PKG);
+    const existingScripts = pkg.scripts ?? {};
+    if (existingScripts.format?.includes("--write") && !existingScripts["format:check"]) {
+      add.scripts["format:check"] = existingScripts.format.replace("--write", "--check");
+    }
   }
   pkg = mergePackageJson(pkg, add);
   await writeJson(pkgPath, pkg);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dianzhong/create-harness-app",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "点众前端项目初始化器：封装 create-vue，叠加 UI 库、axios 层与 AI Harness 治理体系",
   "type": "module",
   "bin": {

package/templates/harness/full/.claude/agents/code-reviewer.md

@@ -11,7 +11,7 @@ tools: Read, Glob, Grep, Bash
 ## Review 范围
 
 - 检查当前 diff 和所有变更文件。
-- 阅读 `CLAUDE.md`、`AGENTS.md`，以及相关 `.claude/rules/*.md`。
+- 阅读 `CLAUDE.md` 以及相关 `.claude/rules/*.md`。
 
 ### Vue / TypeScript 代码质量
 

package/templates/harness/full/.claude/agents/harness-reviewer.md

@@ -15,7 +15,6 @@ tools: Read, Glob, Grep, Bash
 - `.claude/agents/*.md`
 - `.claude/rules/*.md`
 - `CLAUDE.md`
-- `AGENTS.md`
 - `docs/ai-harness.md`
 - `docs/delivery-template.md`
 - `docs/review-checklist.md`
@@ -32,7 +31,6 @@ tools: Read, Glob, Grep, Bash
 - Stop review 必须在质量门禁失败或 P0/P1 review 问题时阻止结束。
 - 完成通知必须兼容 macOS 和 Windows，并在失败时安全降级。
 - skills 必须同步 lock hash（`skills-lock.json` 中每个 skill 的 `computedHash` 必须与当前文件内容一致）。
-- `.agents/skills/` 必须与 `.claude/skills/` 完全镜像（`diff -r .claude/skills/ .agents/skills/` 输出为空）。
 - harness 脚本的测试必须接入 `pnpm harness:check`，不能只放测试文件。
 - 结构检查必须只约束通用工程护栏，不得固化当前占位业务流程或 mock 数据。
 - harness 配置以源文件为准，不维护额外 generated config inventory。

package/templates/harness/full/.claude/rules/skills-mcp.md

@@ -4,10 +4,9 @@
 - 项目 skills 放在 `.claude/skills/`。
 - `skills-lock.json` 必须保存每个 skill 的真实 computed hash。
 
-新增或修改 skill 时，必须同步以下 3 个位置：
+新增或修改 skill 时，必须同步以下 2 个位置：
 
 1. `.claude/skills/{skill}/`
-2. `.agents/skills/{skill}/`（其他 agent 的镜像）
-3. `skills-lock.json`（hash lock）
+2. `skills-lock.json`（hash lock）
 
 修改任何 skill 后必须先运行 `pnpm harness:sync`，再运行 `pnpm harness:check`。

package/templates/harness/full/.claude/settings.json

@@ -81,7 +81,7 @@
         "hooks": [
           {
             "type": "agent",
-            "prompt": "你是强制 AI harness 代码审查子 agent。审查前先运行 `git diff --name-only` 查看本次改动了哪些文件。若任一改动文件匹配 `.claude/**`、`.agents/**`、`.husky/**`、`scripts/verify-skills.mjs`、`scripts/sync-harness-docs.mjs`、`scripts/check-project-structure.mjs`、`scripts/*.test.mjs`、`skills-lock.json`、`package.json`、`CLAUDE.md`、`AGENTS.md`、`GEMINI.md`、`CONTRIBUTING.md`、`docs/ai-harness.md`、`docs/harness-quick-reference.md`、`docs/delivery-template.md`、`docs/review-checklist.md` 或 `docs/verification.md`，就读取 `.claude/agents/harness-reviewer.md` 并严格按其规则审查；否则读取 `.claude/agents/code-reviewer.md` 并严格按其规则审查。不要编辑任何文件。只返回 JSON：{\"ok\":true|false,\"reason\":\"HARNESS_REVIEW_RESULT: PASS|FAIL\\n简短总结。\"}。并提醒用户：Claude 审查不能替代人工最终复核。",
+            "prompt": "你是强制 AI harness 代码审查子 agent。审查前先运行 `git diff --name-only` 查看本次改动了哪些文件。若任一改动文件匹配 `.claude/**`、`.husky/**`、`scripts/verify-skills.mjs`、`scripts/sync-harness-docs.mjs`、`scripts/check-project-structure.mjs`、`scripts/*.test.mjs`、`skills-lock.json`、`package.json`、`CLAUDE.md`、`CONTRIBUTING.md`、`docs/ai-harness.md`、`docs/harness-quick-reference.md`、`docs/delivery-template.md`、`docs/review-checklist.md` 或 `docs/verification.md`，就读取 `.claude/agents/harness-reviewer.md` 并严格按其规则审查；否则读取 `.claude/agents/code-reviewer.md` 并严格按其规则审查。不要编辑任何文件。只返回 JSON：{\"ok\":true|false,\"reason\":\"HARNESS_REVIEW_RESULT: PASS|FAIL\\n简短总结。\"}。并提醒用户：Claude 审查不能替代人工最终复核。",
             "timeout": 300,
             "statusMessage": "运行强制代码审查"
           }

package/templates/harness/full/docs/ai-harness.md

@@ -6,7 +6,7 @@
 
 ## 目标
 
-- Claude Code 优先，同时让其他 agent 能从 `AGENTS.md` 读取同一套核心规则。
+- Claude Code 作为唯一执行工具，统一从 `CLAUDE.md` 读取核心规则。
 - 每次 AI 改动都经过质量门禁和 code review subagent。
 - hooks 跨 macOS 和 Windows 可用，不依赖 `jq`、`bash` 或平台专属通知命令。
 - 重要规范进入仓库，可版本化、可 review、可复用。
@@ -14,13 +14,11 @@
 ## 组成
 
 - `CLAUDE.md`：Claude Code 主入口，定义项目事实和执行流程。
-- `AGENTS.md`：模型通用入口，降低不同 agent 的理解差异。
 - `.claude/settings.json`：Claude Code 权限和 hooks 配置。
 - `.claude/hooks/*.cjs`：跨平台 Node hooks。
 - `.claude/agents/*.md`：项目级 review subagents。
 - `.claude/rules/*.md`：可按任务加载的细分规则。
 - `.claude/skills/`：Claude Code 项目 skills 源。
-- `.agents/skills/`：Codex 和其他 agent 使用的项目 skills 镜像。
 - `scripts/verify-skills.mjs`：校验 skills 文档和 lock 是否同步。
 - `scripts/sync-harness-docs.mjs`：校验 harness 文档入口是否完整、是否仍引用废弃清单。
 - `scripts/check-project-structure.mjs`：校验通用前端结构护栏，不固化当前占位业务。
@@ -37,7 +35,7 @@
 - Hook 行为以 `.claude/hooks/*.cjs` 为准。
 - Review agent 定义以 `.claude/agents/*.md` 为准；`.claude/settings.json` 中的 Stop agent 内联 prompt 是当前强制 review 入口。
 - Rules 以 `.claude/rules/*.md` 为准。
-- Skills 以 `.claude/skills/` 为源，`.agents/skills/` 为其他 agent 镜像，`skills-lock.json` 保存校验 hash。
+- Skills 以 `.claude/skills/` 为源，`skills-lock.json` 保存校验 hash。
 - 业务规格以 OpenSpec 的 `openspec/specs/` 为准；待确认或待实现的业务变更以 `openspec/changes/<change-id>/` 为准。
 - 人工审核交付格式以 `docs/delivery-template.md` 为准。
 
@@ -60,7 +58,7 @@
 - `pnpm check:fix`：显式执行格式化与 lint 自动修复。
 - `pnpm harness:structure`：通用前端结构护栏检查，覆盖 route meta 基础约束、动态菜单组件解析、明显第二套菜单/权限源和高风险 Element Plus 深层覆盖提示。
 - `pnpm harness:test`：运行 harness 脚本测试，覆盖结构检查、skill 校验和 hooks 基础行为。
-- `pnpm harness:check`：skills、docs、lock、入口文档、`.agents/skills` 镜像、项目结构护栏和 harness 脚本测试。
+- `pnpm harness:check`：skills、docs、lock、入口文档、项目结构护栏和 harness 脚本测试。
 - `pnpm build`：生产构建校验，适用于构建配置、路由、样式或依赖变更。
 
 ## 维护规则
@@ -72,6 +70,6 @@
 - 修改人工审核流程或交付要求时，同步 `docs/review-checklist.md` 和 `docs/delivery-template.md`。
 - 当前业务代码是占位实现，不允许把项目看板、审核流、mock 数据或临时页面形态沉淀为 harness 规则或工程规范。
 - 业务规格（页面布局、字段口径、状态机、角色权限矩阵、接口契约等）统一放在 OpenSpec。当前有效规格沉淀到 `openspec/specs/`；PRD 链接、钉钉文档更新或口头需求变更先建 `openspec/changes/<change-id>/`，明确来源、影响页面、接口影响、验收标准和待确认问题。
-- OpenSpec 不自动进入 Claude Code 默认上下文，由 AI 按任务需要主动 view。harness 文档（本文件、`docs/harness-quick-reference.md`、`docs/development.md`、`.claude/rules/*`、`CLAUDE.md`、`AGENTS.md`、`GEMINI.md`）只引用 OpenSpec 入口，不复制业务内容。
+- OpenSpec 不自动进入 Claude Code 默认上下文，由 AI 按任务需要主动 view。harness 文档（本文件、`docs/harness-quick-reference.md`、`.claude/rules/*`、`CLAUDE.md`）只引用 OpenSpec 入口，不复制业务内容。
 - 反复使用的业务规则（全局权限矩阵、跨页面状态机）应做成 `.claude/skills/<name>/`，由 AI 按需加载。
 - `quality-gate.cjs stop` 是唯一允许自动格式化的 hook，用于 Stop 收尾；其他 hooks 不得自动格式化、暂存或改写 repo-tracked 文件。`lint-staged` 作为 pre-commit safety net 是另一处显式例外。

package/templates/harness/full/docs/harness-quick-reference.md

@@ -82,7 +82,7 @@ OpenSpec 只管理业务规格和需求变更；Harness 继续管理 AI 执行
 | 步骤 | 检查项                                                                                                      | 参考文档                      |
 | ---- | ----------------------------------------------------------------------------------------------------------- | ----------------------------- |
 | 1    | 是否修改了 `.claude/settings.json`、hooks、agents、rules、skills？同步入口文档了吗？                        | `docs/ai-harness.md` 维护规则 |
-| 2    | 如果新增或修改 skill，是否同步了 `.claude/skills/{skill}`、`.agents/skills/{skill}` 和 `skills-lock.json`？ | `.claude/rules/skills-mcp.md` |
+| 2    | 如果新增或修改 skill，是否同步了 `.claude/skills/{skill}` 和 `skills-lock.json`？ | `.claude/rules/skills-mcp.md` |
 | 3    | 是否运行了 `pnpm harness:sync` 和 `pnpm harness:check`？                                                    | `docs/ai-harness.md` 质量门禁 |
 | 4    | 是否需要按 `docs/verification.md` 做本地浏览器验证？                                                        | `docs/verification.md`        |
 | 5    | 是否确认 Stop 收尾不会自动 `git add`？                                                                      | `docs/ai-harness.md` 维护规则 |

package/templates/harness/full/docs/review-checklist.md

@@ -1,6 +1,6 @@
 # 人工审核流程
 
-Claude Code 或其他 agent 完成任务后，提交前必须由人做最终复核。AI 的职责是提供可审核的交接单；人的职责是确认业务判断、真实场景和可接受风险。
+Claude Code 完成任务后，提交前必须由人做最终复核。AI 的职责是提供可审核的交接单；人的职责是确认业务判断、真实场景和可接受风险。
 
 ## 收到 AI 交接单后
 

package/templates/harness/full/scripts/verify-skills.mjs

@@ -3,10 +3,9 @@
  * 校验 skills 体系的一致性
  *
  * 检查项：
- * 1. .claude/skills 与 .agents/skills 目录结构完全镜像
- * 2. SKILL.md 内容 hash 一致
- * 3. api/assets/references/scripts/templates 等资源目录内容一致
- * 4. skills-lock.json 的 computedHash 与实际目录内容一致
+ * 1. .claude/skills 下每个 skill 都有 SKILL.md 入口
+ * 2. skills-lock.json 的条目与 .claude/skills 目录完全一致
+ * 3. skills-lock.json 的 computedHash 与实际目录内容一致
  *
  * --write 模式：更新 skills-lock.json（用于发布 skill 变更时）
  */
@@ -18,17 +17,8 @@ import path from 'node:path'
 
 const root = process.cwd()
 const skillsDir = path.join(root, '.claude', 'skills')
-const agentsSkillsDir = path.join(root, '.agents', 'skills')
 const lockPath = path.join(root, 'skills-lock.json')
 const writeMode = process.argv.includes('--write')
-const mirroredResourceDirs = new Set([
-  'api',
-  'assets',
-  'examples',
-  'references',
-  'scripts',
-  'templates',
-])
 
 const defaultSources = {
   'element-plus-vue3': {
@@ -103,13 +93,6 @@ async function hashDirectory(dir) {
   return hash.digest('hex')
 }
 
-// 计算单个文件的 SHA-256 hash
-async function hashFile(filePath) {
-  const hash = createHash('sha256')
-  hash.update(await readFile(filePath))
-  return hash.digest('hex')
-}
-
 async function listSkillNames(dir) {
   if (!existsSync(dir)) {
     return []
@@ -142,13 +125,7 @@ async function main() {
     throw new Error(`Missing skills directory: ${skillsDir}`)
   }
 
-  if (!existsSync(agentsSkillsDir)) {
-    throw new Error(`Missing agents skills mirror directory: ${agentsSkillsDir}`)
-  }
-
   const skillNames = await listSkillNames(skillsDir)
-  const agentsSkillNames = await listSkillNames(agentsSkillsDir)
-  assertEqualSets('.agents/skills mirror entries', new Set(agentsSkillNames), new Set(skillNames))
 
   const hashes = {}
 
@@ -188,46 +165,14 @@ async function main() {
   const skillNameSet = new Set(skillNames)
   assertEqualSets('skills-lock.json entries', lockNames, skillNameSet)
 
-  // 校验每个 skill 的镜像同步、SKILL.md hash、资源目录和 lock hash
+  // 校验每个 skill 的入口文件和 lock hash
   for (const skillName of skillNames) {
-    const skillPath = path.join(skillsDir, skillName)
-    const agentsSkillPath = path.join(agentsSkillsDir, skillName)
-    const sourceSkillMd = path.join(skillPath, 'SKILL.md')
-    const mirroredSkillMd = path.join(agentsSkillPath, 'SKILL.md')
+    const sourceSkillMd = path.join(skillsDir, skillName, 'SKILL.md')
 
     if (!existsSync(sourceSkillMd)) {
       throw new Error(`Missing skill entrypoint: ${sourceSkillMd}`)
     }
 
-    if (!existsSync(mirroredSkillMd)) {
-      throw new Error(`Missing mirrored skill entrypoint: ${mirroredSkillMd}`)
-    }
-
-    if ((await hashFile(sourceSkillMd)) !== (await hashFile(mirroredSkillMd))) {
-      throw new Error(`Mirrored SKILL.md is out of sync for ${skillName}.`)
-    }
-
-    for (const resourceDir of mirroredResourceDirs) {
-      const sourceResourcePath = path.join(skillPath, resourceDir)
-      const mirroredResourcePath = path.join(agentsSkillPath, resourceDir)
-
-      if (!existsSync(sourceResourcePath)) {
-        continue
-      }
-
-      if (!existsSync(mirroredResourcePath)) {
-        throw new Error(
-          `Missing mirrored skill resource: ${toPosix(path.relative(root, mirroredResourcePath))}`,
-        )
-      }
-
-      if (
-        (await hashDirectory(sourceResourcePath)) !== (await hashDirectory(mirroredResourcePath))
-      ) {
-        throw new Error(`Mirrored skill resource is out of sync: ${skillName}/${resourceDir}`)
-      }
-    }
-
     const lockedHash = lock.skills?.[skillName]?.computedHash
 
     if (lockedHash !== hashes[skillName]) {
@@ -238,7 +183,7 @@ async function main() {
   }
 
   process.stdout.write(
-    `Harness skill check passed for ${skillNames.length} skill(s), including .agents/skills mirror.\n`,
+    `Harness skill check passed for ${skillNames.length} skill(s).\n`,
   )
 }
 

package/templates/harness/full/scripts/verify-skills.test.mjs

@@ -4,7 +4,7 @@
  *
  * 覆盖：
  * 1. --write 能生成 lock
- * 2. .agents/skills 镜像内容漂移时会失败
+ * 2. 生成 lock 后复查通过
  */
 
 import assert from 'node:assert/strict'
@@ -43,7 +43,6 @@ description: Sample skill for harness tests.
 `
 
     await writeFixtureFile(root, '.claude/skills/sample-skill/SKILL.md', skill)
-    await writeFixtureFile(root, '.agents/skills/sample-skill/SKILL.md', skill)
 
     await testFn(root)
   } finally {
@@ -60,13 +59,4 @@ await withSkillFixture(async (root) => {
   assert.match(checkResult.stdout, /Harness skill check passed/)
 })
 
-await withSkillFixture(async (root) => {
-  assert.equal(runVerify(root, ['--write']).status, 0)
-  await writeFixtureFile(root, '.agents/skills/sample-skill/SKILL.md', '# Drifted Skill\n')
-
-  const result = runVerify(root)
-  assert.notEqual(result.status, 0)
-  assert.match(result.stderr, /Mirrored SKILL\.md is out of sync/)
-})
-
 console.log('verify-skills tests passed')

package/templates/harness/full/.agents/skills/find-skills/SKILL.md

@@ -1,143 +0,0 @@
----
-name: find-skills
-description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
----
-
-# Find Skills
-
-This skill helps you discover and install skills from the open agent skills ecosystem.
-
-## When to Use This Skill
-
-Use this skill when the user:
-
-- Asks "how do I do X" where X might be a common task with an existing skill
-- Says "find a skill for X" or "is there a skill for X"
-- Asks "can you do X" where X is a specialized capability
-- Expresses interest in extending agent capabilities
-- Wants to search for tools, templates, or workflows
-- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
-
-## What is the Skills CLI?
-
-The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
-
-**Key commands:**
-
-- `npx skills find [query]` - Search for skills interactively or by keyword
-- `npx skills add <package>` - Install a skill from GitHub or other sources
-- `npx skills check` - Check for skill updates
-- `npx skills update` - Update all installed skills
-
-**Browse skills at:** https://skills.sh/
-
-## How to Help Users Find Skills
-
-### Step 1: Understand What They Need
-
-When a user asks for help with something, identify:
-
-1. The domain (e.g., React, testing, design, deployment)
-2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
-3. Whether this is a common enough task that a skill likely exists
-
-### Step 2: Check the Leaderboard First
-
-Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
-
-For example, top skills for web development include:
-
-- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
-- `anthropics/skills` — Frontend design, document processing (100K+ installs)
-
-### Step 3: Search for Skills
-
-If the leaderboard doesn't cover the user's need, run the find command:
-
-```bash
-npx skills find [query]
-```
-
-For example:
-
-- User asks "how do I make my React app faster?" → `npx skills find react performance`
-- User asks "can you help me with PR reviews?" → `npx skills find pr review`
-- User asks "I need to create a changelog" → `npx skills find changelog`
-
-### Step 4: Verify Quality Before Recommending
-
-**Do not recommend a skill based solely on search results.** Always verify:
-
-1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.
-2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
-3. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
-
-### Step 5: Present Options to the User
-
-When you find relevant skills, present them to the user with:
-
-1. The skill name and what it does
-2. The install count and source
-3. The install command they can run
-4. A link to learn more at skills.sh
-
-Example response:
-
-```
-I found a skill that might help! The "react-best-practices" skill provides
-React and Next.js performance optimization guidelines from Vercel Engineering.
-(185K installs)
-
-To install it:
-npx skills add vercel-labs/agent-skills@react-best-practices
-
-Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
-```
-
-### Step 6: Offer to Install
-
-If the user wants to proceed, you can install the skill for them:
-
-```bash
-npx skills add <owner/repo@skill> -g -y
-```
-
-The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
-
-## Common Skill Categories
-
-When searching, consider these common categories:
-
-| Category        | Example Queries                          |
-| --------------- | ---------------------------------------- |
-| Web Development | react, nextjs, typescript, css, tailwind |
-| Testing         | testing, jest, playwright, e2e           |
-| DevOps          | deploy, docker, kubernetes, ci-cd        |
-| Documentation   | docs, readme, changelog, api-docs        |
-| Code Quality    | review, lint, refactor, best-practices   |
-| Design          | ui, ux, design-system, accessibility     |
-| Productivity    | workflow, automation, git                |
-
-## Tips for Effective Searches
-
-1. **Use specific keywords**: "react testing" is better than just "testing"
-2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
-3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
-
-## When No Skills Are Found
-
-If no relevant skills exist:
-
-1. Acknowledge that no existing skill was found
-2. Offer to help with the task directly using your general capabilities
-3. Suggest the user could create their own skill with `npx skills init`
-
-Example:
-
-```
-I searched for skills related to "xyz" but didn't find any matches.
-I can still help you with this task directly! Would you like me to proceed?
-
-If this is something you do often, you could create your own skill:
-npx skills init my-xyz-skill
-```

package/templates/harness/full/.agents/skills/vue-best-practices/LICENSE.md

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 hyf0, SerKo <https://github.com/serkodev>
-
-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.

package/templates/harness/full/.agents/skills/vue-best-practices/SKILL.md

@@ -1,155 +0,0 @@
----
-name: vue-best-practices
-description: MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.
-license: MIT
-metadata:
-  author: github.com/vuejs-ai
-  version: '18.0.0'
----
-
-# Vue Best Practices Workflow
-
-Use this skill as an instruction set. Follow the workflow in order unless the user explicitly asks for a different order.
-
-## Core Principles
-
-- **Keep state predictable:** one source of truth, derive everything else.
-- **Make data flow explicit:** Props down, Events up for most cases.
-- **Favor small, focused components:** easier to test, reuse, and maintain.
-- **Avoid unnecessary re-renders:** use computed properties and watchers wisely.
-- **Readability counts:** write clear, self-documenting code.
-
-## 1) Confirm architecture before coding (required)
-
-- Default stack: Vue 3 + Composition API + `<script setup lang="ts">`.
-- If the project explicitly uses Options API, load `vue-options-api-best-practices` skill if available.
-- If the project explicitly uses JSX, load `vue-jsx-best-practices` skill if available.
-
-### 1.1 Must-read core references (required)
-
-- Before implementing any Vue task, make sure to read and apply these core references:
-  - `references/reactivity.md`
-  - `references/sfc.md`
-  - `references/component-data-flow.md`
-  - `references/composables.md`
-- Keep these references in active working context for the entire task, not only when a specific issue appears.
-
-### 1.2 Plan component boundaries before coding (required)
-
-Create a brief component map before implementation for any non-trivial feature.
-
-- Define each component's single responsibility in one sentence.
-- Keep entry/root and route-level view components as composition surfaces by default.
-- Move feature UI and feature logic out of entry/root/view components unless the task is intentionally a tiny single-file demo.
-- Define props/emits contracts for each child component in the map.
-- Prefer a feature folder layout (`components/<feature>/...`, `composables/use<Feature>.ts`) when adding more than one component.
-
-## 2) Apply essential Vue foundations (required)
-
-These are essential, must-know foundations. Apply all of them in every Vue task using the core references already loaded in section `1.1`.
-
-### Reactivity
-
-- Must-read reference from `1.1`: [reactivity](references/reactivity.md)
-- Keep source state minimal (`ref`/`reactive`), derive everything possible with `computed`.
-- Use watchers for side effects if needed.
-- Avoid recomputing expensive logic in templates.
-
-### SFC structure and template safety
-
-- Must-read reference from `1.1`: [sfc](references/sfc.md)
-- Keep SFC sections in this order: `<script>` → `<template>` → `<style>`.
-- Keep SFC responsibilities focused; split large components.
-- Keep templates declarative; move branching/derivation to script.
-- Apply Vue template safety rules (`v-html`, list rendering, conditional rendering choices).
-
-### Keep components focused
-
-Split a component when it has **more than one clear responsibility** (e.g. data orchestration + UI, or multiple independent UI sections).
-
-- Prefer **smaller components + composables** over one “mega component”
-- Move **UI sections** into child components (props in, events out).
-- Move **state/side effects** into composables (`useXxx()`).
-
-Apply objective split triggers. Split the component if **any** condition is true:
-
-- It owns both orchestration/state and substantial presentational markup for multiple sections.
-- It has 3+ distinct UI sections (for example: form, filters, list, footer/status).
-- A template block is repeated or could become reusable (item rows, cards, list entries).
-
-Entry/root and route view rule:
-
-- Keep entry/root and route view components thin: app shell/layout, provider wiring, and feature composition.
-- Do not place full feature implementations in entry/root/view components when those features contain independent parts.
-- For CRUD/list features (todo, table, catalog, inbox), split at least into:
-  - feature container component
-  - input/form component
-  - list (and/or item) component
-  - footer/actions or filter/status component
-- Allow a single-file implementation only for very small throwaway demos; if chosen, explicitly justify why splitting is unnecessary.
-
-### Component data flow
-
-- Must-read reference from `1.1`: [component-data-flow](references/component-data-flow.md)
-- Use props down, events up as the primary model.
-- Use `v-model` only for true two-way component contracts.
-- Use provide/inject only for deep-tree dependencies or shared context.
-- Keep contracts explicit and typed with `defineProps`, `defineEmits`, and `InjectionKey` as needed.
-
-### Composables
-
-- Must-read reference from `1.1`: [composables](references/composables.md)
-- Extract logic into composables when it is reused, stateful, or side-effect heavy.
-- Keep composable APIs small, typed, and predictable.
-- Separate feature logic from presentational components.
-
-## 3) Consider optional features only when requirements call for them
-
-### 3.1 Standard optional features
-
-Do not add these by default. Load the matching reference only when the requirement exists.
-
-- Slots: parent needs to control child content/layout -> [component-slots](references/component-slots.md)
-- Fallthrough attributes: wrapper/base components must forward attrs/events safely -> [component-fallthrough-attrs](references/component-fallthrough-attrs.md)
-- Built-in component `<KeepAlive>` for stateful view caching -> [component-keep-alive](references/component-keep-alive.md)
-- Built-in component `<Teleport>` for overlays/portals -> [component-teleport](references/component-teleport.md)
-- Built-in component `<Suspense>` for async subtree fallback boundaries -> [component-suspense](references/component-suspense.md)
-- Animation-related features: pick the simplest approach that matches the required motion behavior.
-  - Built-in component `<Transition>` for enter/leave effects -> [transition](references/component-transition.md)
-  - Built-in component `<TransitionGroup>` for animated list mutations -> [transition-group](references/component-transition-group.md)
-  - Class-based animation for non-enter/leave effects -> [animation-class-based-technique](references/animation-class-based-technique.md)
-  - State-driven animation for user-input-driven animation -> [animation-state-driven-technique](references/animation-state-driven-technique.md)
-
-### 3.2 Less-common optional features
-
-Use these only when there is explicit product or technical need.
-
-- Directives: behavior is DOM-specific and not a good composable/component fit -> [directives](references/directives.md)
-- Async components: heavy/rarely-used UI should be lazy loaded -> [component-async](references/component-async.md)
-- Render functions only when templates cannot express the requirement -> [render-functions](references/render-functions.md)
-- Plugins when behavior must be installed app-wide -> [plugins](references/plugins.md)
-- State management patterns: app-wide shared state crosses feature boundaries -> [state-management](references/state-management.md)
-
-## 4) Run performance optimization after behavior is correct
-
-Performance work is a post-functionality pass. Do not optimize before core behavior is implemented and verified.
-
-- Large list rendering bottlenecks -> [perf-virtualize-large-lists](references/perf-virtualize-large-lists.md)
-- Static subtrees re-rendering unnecessarily -> [perf-v-once-v-memo-directives](references/perf-v-once-v-memo-directives.md)
-- Over-abstraction in hot list paths -> [perf-avoid-component-abstraction-in-lists](references/perf-avoid-component-abstraction-in-lists.md)
-- Expensive updates triggered too often -> [updated-hook-performance](references/updated-hook-performance.md)
-
-## 5) Final self-check before finishing
-
-- Core behavior works and matches requirements.
-- All must-read references were read and applied.
-- Reactivity model is minimal and predictable.
-- SFC structure and template rules are followed.
-- Components are focused and well-factored, splitting when needed.
-- Entry/root and route view components remain composition surfaces unless there is an explicit small-demo exception.
-- Component split decisions are explicit and defensible (responsibility boundaries are clear).
-- Data flow contracts are explicit and typed.
-- Composables are used where reuse/complexity justifies them.
-- Moved state/side effects into composables if applicable
-- Optional features are used only when requirements demand them.
-- Performance changes were applied only after functionality was complete.

package/templates/harness/full/.agents/skills/vue-best-practices/SYNC.md

@@ -1,5 +0,0 @@
-# Sync Info
-
-- **Source:** `vendor/vuejs-ai/skills/vue-best-practices`
-- **Git SHA:** `f3dd1bf4d3ac78331bdc903e4519d561c538ca6a`
-- **Synced:** 2026-03-13