القائمة
Review whether code works with framework conventions instead of fighting them with unnecessary abstractions, mixed ecosystems, or upgrade-hostile choices.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | dandy-code-framework-fit |
| description | Review whether code works with framework conventions instead of fighting them with unnecessary abstractions, mixed ecosystems, or upgrade-hostile choices. |
| argument-hint | [file, diff, architecture note, or dependency decision] |
Use this skill when a user asks about framework architecture, repositories, custom abstraction layers, mixing libraries from several frameworks, or postponing upgrades.
The output should distinguish useful boundaries from framework resistance and recommend the simplest convention-aligned path.
This skill may read source, dependency manifests, and architecture notes. It should not change dependencies, framework versions, or architecture artifacts unless the user explicitly asks.
Use configured artifact language for recommendations. Keep framework names, package names, and technical terms unchanged unless configured otherwise.
Review AI-assisted code changes for continuation bias, missing context, architectural asymmetry, security gaps, and code ownership.
Review method and object APIs for argument count, option shape, boolean flags, object parameters, and fluent configuration.
Identify small, reusable components that can be isolated from a large codebase without prematurely forcing microservices.
Review error handling, logging, exception clarity, and debugging seams so failures stay visible and testable.
Simplify control flow with early returns, shallow nesting, explicit conditions, and readable branching.
Review and improve names for variables, methods, classes, files, routes, booleans, units, and paired operations.
