Frontend
Skill chinayin/gox-claude-plugins/plugins/gox-code-rules/skills/frontend
Team coding-standards plugins for Claude Code (Agent Skills marketplace) · 面向 Claude Code 的团队代码规范插件(技能 marketplace)
npx -y skills add chinayin/gox-claude-plugins --skill frontendAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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".
SKILL.md
1.8 KB, 398 tokens by cl100k_base, as published. Nobody here has run it
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 为准。
Gives 0 of the 12 instructions most css styling skills give in 398 tokens
Counted across 586 of the 596 authors here whose files we hold, read 2026-08-06
- avoid excessive centered layoutsin 55 of 586, across 12 files
- bundle code into single HTML filein 54 of 586, across 14 files
- Respect prefers-reduced-motion user settingsin 52 of 586, across 35 files
- avoid purple gradientsin 51 of 586, across 11 files
- avoid uniform rounded cornersin 51 of 586, across 11 files
- avoid Inter fontin 51 of 586, across 11 files
- edit generated files to develop artifactin 50 of 586, across 10 files
- animate only transform and opacity propertiesin 43 of 586
- Make touch targets at least 44x44 pixelsin 41 of 586, across 15 files
- Ensure minimum color contrast of 4.5:1in 39 of 586, across 10 files
- use tailwind cssin 39 of 586, across 24 files
- Use SVG icons instead of emojisin 38 of 586, across 11 files
Said here and by no other author read
- follow team conventions when writing frontend code
- reply and write code comments in Chinese
- read the relevant detailed standards on demand
- read the baseline frontend rules file first by default
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.