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…
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
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…