القائمة
Use when changing an existing website or browser experience and its stack, entry points, ownership, baseline, commands, or verification route are not yet explicit.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a user explicitly requests an independent review, challenge pass, or second opinion on a rendered website or animation artifact. Produces one bounded evaluator report and evidence verdict; it never auto-starts another build pass.
Use when a website task involves visual direction, existing-project discovery, animation, browser verification, or delivery and the smallest bounded route is not yet explicit.
Use when a user gives one sentence, a vague idea, or a loose brief and wants a finished website route. Turns "I want something like X" into an explicit bounded route, a verified artifact, and an honest handoff without autonomous review loops.
Use when claiming a visible, responsive, interactive, scroll-led, canvas, WebGL, or animated browser result is complete and fresh evidence is needed.
Use when website or browser-motion work is being delivered, packaged, released, transferred to another contributor, or described as complete.
Use when browser work needs UI transitions, scroll choreography, GSAP, Motion, canvas, WebGL, responsive motion, or reduced-motion behavior.
| name | website-motion-intake |
| description | Use when changing an existing website or browser experience and its stack, entry points, ownership, baseline, commands, or verification route are not yet explicit. |
Understand the host project before changing it. The existing stack and strongest accepted baseline outrank a preferred architecture.
Capture only information needed for the task: runtime, run/build commands, entry route, content/style/motion owners, verification path, protected files, and rollback point. Say the result back in one sentence before implementation.
Do not replace frameworks, add paid services, alter deployment, expose previews, or touch credentials as a side effect of visual work. Create folders only when they make the next change easier to find.
Use ../../references/project-intake.md for decision guidance and ../../templates/project-intake.md for a copyable working form.
