[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6VGMDQX0EDDCVK0G4ZP13":3,"skill-same:01M7F6VGMDQX0EDDCVK0G4ZP13":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F6VGMDQX0EDDCVK0G4ZP13","migration",null,"Applies a database migration\u002FSQL to production with a safe protocol. Use on: merged, apply the migration, where is the SQL; mergeei, pode aplicar, aplica a migration. Only on the owner's explicit request this turn.","stage2dev\u002Ftune-up","stage2dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F205088513?v=4","01M7F6TJSVA061K0AHEMXHHZAA","01M7F6TJTDN359R5QXK9C5RAZD",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Fskills\u002Fmigration\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: migration\ndescription: \"Applies a database migration\u002FSQL to production with a safe protocol. Use on: merged, apply the migration, where is the SQL; mergeei, pode aplicar, aplica a migration. Only on the owner's explicit request this turn.\"\nargument-hint: \"\u003CPR, file or migration name>\"\nallowed-tools: Bash(sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info)\n---\n\n# Migration in production\n\nTarget: $ARGUMENTS\n\n## Context (injected)\n\nContext: !`sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info`\n\nFields: `language`, `owner`, `reply_style`, `names{}`, `models{}`, `forbidden_subagent_models` (default `[\"fable\"]`), `profile_path`, `plans_dir`, `setup_done`, `tools`, `plugin_source`, `catalog_path`. Write every reply and document in `language`. Never hardcode marker or document names: use the values in `names` (keys such as `need_you`, `progress`, `part_closed`). Call the user `owner`. If the JSON did not load, run the command once with Bash.\n\nShort final reply. Read the project profile (`profile_path`): what production is, ids, database tools, type regeneration, what never to touch.\n\n## Steps\n\n1. **Request in this turn.** Writing to production needs the owner's request in their own words THIS turn (\"go ahead and apply\", \"apply it\"). A \"yes\" to another question, a vague \"go\", or \"recommended\" do not count. Without it: write `names.need_you` asking for the words, and stop.\n2. **Deploy order.** Is the PR merged? (`gh pr view --json state`). The migration goes BEFORE the backend that depends on it. If the backend already shipped without the migration, warn about the risk before applying.\n3. **Read the whole file.** Every statement. Look for: DROP, REVOKE, DELETE without WHERE, triggers, `SECURITY DEFINER`, backfill, long locks.\n4. **Pre-checks (SELECT only on production).** Current state: columns and tables, real production policies (the repo may be stale), affected data (count), whether the migration was already applied.\n5. **Backup and undo.** Before touching data: back up the affected rows and write the SQL that undoes it. Keep them in the scratchpad.\n6. **Apply.** One of two routes:\n   - Through the database tool in the profile, in small slices: one DELETE per call; DROP\u002FREVOKE in a block often fails.\n   - A single file `BEGIN; ...; migration-table record; COMMIT;` + a verification SELECT, tested first on a local Postgres, then copied to the clipboard for the owner to paste in the SQL editor.\n7. **Verify the effect.** Query the catalog (columns, policies, functions, counts). \"Success\" proves nothing.\n8. **Stamp.** The version stored in the migrations table may differ from the file name in the repo. If it differs, note it to align.\n9. **Types.** If the profile says to regenerate types after a schema change, do it and leave it as a local change for the PR.\n10. **Record.** Progress file of the phase (`names.progress`): what was applied, time, verification, undo. If the project has a Claude memory, record a short note there too.\n\n## Rules\n\n- Denied by the permission classifier: do not retry another way. Hand over the ready SQL and ask the owner to apply it.\n- Failed midway: stop. Say what was already applied and run the state queries before any retry.\n- Real customer data in production: only with a clear request and a backup done.\n- Never write a secret (connection string, password) in a file, PR or memory.\n\n## Answer\n\n- What was applied and the proof (query + result).\n- How to undo.\n- Next step in the deploy order and whose it is (owner or you).\n","# Migration in production\n\nTarget: $ARGUMENTS\n\n## Context (injected)\n\nContext: !`sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info`\n\nFields: `language`, `owner`, `reply_style`, `names{}`, `models{}`, `forbidden_subagent_models` (default `[\"fable\"]`), `profile_path`, `plans_dir`, `setup_done`, `tools`, `plugin_source`, `catalog_path`. Write every reply and document in `language`. Never hardcode marker or document names: use the values in `names` (keys such as `need_you`, `progress`, `part_closed`). Call the user `owner`. If the JSON did not load, run the command once with Bash.\n\nShort final reply. Read the project profile (`profile_path`): what production is, ids, database tools, type regeneration, what never to touch.\n\n## Steps\n\n1. **Request in this turn.** Writing to production needs the owner's request in their own words THIS turn (\"go ahead and apply\", \"apply it\"). A \"yes\" to another question, a vague \"go\", or \"recommended\" do not count. Without it: write `names.need_you` asking for the words, and stop.\n2. **Deploy order.** Is the PR merged? (`gh pr view --json state`). The migration goes BEFORE the backend that depends on it. If the backend already shipped without the migration, warn about the risk before applying.\n3. **Read the whole file.** Every statement. Look for: DROP, REVOKE, DELETE without WHERE, triggers, `SECURITY DEFINER`, backfill, long locks.\n4. **Pre-checks (SELECT only on production).** Current state: columns and tables, real production policies (the repo may be stale), affected data (count), whether the migration was already applied.\n5. **Backup and undo.** Before touching data: back up the affected rows and write the SQL that undoes it. Keep them in the scratchpad.\n6. **Apply.** One of two routes:\n   - Through the database tool in the profile, in small slices: one DELETE per call; DROP\u002FREVOKE in a block often fails.\n   - A single file `BEGIN; ...; migration-table record; COMMIT;` + a verification SELECT, tested first on a local Postgres, then copied to the clipboard for the owner to paste in the SQL editor.\n7. **Verify the effect.** Query the catalog (columns, policies, functions, counts). \"Success\" proves nothing.\n8. **Stamp.** The version stored in the migrations table may differ from the file name in the repo. If it differs, note it to align.\n9. **Types.** If the profile says to regenerate types after a schema change, do it and leave it as a local change for the PR.\n10. **Record.** Progress file of the phase (`names.progress`): what was applied, time, verification, undo. If the project has a Claude memory, record a short note there too.\n\n## Rules\n\n- Denied by the permission classifier: do not retry another way. Hand over the ready SQL and ask the owner to apply it.\n- Failed midway: stop. Say what was already applied and run the state queries before any retry.\n- Real customer data in production: only with a clear request and a backup done.\n- Never write a secret (connection string, password) in a file, PR or memory.\n\n## Answer\n\n- What was applied and the proof (query + result).\n- How to undo.\n- Next step in the deploy order and whose it is (owner or you).\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash(sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info)","\u003CPR, file or migration name>","main","bbde73350fc3c138bffa1e546839b190e0d415bc","skills\u002Fmigration",0,"https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up","https:\u002F\u002Fgithub.com\u002Fstage2dev","Tuning the unnecessary.","2026-11-14 05:05:23",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add stage2dev\u002Ftune-up --skill migration",{"tool":39,"command":40},"bunx","bunx skills add stage2dev\u002Ftune-up --skill migration",{"tool":42,"command":43},"pnpm","pnpm dlx skills add stage2dev\u002Ftune-up --skill migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Fskills\u002Fmigration\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M7F6Z7DAMCW5ES2ED8FGCC8C","instalar","One-step setup of the WhatsApp sales screen on this computer: Docker, the local Evolution API and the sales service, step by step in plain words. Use on: install, set up WhatsApp, prepare sales; instalar, preparar, preparar o WhatsApp, setup WhatsApp, configurar vendas.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Fvendas\u002Fskills\u002Finstalar\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7F6Z0BKKW3MGNAM1NJ16JHV","video","Makes a hook-first, business-oriented silent vertical reel (9:16, 1080x1920 MP4, 10 or 15 s) from a briefing, using only the owner-approved brand: strategy, the reel composition of the studio kit filled with the script and a hero drawn for this briefing, motion by the studio JavaScript engine (seek-safe, no network), render or slide reserve, and the studio QA. Runs unattended from the panel actions estudio.video and estudio.video-motion. Use on: vídeo, reel, reels, story em vídeo.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7F6YS17B793E58C07S5EX5R","post","Makes a hook-first, business-oriented still post or carousel (PNG per frame) from a briefing, using only the owner-approved brand: strategy first, one chosen hook, a composition of the studio kit with a hero drawn for this briefing, one call to action, and every frame checked by the studio QA. Runs unattended from the panel action estudio.post. Use on: post, carrossel, carousel, peça estática, post do Instagram.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fpost\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7F6YFJNJP6PT3YTFEBRQW9V","marca","Discovers the project's brand (colors, fonts, logo, name) from its own files and shows it to the owner for approval in the panel. Use on: discover the brand, descobrir marca, identidade visual do projeto, marca do estúdio.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fmarca\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7F6YBJ20F1GJN7ZFJJK8Y7Y","marca-ler","Reads the project's brand (marca.json) and says whether the owner approved it. Read-only: never approves, edits or writes anything. Use on: read the brand, is the brand approved, ler marca, marca aprovada.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fmarca-ler\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7F6Y4KXCDFMA88EHVM0DRVB","anuncio","Makes a hook-first, business-oriented ad from a briefing, using only the owner-approved brand: one master image plus the aspect-ratio adaptations the platform needs, text variations inside the platform limits, and an import sheet with everything Paused (Google Ads Editor CSV, or an experimental Meta sheet). Publishes nothing and calls no ad API. Runs unattended from the panel action estudio.anuncio. Use on: anúncio, anuncio, ad, Google Ads, Meta Ads.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fanuncio\u002FSKILL.md",[],[]]