nw-collapse-detection

Featured

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

AI & Automation 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 ```markdown # 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 ```markdown # How to Configure Authentication First, let's understand what authentication is. Authenticat...

Details

Author
nWave-ai
Repository
nWave-ai/nWave
Created
9 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

testing-anti-patterns

Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.

1,581 Updated 5 months ago
rohitg00
AI & Automation Listed

docs-patterns

Documentation conventions -- doc types, structure, register, per-type rules, and quality standards.

3 Updated yesterday
Jartan-LLC
AI & Automation Listed

rootnode-anti-pattern-detection

Detects seven structural anti-patterns in Claude Projects that cause unpredictable output, ignored instructions, and degraded quality. Diagnoses Monolith, Orphan File, Echo Chamber, Phantom Conversation, Kitchen Sink, Misaligned Hierarchy, and Blurred Layers. Use when user says "what's wrong with my project," "Claude ignores my instructions," "diagnose my project," "why is output inconsistent," "review my project setup." Also trigger on symptom-phrased: "Claude doesn't follow my rules," "my instructions keep getting overridden," "my Project isn't behaving as designed." Use alongside rootnode-project-audit if available for deeper structural analysis. Activate whenever the user describes symptoms of unreliable, inconsistent, or degraded Claude Project output, even if they do not name a specific pattern. Do NOT use when the user's primary request is Memory-layer rebalancing (use rootnode-memory-optimization if available) or scoring a single prompt (use rootnode-prompt-validation if available).

40 Updated 2 weeks ago
drayline