notification-design

Dragoon0x

Communicate without annoying. Patterns for in-app alerts, email triggers, push notification copy, and frequency capping. Use when designing notification systems or any touchpoint that competes for attention.

cross-domain-seeing

Dragoon0x

Pull design principles from architecture, fashion, film, industrial design, and physical spaces into screen-based design. Use when seeking inspiration beyond digital, expanding creative range, or building cross-disciplinary design vocabulary.

type-as-signal

Dragoon0x

Read a designer's taste through their typography decisions alone. Type is the fastest taste signal in any design. Use when evaluating design maturity, assessing portfolio quality, or understanding what typography reveals about design thinking.

empty-states

Dragoon0x

Turn dead ends into moments that build trust and guide action. Covers zero-data screens, error recovery, loading states, and retention micro-copy. Use when handling empty dashboards, failed searches, or moments where users hit a wall.

product-narrative

Dragoon0x

Tell the product story in a way that sticks. Structures origin stories, problem narratives, and transformation arcs. Use when building about pages, launch announcements, or pitch decks.

launch-planning

Dragoon0x

Plan and execute product launches that actually drive adoption, not just announcements. Covers launch tiers, cross-functional coordination, rollout strategy, and post-launch monitoring. Use when preparing a feature or product launch, coordinating across teams, or when past launches haven't moved the needle.

motion-design

Dragoon0x

Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.

taste-gap

Dragoon0x

Navigate the gap between what you can see and what you can make. The Ira Glass gap. Use when a designer is frustrated by the distance between their taste and their output, when mentoring someone through a creative plateau, or when someone is considering quitting because their work doesn't match their vision.

working-with-design

Dragoon0x

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.

competitive-framing

Dragoon0x

Position against alternatives without being negative. Maps competitive landscape, identifies differentiation axes, and generates comparison frameworks. Use when building comparison pages, handling objections, or differentiating from existing solutions.

constraint-evaluation

Dragoon0x

Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.

retention-patterns

Dragoon0x

Design for the second visit, not just the first. Habit loops, re-engagement triggers, and value reinforcement without dark patterns. Use when retention is low, when building engagement features, or when people stop coming back.

zero-to-one

Dragoon0x

First principles decisions for products that don't exist yet. Helps reason about market gaps, user needs, MVP scope, and what to build first. Use when starting from scratch, scoping an MVP, or when the agent needs to think before it builds.

self-assessment

Dragoon0x

Diagnose your taste gaps across six skill areas. Know what to practice. Use when starting a taste development program, checking progress, or identifying specific areas to improve.

pricing-page

Dragoon0x

Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.

visual-audit

Dragoon0x

The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.

landing-structure

Dragoon0x

Information architecture that guides visitors from curiosity to commitment. Enforces section order, content hierarchy, and scroll-depth logic. Use when building landing pages, product pages, or any conversion surface.

competitive-battlecard

Dragoon0x

Create structured competitive battlecards for sales, product, and strategy conversations. Covers positioning, objection handling, competitive landmines, and knowing when to walk away. Use when preparing for competitive deals, losing to a specific competitor, or entering a market with established players.

learning-by-making

Dragoon0x

Build taste through volume of output, deliberate failure, and speed. Taste cannot be developed by watching. It's sharpened by making, failing, and making again. Use when designing practice routines, breaking through creative blocks, or helping someone move from analysis to execution.

ux-intuition

Dragoon0x

Develop the instinct for what makes a product feel right, beyond what data can tell you. Covers quality evaluation, interaction judgment, and knowing when something is off even if you can't articulate why. Use when evaluating designs, reviewing prototypes, or when metrics say it's fine but something feels wrong.

backlog-management

Dragoon0x

Keep the backlog useful instead of letting it become a graveyard of ideas nobody will build. Covers backlog hygiene, grooming practices, and knowing when to kill items. Use when the backlog has hundreds of stale items, sprint planning takes forever, or the team doesn't trust the backlog.

user-research-integration

Dragoon0x

Turn user research into product decisions, not just reports. Covers when to research, what methods to use, and how to act on findings. Use when product direction feels disconnected from users, research exists but isn't informing decisions, or you're building on assumptions.

prd-writing

Dragoon0x

Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.

communicating-decisions

Dragoon0x

Communicate product decisions so teams understand not just what was decided but why. Covers framing, transparency about trade-offs, and handling disagreement gracefully. Use when decisions aren't sticking, teams are relitigating past calls, or when stakeholders feel left out.

cta-patterns

Dragoon0x

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.

persona-mapping

Dragoon0x

Build user models that actually inform decisions. Maps motivations, friction points, and decision triggers beyond demographic templates. Use when building for multiple user types or when the agent needs to reason about different users.

field-notes

Dragoon0x

Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.

feedback-synthesis

Dragoon0x

Turn raw customer feedback from multiple sources into clear product insights and priorities. Covers feedback collection, pattern recognition, and separating signal from noise. Use when feedback feels overwhelming, contradictory, or when the team can't agree on what users actually want.

feature-adoption-diagnosis

Dragoon0x

Diagnose why a feature isn't getting adopted. Most features fail not because they're bad ideas but because of discoverability, onboarding, or positioning problems. Use when a shipped feature has low usage, a popular feature is declining, or deciding whether to kill, improve, or reposition something.

managing-up

Dragoon0x

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.

teaching-taste

Dragoon0x

Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.

market-validation

Dragoon0x

Test assumptions before committing resources. Generates lean validation plans, fake door tests, and interview scripts. Use before building anything expensive or when there's no evidence anyone wants what's being built.

flow-patterns

Dragoon0x

Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.

referral-mechanics

Dragoon0x

Build sharing into the product without it feeling forced. Viral loops, invite flows, referral incentives, and the moments where asking users to share feels natural. Use when building invite systems or when organic growth needs structure.

prioritization-frameworks

Dragoon0x

Score and rank product initiatives using RICE, ICE, and value-effort frameworks. Makes prioritization transparent and defensible while acknowledging that math doesn't remove all judgment. Use when the backlog is growing, stakeholders disagree on priorities, or you need to justify decisions to leadership.

willingness-to-pay

Dragoon0x

Determine what customers will actually pay using structured pricing research frameworks. Covers Van Westendorp, Gabor-Granger, competitive anchoring, and practical approaches for teams without formal research budgets. Use when setting initial pricing, considering a price increase, or entering a new segment.

audience-translation

Dragoon0x

Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.

outcome-thinking

Dragoon0x

Focus product work on outcomes rather than output. Covers defining success, connecting features to results, and knowing the difference between shipping and impact. Use when the team ships lots of features but metrics don't move, when success is defined by delivery dates, or when nobody can say what a feature accomplished.

working-with-engineering

Dragoon0x

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.

critique-vocabulary

Dragoon0x

Precise language for design feedback. Ban vague words. Name what you actually see. Use when giving design feedback, running critiques, or training teams to communicate about quality.

spatial-rhythm

Dragoon0x

Density, whitespace, rhythm, and how space communicates relationships between elements. Use when building layouts, evaluating spacing consistency, or diagnosing why a design feels cramped or empty.

north-star-setting

Dragoon0x

Define a north star metric and product vision that aligns the team and guides daily decisions. Covers metric selection, vision articulation, and connecting daily work to long-term direction. Use when the team lacks clear direction, metrics feel arbitrary, or people can't explain what success looks like.

design-rationale

Dragoon0x

Defend a design decision to skeptical stakeholders with structure and evidence. Use when presenting design work, writing design documentation, or pushing back on requests to change something.

stakeholder-updates

Dragoon0x

Write status updates that executives actually read and act on. Covers structure, signal-to-noise ratio, and knowing what to escalate versus what to summarize. Use when writing weekly updates, project status reports, or board-level summaries.

freemium-vs-paid-gate

Dragoon0x

Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.

design-ranking

Dragoon0x

Rank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.

daily-routines

Dragoon0x

15-minute daily taste exercises. Monday through Friday. Compound effect over time. Use when building personal practice habits, training a team's design eye, or adding structure to professional development.

color-systems

Dragoon0x

Palette roles, restraint, semantic consistency, and when fewer colors means better design. Use when building color palettes, evaluating color usage, or diagnosing color-related design problems.