weber-fechner-law
La percepción de cambio es proporcional al estímulo original. Use cuando diseñe feedback de progreso, sistemas de pricing, o cambios visuales graduales.
La percepción de cambio es proporcional al estímulo original. Use cuando diseñe feedback de progreso, sistemas de pricing, o cambios visuales graduales.
Demasiadas opciones pueden paralizar y reducir satisfacción. Use cuando diseñe menús, catálogos, configuraciones, o cualquier sistema con múltiples opciones.
Comprehensive UX design patterns for Rails applications including responsive design, animations/transitions, dark mode, loading states, form UX, and performance optimization. Use this skill when implementing user-facing features requiring polished interactions and responsive layouts. Trigger keywords: UX, responsive, mobile-first, animation, transition, dark mode, loading, skeleton, progress, toast, form validation, performance, Core Web Vitals, user flow
Use before any creative work - creating features, building components, adding functionality, or modifying behavior to explore intent, requirements, and design before implementation.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Write clear, testable requirements using User Stories and Gherkin scenarios for Manifest Logistics SaaS. Capture functional and non-functional requirements with proper acceptance criteria. Use when defining new features or documenting system behavior.
Use when traditional problem/solution pitches fail to differentiate, when teams are misaligned around messaging, or when entering Series B/scaling phases where founder-led sales no longer scale
Use when creating or developing ideas before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning with Shannon quantitative validation, alternative exploration, and incremental validation. Don't use during clear mechanical processes
Update and evolve existing brand identity based on new direction or feedback
Transform stakeholder needs into structured, testable specifications with user stories, acceptance criteria, and business rules. Use when: (1) creating requirements documents, (2) writing user stories with acceptance criteria, (3) defining business rules and process flows, (4) analyzing feature requests.
Gathers, refines, and documents requirements from Discovery outputs
UIデザインレビューガイド。 アクセシビリティ、レスポンシブ、UXパターン、パフォーマンスをチェック。
Building and growing developer communities from scratch to scale
Operational support and maintenance for released software. Monitoring and observability, incident management, maintenance and patch management, continuous improvement, security operations, compliance and audit, support and user satisfaction, backup and disaster recovery.
Create clear leadership presentations that communicate findings and enable good decisions. Use at end of each phase or before major commitments.
Use when asked to "position my product", "positioning canvas", "differentiate from competitors", "figure out our category", "repositioning", or "why customers should pick us". Helps define competitive alternatives, differentiated value, target customers, and market category. April Dunford's positioning framework from "Obviously Awesome" makes your product's value obvious to the right customers.
Use when asked to "strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", or "movement narrative". Helps craft compelling narratives that define movements rather than just selling products. The Strategic Narrative framework (created by Andy Raskin) transforms pitches from feature lists into stories about change.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
PRD parsing and task decomposition patterns for intake workflows.
Use in power-law businesses like platforms or VC, when conversion rate optimization shrinks your funnel, or when efficiency metrics block potential outlier winners