القائمة
Use for core product areas defining long-term brand value, when A/B tests are fragmenting product vision, or when short-term optimization threatens architectural integrity
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is critical.
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
View yourself as an entity with infinite dimensions rather than a single good/bad identity. Strengths and weaknesses are often the same trait in different contexts. Use during performance reviews or when receiving tough feedback.
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
| name | taste-driven-core |
| description | Use for core product areas defining long-term brand value, when A/B tests are fragmenting product vision, or when short-term optimization threatens architectural integrity |
A product development philosophy that removes metrics/KPIs from core product teams, relying instead on founder intuition ("Taste"), long-term vision, and technical quality.
Core principle: Make the best product first, make money second. Never reverse them.
┌─────────────────────────────────────────────────────────────────┐
│ 100-YEAR VISION │
│ (The North Star) │
├─────────────────────────────────────────────────────────────────┤
│ TASTE & INTUITION │
│ (The "Okay-to" Review Process) │
│ Every release reviewed by leadership via video │
├─────────────────────────────────────────────────────────────────┤
│ TECHNICAL ARCHITECTURE │
│ (The "How" Enables Optionality) │
│ Spend time debating architecture, not just shipping │
└─────────────────────────────────────────────────────────────────┘
| Principle | Description |
|---|---|
| No KPIs for core | Metrics are banned for brand-defining work |
| Taste over data | Founder intuition drives decisions |
| "Okay-to" reviews | Leadership approves via video demos |
| Aim heavy | Build 100-year solution, not A/B test winner |
Source: Archie Abrams (Shopify VP Product & Growth) via Lenny's Podcast