القائمة
Documentation collapse anti-patterns - detection rules, bad examples, and remediation strategies for type-mixing violations
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/nWave-ai/nWave --skill nw-collapse-detectionيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
استنادا إلى تصنيف SOC المهني
| name | nw-collapse-detection |
| description | Documentation collapse anti-patterns - detection rules, bad examples, and remediation strategies for type-mixing violations |
| user-invocable | false |
| disable-model-invocation | true |
Documentation collapse = types merge inappropriately, serving no audience well.
Description: Tutorial explains "why" extensively | Detection: explanation >20% | Fix: extract to separate doc, link back
Description: How-to teaches basics first | Detection: teaching fundamentals before steps | Fix: link to tutorial, assume baseline
Description: Reference includes conversational prose | Detection: prose paragraphs in entries | Fix: move to explanation doc, keep factual
Description: Explanation ends with "do this" steps | Detection: step-by-step in explanation | Fix: move steps to how-to, link
Description: Single doc tries all four types | Detection: 3+ quadrants in one doc | Fix: split with clear boundaries
Flag collapse when:
20% content from adjacent quadrant | Two user needs served simultaneously | Ambiguous user journey stage
# 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 Configure Authentication
First, let's understand what authentication is. Authentication is...
Problem: Should assume user knows what authentication is. Link to a tutorial instead.
## 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.
# 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.