Follow 代码审查

AI 智能社区

作者仓库星标 0
作者仓库 skills-registry

解读按原文结构重写，命令、链接、术语均保留；右侧可核对作者原始 SKILL.md

方法与流程

Workflow：Classify the change: Which layers and files are involved (app, features, components, lib)? Pull in rules: At minimum, skim architecture.mdc + layers.mdc for anything that adds imports or new modules. Add styling.mdc for UI; naming.mdc for new files;…

适用与边界

当前原文没有单列适用场景。
Rule map (what to read when)：File · Use when architecture.mdc · Deciding where new code belongs; import direction (App → Features → Lib/Components); feature public API via index.ts layers.mdc · Placing or reviewing code under src/app/, src/features/, src/components/, or src/lib/

原文中的明确线索

要点：「(always applied in Cursor). Do not rely on memory alone—」、「AGENTS.md」、「Classify the change」、「Pull in rules」、「Implement」、「Before finishing」、「.cursor/rules」、「architecture / layers」
文件与命令：.cursor/rules/.mdc、.mdc、AGENTS.md、nodemodules/next/dist/docs/、architecture.mdc、App → Features → Lib/Components、index.ts、layers.mdc

流狐整理：以上内容来自当前 SKILL.md 的章节与原词；未补写作者没有声明的工具、兼容性或能力。

Follow workspace rules

Source of truth

Project conventions live in .cursor/rules/*.mdc (always applied in Cursor). Do not rely on memory alone—open and follow the relevant .mdc file when the task touches that area.

Also heed AGENTS.md (Next.js: consult node_modules/next/dist/docs/ before using framework APIs you are unsure about).

Rule map (what to read when)

File	Use when
`architecture.mdc`	Deciding where new code belongs; import direction (`App → Features → Lib/Components`); feature public API via `index.ts`
`layers.mdc`	Placing or reviewing code under `src/app/`, `src/features/`, `src/components/`, or `src/lib/`
`naming.mdc`	New files, folders, hooks, services, tests
`styling.mdc`	Tailwind/`cn()`, `NavLink`, design tokens, `globals.css` utilities
`anti-patterns.mdc`	Quick pass for common violations (duplicate link styling, wrong layer imports, hook misuse, etc.)
`performance.mdc`	State placement, lists, memoization, context providers

Repo path (for search/open): .cursor/rules/<file>.

Workflow

Classify the change: Which layers and files are involved (app, features, components, lib)?
Pull in rules: At minimum, skim architecture.mdc + layers.mdc for anything that adds imports or new modules. Add styling.mdc for UI; naming.mdc for new files; performance.mdc when changing state, context, or large lists.
Implement so that:
- Dependency flow matches the architecture table (no upward imports; no feature-to-feature imports; lib stays free of feature/component imports).
- UI matches styling rules (NavLink for links, cn() for conditional classes, tokens from tailwind.config.js / globals—not ad-hoc patterns that break safelisting).
Before finishing: Re-read anti-patterns.mdc for a fast sanity check on the touched surface.

Conflict resolution

If a suggestion conflicts with .cursor/rules, the rules win. If two rules seem to conflict, prefer architecture / layers for structure, then styling and anti-patterns for UI and React habits.

Relation to other project skills

ui-design-review focuses on visual quality and hierarchy; this skill covers repository-wide conventions (layers, naming, Tailwind/NavLink rules, performance guardrails). Use both when polishing UI that must also match project standards.

Source: andraderaul/random-fy — distributed by TomeVault.

流狐档案作者与许可取自来源；运行、权限和网络为流狐检测或估算

流狐分类: AI 智能
作者声明 Agent: 未找到明确声明；不据此推断已兼容或已测试
静态检查: 88 / 100 · 启发式扫描，不代表运行安全
作者 / 版本 / 许可: @tomevault-io · 未声明 license
流狐 Token 估算: 低消耗
流狐接入估算: 即装即用
是否需要外部 API Key: 未发现要求
检测到的系统要求: 未声明
底层运行要求: 未声明
检测到的文件与系统行为: 只读
检测到的网络行为: 仅限本地
安装命令数: 无（仅作为资料）

档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

输出预览 follow-workspace-rules.preview

作者没有在当前 SKILL.md 中定义固定输出样例。

SKILL.md SKILL.md

# Follow workspace rules

## Source of truth

Project conventions live in **`.cursor/rules/*.mdc`** (always applied in Cursor). Do not rely on memory alone—**open and follow the relevant `.mdc` file** when the task touches that area.

Also heed **`AGENTS.md`** (Next.js: consult `node_modules/next/dist/docs/` before using framework APIs you are unsure about).

## Rule map (what to read when)

| File                                                 | Use when                                                                                                                 |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| [`architecture.mdc`](../../rules/architecture.mdc)   | Deciding where new code belongs; import direction (`App → Features → Lib/Components`); feature public API via `index.ts` |
| [`layers.mdc`](../../rules/layers.mdc)               | Placing or reviewing code under `src/app/`, `src/features/`, `src/components/`, or `src/lib/`                            |
| [`naming.mdc`](../../rules/naming.mdc)               | New files, folders, hooks, services, tests                                                                               |
| [`styling.mdc`](../../rules/styling.mdc)             | Tailwind/`cn()`, `NavLink`, design tokens, `globals.css` utilities                                                       |
| [`anti-patterns.mdc`](../../rules/anti-patterns.mdc) | Quick pass for common violations (duplicate link styling, wrong layer imports, hook misuse, etc.)                        |

…

证据边界与执行链路

作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。

章节    -> Source of truth → Rule map (what to read when) → Workflow → Conflict resolution → Relation to other project skills
要点    -> (always applied in Cursor). Do not rely on memory alone— · AGENTS.md · Classify the change · Pull in rules · Implement · Before finishing · .cursor/rules · architecture / layers
文件/命令 -> .cursor/rules/.mdc · .mdc · AGENTS.md · nodemodules/next/dist/docs/ · architecture.mdc · App → Features → Lib/Components · index.ts · layers.mdc
内容 SHA-256 -> c5161da9e665