القائمة
Create, edit, or promote a standard in context/standards/ — from the conversation, a graduated lesson, or another project.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/dikamilo/dx-workflow --skill dx-standards-updateيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Archive a completed change or effort — move its folder to context/archive/ and stamp it archived.
Record one finding — a warning or a decision-with-rationale — as an append-only entry in foundation/lessons.md.
Start a new piece of work — creates a change or an effort and points you at the next step.
عرض SKILL.md
| name | dx-standards-update |
| description | Create, edit, or promote a standard in context/standards/ — from the conversation, a graduated lesson, or another project. |
| argument-hint | ["--from=PATH"] |
Land a rule in the right context/standards/<layer>/<topic>.md. Standards are the rulebook — prescriptive, project-wide, stable, and edited in place (a catalog, not an append-only log). Read foundation/glossary.md for naming (a one-line habit — no section).
Guard. context/standards/ must exist. If it is missing, tell the user to run /dx-init first.
foundation/lessons.md entry that has stopped being "this one time" and become "how we do it here." Read it and carry its rule forward.--from=PATH — read the named file (e.g. a graduated lesson, or another project's context/standards/…) and take the rule from it.dx-references with knowledge-layer)Use it for the standards-vs-lessons distinction, the standard entry shape, and the promotion criteria — confirm this rule is recurring and generalized, not a one-off (a one-off stays a lesson).
Pick the file by layer (global / frontend / backend / testing) × topic (the existing filename it belongs in, e.g. coding-style.md, error-handling.md). Prefer an existing file; create a new <topic>.md only when nothing fits.
Append the rule or refine an existing entry — a ## <heading> plus one to a few prescriptive lines ("do this"), matching the shape and tone of the neighbours. No preamble, no rationale essays. If you are promoting a lesson, add a one-line note to that foundation/lessons.md entry that it graduated (leave the entry — lessons are append-only).
The rule lives in one context/standards/ file, prescriptive and concise; any promoted lesson is marked graduated. Then print what changed and stop:
Standard updated: context/standards/<layer>/<topic>.md — <one-line what changed>
Next: /dx-plan <change-id> — the checklist will now match this standard
Stop. Do not chain into another skill.