minimal-agent 0.1.0

package/skills/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/skills/frontend-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
+
+**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
+
+Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/skills/init/SKILL.md

@@ -0,0 +1,238 @@
+---
+name: init
+description: 项目初始化技能。当用户输入 "/init" 且没有任何其他内容时触发。用于分析当前项目结构并生成 minimal-agent.md 项目文档。
+---
+
+# Init Skill
+
+当用户输入 `/init` 时触发，执行以下任务：
+
+1. 分析项目目录结构
+2. 识别技术栈和框架
+3. 提取关键配置文件和入口点
+4. 深入理解核心模块的运作机制
+5. 生成或更新 `minimal-agent.md` 项目文档
+
+---
+
+## 执行步骤
+
+### Step 1: 分析项目结构
+
+使用 Glob 扫描项目，识别：
+- 源码目录结构（src/、lib/、app/ 等）
+- 配置文件
+- 根目录的文档文件
+- 测试文件位置
+
+扫描策略：
+- 根据语言类型选择对应的源码目录（TS/JS 用 src/，Python 用 lib/ 或直接是 .py 文件）
+- 根据语言类型识别配置文件（TS 用 tsconfig.json，Python 用 pyproject.toml 或 requirements.txt）
+
+### Step 2: 识别技术栈
+
+读取项目根目录的配置文件（根据语言类型选择）：
+- `package.json` → Node.js/Bun 项目
+- `pyproject.toml` / `requirements.txt` → Python 项目
+- `Cargo.toml` → Rust 项目
+- `go.mod` → Go 项目
+
+识别要点：
+- 运行时（Node.js / Bun / Deno / Python / Rust / Go）
+- 语言（TypeScript / JavaScript / Python / Rust / Go 等）
+- 框架
+- 构建工具/包管理器
+
+### Step 3: 提取项目元信息
+
+从以下位置提取：
+- `package.json` / `pyproject.toml` / `Cargo.toml` → 项目名、版本、描述
+- `README.md` → 项目简介（如果存在）
+- `CLAUDE.md` → 如果存在，参考其描述风格（尤其是"核心架构"部分的深度）
+- 根目录的 `*.md` 文件 → 了解项目文档结构
+
+### Step 4: 深入理解核心模块
+
+这是最关键的一步。
+
+**识别核心模块的方法**：
+1. 找到程序入口文件（名字可能是 main、index、app、run、start 等）
+2. 找到类型定义文件（types、models、schemas 等）
+3. 找到配置管理文件（config、settings、env 等）
+4. 识别主要的功能目录（如 tools/、services/、handlers/ 等）
+
+**读取文件的原则**：
+- 不硬编码文件名，根据项目实际情况推断
+- 优先读取：有顶部大段注释的文件（通常包含设计意图）
+- 优先读取：入口文件和类型定义文件
+- 用文件名和目录结构推断模块职责
+
+**需要提取的关键信息**：
+
+| 模块类型 | 需要了解的内容 |
+|----------|---------------|
+| 主循环/入口 | 工作流程、关键步骤、核心函数 |
+| 客户端/通信 | 协议、接口格式、关键函数 |
+| 工具/功能集合 | 工具列表、注册方式、参数校验 |
+| 上下文管理 | 触发条件、保留策略、关键函数 |
+| UI/界面 | 组件结构、状态管理 |
+
+**判断模块类型的信号**：
+- 文件名含 `loop`、`main`、`run`、`start` → 主循环类型
+- 文件名含 `client`、`http`、`request`、`api` → 通信类型
+- 目录名含 `tools`、`handlers`、`commands` → 工具类型
+- 文件名含 `context`、`memory`、`history` → 上下文类型
+
+### Step 5: 提取设计原则
+
+从以下位置提取：
+- 关键文件顶部的大段注释（通常描述设计理念）
+- README.md 中的设计理念
+- 代码注释（TODO、FIXME、NOTE 等标记）
+
+---
+
+## 生成 minimal-agent.md
+
+### 文档结构
+
+```markdown
+# [项目名]
+
+> [一句话项目简介，从项目配置或 README 提取]
+
+## 技术栈
+
+- **运行时**: [根据项目实际填写]
+- **语言**: [根据项目实际填写]
+- **框架**: [根据项目实际填写]
+- **构建工具/包管理器**: [根据项目实际填写]
+- **其他关键依赖**: [列出 2-4 个重要依赖]
+
+## 项目结构
+
+```
+[项目名]/
+├── [主要源码目录]
+│   ├── [按功能划分的子目录或文件]
+│   └── ...
+├── [其他目录]
+└── 配置文件
+```
+
+## 快速开始
+
+```bash
+[根据项目实际命令填写]
+```
+
+## 环境配置
+
+[如果有 .env.example 或类似配置，提取环境变量]
+
+## 核心架构
+
+[对于每个核心模块，详细描述其运作机制]
+
+### [模块名]
+
+[一段话描述模块的职责和定位]
+
+[根据模块类型选择描述方式]
+- **主循环类型**：列出关键步骤（1. 2. 3. ...）
+- **工具类型**：列出工具/功能列表和重要特性
+- **通信类型**：描述协议、接口格式
+- **数据处理类型**：描述数据流向
+
+关键函数/类：
+- `[名称]` — [一句话描述]
+
+## 设计原则
+
+- [从代码或文档中提取的设计原则，每条一句话]
+
+## 维护提示
+
+> ⚠️ 本文档由 `/init` 自动生成，是了解项目的**线索**而非**真理**。随着项目演进，内容可能变得不准确。涉及代码的具体实现，请在实际使用中核实相关源文件。
+```
+
+### 内容质量要求（核心）
+
+**项目简介**：
+- 一句话说清楚项目做什么
+- 说明项目的定位（学习用/生产用/工具类等）
+
+**技术栈**：
+- 只列出最重要的 4-6 项
+- 用「**运行时**」「**语言**」「**框架**」等标签
+
+**项目结构**：
+- 用目录树展示，不列出具体文件
+- 根据项目实际结构描述（不一定是 src/，可能是 lib/ 或直接是根目录的源文件）
+- 用 `...` 省略次要文件
+
+**快速开始**：
+- 只列出最核心的 4-6 个命令
+- 根据项目类型填写（Python 可能是 `pip install` + `python main.py`，Rust 可能是 `cargo build` + `./target/...`）
+
+**核心架构（最重要！）**：
+- 这部分是让 agent 能够"修改项目"的关键
+- 根据实际识别的模块来描述，不拘泥于固定数量
+- 每个模块用"###"小标题
+- 描述模块职责和定位（一段话）
+- **主循环类型**：列出关键步骤
+- **工具类型**：列出工具列表和特性
+- **关键函数/类**：用列表展示名称和一句话描述
+
+**设计原则**：
+- 只保留真正重要的设计决策
+- 每条原则一行，简洁明了
+- 3-5 条足够
+
+### 写作风格
+
+**参考 CLAUDE.md 的写作风格**：
+
+✅ 好的描述：
+- "当 context 接近上限（contextWindow - 13000 token）时触发压缩"
+- "基于 `Tool` 接口（name / description / inputSchema / parameters / call）"
+
+❌ 糟糕的描述：
+- "这是一个处理文件的模块"（太模糊）
+- "通过某种方式实现了功能"（太模糊）
+
+**写作原则**：
+- 写"是什么"和"为什么"，不写"怎么做"
+- 用具体数字/名称，不写"[某个值]"
+- 让读者知道改哪里、怎么改
+
+---
+
+## 已有文件处理
+
+**如果 `minimal-agent.md` 已存在：**
+
+1. **读取现有内容**，对比新分析的结果
+2. **识别差异**：
+   - 哪些部分过时了（技术栈变化、模块重构等）
+   - 哪些部分仍然有效
+   - 哪些新内容需要添加
+3. **编辑更新**（而非覆盖）：
+   - **保留**：用户之前强调过的规则、设计原则、特殊约定
+   - **删除**：过时的模块、不再使用的配置、错误的描述
+   - **补充**：新发现的模块、新增的配置、更新后的命令
+4. **保持结构一致**：尽量保留原文档的结构，只做局部修改
+5. **不改动用户强调的内容**：如果文件中用户用特殊标记（如「注意」「警告」「重要」）强调的内容，要保留
+
+**如果 `minimal-agent.md` 不存在：**
+- 按照上面的模板生成新文件
+
+---
+
+## 输出要求
+
+- 输出文件：`minimal-agent.md`（项目根目录）
+- 使用中文编写
+- 保持简洁，但核心架构部分要有深度
+- 不写具体实现细节，但要让读者知道如何修改
+- 文件长度建议 100-150 行

package/skills/init/evals/evals.json

@@ -0,0 +1,28 @@
+{
+  "skill_name": "init",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "/init",
+      "expected_output": "生成或更新项目根目录的 minimal-agent.md 文件，包含：项目简介、技术栈、项目结构、快速开始命令、环境配置、核心模块",
+      "files": [],
+      "expectations": [
+        "生成了 minimal-agent.md 文件",
+        "文件包含技术栈信息",
+        "文件包含快速开始命令",
+        "使用中文编写"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "/init",
+      "expected_output": "对于已存在的 minimal-agent.md，应进行编辑更新：删除过时内容、保留有效内容、补充新内容",
+      "files": [],
+      "expectations": [
+        "没有覆盖整个文件，而是局部编辑",
+        "更新了变化的技术栈或模块信息",
+        "保留了仍然正确的设计原则"
+      ]
+    }
+  ]
+}