imamirezaei
UserProduct Team Skills
Categories
Indexed Skills (25)
design-handoff
Use this skill to prepare a complete handoff document for engineering. Triggers: 'prepare the handoff', 'write the handoff doc', 'I'm ready to hand off this feature', 'generate the spec for engineering', or when running as step 2 in the /design-handoff chain.
design-policy-review
Use this skill WHILE the design is in progress — not when it is finished. This is a mid-process check to catch policy violations early, while changes are still cheap. Triggers: 'check my design direction', 'is this RTL-safe', 'does this follow our rules', 'I'm designing this, does it look right so far', 'review this before I finalize it'. Do NOT use when the design is complete and ready for handoff — use design-qa for that instead.
design-qa
Use this skill ONLY when the design is complete and ready for handoff — not while it is still in progress. This is the final gate before engineering gets the file. Triggers: 'QA this design', 'is this ready for handoff', 'run a final check', 'check the design before I send it to engineering'. Do NOT use mid-process — use design-policy-review for that instead.
design-research
Use this skill to understand the design context before starting visual work: existing patterns, component inventory, and open UX decisions. Triggers: 'what components are already in use', 'what design patterns exist for this', 'help me understand the current UI', 'before I start designing', or when picking up a feature for the first time.
figma-to-code
Use this skill to translate a Figma design into Vue 3 + Vuetify 3 component code. Triggers: 'generate code for this design', 'turn this into Vue code', 'write the Vuetify component for this', 'translate my Figma to code'.
implementation-review
Use this skill when the designer wants to verify that what engineering implemented matches the Figma design. Reads both Figma and the codebase, compares them, and produces a gap report. Triggers: 'does the implementation match the design', 'check what was built against Figma', 'review the implemented component', 'QA the dev output', 'does the code match my design'.
microcopy-writer
Use this skill to write or review UI copy: button labels, error messages, empty states, tooltips, confirmation dialogs, and other in-product text. Triggers: 'write copy for this', 'help me write the error message', 'what should this button say', 'review this microcopy', 'write the empty state text'.
vuetify-constraint-check
Use this skill to verify that every UI component in a design can be implemented with Vuetify 3. Triggers: 'check Vuetify compatibility', 'can this be built with Vuetify', 'verify component coverage', 'are there any Vuetify gaps', or when running as step 1 in the /design-handoff chain.
decision-logger
Use this skill when an important product decision has been made and needs to be documented before it gets lost. Triggers: 'we need to write this decision down', 'why did we choose this design', 'why did we not build this feature', 'the meeting ended and we decided something but nobody wrote it down', 'we reduced scope but never documented why', or any situation where a decision was made but not documented.
edge-case-finder
Use this skill when the PM has defined a feature and wants to find what could go wrong or what they haven't thought of. Triggers: 'what did I miss', 'what are the edge cases for this feature', 'I want to make sure nothing is left out', 'engineering said we didn't consider this case', or any situation where a feature definition needs stress-testing before engineering starts.
feature-dependency
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.
feature-prioritization
Use this skill when the PM needs to prioritize features, compare options against the roadmap, or build a defensible argument for or against a feature request. Triggers: 'which one should we build first', 'this conflicts with our roadmap', 'management wants this feature but I don't think it's a priority', 'how do I justify not doing this', 'if we add this what do we drop', or any situation where the PM needs to make a prioritization decision or defend one.
feature-spec
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.
problem-framing
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.
qa-guide
Use this skill when a feature is ready for testing and the PM or QA engineer needs a complete, prioritized test plan. Triggers: 'we need to test this, what do we check', 'what is the test plan for this feature', 'what should QA test', 'we changed the payment module and need to make sure nothing broke', or any situation where a structured testing guide is needed before or after a release.
release-impact
Use this skill when a feature or change is ready to be released and the PM needs to understand what other parts of the system might be affected. Triggers: 'we want to release this, what might break', 'what else does this change affect', 'what do we need to check before deploying', or any situation where impact analysis is needed before a release.
requirement-writer
Use this skill when the PM needs a precise, engineering-focused requirement document — not the broader team spec. This is the document engineering reads to implement without asking follow-up questions. Triggers: 'I need engineering to have all the details', 'write the technical requirements for this', 'engineering said the requirements are incomplete', 'I need to specify every error state', 'I need validation rules and business rules documented'. Do NOT use for team-facing feature alignment — use feature-spec for that instead.
scope-check
Use this skill when a feature that is already defined or in progress has grown beyond its original boundaries. This is a scope creep intervention tool — not an initial scoping tool. Triggers: 'this feature keeps growing', 'engineering said there is too much work', 'I want to reduce scope', 'this is taking longer than expected', 'we keep adding things to this feature', 'management is adding requirements mid-sprint'. Do NOT use for initial feature definition — use problem-framing for that. The difference: problem-framing defines scope upfront; scope-check catches and trims scope that has already drifted.
telegram-rich-message
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.
design-system-check
Use this skill when the PM or designer is planning a new feature and needs to know what UI components already exist in the design system before requesting new ones. Triggers: 'what components do we have', 'do we need to build this UI from scratch or do we have a component', 'I want to make sure we are not building something that already exists', 'the designer said we need a new component', or any situation where UI/UX planning requires knowing what already exists.
meeting-support
Use this skill to prepare for or follow up on a team meeting. Triggers: 'prepare the agenda for our sprint planning', 'summarize what we decided', 'extract action items from this meeting', 'log the decisions from today', 'what are the open questions from the meeting', or any situation before or after a team meeting where the PM needs structure.
presentation-style
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.
prompt-optimizer
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.
wireframe-generator
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.
task-writer
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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.