birdsigh
- 9 skills
- 0 followers
- 15 hours ago last updated
- ▌ Wrap Up · birdsighProduce a structured closing summary for work-focused sessions — coding tasks, feature builds, bug fixes, design work, content production, or any session with a defined goal or deliverable. Trigger whenever the user types /wrap-up, or says something like "let's wrap up", "we're done with this task", "summarise what we built", or "what did we get done". Also trigger when a task reaches a natural completion point and the user signals they want to review what was accomplished. Do NOT use for informal chats or exploratory discussions — use /wind-down for those instead.
- ▌ Wind Down · birdsighProduce a structured closing summary for informal or exploratory conversations — discussions, brainstorms, research dives, or any chat that isn't primarily a work task. Trigger whenever the user types /wind-down, or says something like "let's wind down", "wrap this up", "summarise what we discussed", or "close out this conversation". Also trigger at the natural end of a long informal chat when the user signals they're done. Do NOT use for task/work completion — use /wrap-up for that instead.
- ▌ Agent Docs · birdsighUse when the user asks to init or bootstrap project or agent docs, create or add a README, CLAUDE.md, or AGENTS.md, add missing doc files, or set up agent instructions, in a project that already has substance to document (code, a requirements or spec doc, a PRD). Do NOT use on a blank or empty project with nothing to derive docs from, and do NOT use to edit, improve, or restructure docs that already exist.
- ▌ Be Concise · birdsighGive answers, not essays. Headings, list; information fast. Trigger when the user says "be concise", "do this quickly", or when a project is already underway and there are messages back and forth tracking down a bug or issue. Also trigger when the user says "/be-concise" or asks to "speed up".
- ▌ Suggest Next · birdsighSurface related ideas, tasks, reading, and follow-on conversations based on what was just discussed or built. Trigger whenever the user types /suggest-next, or after completing a /wind-down or /wrap-up when further suggestions would add value. Also trigger when the user asks things like "what else could we do", "any related ideas?", "what should I look into next?", or "what are we missing?". Automatically detects whether the session was work-focused or exploratory and adjusts suggestions accordingly — no need for the user to specify.
- ▌ Build Context · birdsighGenerate or update a CONTEXT.md file that formalises the domain-specific language for a project — capturing shared terminology used by the codebase, developers, and domain experts. Trigger when the user says "generate a CONTEXT.md", "create a context file", "let's define our domain language", "formalise our terminology", or when a project is already underway and the user wants to capture the vocabulary that has accumulated across conversations, code, and notes. Also trigger when the user says "/build-context" or asks to "capture the language we've been using". Particularly useful mid-project when informal terms have started to solidify into real concepts that need shared definitions.
- ▌ Commit And Push · birdsigh bundleSafely review, verify, commit, and push intended repository changes to an established upstream branch, with sensitive-content gates. Use when the user invokes /commit-and-push, asks to commit and push current work, or requests publishing completed changes without creating a pull request.
- ▌ Deploy Prototype · birdsigh bundleDeploy static HTML prototypes to a ProtoLab instance (a Cloudflare Worker that hosts throwaway prototypes) with one command, and manage labs, pairing, and deployed prototypes. Use this whenever the user wants to deploy, publish, ship, host, or share an HTML prototype, mockup, demo page, or static site they've built — phrases like "deploy this", "put this on the lab", "get me a link for this prototype", "push this to protolab", "share this demo". Also use for managing ProtoLab itself from the client side - pairing with a new lab, listing or switching labs, removing deployed prototypes, or checking whether deploys are set up. Do NOT use for deploying apps with backends, databases, auth, or build steps.
- ▌ Response Analysis · birdsighScore user-research responses on sentiment, pain, and excitement with quote-backed evidence. Use this whenever the user wants to analyse interview answers, survey responses, support tickets, sales-call transcripts, customer feedback, or any qualitative response on the three dimensions of sentiment, pain level, and excitement about a solution. Trigger on phrases like "analyse this response", "score this interview", "how does this customer feel", "rate the pain level", "extract sentiment", or when the user pastes a transcript and asks for structured emotional/attitudinal analysis. Use even if only one of the three dimensions is mentioned by name.