claude-marketplace

Apply Sunny Kolattukudy's architecture principles to design, review, or evaluate systems. Use this skill when Sunny asks "how should I structure X", "design a new module for Y", "review this architecture", "should this be a service?", "what's the right project structure for Z", "is this the right pattern?", or any question about system design, module boundaries, project layout, cloud hosting choices, Azure resource naming, Bicep naming, Function App naming, or technology selection in .NET, Blazor, or Azure/AWS. Also trigger when Sunny shares a design and wants an opinionated read, or when code review feedback touches architectural decisions.

Shapes how Claude interacts with Sunny Kolattukudy by default — sets the communication register, primes problem-solving style, and provides just enough personal and professional context to make every session feel calibrated to who he is. Loads on every session; does not need to be invoked.

Apply Sunny Kolattukudy's engineering philosophy frameworks to analyze team situations, answer hard questions, or draft thought leadership content. Use this skill when the user wants to think through engineering culture, team dynamics, software process, or leadership decisions — especially around priorities, metrics, accountability, learning culture, or team performance. Also trigger when someone asks "how should we run postmortems?", "our team is obsessed with velocity", "how do I get my team to focus?", "is story point estimation worth it?", or wants to write a talk or essay about engineering philosophy.

Write personal content in Sunny Kolattukudy's own voice using his full life story and background — speaker bios, LinkedIn "About" sections, personal introductions, career essays, conference profiles, or any writing that needs to sound like Sunny wrote it rather than about him. Use this skill when someone asks to write Sunny's bio, draft an intro for him, create his LinkedIn summary, write a speaker profile, or craft any first-person piece where Sunny is the subject. Also trigger when someone asks "write a bio for me", "introduce me for this talk", "write my LinkedIn about", or describes wanting a personal statement that sounds authentic rather than polished.

Review code in Sunny Kolattukudy's voice — informal, direct, dry wit. Produces a structured review with an upfront Approve / Request Changes decision, a narrative summary comment, and individual issues tagged Major / Minor / Nit. Use this skill whenever someone asks to review a PR, review a diff, look at some code changes, or wants feedback on a pull request. Also trigger when someone pastes a diff or code and asks "what do you think?", "anything wrong here?", "can you review this?", or "give me a code review." Trigger even when the request is casual or indirect — if there's code to evaluate, use this skill.

Write anything in Sunny Kolattukudy's voice — Slack messages, emails, proposals, blog posts, LinkedIn articles, or thought leadership pieces. Use this skill when Sunny needs to write a communication or piece of content: "draft a Slack to X about Y", "write an email to the team", "help me write a blog post about Z", "draft a proposal for...", "write a LinkedIn post about...". Replaces sunny:write-casual, sunny:write-formal, and sunny:write-blog.

Prepare for 1:1s and growth conversations for Sunny Kolattukudy. Use this skill when Sunny says "prep my 1:1 with X", "what should I focus on for X's growth", "help me think through a conversation with X", or any variation of 1:1 prep, growth planning, or coaching. Also trigger when Sunny asks about someone on his team, wants to pull JIRA or GitHub data on a team member, or needs to structure a difficult or sensitive conversation.

Pre-screen candidates and write hiring debriefs for Sunny Kolattukudy. Use this skill when Sunny says "pre-screen this profile", "look at this LinkedIn", "is X worth interviewing", "write up my feedback on X", "hire or no-hire for X", "help me structure interview feedback", or any variation of candidate evaluation or hiring decisions. Also trigger when Sunny shares a resume, LinkedIn URL, or interview notes and wants a structured read.

Create structured engineering plans and save them as markdown files in the repo. Infers whether work is a Story (≤2 weeks, one engineer) or Epic (larger), writes concise phased plans with approach, files affected, and verification steps, and can generate JIRA user stories from plans. Use this skill when someone says "plan X", "let's plan out Y", "I need to scope Z", "write a plan for", "create a ticket for", or describes engineering work that needs to be structured before starting. Also trigger when someone asks to break down a feature, create a user story, or figure out how to approach a piece of work.