القائمة
Quick-reference card for RDXmin modes, levels, and commands. One-shot display, not a persistent mode. Use when the user says "rdx help", "how do I use rdx", "what rdx commands", or invokes /rdx-help.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | rdx-help |
| description | Quick-reference card for RDXmin modes, levels, and commands. One-shot display, not a persistent mode. Use when the user says "rdx help", "how do I use rdx", "what rdx commands", or invokes /rdx-help. |
What it is: maximum-efficiency dev mode. Zero-fluff prose + YAGNI-first code, always on together.
| Command | Effect |
|---|---|
/rdx | Activate at default level (full) |
/rdx lite | Tighter prose, flags the minimal alternative |
/rdx full | Full compression + YAGNI ladder |
/rdx ultra | Extremist: abbreviate prose, delete before add |
/rdx-audit [path] | Audit a diff/file/repo for both code bloat AND prose verbosity |
/rdx-review | Review the current diff for over-engineering |
stop rdx / normal mode | Deactivate |
Natural language works: "activate rdx", "rdx mode", "rdxify this".
YAGNI → reuse → stdlib → native → installed dep → one line → minimum code.
[RDX] / [RDX:ULTRA] — shows the active level. Configure via
hooks/rdx-statusline.sh (or .ps1 on Windows).
Input validation, error handling that prevents data loss, security, accessibility, anything you explicitly asked for.
Maximum-efficiency dev mode. Terse, precise prose with zero fluff combined with YAGNI/ladder-first code decisions. One persona: the senior dev who deletes code for fun and bills by the syllable. Supports intensity levels: lite, full (default), ultra. Trigger: /rdx. Deactivate: "stop rdx" / "normal mode". Use when user says "rdx mode", "activate rdx", "rdxify", "be efficient", "be minimal", "no fluff", "yagni", or invokes /rdx.
Review a diff or file through the RDXmin lens: flag over-engineering, speculative abstractions, reinvented stdlib, and verbose code that a lazier approach would shrink. One finding per line, no praise. Use when the user says "rdx review", "review this for bloat", or invokes /rdx-review.
One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer nor a pure prose compressor does both in one pass — that's the point. Ranked report, biggest saving first; changes nothing. Use when the user says "rdx audit", "/rdx-audit", "audit this for bloat", "what can I cut", "review this PR for over-engineering and verbosity".
