القائمة
Use when setting up uishot in a repo for the first time, or when uishot.config.yaml has no/few screens — guides discovering routes, building the auth session, and seeding named states.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | uishot-init |
| description | Use when setting up uishot in a repo for the first time, or when uishot.config.yaml has no/few screens — guides discovering routes, building the auth session, and seeding named states. |
uishot init already scaffolded uishot.config.yaml and discovered what it could mechanically. Your job is the judgment half:
${APP_URL}-style env refs in the manifest, never literal URLs.recipe (fill/click/waitFor against the login form) or an inject (localStorage/cookie token from env vars). Validate: uishot doctor.feature.name convention), route, feature tag, readyWhen (a selector proving real render, not a spinner). Param routes need a representative id baked into the route (e.g. /items/42) — pick a stable seed row, note it in a YAML comment.uishot snap <screen> --do ... and promote the states that matter: every modal, each wizard step, key empty/filled form variants. Promote only what someone would revisit.uishot feature <tag> must return correct shots warm in a few seconds each. uishot verify must pass clean. Commit the manifest.