mezotv

Upload a local screenshot, GIF, or short video to temporary public storage and get a presigned URL to embed in a PR description, issue comment, or agent report. Use WHENEVER you (or another skill) have a local image/video that needs to be SHOWN to a human in GitHub — before/after design screenshots, a recorded flow, QA or canary evidence, "attach a screenshot/video to the PR". Prefer this over pasting local file paths, which GitHub cannot render.

Repo file-organization convention for TypeScript projects. ALWAYS use this when creating new files or deciding where code goes — types, schemas, validation, utility/helper functions, constants, enums, and config literals each belong in their own dedicated folder, not inline next to feature code or dumped in one grab-bag file. Use whenever you add a type/interface, a validation schema, a util/helper, a constant, or are asked where something should live, how to structure the repo, or to organize/refactor file layout.

Git workflow for pushing code and opening pull requests on GitHub. ALWAYS use this before you git push, push to a remote, open or create a pull request, raise a PR, or "ship" code. Covers confirming the user actually asked to push, cutting a Conventional-Commits feature branch off main, writing a Conventional-Commit PR title, and using the repo's .github PR template as the body. Use whenever the user says push, ship, open/create a PR, raise a pull request, or commit-and-push.