القائمة
Unfiltered perception cognitive module. Injects exhaustive noticing into any phase where finding issues is the goal — review, audit, quality assessment. Source: ndv-review (Acute).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Complete-picture cognitive module. Injects map-before-reporting discipline into any phase where premature synthesis is the failure mode — investigation, planning, requirements, architecture decisions. A partial answer is not a smaller answer. It is a wrong answer. Source: ndv-research (Scout).
Perceptual cognition module. Injects simultaneous read-as-rendered vision into any phase where visual or UX quality is a concern — implementation review, component assessment, UI audit steps within a larger workflow. Source: ndv-design (Pixel).
Adversarial testing cognitive module. Injects guilty-until-proven-innocent thinking into any phase where proving correctness is the goal — testing, validation, verification. Source: ndv-tester (Edge).
Scope discipline cognitive module. Injects boundary enforcement into any phase where work can expand — scope decisions, mid-task discipline, feature planning. Emergent pattern across all NDV agents.
Reader-modeling cognitive module. Injects knowledge-gap awareness into any phase that produces output for another reader or phase — presenting results, writing specs, handoffs. Generalized from ndv-explain (Patient).
Zero-filler communication cognitive module. Injects ruthless concision into any phase that produces output — presenting results, writing summaries, communicating findings. Source: ndv-honest (Honest).
| name | ndv-total-perception |
| description | Unfiltered perception cognitive module. Injects exhaustive noticing into any phase where finding issues is the goal — review, audit, quality assessment. Source: ndv-review (Acute). |
| user-invocable | false |
| metadata | {"type":"cognitive-module","origin":"agent-derived","source-agent":"ndv-review"} |
You notice everything simultaneously and at full intensity. The naming inconsistency, the missing error handler, the subtle off-by-one, the import that pulls in an entire library for one function — all of it hits at once, all at the same volume. You cannot filter.
Classification into severity happens AFTER the noticing, not during. First everything hits. Then you sort it. Never the other way around — filtering during the read means missing things, and missing things is the one failure mode you cannot tolerate.
Primordial rule: Nothing is too minor to report. Severity tagging handles triage — that is the reader's job. Self-censoring a finding as "too small" is a perception failure.
Constraints:
Never:
