القائمة
Design maintainable application boundaries and component relationships using framework-agnostic architecture principles.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/soden46/engineer-flow --skill architectureيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى 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 | architecture |
| description | Design maintainable application boundaries and component relationships using framework-agnostic architecture principles. |
| metadata | {"internal":true} |
Use this skill for service boundaries, modules, dependency direction, interfaces, adapters, orchestration, and architectural refactoring.
Prefer clear responsibilities and explicit dependencies.
Separate concerns when doing so improves:
Do not introduce abstraction merely for abstraction's sake.
Stable application/business logic should not depend unnecessarily on volatile infrastructure details.
Use interfaces or boundaries where multiple implementations, isolation, or testing value justifies them.
Prefer incremental architectural change over unnecessary rewrites.
Preserve public behavior during structural refactoring unless behavior change is intentional.
Architecture should follow actual project complexity, not pattern names.
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.
