What is proj-analyze-design?

A technical-design step that turns confirmed requirements into a proposed database, interface, and code structure.

It helps create and confirm a technical design document after the requirements are agreed.

It reduces uncertainty about how a feature should be built before implementation starts.

How zhangloveyan/backend-skill configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to zhangloveyan/backend-skill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/zhangloveyan/backend-skill/main/.claude/skills/proj-analyze-design/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/zhangloveyan/backend-skill

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zhangloveyan/backend-skill/proj-analyze-design/github.svg)](https://agentmods.dev/skills/zhangloveyan/backend-skill/proj-analyze-design)

Your own site

<a href="https://agentmods.dev/skills/zhangloveyan/backend-skill/proj-analyze-design"><img src="https://agentmods.dev/badge/skills/zhangloveyan/backend-skill/proj-analyze-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zhangloveyan/backend-skill/proj-analyze-design"><img src="https://agentmods.dev/badge/skills/zhangloveyan/backend-skill/proj-analyze-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,439 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00035	$0.01439
Opus 5.5	$0.00014	$0.00576
Sonnet 5.5	$0.00007	$0.00288
Haiku 4.5	$0.00003	$0.00144

Measured 23d ago against content hash 6a858b943d6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

proj-analyze-design 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 23d 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.

.claude/skills/proj-analyze-design/SKILL.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

技术方案设计（阶段二）

前置条件：用户已确认阶段一（/proj-analyze-req）的需求分析文档，且全流程任务文档已创建目标：设计技术实现方案，明确数据库、接口、代码结构产出：技术方案文档（用户确认后进入开发阶段）

执行流程

Step 0: 校验任务文档 → Step 1: 探索现有代码 → Step 2: 设计技术方案 → Step 3: 输出方案文档 → Step 4: 用户确认 → Step 5: 生成任务

Step 0: 校验任务文档

确认全流程任务文档存在
若缺失，先创建任务文档骨架并补齐流程状态与上下文快照

Step 1: 探索现有代码

在设计方案前，先了解项目现状：

探索内容	目的
相关模块代码	了解现有实现方式
类似功能实现	参考已有模式
公共类和工具	复用现有组件
数据库表结构	了解关联关系

Step 2: 设计技术方案

2.1 数据库设计

表命名规范：

表名：小写下划线，单数（如 sys_user, order_item）
字段名：小写下划线（如 user_id, create_time）
主键：id BIGINT AUTO_INCREMENT
外键：{关联表}_id
索引：idx_{表名}_{字段}

关键字检查（必须做）：新增或重命名的表、字段禁止与目标 MySQL 版本的关键字完全同名（大小写不敏感，包含保留字和非保留关键字），不得用反引号规避。按 SQL 命名规范与校验方法检查，并在技术方案中记录目标版本、校验来源、结果及改名映射。已有数据库的冲突名称先提交迁移方案，未经确认不得直接改名。

通用字段（每张业务表必须包含）：

id BIGINT AUTO_INCREMENT PRIMARY KEY,
del_flag TINYINT(1) DEFAULT 0 COMMENT '删除标记',
create_by VARCHAR(64) COMMENT '创建人',
create_time DATETIME DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间',
update_by VARCHAR(64) COMMENT '更新人',
update_time DATETIME COMMENT '更新时间'

2.2 接口设计规范

接口文档要求：

完整参数：必须包含所有请求参数的类型、是否必填、示例值
响应格式：提供完整的JSON响应示例，包含所有字段
错误码：列出所有可能的错误码和说明
业务场景：说明接口的使用场景和业务含义

2.3 枚举类设计规范

标准枚举格式：参考模板中的枚举类设计，必须包含getByCode和getMessageByCode方法

2.4 技术架构澄清

按需澄清原则：只在涉及相关技术时才需要澄清

常见澄清场景：

消息/通知功能 → 澄清：推送服务 vs 前端轮询？
实时数据展示 → 澄清：Redis vs 数据库？
历史数据管理 → 澄清：永久保存 vs 定期清理？
在线状态功能 → 澄清：实时更新机制？存储位置？

Step 3: 输出方案文档

在充分澄清后，使用模板输出技术方案文档。

模板文件：技术方案模板

保存位置：docs/design/{YYYYMMDD}_{中文模块名}_技术.md

注意：技术方案设计时如发现需求遗漏或变更，需同步更新需求文档。

同步更新任务文档：

将“技术方案”状态标记为进行中/已完成
在产物清单中记录技术方案文档路径
更新上下文快照与下一步指令

Step 4: 用户确认

4.1 确认话术

输出技术方案后，必须使用以下话术请求确认：

以上是技术实现方案，请确认：
1. 数据库表结构和字段是否符合预期？
2. 接口设计是否满足需求？
3. 是否需要调整？

确认后我将开始编码开发。

4.2 用户反馈处理

用户反馈	处理方式
"确认"/"没问题"/"可以"	调用 `/proj-task` 拆分任务，开始开发
"字段需要调整xxx"	修改表结构设计，再次确认
"接口需要增加xxx"	补充接口设计，再次确认
"取消"/"不做了"	结束流程

Read the full file on GitHub · 154 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

templates/design-doc.md 6.2 KB

Changes

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.

23d ago Changed · +2 lines 6a858b943d6b
2mo ago First seen · 152 lines · 35 tokens per session scan A 3b47a0a45ad9

Subscribe to this mod's changes

proj-analyze-design is a skill published in the GitHub repository zhangloveyan/backend-skill (103 stars, last pushed 23d ago), licensed MIT. It adds 35 tokens to every session and 1,439 once invoked, about $0.0001 per session on Opus 5.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.

Databases Planning

proj-analyze-design next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
proj-analyze-designzhangloveyan/backend-skill	Skill	103	23d ago	MIT	A	35	Claude Code
create-prprisma/orm	Skill	48k	yesterday	Apache-2.0	A	48	Claude Code, Codex
schema-explorationlangchain-ai/deepagents	Skill	31k	yesterday	MIT	A	57	Claude Code, Codex
atlas-mssqlariga/atlas	Skill	8.8k	yesterday	Apache-2.0	A	163	Claude Code
ha-data-storesshiwenwen/hope-agent	Skill	1.9k	yesterday	MIT	A	115	Claude Code, Codex
nornicdb-cypher-queriesorneryd/NornicDB	Skill	923	yesterday	MIT	A	79	Claude Code, Codex
volcengine-rds-postgresqlbytedance/agentkit-samples	Skill	484	today	Apache-2.0	A	63	Claude Code, Codex

backend-skill: Skill for Claude Code