Community写作与编辑github.com

bencium/negentropy-lens

一个决策支持框架,通过熵(衰败)与负熵(成长)的视角评估系统、架构和策略,同时揭示隐性知识缺口。

negentropy-lens 是什么?

这是一个为AI代理(如Claude Code、Cursor、Codex)设计的决策支持技能,名为“负熵透镜”。它通过熵(系统衰败趋势)与负熵(系统成长趋势)的二元视角,帮助开发者评估系统设计、技术架构、战略选择,并识别隐性知识(Tacit Knowledge)的缺失区域。该技能适用于架构决策、方案对比、现有系统审计等场景,并会自动检测用户是否处于决策节点,即使未明确请求,也会通过提示熵/负熵维度来引导用户进行更全面的评估。其核心机制基于一个定义熵和负熵指标的框架,并包含识别隐性知识缺失的步骤,最终输出结构化的评估报告。该技能支持所有主流AI代理平台,旨在提升决策质量,避免因忽视系统熵增而导致的长期维护成本。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/bencium/bencium-marketplace/tree/main/skills/negentropy-lens

Installed? Explore more 写作与编辑 skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

negentropy-lens 是做什么的?

一个决策支持框架,通过熵(衰败)与负熵(成长)的视角评估系统、架构和策略,同时揭示隐性知识缺口。每当用户正在进行架构决策、评估系统设计、审查技术方案、在选项之间进行选择、审计现有系统或规划策略时,请使用此技能。当用户明确要求“应用负熵透镜”或提及“熵”、“负熵”、“隐性知识”、“知识引擎”或“翻转开关”时,也应触发此技能。即使你检测到用户处于决策点但尚未要求此透镜,也应通过简要指出熵/负熵维度来引导激活,然后再继续其他讨论。

目标

通过系统性地评估“推动系统走向无序(熵)”与“促进结构化和增长(负熵)”的力量,帮助做出更明智的决策。

使用场景

  • 架构决策:评估组件分解、服务边界或数据流的设计。
  • 解决方案评审:对比技术方案,确定哪种方案能更好地管理复杂性。
  • 策略规划:评估路线图或组织变革的长期影响。
  • 系统审计:识别现有系统中的技术债务或衰减趋势。
  • 揭示隐性知识:在讨论不同方案时,主动询问“我们可能在这里遗漏了哪些未言明的知识?”

如何应用透镜

  1. 识别决策上下文:用户面临的具体决策或权衡是什么?
  2. 评估熵(衰败)指标:
    • 耦合度是否过高?
    • 是否存在临时的技术债务?
    • 是否缺少清晰的文档或所有权?
    • 团队是否因低效而减缓了交付速度?
    • 隐式依赖是否在增加?
  3. 评估负熵(成长)指标:
    • 系统是否拥有内聚的抽象层?
    • 是否引入了自动化测试或可观察性?
    • 团队是否在处理关键的不确定性?
    • 是否存在主动重构或模块化的证据?
    • 隐性知识是否被主动记录或分享?
  4. 权衡并总结:在给定的选项或系统现状中,哪一方面的力量更强?结论对技术债务、可维护性或决策速度意味着什么?
  5. 揭示隐性知识:明确询问用户:“是否存在未明确的关键知识假设?如果我们遗漏了这些关于[具体领域]的知识,可能会如何改变我们的决策?”

输出格式

输出结构化的评估报告,使用问题和/或表格清晰展示熵和负熵指标,并附上一个明确的、可操作的结论。

最佳实践

  • 针对用户的具体上下文定制指标。
  • 将结论与用户面临的实际决策紧密关联。
  • 如果熵高出奇,考虑是否需要建议一个“减少复杂性”的步骤。
  • 始终留出空间以揭示潜在的隐性知识。

Individual skills in this repo

This repo contains 12 individual skills — each has its own dedicated page.

bencium/adaptive-communication

Use when detecting ambiguous user intent, hedging language, open-ended framing, personal context before requests, or when unsure whether user wants exploration vs direct answer. Applies to all conversations.

bencium/agentic-ux-design---relationship-centric-interfaces

Design AI-first interfaces that build ongoing relationships through memory, trust evolution, and collaborative planning, not just isolated screen interactions

bencium/bencium-aeo

Generate AEO-optimized content (Answer Engine Optimization) for AI search visibility - ChatGPT, Claude, Gemini, AI Overviews. Use when optimizing websites for AI citations, creating FAQ schemas, evidence panels, or analyzing content for LLM extraction readiness.

bencium/bencium-code-conventions

Bence's code style, tech stack, and workflow conventions

bencium/bencium-controlled-ux-designer

Expert UI/UX design guidance for unique, accessible interfaces. Use for visual decisions, colors, typography, layouts. Always ask before making design decisions. Use this skill when the user asks to build web components, pages, or applications.

bencium/bencium-impact-designer

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. Based on Anthropic's Frontend Designer Skill

bencium/bencium-innovative-ux-designer

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

bencium/design-audit

Premium UI/UX design audit and refinement skill. Conducts systematic visual audits of existing apps and produces phased, implementation-ready design plans. Use this skill whenever the user asks to audit a UI, improve an app's visual design, make an interface feel more polished or premium, review design consistency, fix visual hierarchy, or refine spacing/typography/color. Also trigger when the user says "design review", "make it look better", "UI polish", "visual refinement", "design pass", "audit the design", or references making an app feel more professional. This skill is purely visual — it does not touch functionality, logic, or features. It elevates what exists.

bencium/human-architect-mindset

Systematic architectural thinking for irreplaceable human capabilities - domain modeling, systems thinking, constraint navigation, and AI-aware problem decomposition. Use proactively when detecting architectural decisions, system design discussions, or multi-component planning.

bencium/renaissance-architecture

Software architecture and UI/UX principles for building genuinely new solutions, not derivative work. Use when designing features, architecting software, brainstorming apps, reviewing designs, or during strategy discussions. Focuses on first-principles thinking, simplicity where it matters, and creating rather than commenting.

bencium/ui-typography

Professional typography rules for UI design, web applications, software interfaces, and all screen-based text. Enforces timeless typographic correctness that LLMs consistently get wrong: proper quote marks, dashes, spacing, hierarchy, and layout. ENFORCEMENT MODE: When generating ANY HTML, CSS, React, JSX, or UI code containing visible text, auto-apply every rule in this skill silently — do not ask, do not explain, just produce correct typography. AUDIT MODE: When reviewing or improving existing interfaces or legacy code, flag violations and provide fixes. Trigger on: any HTML/CSS/React artifact creation, "build a landing page", "create a component", "design a UI", "fix the typography", "make this look professional", "review this layout", web design, presentation design, dashboard creation, document generation, or any task producing visible text for humans. Even if the user doesn't mention typography, apply these rules whenever generating UI output.

bencium/vanity-engineering-review

Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or business value. Triggers on: "review this code", "is this over-engineered", "code review", "architecture review", "complexity audit", "vanity check", "is this necessary", "simplify this", "tech debt review", or any request to evaluate whether code or architecture is justified by actual requirements. Also trigger when the user shares a codebase and asks for feedback, when discussing framework/library choices, when reviewing PRs, or when someone is debating whether to refactor or rebuild. Nudge activation when you detect patterns of unnecessary abstraction, premature optimization, or resume-driven technology choices in code the user shares — even if they haven't asked for a vanity review.

相关技能