npm - @alanwang-merit/meritdata-platform-skill-package - Versions diffs - 1.0.10 → 1.0.12 - Mend

@alanwang-merit/meritdata-platform-skill-package 1.0.10 → 1.0.12

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.

Files changed (631) hide show

package/skills/meritdata-platform-ui-components/references/guide.md DELETED Viewed

@@ -1,199 +0,0 @@
-# 平台 UI 组件基础指南（ui-components）
-> 平台 UI 组件基于 antd 封装，统一了人员、组织、字典、上传等通用场景。
----
-## 1. 引入
-```bash
-npm install @meritdata/platform-ui-components
-```
-```typescript
-import { UserPicker, OrgTreeSelect, LookupSelect, Upload } from '@meritdata/platform-ui-components';
-```
-## 2. 组件清单
-| 组件 | 用途 | 替代自实现 |
-|------|------|-----------|
-| UserPicker | 人员选择（单/多）| ✅ |
-| OrgTreeSelect | 组织树下拉 | ✅ |
-| LookupSelect | 字典下拉 | ✅ |
-| LookupCascader | 字典级联 | ✅ |
-| Upload | 文件上传 | ✅ |
-| BpmnDesigner | 流程设计器 | ✅ |
-| RichTextEditor | 富文本编辑器 | ✅ |
-| DateRangePicker | 日期范围 | 部分 |
-| DataTable | 业务表格（含权限列）| ✅ |
-| AuthButton | 按钮（带权限）| ✅ |
-## 3. UserPicker
-### 3.1 基本用法
-```tsx
-import { UserPicker } from '@meritdata/platform-ui-components';
-<Form.Item label="负责人" name="ownerId">
-  <UserPicker
-    multiple={false}
-    orgId={currentOrgId}
-    placeholder="选择负责人"
-  />
-</Form.Item>
-```
-### 3.2 Props
-| Prop | 类型 | 默认 | 说明 |
-|------|------|------|------|
-| multiple | boolean | false | 是否多选 |
-| orgId | string | - | 限定组织范围 |
-| roleCode | string | - | 限定角色范围 |
-| disabled | boolean | false | 禁用 |
-| excludeUserIds | string[] | - | 排除某些用户 |
-### 3.3 返回值
-```typescript
-{
-  userId: '10001',
-  realName: '张三',
-  username: 'zhangsan',
-  orgName: '研发部'
-}
-```
-## 4. OrgTreeSelect
-```tsx
-import { OrgTreeSelect } from '@meritdata/platform-ui-components';
-<Form.Item label="所属部门" name="orgId">
-  <OrgTreeSelect
-    multiple={false}
-    showLeafOnly={false}
-    placeholder="选择部门"
-  />
-</Form.Item>
-```
-Props：
-| Prop | 类型 | 说明 |
-|------|------|------|
-| multiple | boolean | 多选 |
-| showLeafOnly | boolean | 只显示叶子节点 |
-| rootOrgId | string | 根节点（限制范围）|
-## 6. LookupSelect
-```tsx
-import { LookupSelect } from '@meritdata/platform-ui-components';
-<Form.Item label="订单状态" name="status">
-  <LookupSelect typeCode="ORDER_STATUS" placeholder="选择状态" />
-</Form.Item>
-```
-Props：
-| Prop | 类型 | 说明 |
-|------|------|------|
-| typeCode | string | 字典类型编码 |
-| multiple | boolean | 多选 |
-| showCode | boolean | 是否显示 code |
-## 7. Upload
-### 7.1 基本用法
-```tsx
-import { Upload } from '@meritdata/platform-ui-components';
-<Upload
-  bizType="ORDER_ATTACHMENT"
-  bizId={orderId}
-  accept=".pdf,.doc,.docx"
-  maxSize={50}              // 50 MB
-  onChange={(files) => console.log(files)}
-/>
-```
-### 7.2 平台上传组件特性
-- 自动关联业务（bizType + bizId）
-- 集成平台存储（OSS / 本地）
-- 自动生成缩略图（图片类型）
-- 病毒扫描（可选）
-## 8. AuthButton（带权限）
-```tsx
-import { AuthButton } from '@meritdata/platform-ui-components';
-<AuthButton permission="order:approve" type="primary" onClick={handleApprove}>
-  审批
-</AuthButton>
-```
-无权限 → 按钮不显示。
-## 9. DataTable
-### 9.1 用法
-```tsx
-import { DataTable } from '@meritdata/platform-ui-components';
-<DataTable
-  columns={[
-    { title: '订单号', dataIndex: 'orderNo' },
-    {
-      title: '金额',
-      dataIndex: 'amount',
-      sensitive: true,           // 自动脱敏
-      permission: 'order:cost:view'  // 仅财务可见
-    }
-  ]}
-  dataSource={orders}
-  pageSize={20}
-/>
-```
-## 10. ❌ 反模式
-### 10.1 ❌ 自实现人员选择器
-```tsx
-// ❌ 错：自己写人员选择 + 接口调用
-const <Select onClick="fetchUsers" />
-```
-✅ 用 `UserPicker`。
-### 10.2 ❌ 自实现权限按钮
-```tsx
-// ❌ 错
-{permissions.includes('order:approve') && <Button>审批</Button>}
-```
-✅ 用 `AuthButton`。
-### 10.3 ❌ 自实现上传
-```tsx
-// ❌ 错：自己写 upload + 调 OSS
-const <input type="file" onClick="handleUpload" />
-```
-✅ 用 `Upload`（关联 bizType + 病毒扫描）。
-## 11. 关联阅读
-- [business-wrappers.md](business-wrappers.md) — 业务组件封装
-- [theme-and-i18n.md](theme-and-i18n.md) — 主题定制 + 国际化
-- [SKILL.md](../SKILL.md)

package/skills/meritdata-platform-ui-components/references/theme-and-i18n.md DELETED Viewed

@@ -1,226 +0,0 @@
-# 主题定制与国际化（ui-components）
-> 主题令牌（design token）/ 国际化（i18n）/ 暗色模式。
----
-## 1. Design Token
-### 1.1 平台默认令牌
-```typescript
-// @meritdata/platform-ui-components/theme/tokens.ts
-export const tokens = {
-  colorPrimary: '#1890ff',
-  colorSuccess: '#52c41a',
-  colorWarning: '#faad14',
-  colorError: '#ff4d4f',
-  colorInfo: '#1890ff',
-  fontSize: 14,
-  borderRadius: 4,
-  spacing: {
-    xs: 4,
-    sm: 8,
-    md: 16,
-    lg: 24,
-    xl: 32,
-  },
-};
-```
-### 1.2 使用
-```tsx
-import { theme } from 'antd';
-import { tokens } from '@meritdata/platform-ui-components/theme';
-const { token } = theme.useToken();
-<Button style={{ backgroundColor: tokens.colorPrimary }}>
-  主要按钮
-</Button>
-```
-### 1.3 业务定制
-```typescript
-// business-ui-components/theme.ts
-export const businessTokens = {
-  ...tokens,
-  colorPrimary: '#FF6B35',     // 业务色
-  fontSize: 13,
-  borderRadius: 6,
-};
-// 全局覆盖
-import { ConfigProvider } from 'antd';
-<ConfigProvider theme={{ token: businessTokens }}>
-  <App />
-</ConfigProvider>
-```
-## 2. 暗色模式
-### 2.1 平台支持
-```tsx
-import { ConfigProvider, theme as antdTheme } from 'antd';
-<ConfigProvider
-  theme={{
-    algorithm: isDark ? antdTheme.darkAlgorithm : antdTheme.defaultAlgorithm,
-  }}
->
-  <App />
-</ConfigProvider>
-```
-### 2.2 切换按钮
-```tsx
-import { Switch } from 'antd';
-import { useTheme } from '@/hooks/useTheme';
-const { isDark, toggleTheme } = useTheme();
-<Switch
-  checked={isDark}
-  onChange={toggleTheme}
-  checkedChildren="🌙"
-  unCheckedChildren="☀️"
-/>
-```
-### 2.3 业务组件适配
-```tsx
-import { theme } from 'antd';
-const { token } = theme.useToken();
-<Card style={{ backgroundColor: token.colorBgContainer }}>
-  ...
-</Card>
-```
-## 3. 国际化（i18n）
-### 3.1 平台 i18n 配置
-```typescript
-// @meritdata/platform-ui-components/locale/
-import zh_CN from '@meritdata/platform-ui-components/locale/zh_CN';
-import en_US from '@meritdata/platform-ui-components/locale/en_US';
-<ConfigProvider locale={currentLocale}>
-  <App />
-</ConfigProvider>
-```
-### 3.2 业务 i18n（react-i18next）
-```bash
-npm install react-i18next i18next
-```
-```typescript
-// i18n/config.ts
-import i18n from 'i18next';
-import { initReactI18next } from 'react-i18next';
-import zh_CN from './locales/zh_CN.json';
-import en_US from './locales/en_US.json';
-i18n.use(initReactI18next).init({
-  resources: {
-    'zh-CN': { translation: zh_CN },
-    'en-US': { translation: en_US },
-  },
-  lng: localStorage.getItem('lang') || 'zh-CN',
-  fallbackLng: 'zh-CN',
-});
-```
-### 3.3 使用
-```tsx
-import { useTranslation } from 'react-i18next';
-const { t } = useTranslation();
-<Button>{t('order.create')}</Button>
-<LookupSelect typeCode="ORDER_STATUS" placeholder={t('order.status.placeholder')} />
-```
-### 3.4 字典项多语言
-字典项支持多语言（详见 [lookup-api tree-and-i18n](../meritdata-platform-lookup-api/references/tree-and-i18n.md)）：
-```typescript
-<LookupSelect
-  typeCode="ORDER_STATUS"
-  lang={currentLang}
-/>
-```
-## 4. 主题与 i18n 集成
-```tsx
-import { ConfigProvider } from 'antd';
-import { useTranslation } from 'react-i18next';
-import { useTheme } from '@/hooks/useTheme';
-const App: React.FC = () => {
-  const { i18n } = useTranslation();
-  const { isDark } = useTheme();
-  return (
-    <ConfigProvider
-      locale={getAntdLocale(i18n.language)}
-      theme={{ algorithm: isDark ? darkAlgorithm : defaultAlgorithm }}
-    >
-      <Router />
-    </ConfigProvider>
-  );
-};
-```
-## 5. ❌ 反模式
-### 5.1 ❌ 硬编码颜色
-```tsx
-// ❌ 错
-<Button style={{ backgroundColor: '#1890ff' }}>提交</Button>
-```
-✅ 用 design token。
-### 5.2 ❌ 硬编码文案
-```tsx
-// ❌ 错
-<Button>提交</Button>
-```
-✅ 用 i18n：`{t('common.submit')}`。
-### 5.3 ❌ 多语言未覆盖所有语言
-```json
-// ❌ 错：zh-CN 有 100 条，en-US 只有 50 条
-{
-  "zh-CN": {...100条...},
-  "en-US": {...50条...}
-}
-```
-✅ 关键文案双语 100% 覆盖。
-## 6. 关联阅读
-- [guide.md](guide.md) — 平台组件基础
-- [business-wrappers.md](business-wrappers.md) — 业务组件封装
-- [SKILL.md](../SKILL.md)

package/skills/prototype/LOGIC.md DELETED Viewed

@@ -1,79 +0,0 @@
-# Logic Prototype
-A tiny interactive terminal app that lets the user drive a state model by hand. Use this when the question is about **business logic, state transitions, or data shape** — the kind of thing that looks reasonable on paper but only feels wrong once you push it through real cases.
-## When this is the right shape
-- "I'm not sure if this state machine handles the edge case where X then Y."
-- "Does this data model actually let me represent the case where..."
-- "I want to feel out what the API should look like before writing it."
-- Anything where the user wants to **press buttons and watch state change**.
-If the question is "what should this look like" — wrong branch. Use [UI.md](UI.md).
-## Process
-### 1. State the question
-Before writing code, write down what state model and what question you're prototyping. One paragraph, in the prototype's README or a comment at the top of the file. A logic prototype that answers the wrong question is pure waste — make the question explicit so it can be checked later, whether the user is watching now or returning to it AFK.
-### 2. Pick the language
-Use whatever the host project uses. If the project has no obvious runtime (e.g. a docs repo), ask.
-Match the project's existing conventions for tooling — don't add a new package manager or runtime just for the prototype.
-### 3. Isolate the logic in a portable module
-Put the actual logic — the bit that's answering the question — behind a small, pure interface that could be lifted out and dropped into the real codebase later. The TUI around it is throwaway; the logic module shouldn't be.
-The right shape depends on the question:
-- **A pure reducer** — `(state, action) => state`. Good when actions are discrete events and state is a single value.
-- **A state machine** — explicit states and transitions. Good when "which actions are even legal right now" is part of the question.
-- **A small set of pure functions** over a plain data type. Good when there's no implicit current state — just transformations.
-- **A class or module with a clear method surface** when the logic genuinely owns ongoing internal state.
-Pick whichever shape best fits the question being asked, *not* whichever is easiest to wire to a TUI. Keep it pure: no I/O, no terminal code, no `console.log` for control flow. The TUI imports it and calls into it; nothing flows the other direction.
-This is what makes the prototype useful past its own lifetime: when the question's been answered, the validated reducer / machine / function set can be lifted into the real module on its own.
-### 4. Build the smallest TUI that exposes the state
-Build it as a **lightweight TUI** — on every tick, clear the screen (`console.clear()` / `print("\033[2J\033[H")` / equivalent) and re-render the whole frame. The user should always see one stable view, not an ever-growing scrollback.
-Each frame has two parts, in this order:
-1. **Current state**, pretty-printed and diff-friendly (one field per line, or formatted JSON). Use **bold** for field names or section headers and **dim** for less important context (timestamps, IDs, derived values). Native ANSI escape codes are fine — `\x1b[1m` bold, `\x1b[2m` dim, `\x1b[0m` reset. No need to pull in a styling library unless one is already in the project.
-2. **Keyboard shortcuts**, listed at the bottom: `[a] add user  [d] delete user  [t] tick clock  [q] quit`. Bold the key, dim the description, or vice-versa — whatever reads cleanly.
-Behaviour:
-1. **Initialise state** — a single in-memory object/struct. Render the first frame on start.
-2. **Read one keystroke (or one line)** at a time, dispatch to a handler that mutates state.
-3. **Re-render** the full frame after every action — don't append, replace.
-4. **Loop until quit.**
-The whole frame should fit on one screen.
-### 5. Make it runnable in one command
-Add a script to the project's existing task runner (`package.json` scripts, `Makefile`, `justfile`, `pyproject.toml`). The user should run `pnpm run <prototype-name>` or equivalent — never need to remember a path.
-If the host project has no task runner, just put the command at the top of the prototype's README.
-### 6. Hand it over
-Give the user the run command. They'll drive it themselves; the interesting moments are when they say "wait, that shouldn't be possible" or "huh, I assumed X would be different" — those are the bugs in the _idea_, which is the whole point. If they want new actions added, add them. Prototypes evolve.
-### 7. Capture the answer and the prototype
-Once the prototype has answered its question, capture the answer, then capture the prototype the way the [SKILL](SKILL.md) describes. The logic-specific mapping: the validated reducer / machine / function set lifts into the real module (the decision, absorbed); the TUI shell rides along to the throwaway branch that keeps the prototype as a primary source.
-## Anti-patterns
-- **Don't add tests.** A prototype that needs tests is no longer a prototype.
-- **Don't wire it to the real database.** Use an in-memory store unless the question is specifically about persistence.
-- **Don't generalise.** No "what if we wanted to support X later." The prototype answers one question.
-- **Don't blur the logic and the TUI together.** If the reducer / state machine references `console.log`, prompts, or terminal escape codes, it's no longer portable. Keep the TUI as a thin shell over a pure module.
-- **Don't ship the TUI shell into production.** The shell is optimised for being driven by hand from a terminal. The logic module behind it is the bit worth keeping.

package/skills/prototype/SKILL.md DELETED Viewed

@@ -1,26 +0,0 @@
----
-name: prototype
-description: Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
----
-# Prototype
-A prototype is **throwaway code that answers a question**. The question decides the shape.
-## Pick a branch
-Identify which question is being answered — from the user's prompt, the surrounding code, or by asking if the user is around:
-- **"Does this logic / state model feel right?"** → [LOGIC.md](LOGIC.md). Build a tiny interactive terminal app that pushes the state machine through cases that are hard to reason about on paper.
-- **"What should this look like?"** → [UI.md](UI.md). Generate several radically different UI variations on a single route, switchable via a URL search param and a floating bottom bar.
-The two branches produce very different artifacts — getting this wrong wastes the whole prototype. If the question is genuinely ambiguous and the user isn't reachable, default to whichever branch better matches the surrounding code (a backend module → logic; a page or component → UI) and state the assumption at the top of the prototype.
-## Rules that apply to both
-1. **Throwaway from day one, and clearly marked as such.** Locate the prototype code close to where it will actually be used (next to the module or page it's prototyping for) so context is obvious — but name it so a casual reader can see it's a prototype, not production. For throwaway UI routes, obey whatever routing convention the project already uses; don't invent a new top-level structure.
-2. **One command to run.** Whatever the project's existing task runner supports — `pnpm <name>`, `python <path>`, `bun <path>`, etc. The user must be able to start it without thinking.
-3. **No persistence by default.** State lives in memory. Persistence is the thing the prototype is _checking_, not something it should depend on. If the question explicitly involves a database, hit a scratch DB or a local file with a clear "PROTOTYPE — wipe me" name.
-4. **Skip the polish.** No tests, no error handling beyond what makes the prototype _runnable_, no abstractions. The point is to learn something fast.
-5. **Surface the state.** After every action (logic) or on every variant switch (UI), print or render the full relevant state so the user can see what changed.
-6. **Capture it when done.** Fold any validated decision into the real code, then capture the prototype itself as a **primary source**: commit it to a throwaway branch, out of main, and leave a context pointer to that branch on the implementation issue. Capture the answer too — the verdict and the question it settled — in the issue or a commit. The main branch keeps only the validated decision.

package/skills/prototype/UI.md DELETED Viewed

@@ -1,112 +0,0 @@
-# UI Prototype
-Generate **several radically different UI variations** on a single route, switchable from a floating bottom bar. The user flips between variants in the browser, picks one (or steals bits from each), then throws the rest away.
-If the question is about logic/state rather than what something looks like — wrong branch. Use [LOGIC.md](LOGIC.md).
-## When this is the right shape
-- "What should this page look like?"
-- "I want to see a few options for this dashboard before committing."
-- "Try a different layout for the settings screen."
-- Any time the user would otherwise spend a day picking between three vague mockups in their head.
-## Two sub-shapes — strongly prefer sub-shape A
-A UI prototype is much easier to judge when it's **butting up against the rest of the app** — real header, real sidebar, real data, real density. A throwaway route on its own is a vacuum: every variant looks fine in isolation. Default to sub-shape A whenever there's a plausible existing page to host the variants. Only reach for sub-shape B if the prototype genuinely has no nearby home.
-### Sub-shape A — adjustment to an existing page (preferred)
-The route already exists. Variants are rendered **on the same route**, gated by a `?variant=` URL search param. The existing data fetching, params, and auth all stay — only the rendering swaps. This is the default; pick it unless there's a specific reason not to.
-If the prototype is for something that doesn't yet have a page but *would naturally live inside one* (a new section of the dashboard, a new card on the settings screen, a new step in an existing flow) — that's still sub-shape A. Mount the variants inside the host page.
-### Sub-shape B — a new page (last resort)
-Only use this when the thing being prototyped genuinely has no existing page to live inside — e.g. an entirely new top-level surface, or a flow that can't be embedded anywhere sensible.
-Create a **throwaway route** following whatever routing convention the project already uses — don't invent a new top-level structure. Name it so it's obviously a prototype (e.g. include the word `prototype` in the path or filename). Same `?variant=` pattern.
-Before committing to sub-shape B, sanity-check: is there really no existing page this could be embedded in? An empty route hides design problems that a populated one would expose.
-In both sub-shapes the floating bottom bar is identical.
-## Process
-### 1. State the question and pick N
-Default to **3 variants**. More than 5 stops being radically different and starts being noise — cap there.
-Write down the plan in one line, in the prototype's location or a top-of-file comment:
-> "Three variants of the settings page, switchable via `?variant=`, on the existing `/settings` route."
-This works whether the user is here to push back or not.
-### 2. Generate radically different variants
-Draft each variant. Hold each one to:
-- The page's purpose and the data it has access to.
-- The project's component library / styling system (TailwindCSS, shadcn, MUI, plain CSS, whatever).
-- A clear exported component name, e.g. `VariantA`, `VariantB`, `VariantC`.
-Variants must be **structurally different** — different layout, different information hierarchy, different primary affordance, not just different colours. Three slightly-tweaked card grids isn't a UI prototype, it's wallpaper. If two drafts come out too similar, redo one with explicit "do not use a card grid" guidance.
-### 3. Wire them together
-Create a single switcher component on the route:
-```tsx
-// pseudo-code — adapt to the project's framework
-const variant = searchParams.get('variant') ?? 'A';
-return (
-  <>
-    {variant === 'A' && <VariantA {...data} />}
-    {variant === 'B' && <VariantB {...data} />}
-    {variant === 'C' && <VariantC {...data} />}
-    <PrototypeSwitcher variants={['A','B','C']} current={variant} />
-  </>
-);
-```
-For sub-shape A (existing page): keep all the existing data fetching above the switcher; only the rendered subtree changes per variant.
-For sub-shape B (new page): the throwaway route under `/prototype/<name>` mounts the same switcher.
-### 4. Build the floating switcher
-A small fixed-position bar at the bottom-centre of the screen with three pieces:
-- **Left arrow** — cycles to the previous variant (wraps around).
-- **Variant label** — shows the current variant key and, if the variant exports a name, that name too. e.g. `B — Sidebar layout`.
-- **Right arrow** — cycles forward (wraps around).
-Behaviour:
-- Clicking an arrow updates the URL search param (use the framework's router — `router.replace` on Next, `navigate` on React Router, etc) so the variant is shareable and reload-stable.
-- Keyboard: `←` and `→` arrow keys also cycle. Don't intercept arrow keys when an `<input>`, `<textarea>`, or `[contenteditable]` is focused.
-- Visually distinct from the page (e.g. high-contrast pill, subtle shadow) so it's obviously not part of the design being evaluated.
-- Hidden in production builds — gate on `process.env.NODE_ENV !== 'production'` or an equivalent check, so a stray prototype merge can't ship the bar to users.
-Put the switcher in a single shared component so both sub-shapes can reuse it. Locate it wherever shared UI lives in the project.
-### 5. Hand it over
-Surface the URL (and the `?variant=` keys). The user will flip through whenever they get to it. The interesting feedback is usually **"I want the header from B with the sidebar from C"** — that's the actual design they want.
-### 6. Capture the answer and clean up
-Once a variant has won, capture the answer — which variant and why — then capture the prototype the way the [SKILL](SKILL.md) describes. Fold the winner into the real code and move the rest onto the throwaway branch, not into main:
-- **Sub-shape A** — fold the winner into the existing page; drop the losing variants and the switcher from main.
-- **Sub-shape B** — promote the winning variant to a real route; drop the throwaway route and the switcher from main.
-The full set of variants is the primary source, so it lands on the throwaway branch, not the bin — variant components and the switcher left in the main branch rot fast and confuse the next reader.
-## Anti-patterns
-- **Variants that differ only in colour or copy.** That's a tweak, not a prototype. Real variants disagree about structure.
-- **Sharing too much code between variants.** A shared `<Header>` is fine; a shared `<Layout>` defeats the point. Each variant should be free to throw out the layout.
-- **Wiring variants to real mutations.** Read-only prototypes are fine. If a variant needs to mutate, point it at a stub — the question is "what should this look like", not "does the backend work".
-- **Promoting the prototype directly to production.** The variant code was written under prototype constraints (no tests, minimal error handling). Rewrite it properly when you fold it in.

package/skills/prototype/agents/openai.yaml DELETED Viewed

@@ -1,3 +0,0 @@
-interface:
-  display_name: "Prototype"
-  short_description: "Prototype to answer a design question"