@givolt/i3-composer-agent 3.1.0 → 4.0.0

package/skills/i3-incremental-implementation/SKILL.md

@@ -192,10 +192,6 @@ Each increment should be independently revertable:
 - Database migrations should have corresponding rollback migrations
 - Avoid deleting something in one commit and replacing it in the same commit — separate them
 
-## UI Slices with Prototype Baselines
-
-For a UI slice, check `prototypes/index.json` (legacy `.i3-ui-prototypes.json` fallback) for an applicable approved prototype. Match explicit module IDs against appliesTo; an empty array is unbound. Resolve conflicting indices or multiple matches instead of applying a prototype globally. New appliesTo values come from fixed scope.moduleIds through `i3-ui-prototype`. Read its design contract, business mapping and baseline before implementation, and include affected interaction/visual checks in the slice acceptance. Preserve prior snapshots; coordinate contract changes through `i3-ui-prototype`. Backend-only slices and projects without a baseline continue the existing increment workflow.
-
 ## Working with Agents
 
 When directing an agent to implement incrementally:

package/skills/i3-performance-optimization/SKILL.md

@@ -217,8 +217,8 @@ Lighthouse Performance score: ≥ 90
 # Bundle size check
 npx bundlesize --config bundlesize.config.json
 
-# Lighthouse CI
-npx lhci autorun
+# Lighthouse CI. The CLI package is @lhci/cli; unscoped `lhci` on npm is not it.
+npx --package=@lhci/cli lhci autorun
 ```
 
 ## See Also

package/skills/i3-security-and-hardening/references/hardening-patterns.md

@@ -73,6 +73,11 @@ const clean = DOMPurify.sanitize(userInput);
 // Always check authorization, not just authentication
 app.patch('/api/tasks/:id', authenticate, async (req, res) => {
   const task = await taskService.findById(req.params.id);
+  if (!task) {
+    return res.status(404).json({
+      error: { code: 'NOT_FOUND', message: 'Task not found' }
+    });
+  }
 
   // Check that the authenticated user owns this resource
   if (task.ownerId !== req.user.id) {

package/skills/i3-source-driven-development/SKILL.md

@@ -170,8 +170,9 @@ form submission state. React 19 replaced the manual
 isPending/setIsPending pattern with this hook.
 
 Source: https://react.dev/blog/2024/12/05/react-19#actions
-"useTransition now supports async functions [...] to handle
-pending states automatically"
+"In React 19, we're adding support for using async functions in
+transitions to handle pending states, errors, forms, and optimistic
+updates automatically."
 ```
 
 **Citation rules:**

package/skills/i3-spec-driven-development/SKILL.md

@@ -101,7 +101,7 @@ Don't silently fill in ambiguous requirements. The spec's entire purpose is to s
    ```
    Build: npm run build
    Test: npm test -- --coverage
-   Lint: npm run lint --fix
+   Lint: npm run lint -- --fix
    Dev: npm run dev
    ```
 

package/skills/i3-ui-demo/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: i3-ui-demo
 description: "基于业务文档或提示词和内置模板创建、增量修改 Vue 3 与 antdv-next 1.6.0 交互原型。适用于明确请求 ui-demo、模板驱动的界面演示与只读方案分析，以及新增页面、调整设计或修复交互；结合自有能力定义、原生组件映射、模板视觉变量和专业技能完成生成与检查。"
-# i3-description-source: "description: Creates and incrementally updates runnable Vue 3 and antdv-next 1.6.0 UI demos from business documents or prompts using owned templates and required UI/UX Pro Max. Use when requesting ui-demo, a template-based UI demo, or adding pages and revising its design and interactions."
+# i3-description-source: "description: Creates reviewable interactive UI prototypes from business requirements, documents or prompts, and incrementally updates runnable Vue 3 and antdv-next 1.6.0 UI demos using owned templates and required UI/UX Pro Max. Use when requesting ui-demo, an interactive UI prototype, a template-based UI demo, or adding pages and revising its design and interactions."
 ---
 
 <!-- i3:zh-CN:start -->
@@ -187,6 +187,8 @@ Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、
 分别说明实现完成情况、技术验证结果和用户评审状态；技术通过仍可待用户评审。
 认可必须对应具体版本，不从构建、浏览器结果或技能记录推断用户批准。
 
+来自企业 SOP 的任务沿用已选 PRD 的路径、版本及已确定的 EBC／PBC 和主题身份，在现有 `HANDOFF.md` 记录来源、当前实现版本、设计与 QA 位置及实际评审状态，供 PRD／AD 固定引用。普通提示词任务仍可独立开展；不要求为制作原型补齐企业文档，不创建另一套索引或基线管理流程。已有业务原型先读取结构和版本，按明确范围增量维护，保留人工修改和历史。
+
 ## Incremental Changes
 
 先读取现有代码、全局设计系统和相关页面规则，不整体重新生成。

package/skills/i3-ui-demo/references/dependencies.md

@@ -49,7 +49,7 @@ global 仅在用户已经授权对应全局宿主范围时使用；优先项目
 - antDv 官方源固定提交和下载摘要；使用 `assets/antdv-build/` 的锁定构建环境编译未修改的官方源码，不用 npm 上缺失目标数据的 CLI 包替代。
 - 固定的数据文件、索引及官方源码摘要可核对；构建环境只用于工具准备，不进入业务项目 app/。
 - 官方构建器需要 Node.js 22.18.x 或 24.11+。优先当前 Node，否则只读查找 PATH 中已有兼容 Node；缺失时在安装前说明要求，不自动升级全局 Node。已经准备好的 CLI 可在兼容的 Node 20 环境继续复用，不触发重建。
-- 新工具使用独立的宿主工具目录，不覆盖旧 i3-prototype 工具或旧组件配置。
+- 新工具使用独立的宿主工具目录，保留已有工具和组件配置。
 - 版本不兼容或无法验证的技能和工具保留并报告，不按“文件存在”判为就绪。安装完成必须两项均通过；CLI 的较高版本不改变 antdv-next 1.6.0 和知识 1.6.0。
 
 支持用 `--archive <本地官方源码tgz>` 复用已下载的同一固定归档，仍校验其摘要。

package/skills/i3-ui-demo/references/resources.md

@@ -129,7 +129,7 @@ python3 "<ui-ux-pro-max技能绝对目录>/scripts/search.py" "<业务与设计
 - `requirements-map.json`：原文需求到页面、操作、状态、实施文件及验证场景的对应。
 - `design-system/<project-slug>/MASTER.md` 与 pages/：ui-ux-pro-max 的原生设计系统与页面覆盖。
 - `qa/`：对应当前代码和构建的真实检查结果、截图及未完成项。
-- `HANDOFF.md`：本次完成范围、用户选择、版本、启动与预览入口、缺项和下一步。
+- `HANDOFF.md`：准确需求来源及版本、本次完成范围、用户选择、当前实现版本、设计／QA 位置、实际认可范围、启动与预览入口、缺项和下一步。SOP 场景沿用已确定的 EBC／PBC 与主题身份，供 PRD／AD 引用。
 
 这些名称用于新实例约定；已有原型沿用现有资料，不为了统一格式自动迁移。
 只维护一份任务状态。需求映射保存来源和对应关系，不再创建第二份独立任务勾选清单。

package/skills/i3-ui-demo/scripts/dependencies.cjs

@@ -100,9 +100,6 @@ function resolveOfficial(location, options = {}) {
     if (fs.existsSync(directory)) for (const name of fs.readdirSync(directory).sort()) {
       if (name.startsWith('antdv-')) candidates.push(path.join(directory, name, 'source'));
     }
-    // Read the old install's version; a required upgrade is prepared in the
-    // new owned directory without deleting the old tool or its user files.
-    candidates.push(path.join(base, 'tools/i3-prototype/antdv-cli/node_modules/@antdv-next/cli'));
   }
   candidates.push(path.join(location.project, 'node_modules/@antdv-next/cli'), path.resolve(path.dirname(process.execPath), '../lib/node_modules/@antdv-next/cli'));
   const env = options.env || process.env;

package/skills/i3-using-agent-skills/SKILL.md

@@ -33,7 +33,7 @@ Task arrives
     ├── New project/feature/change? ──→ i3-spec-driven-development
     ├── No quality bar written down? ──→ i3-constraint-driven-development
     ├── Have a spec, need tasks? ──────→ i3-planning-and-task-breakdown
-    ├── UI prototype work? ───────────→ i3-ui-prototype
+    ├── UI prototype work? ───────────→ i3-ui-demo
     ├── Implementing code? ────────────→ i3-incremental-implementation
     │   ├── UI work? ─────────────────→ i3-frontend-ui-engineering
     │   ├── API work? ────────────────→ i3-api-and-interface-design
@@ -184,7 +184,7 @@ Not every task needs every skill. A bug fix might only need: `i3-debugging-and-e
 | Define | i3-idea-refine | Refine ideas through structured divergent and convergent thinking |
 | Define | i3-spec-driven-development | Requirements and acceptance criteria before code |
 | Plan | i3-planning-and-task-breakdown | Decompose into small, verifiable tasks |
-| Prototype | i3-ui-prototype | Create, inspect and iterate reviewable UI prototypes |
+| Prototype | i3-ui-demo | Create, inspect and iterate reviewable UI prototypes |
 | Build | i3-incremental-implementation | Thin vertical slices, test each before expanding |
 | Build | i3-source-driven-development | Verify against official docs before implementing |
 | Build | i3-doubt-driven-development | Adversarial fresh-context review of every non-trivial decision |

package/.claude/commands/i3-prototype.md

@@ -1,23 +0,0 @@
----
-description: "在主会话中分析、创建、检查与迭代 UI 交互原型。"
-# i3-description-source: "description: Create, analyze, inspect and iterate UI prototypes in the main session"
----
-
-<!-- i3:zh-CN:start -->
-## 中文交互与输出
-
-默认使用简体中文回复，包括追问、选项说明、阶段进度、分析、规格、计划、验收、代码审查与发布报告。只有用户明确要求其他语言时才切换；输入中出现英文术语、代码或引用不构成切换语言的要求。
-下文的工程步骤、审批要求、退出条件和工具约束完整有效。英文示例中的人类可读标题、说明和占位内容在实际输出时应译为中文；保留原有信息与验证标准，不删减方法。
-Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、工具调用参数、JSON 键/类型/枚举、机器状态、测试期望字面量及引用原文保持原样。生成文档正文用中文，SPEC.md、tasks/plan.md、tasks/todo.md、CONSTRAINTS.md 等约定路径不改名。
-严重程度按原规则判断，面向用户可写“严重（Critical）”“必须修复（Required）”“小问题（Nit）”“可选（Optional）”“建议考虑（Consider）”“仅供参考（FYI）”；High/Medium/Low、APPROVE/REQUEST CHANGES 和 GO/NO-GO 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
-
-适用说明：在主会话中分析、创建、检查与迭代 UI 交互原型。
-<!-- i3:zh-CN:end -->
-
-Use the i3-ui-prototype skill in the main session for the user's request below. Follow its shared preflight, operation boundaries and applicable runtime workflow.
-
-$ARGUMENTS
-
-With no arguments use create; explicit analysis or read-only limits take precedence. Preserve the user's scope, manual edits, fixed inputs and approved baselines. Use supporting engineering, framework, design and browser skills as the working skill requires; keep its workflow and evidence requirements there.
-
-Create the prototype in the current session. Load the required frontend/framework/design Skills before implementation and use the browser Skill for interaction acceptance. Installed Hooks run automatically; do not inspect Hook internals, search host logs, or run a manual binding step. When a required Skill is missing, invoke it and retry; report an infrastructure failure briefly through the separate maintenance entry.

package/.gemini/commands/i3-prototype.toml

@@ -1,23 +0,0 @@
-description = "在主会话中分析、创建、检查与迭代 UI 交互原型。"
-# i3-description-source: "description = \"Create, analyze, inspect and iterate UI prototypes in the main session\""
-
-prompt = """
-<!-- i3:zh-CN:start -->
-## 中文交互与输出
-
-默认使用简体中文回复，包括追问、选项说明、阶段进度、分析、规格、计划、验收、代码审查与发布报告。只有用户明确要求其他语言时才切换；输入中出现英文术语、代码或引用不构成切换语言的要求。
-下文的工程步骤、审批要求、退出条件和工具约束完整有效。英文示例中的人类可读标题、说明和占位内容在实际输出时应译为中文；保留原有信息与验证标准，不删减方法。
-Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、工具调用参数、JSON 键/类型/枚举、机器状态、测试期望字面量及引用原文保持原样。生成文档正文用中文，SPEC.md、tasks/plan.md、tasks/todo.md、CONSTRAINTS.md 等约定路径不改名。
-严重程度按原规则判断，面向用户可写“严重（Critical）”“必须修复（Required）”“小问题（Nit）”“可选（Optional）”“建议考虑（Consider）”“仅供参考（FYI）”；High/Medium/Low、APPROVE/REQUEST CHANGES 和 GO/NO-GO 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
-
-适用说明：在主会话中分析、创建、检查与迭代 UI 交互原型。
-<!-- i3:zh-CN:end -->
-
-Use the i3-ui-prototype skill in the main session for the user's request below. Follow its shared preflight, operation boundaries and applicable runtime workflow.
-
-$ARGUMENTS
-
-With no arguments use create; explicit analysis or read-only limits take precedence. Preserve the user's scope, manual edits, fixed inputs and approved baselines. Use supporting engineering, framework, design and browser skills as the working skill requires; keep its workflow and evidence requirements there.
-
-Create the prototype in the current session. Load the required frontend/framework/design Skills before implementation and use the browser Skill for interaction acceptance. Installed Hooks run automatically; do not inspect Hook internals, search host logs, or run a manual binding step. When a required Skill is missing, invoke it and retry; report an infrastructure failure briefly through the separate maintenance entry.
-"""

package/commands/i3-prototype.toml

@@ -1,23 +0,0 @@
-description = "在主会话中分析、创建、检查与迭代 UI 交互原型。"
-# i3-description-source: "description = \"Create, analyze, inspect and iterate UI prototypes in the main session\""
-
-prompt = """
-<!-- i3:zh-CN:start -->
-## 中文交互与输出
-
-默认使用简体中文回复，包括追问、选项说明、阶段进度、分析、规格、计划、验收、代码审查与发布报告。只有用户明确要求其他语言时才切换；输入中出现英文术语、代码或引用不构成切换语言的要求。
-下文的工程步骤、审批要求、退出条件和工具约束完整有效。英文示例中的人类可读标题、说明和占位内容在实际输出时应译为中文；保留原有信息与验证标准，不删减方法。
-Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、工具调用参数、JSON 键/类型/枚举、机器状态、测试期望字面量及引用原文保持原样。生成文档正文用中文，SPEC.md、tasks/plan.md、tasks/todo.md、CONSTRAINTS.md 等约定路径不改名。
-严重程度按原规则判断，面向用户可写“严重（Critical）”“必须修复（Required）”“小问题（Nit）”“可选（Optional）”“建议考虑（Consider）”“仅供参考（FYI）”；High/Medium/Low、APPROVE/REQUEST CHANGES 和 GO/NO-GO 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
-
-适用说明：在主会话中分析、创建、检查与迭代 UI 交互原型。
-<!-- i3:zh-CN:end -->
-
-Use the i3-ui-prototype skill in the main session for the user's request below. Follow its shared preflight, operation boundaries and applicable runtime workflow.
-
-$ARGUMENTS
-
-With no arguments use create; explicit analysis or read-only limits take precedence. Preserve the user's scope, manual edits, fixed inputs and approved baselines. Use supporting engineering, framework, design and browser skills as the working skill requires; keep its workflow and evidence requirements there.
-
-Create the prototype in the current session. Load the required frontend/framework/design Skills before implementation and use the browser Skill for interaction acceptance. Installed Hooks run automatically; do not inspect Hook internals, search host logs, or run a manual binding step. When a required Skill is missing, invoke it and retry; report an infrastructure failure briefly through the separate maintenance entry.
-"""

package/docs/upstream-repository/AGENTS.md

@@ -1,92 +0,0 @@
-# AGENTS.md
-
-This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, Antigravity, etc.) when working with code in this repository.
-
-> **Scope:** This file configures agents working on the [`addyosmani/agent-skills`](https://github.com/addyosmani/agent-skills) repository itself. It is not meant to be copied into other projects or into a global agent configuration; the reusable assets are the skills in `skills/`, not this file.
-
-## Repository Overview
-
-A collection of skills for Claude.ai and Claude Code for senior software engineers. Skills are packaged instructions and scripts that extend Claude and your coding agents capabilities.
-
-## OpenCode Integration
-
-OpenCode uses a **skill-driven execution model** powered by the `skill` tool and this repository's `/skills` directory.
-
-### Core Rules
-
-- If a task matches a skill, you MUST invoke it
-- Skills are located in `skills/<skill-name>/SKILL.md`
-- Never implement directly if a skill applies
-- Always follow the skill instructions exactly (do not partially apply them)
-
-### Intent → Skill Mapping
-
-The agent should automatically map user intent to skills:
-
-- Feature / new functionality → `spec-driven-development`, then `incremental-implementation`, `test-driven-development`
-- Planning / breakdown → `planning-and-task-breakdown`
-- Bug / failure / unexpected behavior → `debugging-and-error-recovery`
-- Code review → `code-review-and-quality`
-- Refactoring / simplification → `code-simplification`
-- API or interface design → `api-and-interface-design`
-- UI work → `frontend-ui-engineering`
-
-### Lifecycle Mapping (Implicit Commands)
-
-OpenCode does not support slash commands like `/spec` or `/plan`.
-
-Instead, the agent must internally follow this lifecycle:
-
-- DEFINE → `spec-driven-development`
-- PLAN → `planning-and-task-breakdown`
-- BUILD → `incremental-implementation` + `test-driven-development`
-- VERIFY → `debugging-and-error-recovery`
-- REVIEW → `code-review-and-quality`
-- SHIP → `shipping-and-launch`
-
-### Execution Model
-
-For every request:
-
-1. Determine if any skill applies (even 1% chance)
-2. Invoke the appropriate skill using the `skill` tool
-3. Follow the skill workflow strictly
-4. Only proceed to implementation after required steps (spec, plan, etc.) are complete
-
-### Anti-Rationalization
-
-The following thoughts are incorrect and must be ignored:
-
-- "This is too small for a skill"
-- "I can just quickly implement this"
-- "I’ll gather context first"
-
-Correct behavior:
-
-- Always check for and use skills first
-
-This ensures OpenCode behaves similarly to Claude Code with full workflow enforcement.
-
-## Orchestration: Personas, Skills, and Commands
-
-This repo has three composable layers. They have different jobs and should not be confused:
-
-- **Skills** (`skills/<name>/SKILL.md`) — workflows with steps and exit criteria. The *how*. Mandatory hops when an intent matches.
-- **Personas** (`agents/<role>.md`) — roles with a perspective and an output format. The *who*.
-- **Slash commands** (`.claude/commands/*.md`) — user-facing entry points. The *when*. The orchestration layer.
-
-Composition rule: **the user (or a slash command) is the orchestrator. Personas do not invoke other personas.** A persona may invoke skills.
-
-The only multi-persona orchestration pattern this repo endorses is **parallel fan-out with a merge step** — used by `/ship` to run `code-reviewer`, `security-auditor`, and `test-engineer` concurrently and synthesize their reports. Do not build a "router" persona that decides which other persona to call; that's the job of slash commands and intent mapping.
-
-See [docs/agents.md](docs/agents.md) for the decision matrix and [references/orchestration-patterns.md](references/orchestration-patterns.md) for the full pattern catalog.
-
-**Claude Code interop:** the personas in `agents/` work as Claude Code subagents (auto-discovered from this plugin's `agents/` directory) and as Agent Teams teammates (referenced by name when spawning). Two platform constraints align with our rules: subagents cannot spawn other subagents, and teams cannot nest. Plugin agents silently ignore the `hooks`, `mcpServers`, and `permissionMode` frontmatter fields.
-
-## Creating a New Skill
-
-> **Before you start:** run the pre-flight checks in [CONTRIBUTING.md](CONTRIBUTING.md#before-proposing-a-new-skill), search the catalog, check open PRs (`gh pr list --state open`), confirm the idea fits [docs/skill-anatomy.md](docs/skill-anatomy.md), and justify the gap in your PR description. Most new-skill ideas overlap an existing skill or an open PR; prefer extending an existing skill over adding a near-duplicate. CONTRIBUTING.md is the single source of truth for this workflow.
-
-Skills in this repo are markdown-first: each lives at `skills/<kebab-case-name>/SKILL.md` with YAML frontmatter (`name`, `description`) and follows the section anatomy (Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification). Add a `scripts/` directory only when the skill ships runnable helpers; most skills are markdown only, and there are no per-skill zip packages.
-
-For the full format, naming conventions, frontmatter rules, supporting-file thresholds, and writing principles, see [docs/skill-anatomy.md](docs/skill-anatomy.md), the single source of truth for skill structure. Do not restate that guidance here, link to it.

package/docs/upstream-repository/CLAUDE.md

@@ -1,60 +0,0 @@
-# agent-skills
-
-This is the agent-skills project — a collection of production-grade engineering skills for AI coding agents.
-
-> **Scope:** This file configures agents working on the [`addyosmani/agent-skills`](https://github.com/addyosmani/agent-skills) repository itself, not other projects. Don't copy it into another project or a global agent configuration; the reusable assets are the skills in `skills/`.
-
-## Project Structure
-
-```
-skills/       → Core skills (SKILL.md per directory)
-agents/       → Reusable agent personas (code-reviewer, test-engineer, security-auditor, web-performance-auditor)
-hooks/        → Session lifecycle hooks
-.claude/commands/ → Slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship; plus /webperf specialist audit)
-references/   → Supplementary checklists (testing, performance, security, accessibility, observability)
-evals/        → Skill eval cases + framework (see evals/README.md)
-docs/         → Setup guides for different tools
-```
-
-## Skills by Phase
-
-**Define:** interview-me, idea-refine, spec-driven-development
-**Plan:** planning-and-task-breakdown
-**Build:** incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, frontend-ui-engineering, api-and-interface-design
-**Verify:** browser-testing-with-devtools, debugging-and-error-recovery
-**Review:** code-review-and-quality, code-simplification, security-and-hardening, performance-optimization
-**Ship:** git-workflow-and-versioning, ci-cd-and-automation, deprecation-and-migration, documentation-and-adrs, observability-and-instrumentation, shipping-and-launch
-
-## Conventions
-
-- Every skill lives in `skills/<name>/SKILL.md`
-- YAML frontmatter with `name` and `description` fields
-- Description starts with what the skill does (third person), followed by trigger conditions ("Use when...")
-- Every skill has: Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification
-- Shared references are in the root `references/` directory; the emerging convention for self-contained, distributable skills keeps a skill's own references inside `skills/<name>/references/`
-- Supporting files only created when content exceeds 100 lines
-
-## Contributing
-
-Before adding a new skill or significantly reworking an existing one, run the pre-flight checks in [CONTRIBUTING.md](CONTRIBUTING.md#before-proposing-a-new-skill): search the catalog, check open PRs, confirm the idea fits [docs/skill-anatomy.md](docs/skill-anatomy.md), and justify the gap. Prefer extending an existing skill over adding a near-duplicate. CONTRIBUTING.md is the single source of truth for this workflow; do not restate its checklist here or elsewhere, link to it.
-
-## Commands
-
-- `npm test` — Not applicable (this is a documentation project)
-- Validate: Check that all SKILL.md files have valid YAML frontmatter with name and description
-- Evals: `node scripts/run-evals.js` — trigger/routing evals for every skill (CI); `--behavioral <skill>` for graded runs
-
-## Pull Requests
-
-PRs target the upstream repository's default branch. In a typical fork setup the upstream remote is `upstream` and your fork is `origin`, but the exact remote names are not what matters here.
-
-- Before opening a PR, search the upstream repository's open PRs and issues for work that touches the same files or rules. If any overlaps, coordinate (build on it, align your rules with it, or rebase after it merges) instead of opening a conflicting PR.
-- Prefer small, focused PRs over large refactors of widely shared files (for example, files under `scripts/`), which are more likely to collide with in-flight work.
-
-## Boundaries
-
-- Always: Run the CONTRIBUTING.md pre-flight checks before creating a new skill directory
-- Always: Follow the skill-anatomy.md format for new skills
-- Always: Check the upstream repo's open PRs and issues for overlap before opening a new PR
-- Never: Add skills that are vague advice instead of actionable processes
-- Never: Duplicate content between skills — reference other skills instead

package/docs/upstream-repository/CONTRIBUTING.md

@@ -1,137 +0,0 @@
-# Contributing to Agent Skills
-
-Thanks for your interest in contributing! This project is a collection of production-grade engineering skills for AI coding agents.
-
-New here? [docs/developer-onboarding.md](docs/developer-onboarding.md) is a guided tour of how the repo fits together (the five layers, the verification loop, and the contribution paths) and tells you when to read this document, [skill-anatomy.md](docs/skill-anatomy.md), and [evals/README.md](evals/README.md). This file is the authoritative rulebook; the onboarding guide is the map.
-
-## Adding a New Skill
-
-### Before proposing a new skill
-
-This pack already covers most of the development lifecycle, and many proposals overlap with an existing skill or another open PR. Before opening one, do these checks so reviewers aren't triaging duplicates:
-
-1. **Search the catalog.** Browse [the skill list in the README](README.md) and skim `skills/` for an existing skill that covers your idea, whole or in part.
-2. **Check open PRs.** Run `gh pr list --state open` (or browse the PRs tab) and look for proposals on the same topic. Clusters of near-duplicate skills already exist; don't add to them.
-3. **Check rejected proposals.** Search the [skill-change rejection ledger](evals/skill-impact.md) for earlier proposals that overlap with your idea and review their eval evidence before repeating the work.
-4. **Read the anatomy.** Confirm your idea fits the format in [docs/skill-anatomy.md](docs/skill-anatomy.md), an actionable workflow with verification, not vague advice.
-5. **Justify the gap in your PR description.** State explicitly why this isn't covered by an existing skill, open PR, or previously rejected proposal. If it overlaps, propose extending the existing skill instead of adding a new one.
-6. **Strip model-specific workarounds.** If a step can't be justified without naming a model, a model version, or one agent's private tool name, it doesn't belong in a skill — describe the capability instead (see [Write the Procedure, Not the Workaround](docs/skill-anatomy.md#write-the-procedure-not-the-workaround)).
-
-If your idea is a refinement of an existing skill, prefer a focused edit to that skill over a new directory.
-
-### Creating the skill
-
-1. Create a directory under `skills/` with a kebab-case name
-2. Add a `SKILL.md` following the format in [docs/skill-anatomy.md](docs/skill-anatomy.md)
-3. Include YAML frontmatter with `name` and `description` fields, and no vendor or runtime keys at the top level (those go under `metadata` or in a per-agent adapter file; see [docs/advanced-per-agent-configuration.md](docs/advanced-per-agent-configuration.md))
-4. Ensure the `description` starts with what the skill does (third person), then includes one or more `Use when` trigger conditions
-
-### Skill Quality Bar
-
-Skills should be:
-
-- **Specific** — Actionable steps, not vague advice
-- **Verifiable** — Clear exit criteria with evidence requirements
-- **Battle-tested** — Based on real engineering workflows, not theoretical ideals
-- **Minimal** — Only the content needed to guide the agent correctly
-
-### Structure
-
-Every new skill must have:
-
-- `SKILL.md` in the skill directory
-- YAML frontmatter with valid `name` and `description`
-- An eval case file at `evals/cases/<skill-name>.json` — at least 3 positive triggers, 2 negative triggers (with `owner` where possible), and 1 behavioral eval. Execution evals must be backed by real files under `evals/fixtures/`; conversation-shaped skills may use a reviewer-gated `kind: "dialogue"` eval instead (see [evals/README.md](evals/README.md)). CI enforces these requirements.
-
-New skills should generally follow the standard anatomy:
-
-- **Overview** — What this skill does and why it matters
-- **When to Use** — Triggering conditions
-- **Process** — Step-by-step workflow
-- **Common Rationalizations** — Excuses agents use to skip steps, with rebuttals
-- **Red Flags** — Warning signs that the skill is being applied incorrectly
-- **Verification** — How to confirm the skill was applied correctly
-
-The frontmatter fields above are required. The section anatomy is a recommended pattern: equivalent headings such as `How It Works`, `Workflow`, or `Core Process` are fine when they preserve the same intent and keep the skill easy to follow.
-
-### What Not to Do
-
-- Don't duplicate content between skills — reference other skills instead
-- Don't add skills that are vague advice instead of actionable processes
-- Don't create supporting files unless content exceeds 100 lines
-- Don't create an empty `scripts/` directory just to match another skill — add `scripts/` only when the skill includes runnable helpers
-- Don't put reference material inside skill directories — use `references/` instead
-
-## Modifying Existing Skills
-
-Before proposing a change, search the [skill-change rejection ledger](evals/skill-impact.md) for previous attempts affecting the same skill and review their eval evidence.
-
-- Keep changes focused and minimal
-- Preserve the existing structure and tone
-- Test that YAML frontmatter remains valid after edits
-
-If a skill or description change is rejected based on eval results, add one row to the ledger with the date, affected skill, concise attempted change, before-to-after rank-1 score, and rejected PR link and outcome. Land that ledger-only update separately on the default branch; do not leave it only on the rejected proposal branch, where closing or force-pushing the proposal could discard the record.
-
-## Adding a Host Guide
-
-The README install section lists only hosts a maintainer has installed and run the current release on. Every other host gets one line in [docs/other-hosts.md](docs/other-hosts.md): the host name and its install command. No dedicated setup page, vendor links, logos, emoji, or screenshots.
-
-- If you work for the company behind the host, say so in the PR.
-- A host moves into the README once a maintainer has run it and is willing to keep its entry current.
-- Host guides are reviewed in the order they were opened.
-
-## Repo-scoped files
-
-`AGENTS.md` and `CLAUDE.md` at the repo root configure agents working on the [`addyosmani/agent-skills`](https://github.com/addyosmani/agent-skills) repository itself. When writing setup guides or docs, do not instruct users to copy these files into their own projects or into a global agent configuration; the reusable assets are the skills in `skills/`.
-
-## Translations
-
-We don't accept translations of the documentation (README, `docs/`) or of skills and their content. Translated copies drift out of sync as skills and docs evolve, and we have no way to maintain them long-term without leaning on agent translations plus community corrections, which adds maintenance cost for limited value. Keep all skills, docs, and contributions in English.
-
-## Testing Hooks
-
-The session-start script (`hooks/session-start.sh`) injects the `using-agent-skills` meta-skill when wired into a host's `SessionStart` hook. The Claude Code plugin does not register it — Claude Code routes skills natively, and always-on injection would create two routers for the same task (see [docs/getting-started.md](docs/getting-started.md)); the script remains for hosts without native skill routing. A regression test at `hooks/session-start-test.sh` validates the script's JSON payload — both when `jq` is available and when it isn't.
-
-Run it before opening any PR that touches:
-
-- `hooks/session-start.sh`
-- `skills/using-agent-skills/SKILL.md` (the meta-skill content embedded by the hook)
-
-```bash
-bash hooks/session-start-test.sh
-```
-
-Expected output: `session-start JSON payload OK`. The script exits non-zero on any assertion failure.
-
-### Reproducing the no-jq fallback
-
-The hook still emits the same `hookSpecificOutput` envelope when `jq` isn't on `PATH`, with `additionalContext` explaining that `jq` is required. To exercise that branch locally, strip `jq`'s directory from `PATH` for the test invocation:
-
-```bash
-JQ_DIR=$(dirname "$(command -v jq)")
-PATH=$(echo "$PATH" | tr ':' '\n' | grep -v "^${JQ_DIR}$" | tr '\n' ':' | sed 's/:$//') \
-  bash hooks/session-start-test.sh
-```
-
-This works cleanly when `jq` lives in its own directory (e.g. `/opt/homebrew/bin` from Homebrew, `/usr/local/bin` from a manual install). If your `jq` shares a system bin with other tools the test depends on (such as `mktemp` in `/usr/bin`), the simpler approach is to install `jq` via a separate package manager so it has its own bin directory, then re-run.
-
-The hook's `command -v jq` check fails under the stripped `PATH`, the jq-missing fallback runs, and the test asserts the `jq is required` guidance in `additionalContext` instead of the meta-skill body.
-
-## Reporting Issues
-
-Open an issue if you find:
-
-- A skill that gives incorrect or outdated guidance
-- Missing coverage for a common engineering workflow
-- Inconsistencies between skills
-
-If a skill's guidance was wrong, outdated, or did not apply in your project
-(for example, it assumed `npm test` in a Maven or Gradle repo), use the
-[Skill gap](https://github.com/addyosmani/agent-skills/issues/new?template=skill-gap.yml)
-issue form. It asks for the affected skill, the relevant excerpt, your project
-context, and what you did instead — enough for maintainers to triage without a
-freeform write-up.
-
-## License
-
-By contributing, you agree that your contributions will be licensed under the MIT License.

package/docs/upstream-repository/README.md

@@ -1,8 +0,0 @@
-# 上游原版仓库资料
-
-来源：addyosmani/agent-skills，固定提交 aeac41d4d005999432bb7312f7ff06383a91d59d。
-
-本目录保留原版仓库规则、贡献资料和配置的完整原文字节，供阅读和恢复；不会注册为业务项目或宿主的活动规则。
-文件对应关系、原始路径、Git 模式和摘要见 manifest.json。gitignore.txt、gitattributes.txt 使用可随包交付的文件名。
-opencode-skills.link 保存原链接目标 ../skills/，manifest.json 保留其 120000 模式；这是可恢复的链接表示，实际技能发现继续使用所选宿主的登记。
-此处的命令、路径和文档链接保留上游语境，需结合完整上游仓库阅读；不把它们当成本项目的执行指令。

package/docs/upstream-repository/gitattributes.txt

@@ -1 +0,0 @@
-* text=auto eol=lf

package/docs/upstream-repository/gitignore.txt

@@ -1,10 +0,0 @@
-.DS_Store
-node_modules/
-.env
-.env.*
-*.log
-.claude/.simplify-ignore-cache/
-.claude/sdd-cache/
-evals/results/
-evals/plugin/results/
-__pycache__/

package/docs/upstream-repository/manifest.json

@@ -1,71 +0,0 @@
-{
-  "schemaVersion": 1,
-  "upstreamCommit": "aeac41d4d005999432bb7312f7ff06383a91d59d",
-  "files": [
-    {
-      "path": "AGENTS.md",
-      "preservedPath": "docs/upstream-repository/AGENTS.md",
-      "mode": "100644",
-      "blob": "e97670ed868e90b73753fafbe305cdabc7f55ad3",
-      "sha256": "a12bac68c447f8043a75c2259175b36a57a37617a5ab92900ab1e3e9afa381be"
-    },
-    {
-      "path": "CLAUDE.md",
-      "preservedPath": "docs/upstream-repository/CLAUDE.md",
-      "mode": "100644",
-      "blob": "97674d0b173c7c25764e11dc816a298a63119594",
-      "sha256": "f03b7aaf2c08ab93e70a020442634a09f518286ff1beb7b8353dde92533ff9b0"
-    },
-    {
-      "path": "CONTRIBUTING.md",
-      "preservedPath": "docs/upstream-repository/CONTRIBUTING.md",
-      "mode": "100644",
-      "blob": "3c3a015be673a04efd8647c201acfbb2fad7189a",
-      "sha256": "fe5d17011565e9cfeb8a02510c81a243f3e4d829b800e2eab239039fcac214e7"
-    },
-    {
-      "path": ".gitattributes",
-      "preservedPath": "docs/upstream-repository/gitattributes.txt",
-      "mode": "100644",
-      "blob": "6313b56c57848efce05faa7aa7e901ccfc2886ea",
-      "sha256": "d60f352d0db1404c70afb4bb8b2ca3fd1c610572aa40720e8a0b7baa7885418c"
-    },
-    {
-      "path": ".gitignore",
-      "preservedPath": "docs/upstream-repository/gitignore.txt",
-      "mode": "100644",
-      "blob": "167e5ad35e10c75795667a7b71c950eda641cdd8",
-      "sha256": "09bc8ca679551d8d723abeaadf303f3dcdaf93b94d0ad211873942a47c8559a2"
-    },
-    {
-      "path": ".claude/rules/skills-contributing.md",
-      "preservedPath": "docs/upstream-repository/skills-contributing.md",
-      "mode": "100644",
-      "blob": "8553dc3b0d4aba42f014605b488097b6e06e9060",
-      "sha256": "6f8ff659388c3b957322ac46f788ff16d996e5c751f71a6c1e59e4761c437bbd"
-    },
-    {
-      "path": ".github/ISSUE_TEMPLATE/skill-gap.yml",
-      "preservedPath": "docs/upstream-repository/skill-gap.yml",
-      "mode": "100644",
-      "blob": "dac6216a5ace3cd1f34bb2b9a753c6f133592892",
-      "sha256": "f6a7748bfe8a1a43c42c7a5e7317c66689b66afd514ee091eb6f8ce07e46d5a4"
-    },
-    {
-      "path": ".github/workflows/test-plugin-install.yml",
-      "preservedPath": "docs/upstream-repository/test-plugin-install.yml",
-      "mode": "100644",
-      "blob": "b25ba319a8d371c6c1924f8b75173bb319313ab2",
-      "sha256": "fe1437efbdd99bd9ea1fa2bf79aa921f8bdd68a067802e4b41af531a3aa39597"
-    },
-    {
-      "path": ".opencode/skills",
-      "preservedPath": "docs/upstream-repository/opencode-skills.link",
-      "mode": "120000",
-      "blob": "7fc7d9f7be858ee62e454c529b3f8deddd83e1d2",
-      "sha256": "9d36d6a253d6844eb107d26dc0dcd8252808449433b251eceb14cee3517a185a",
-      "target": "../skills/",
-      "representation": "serialized-symlink"
-    }
-  ]
-}

package/docs/upstream-repository/opencode-skills.link

@@ -1 +0,0 @@
-../skills/