القائمة
Design and implement APIs, external integrations, webhooks, clients, and service boundaries using technology-agnostic principles.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/soden46/engineer-flow --skill api-integrationيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى 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 | api-integration |
| description | Design and implement APIs, external integrations, webhooks, clients, and service boundaries using technology-agnostic principles. |
| metadata | {"internal":true} |
Use this skill for APIs, HTTP clients, webhooks, third-party integrations, service communication, pagination, retries, and integration boundaries.
Define explicit contracts for requests, responses, errors, and side effects.
Validate data crossing external boundaries.
Distinguish transport concerns from business logic.
For outbound calls consider:
Do not retry non-idempotent operations blindly.
For webhooks consider:
Keep provider-specific assumptions isolated where practical.
Do not leak transport-specific details throughout unrelated application code.
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.
