team-standards

Plugin team-standards from marketplace team-standards in exception-coder/team-standards. Commands read from the repo's manifest — yesterday.

Skills (26)

• architecture-ddd-lite-fullstack

  Use before writing or reviewing business code in Java, Go, Python, React, or Vue to choose layers, feature boundaries, reusable capabilities, and one-way dependencies.

• architecture-diagram-design

  绘制、重绘或美化架构说明图（含 draw.io/drawio）时使用；根据受众选择汇报、设计或实施视图，提炼主线，组织布局、图标和配色，交付可编辑源图并实际检查。支持能力、分层、协作、执行与演进图；ER、时序和部署图按需采用，不用于业务统计图表或普通 UI 页面。

• architecture-reasoning

  悟道：在功能名称代替需求、方案未定或担心过度设计时，核实业务目标、约束与已有能力，选择最小充分方案及必要升级条件。适用于需求澄清与方案取舍；明确小改、既定方案执行和纯文字改写不单独触发。

• backend-evidence

  Use for backend changes or analysis involving DDL, SQL, data relations, states, fields, events, APIs, domain invariants, reverse impact, runtime evidence, or query performance. Keeps Graphify implementation facts, OpenSpec behavior, and database/runtime truth distinct.

• bug-doc-required

  Use to investigate reported bugs, errors, timeouts, or unexpected behavior; perform an authorized fix; or write a requested incident analysis. Requires diagnostic evidence and regression results, while keeping separate reports optional for simple bugs.

• business-knowledge-maintenance

  业务规则、流程、术语、数据范围或用户可见能力变化时，按需更新所属项目的 Markdown 业务知识；也用于显式归档、精简或核对业务知识。纯样式、性能优化和保持行为的内部重构不触发，不要求图谱或集中服务。

• business-logic-orientation

  Use to understand existing business logic before refactoring, rewriting, migration, or regression review, or when aligning ambiguous business terminology or explicitly documenting current logic. Uses project documents and targeted source evidence; Graphify is optional for complex relationships.

• business-ontology-modeling

  从原始代码和数据库反向建立业务模型，或围绕业务问题补齐本体、属性、关系、状态和指标口径；优先复用Graphify与现有数据库工具，核实证据和接入缺口。适用于没有知识库的存量业务梳理、模型补全、跨系统术语对齐和业务Agent可回答性分析；普通代码定位、单表字段说明或已有规则下的小修复不单独触发。

• business-visualization-advisor

  涉及 Web 前端业务图表、统计概览、数据可视化或图表看板的创建、改造、选图和评审时使用，包括用户只说给业务页面加图表的情况。自动探索业务对象、生命周期状态和指标口径，先发现值得关注的问题，再选择清晰且可行动的图表并组织看板。纯样式修复、普通 CRUD 页面、静态科学绘图不触发。

• change-readiness

  Guide implementation preparation: understand the existing behavior, identify affected code and maintain relevant specifications and designs without requiring governance bindings or tool-specific approval.

• clear-design-docs

  编写、精简或独立评审概设、详设与技术方案；将功能清单和设计汇总为项目过会稿、方案宣讲材料。过会用结论标题、可编辑 draw.io 与简明要点讲清重点难点和待定事项，细节按需查阅；独立评审默认只读。普通文案润色、周报和会议纪要不触发。

• coding-standards-common

  Use when writing, reviewing, or modifying source code, explicitly cleaning comments, or handling coding-standard corrections. Provides cross-language structure, naming, errors, testing, comments, and optional maintenance modes.

• cross-system-handoff

  团队版交接：将项目或迭代开发、跨系统变更、接入和问题整理成可直接转发给同事或其AI执行的交接说明。用于用户要求移交项目、需求或接入任务给开发同事及AI时；普通答疑和周报不使用。

• database-design

  设计关系型数据库、业务实体关系、物理库表、索引、核心 SQL 和数据演进。适用于从需求设计库表或为存量结构变更制定可开发、可审核的方案。单纯查库、排查 SQL、修改查询且不涉及库表决策时走现有证据或实施入口。

• delivery-verification

  Guide proportionate verification and honest delivery reporting after changes. Use project-native checks or explicitly adopted tooling; missing governance records do not prevent a progress or final response.

• frontend-excellence

  Build or improve Web/H5 interfaces; simplify forms, approvals, search, navigation and workflows that feel complex. Supports interaction design, implementation, visual review and design-system modes. Pure backend work and copy-only edits are excluded.

• git-commit-standards

  Use before committing completed work or when querying, summarizing, or explicitly recording work history. Requires atomic logical commits, synchronized documentation, current validation, a three-part Chinese body, and a real Author; push authorization is separate.

• go-coding-standards

  Use when writing, reviewing, or modifying Go code. Adds idiomatic package and interface design, error handling, context cancellation, concurrency ownership, resource safety, and Go verification to the common coding standards.

• init-project-docs

  用于接入项目，以及初始化、刷新或检查项目上下文；默认复用现有业务文档、从代码补齐知识缺口并标注待确认，交付简明业务概览和 draw.io 全景图，随项目维护；OpenSpec 和 Graphify 按需使用。

• java-coding-standards

  Use when writing, reviewing, or modifying Java code. Covers Java-specific rules derived from the Alibaba Huangshan guidelines and complements the common coding standards.

• llm-agent-coding-standards

  Use when code integrates LLM SDKs, agents, prompts, tools or function calling, structured model output, or agent loops. Covers trust boundaries, deterministic contracts, and loop safeguards.

• markdown-writing-standards

  团队文档统一写作入口。编写、精简、同步或发布项目文档时先选读者和文档类型，再核对正文、归属、图件及发布位置。覆盖方案、过会稿、Quickstart、交接和 Markdown 维护。

• openspec-auto

  Automatically choose specification depth for development tasks: L1 direct implementation, L2 lightweight planning, L3 the project's full OpenSpec workflow. Reassess when scope or risk grows. Prefer the project's own openspec-auto and reuse its quality gates.

• page-delivery-plan

  将需求、原型或已有页面整理成简明的页面功能交付计划，说明要补的功能、交付顺序和完成标准，供人和 AI 逐项推进。用户要求页面加功能点、开发计划或功能交付安排时使用。普通单点编码与纯技术方案走现有实施或设计入口。

• plain-writing

  人话：编写或改写面向人的方案说明、评审结论、提交说明、工作回复、图示标签及界面文案，让具体对象、动作与结果容易理解，保留事实、条件和技术含义。用户要求说人话、去套话或降低阅读成本时使用；不改变技术决策，不用于机器契约改名。

• technical-implementation-design

  设计需求在现有系统中的技术实现、模块职责、接口契约和执行流程，按实际影响展开事务、异常、权限、兼容与发布。适用于编写或实质调整可交接开发的模块或功能技术方案。纯库表决策、独立评审和纯文案精简分别走对应入口。

Hooks (4)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/check-commit-no-ai-signature.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/write-guard-dispatcher.js"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/prompt-signal-capture.js"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/check-plugin-version-stale.js"

Similar plugins