메뉴
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | cta-patterns |
| description | Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic. |
Design calls-to-action that people actually click.
/cta-patterns Apply CTA constraints to this conversation.Bring engineering, design, research, marketing, and sales onto the same page and keep them there. Covers alignment levels, RACI clarity, and continuous maintenance. Use when teams have different understandings of what's being built, cross-team dependencies are causing problems, or alignment keeps breaking down.
Get buy-in and drive alignment when you have no direct power over the people you need to move. Covers stakeholder framing, pre-wiring decisions, and building credibility over time. Use when pushing for a direction without exec authority, navigating disagreements, or when a proposal keeps getting blocked.
Build a productive relationship with leadership by communicating effectively, managing expectations, and knowing when to push back. Use when navigating executive relationships, seeking alignment on direction, or when leadership requests conflict with team capacity.
Partner with design to create better products, not just prettier ones. Covers when to involve design, how to give useful feedback, and respecting the design process. Use when PM-design handoffs feel clunky, design feedback conversations are unproductive, or design is brought in too late.
Partner with engineering as a collaborator, not a ticket-writer. Covers communication norms, technical empathy, scope negotiation, and building mutual trust. Use when PM-engineering relationships feel transactional, technical decisions are made without product input, or scope conversations become adversarial.
Partner with marketing, sales, and customer success to bring products to market effectively. Covers launch coordination, sales enablement, and feedback loops. Use when launches aren't driving adoption, sales can't articulate the value prop, or customer feedback isn't reaching the product team.