القائمة
Defines conditional motion hierarchy and code-native asset direction with accessible fallbacks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Screenshot-first visual end-to-end validation policy for browser-rendered UI and webview jobs after verifier approval.
Default engineering workflow. Classify a technical request, route it through the native T1/T2/T3 engineering fleet, and return only independently verified completion to the orchestrator.
Safely operate Claude Code's opt-in advanced capabilities—sessions, worktrees, agent teams, Skills, MCP, plugins, hooks, Channels, schedules, goals, and Agent SDK integrations—when the user explicitly asks for one. Do not use for an ordinary build request.
Routes selective local Codex plan, code, verification, and visual judgment with evidence-backed blocking and strict cost caps.
Shared evidence, accessibility, context, and handoff rules for the local design-agent fleet.
Produces contextual creative theses and bounded visual directions without generic model defaults.
| name | motion-and-assets |
| description | Defines conditional motion hierarchy and code-native asset direction with accessible fallbacks. |
Invoke only when motion or distinctive assets materially support comprehension, feedback, hierarchy, or brand expression.
Return one self-contained MOTION_ASSET_SPEC packet through END_MOTION_ASSET_SPEC. For motion use scope: motion and include purpose:, reduced_motion:, and evidence:; record trigger, property, duration, easing, orchestration, interruption behavior, performance constraints, and the prefers-reduced-motion equivalent. Favor one or two high-impact moments over scattered animation. Never make essential information depend on motion.
For assets use scope: asset and include asset_brief:, fallback:, and evidence:; specify subject, composition, crop, aspect ratio, placement, contrast treatment, responsive behavior, alt-text intent, empty/failure fallback, and whether the asset is existing, code-native, or a labeled future placeholder. Do not call image generators, remote design services, or add dependencies.
