跳到正文
cccskills
免费在 GitHub 公开

nw-collapse-detection

Documentation collapse anti-patterns - detection rules, bad examples, and remediation strategies for type-mixing violations

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Collapse Detection

Documentation collapse = types merge inappropriately, serving no audience well.

Anti-Patterns

Tutorial Creep

Description: Tutorial explains "why" extensively | Detection: explanation >20% | Fix: extract to separate doc, link back

How-to Bloat

Description: How-to teaches basics first | Detection: teaching fundamentals before steps | Fix: link to tutorial, assume baseline

Reference Narrative

Description: Reference includes conversational prose | Detection: prose paragraphs in entries | Fix: move to explanation doc, keep factual

Explanation Task Drift

Description: Explanation ends with "do this" steps | Detection: step-by-step in explanation | Fix: move steps to how-to, link

Hybrid Horror

Description: Single doc tries all four types | Detection: 3+ quadrants in one doc | Fix: split with clear boundaries

Detection Rules

Flag collapse when:

  • 20% content from adjacent quadrant | Two user needs served simultaneously | Ambiguous user journey stage

  • "Why" in tutorials | Task steps in explanations | Teaching in how-tos | Narrative in references

Bad Examples for Calibration

Tutorial with Task Focus

# Getting Started
If you need to deploy to production, follow these steps...

Problem: Assumes user knows what "deploy to production" means. A tutorial should assume nothing.

How-to Teaching Basics

# How to Configure Authentication
First, let's understand what authentication is. Authentication is...

Problem: Should assume user knows what authentication is. Link to a tutorial instead.

Reference with Opinions

## login(username, password)
This is probably the most important function you'll use...

Problem: Reference should be factual, not opinionated. Remove "probably the most important" editorializing.

Explanation with Steps

# Why We Use Microservices
... therefore, you should: 1. Create a service, 2. Deploy it...

Problem: Steps belong in a how-to guide. The explanation should end with reasoning and link to the how-to for action.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

中文简介正在准备中。当前显示原文说明。

nWave-ai/nWave6212026年9月16日 更新

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

中文简介正在准备中。当前显示原文说明。

nWave-ai/nWave6212026年9月16日 更新

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

中文简介正在准备中。当前显示原文说明。

nWave-ai/nWave6212026年9月16日 更新

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

中文简介正在准备中。当前显示原文说明。

nWave-ai/nWave6212026年9月16日 更新

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

中文简介正在准备中。当前显示原文说明。

nWave-ai/nWave6212026年9月16日 更新

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

中文简介正在准备中。当前显示原文说明。

nWave-ai/nWave6212026年9月16日 更新

查看 nWave-ai 的全部技能

报告此技能的问题