Frontend

Team frontend architecture and coding standards. Use this whenever designing or writing frontend code in this repo — React/Vue components, TypeScript/JavaScript, styling (CSS/SCSS), state management, data fetching, or build/tooling config (package.json, tsconfig, vite/eslint). Consult it any time you touch frontend code — including small changes like one component prop or a style tweak — even if the user never says "standards". Currently a skeleton — core rules are TODO; confirm conventions with the team instead of guessing.

chinayin 9fd8463 2 files · 2.3 KB Updated

File contents

Team Frontend Standards

占位骨架(TODO):团队前端规范正文待填充。 结构与 go 技能一致:SKILL.md 当索引,详规按需放 references/。填充时把下面的 TODO 换成团队真实约定即可。

Follow team conventions when writing or designing frontend code in this repo. Reply and write code comments in Chinese. Read the detailed standards in references/ on demand per the index below — only the file relevant to the current task.

When to read which (index)

What you're doing Read this
Any frontend code (baseline: structure, naming, TS config, lint…) references/rules.md ← read first by default

扩展时按领域加 reference 并在本表登记,例如:components.md(组件)、styling.md(样式)、state.md(状态管理)、api.md(数据请求)。

Core rules (TODO — 填入团队前端铁律)

  • TODO: 框架与版本下限(React / Vue?具体版本?)
  • TODO: TypeScript 严格度与 any 政策
  • TODO: 样式方案(CSS Modules / Tailwind / styled-components?)
  • TODO: 状态管理与数据请求约定
  • TODO: 组件 / 文件命名与目录结构

这些是会话内的软引导;最终强制以仓库的 eslint / prettier / tsc / CI / PR review 为准。

chinayin/gox-claude-plugins/tree/main/plugins/gox-code-rules/skills/frontend commit 9fd8463a4c

Frequently asked questions

npx skillmds@latest add chinayin/frontend