vijaykpatel
@vijaykpatel
Public Skills
design-taste
by vijaykpatel
Apply principles of good design taste when creating, reviewing, or critiquing any creative or technical work. Use this skill whenever the user asks you to design something, review a design, create UI/UX, architect a system, write something with aesthetic intent, evaluate the quality of code or creative work, or asks for feedback on whether something is "good." Also trigger when users mention taste, aesthetics, beauty in design, elegance, simplicity, or when they want help making something not just functional but genuinely well-crafted. This skill applies across domains: software, writing, visual design, architecture, presentations, APIs, data models, and more. Even if the user doesn't explicitly mention "design," use this skill when the underlying task is about making something better, more elegant, or more refined.
cold-outreach
by vijaykpatel
"Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail."
pr-review-handler
by vijaykpatel
Handle PR review feedback by checking for comments, determining necessary changes, responding appropriately to reviewers, implementing fixes, and pushing updates. Use when the user asks to work on an existing open PR, address PR feedback, fix review comments, or handle bot review suggestions (Devin AI, Cursor Bugbot, etc.).
continuous-claudemd-updates
by vijaykpatel
Maintains CLAUDE.md in sync with codebase changes after commits. Use when (1) A commit has been made and CLAUDE.md needs updating, (2) User explicitly requests CLAUDE.md update or audit, (3) Major refactoring or architectural changes occur, (4) New conventions or patterns are established, (5) Files referenced in CLAUDE.md are deleted/moved. Keeps documentation concise by moving verbose content to docs/ folder with links, removes outdated information, and ensures CLAUDE.md reflects current codebase state.