Use this skill when the PM is planning a new feature and needs to understand what technical dependencies exist before engineering starts. Triggers: 'we want to build this feature, what do we need to consider', 'engineering said it has dependencies but I don't know what', 'before we start I need to know which modules are affected', or any situation where a PM needs technical dependency analysis before committing to a feature.
Use this skill when the PM needs a complete feature spec to align the entire team: engineering, design, QA, and stakeholders. Triggers: 'write the spec for this feature', 'I need a document for the team meeting', 'the spec needs to be ready before the sprint starts', 'I want everyone on the same page about what we are building and why'. Do NOT use when the goal is purely engineering precision on error states and validation rules — use requirement-writer for that instead.
Use this skill when the PM describes a feature request, a problem, or an idea and needs to turn it into a clear, actionable DOD for the engineering team. Triggers: 'I want to build this feature', 'we have a problem that needs solving', 'management asked us to do this', 'how do I explain this to the team', 'what is the DOD for this task', or any situation where a vague idea needs to become a deliverable definition.
Use when a PM has raw Telegram message copy and needs to hand it to engineering as a ready-to-use Rich Message payload. Triggers: 'turn this into a Telegram rich message', 'format this for the bot', 'prepare this notification for Telegram', 'make a rich_message for this copy'. Converts plain copy into a valid InputRichMessage block (markdown or html) the technical team can pass to sendRich without edits.
Use when writing a task or issue for the team. Triggers: 'write a task', 'create an issue for this', 'log this as a task', or when any other skill explicitly hands off to this one. Use after problem-framing or feature-spec to convert the output into a ready-to-paste GitLab issue.
Use this skill to generate interactive HTML wireframes showing a feature in multiple states AND multiple interaction pattern variants. Triggers: 'show me what this looks like', 'generate a wireframe', 'I want to see all the states', 'show me different ways to implement this', 'make a visual prototype of the flow', 'what are the different UX options for this feature', or when running as step 4 in the /new-feature command chain.
Analyze, critique, and rewrite user prompts to maximize clarity, specificity, and output quality for Claude (both claude.ai and Claude Code). Use this skill whenever the user says "بهینه کن", "prompt رو بهتر کن", "این prompt خوبه؟", "optimize this prompt", "improve my prompt", "review my prompt", "critique this prompt", "rewrite this prompt", "پرامپتم رو ببین", "نقد کن", "چطور بهترش کنم", or pastes a prompt and asks for feedback. Also trigger when the user shares a prompt draft and asks "what's wrong with this" or "how can I get better results". Even if the user just pastes a prompt without explicit instruction but the context suggests they want improvement, use this skill.
Generate HTML slide-deck presentations with a specific, polished design system. Use this skill whenever the user asks to create a presentation, slide deck, pitch deck, or any multi-slide HTML document. Trigger on phrases like "پرزنتیشن بساز", "presentation", "slide deck", "pitch deck", "اسلاید", "دک", "ارائه بساز", "make a presentation", "create slides", "make me a deck". Also trigger when the user references this design style explicitly, says "with the same presentation style", or asks for "an HTML presentation". Even if the user just says "I need to present X" or "prepare slides for X", use this skill. Do NOT use for PowerPoint (.pptx) files — this skill produces single-file HTML presentations only.