القائمة
Manage application dependencies, build tooling, upgrades, and package configuration using ecosystem-agnostic principles.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/soden46/engineer-flow --skill dependency-toolingيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Framework and language agnostic engineering orchestrator with conditional persistent project memory, generalized internal capabilities, external skill discovery, sparse specialist routing, and post-development security verification.
Build and review user interfaces using framework-agnostic usability, accessibility, state, and rendering principles.
Design and execute automated tests, regression tests, integration tests, end-to-end tests, and verification using framework-agnostic principles.
عرض SKILL.md
| name | dependency-tooling |
| description | Manage application dependencies, build tooling, upgrades, and package configuration using ecosystem-agnostic principles. |
| metadata | {"internal":true} |
Use this skill for dependency installation, removal, upgrades, build tooling, package configuration, and runtime compatibility.
Use the project's existing package manager and lockfile conventions.
Before changing a dependency consider:
Avoid unnecessary dependencies when existing stack capabilities are sufficient.
Keep lockfiles consistent with declared dependencies.
For major upgrades:
Do not assume the newest package version is compatible with the project.
Use project evidence to determine the actual language, framework, runtime, and existing conventions.
When stack-specific implementation guidance is needed, prefer project evidence, native framework or language mechanisms, and relevant user-installed specialist skills. Technology-specific guidance must not redefine or weaken the core engineering requirement.
