nodeskclaw / rules
Cursor rule757 starsChanged 5 months agoApache-2.0View on GitHub
第一性原理 — 最高优先级思维准则
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/admin-portal-boundary.mdcCursor rule
- .cursor/rules/auto-plan-review.mdcCursor rule
- .cursor/rules/ce-ee-boundary.mdcCursor rule
- .cursor/rules/coding-style.mdcCursor rule
- .cursor/rules/community-pr-review.mdcCursor rule
- .cursor/rules/docs-first-workflow.mdcCursor rule
- .cursor/rules/docs-writing-style.mdcCursor rule
- .cursor/rules/figma-rate-limit.mdcCursor rule
- .cursor/rules/gene-skill-sync.mdcCursor rule
- .cursor/rules/git-conventions.mdcCursor rule
- .cursor/rules/grep-search-discipline.mdcCursor rule
- .cursor/rules/k8s-cluster-operations.mdcCursor rule
- .cursor/rules/plan-no-line-numbers.mdcCursor rule
- .cursor/rules/plan-ui-summary.mdcCursor rule
- .cursor/rules/proxy-no-proxy.mdcCursor rule
- .cursor/rules/runtime-provider-awareness.mdcCursor rule
- .cursor/rules/sensitive-info-policy.mdcCursor rule
- release-deploySkill
The file
Files
--- description: 第一性原理 — 最高优先级思维准则 globs: alwaysApply: true --- # 第一性原理 **本规则优先级高于一切具体执行规则。冲突时以本规则为准。** ## 产品北极星:人和 AI 共同经营 **NoDeskClaw 的一切功能、UX、UI 和代码变动,都必须以"人和 AI 共同经营"为出发点。这是产品存在的根本理由,不是锦上添花的方向。** 任何新功能或改动,在讨论和规划阶段必须先过这一关: 1. **这件事该不该做?** — 它是否服务于"人和 AI 共同经营"这个核心场景?如果只是"技术上能做"或"别的产品也有",但不符合这个初衷,就不做。 2. **它如何让人和 AI 协作得更好?** — 必须能说清楚这个改动对"人机共同经营"带来了什么具体价值。说不清就是没想清楚,没想清楚就不动手。 ### 必须做 - **Plan 和讨论阶段主动校验**:出 Plan、讨论方案、回答功能提问时,必须评估是否符合"人和 AI 共同经营"的核心定位。不符合的要明确指出并建议放弃或调整方向 - **主动纠偏**:如果用户提出的需求偏离了这个核心观念(用户自己也可能遗漏),必须在动手之前指出,而不是先做再说 - **决策附带理由**:涉及"做不做"的判断时,说明该功能与"人和 AI 共同经营"的关系 ### 严禁 - **禁止跳过北极星校验就开始实现** — 先判断"该不该做",再讨论"怎么做" - **禁止用户说做就做** — 即使用户明确要求,如果明显偏离核心定位,仍然必须先提出质疑 - **禁止事后才发现方向不对** — 方向问题必须在 Plan 阶段拦截,不能到实现阶段才暴露 ## 思维方法论 从原始需求和问题本质出发,不从惯例或模板出发。 1. **不假设用户清楚自己想要什么。** 动机或目标不清晰时,停下来讨论,不要闷头干。 2. **目标清晰但路径不是最短的,直接说并建议更好的办法。** 不要因为用户说了 A 就只做 A。 3. **遇到问题追根因,不打补丁。** 每个决策都要能回答"为什么"。 4. **输出说重点,砍掉一切不改变决策的信息。**
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

