Borrowing it
Nothing to install: this file belongs to vigorX777/product-design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vigorX777/product-design-system/main/AGENTS.mdgit clone --depth 1 https://github.com/vigorX777/product-design-systemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/vigorx777/product-design-system/agents-md)<a href="https://agentmods.dev/instructions/vigorx777/product-design-system/agents-md"><img src="https://agentmods.dev/badge/instructions/vigorx777/product-design-system/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.03777 | $0.03777 |
| Opus 5 | $0.01888 | $0.01888 |
| Sonnet 5 | $0.00755 | $0.00755 |
| Haiku 4.5 | $0.00378 | $0.00378 |
Grade A, and why
product-design-system AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
产品设计辅助系统
系统说明
本系统是一个自进化的产品设计辅助系统，采用分层架构设计，包含通用产品设计层与产品专属规则层。作为系统的入口文件，本规则指导产品设计助手协助产品经理完成交互原型搭建、需求文档编写以及经验复盘提炼。工作语言为中文。
一、通用产品设计规则
本章节规则适用于所有产品线的设计沟通与协作。
1. 文件夹结构规则
每个需求功能点为独立文件夹，文件夹下包含标准的三件套：
需求名称/
├── {需求名称}.html # 交互原型（单文件 HTML，内联 CSS + JS，文件名与文件夹同名）
├── 需求说明文档.md # 需求说明（最终态，始终反映最新设计）
├── CHANGELOG.md # 变更日志（精简表格，记录每次变更的时间和摘要）
├── _进展备忘.md # 【可选】过程沉淀，长周期需求使用，复盘生成后删除
└── *.png / *.jpg # 截图参考
文件命名规则：HTML 原型文件名必须与需求文件夹名称一致。例如需求文件夹为「用户列表筛选优化」，则原型文件为
用户列表筛选优化.html。
2. 需求说明文档规范
需求说明文档是最终态文档，始终反映当前最新的产品设计，不保留历史过程。每次变更后直接更新为最新状态。
文档结构
# {需求标题}
## 问题
1. {业务痛点/场景问题，从用户视角出发}
2. ...
## 需求设计
### 一、{功能模块名称}
{1-2 句概括该模块的定位和上下文}
1. {功能点}：
- {具体规则}；
- {具体规则}。
2. ...
### 二、{功能模块名称}
...
### N-1、权限说明（新增页面时必须包含）
{说明该页面的访问权限、操作权限等}
### N、操作日志（新增页面时必须包含）
{说明该页面的关键操作需要记录哪些操作日志}
写作风格规则
| 规则 | 说明 | 示例 |
|---|---|---|
| 问题先行 | ## 问题 部分罗列业务痛点，每条从用户视角出发 |
"用户无法在列表页快速判断某条记录的配置状态" |
| 模块编号用中文序号 | 章节标题用「一、二、三、四」 | ### 三、批量操作弹窗 |
| 每节有引导段 | 标题下先用 1-2 句话说明上下文，再展开细节 | "点击「批量操作」按钮时，先判断是否存在不可执行的选中项：" |
| 界面文案用「」包裹 | 所有按钮名、标题、提示语统一用中文书名号 | 「新建」「查看详情」「确认删除」 |
| 引用块展示 UI 原文 | 用 > 展示界面上实际显示的提示文案 |
> 当前记录已被引用，无法删除。 |
| 条件分支用加粗 | 不同场景用 **如果有**、**如果无** 开头 |
1. **如果有**，弹出选择弹窗 |
| 字段描述用破折号 | 列举字段时格式为 **字段名** — 说明 |
**创建时间** — 显示记录的创建时间； |
| 补充说明用括号 | 业务规则的补充放在句末括号里 | "（此处统计口径为已启用状态的记录数量）" |
| 不写实现细节 | 不出现 CSS 类名、JS 函数名，只描述产品行为 | ✅ "置顶显示，以浅蓝色背景行高亮" ❌ "添加 .row-new 类名" |
| 数字编号表示并列 | 同级功能点用 1. 2. 3. |
见文档中各章节 |
| 缩进列表列举规则 | 功能点下的具体规则用缩进 - 列表 |
每条以分号 ； 结尾，最后一条用句号 。 |
3. 变更日志规范
变更日志是过程记录，以表格形式记录每次变更的时间点和摘要，用于追溯设计演变过程。
格式
# 变更日志
| 序号 | 日期 | 变更摘要 | 影响模块 |
|------|------|----------|----------|
| 1 | 2026-01-10 | 列表新增「状态」列，支持快速筛选 | 列表页 |
| 2 | 2026-01-12 | 状态标签颜色调整为品牌色方案 | 列表页 |
规则
- 序号从 1 开始递增，不重置；
- 日期格式
YYYY-MM-DD； - 变更摘要一句话概括，不写实现细节；
- 影响模块对应需求说明文档中的章节名称（如「列表页」「操作弹窗」）。
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 291 lines · 3,777 tokens per session scan A 4454fb79e82f
product-design-system AGENTS.md is an instructions file published in the GitHub repository vigorX777/product-design-system (375 stars, last pushed 5mo ago), licensed MIT. It adds 3,777 tokens to every session, about $0.0189 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.