flyee 0.1.0

package/core/skills/brainstorming/dynamic-questioning.md

@@ -0,0 +1,373 @@
+# Dynamic Question Generation
+
+> **PRINCIPLE:** Questions are not about gathering data—they are about **revealing architectural consequences**.
+>
+> Every question must connect to a concrete implementation decision that affects cost, complexity, or timeline.
+
+---
+
+## 🧠 Core Principles
+
+### 1. Questions Reveal Consequences
+
+A good question is not "What color do you want?" but:
+
+```markdown
+❌ BAD: "What authentication method?"
+✅ GOOD: "Should users sign up with email/password or social login?
+
+   Impact:
+   - Email/Pass → Need password reset, hashing, 2FA infrastructure
+   - Social → OAuth providers, user profile mapping, less control
+
+   Trade-off: Security vs. Development time vs. User friction"
+```
+
+### 2. Context Before Content
+
+First understand **where** this request fits:
+
+| Context | Question Focus |
+|---------|----------------|
+| **Greenfield** (new project) | Foundation decisions: stack, hosting, scale |
+| **Feature Addition** | Integration points, existing patterns, breaking changes |
+| **Refactor** | Why refactor? Performance? Maintainability? What's broken? |
+| **Debug** | Symptoms → Root cause → Reproduction path |
+
+### 3. Minimum Viable Questions
+
+**PRINCIPLE:** Each question must eliminate a fork in the implementation road.
+
+```
+Before Question:
+├── Path A: Do X (5 min)
+├── Path B: Do Y (15 min)
+└── Path C: Do Z (1 hour)
+
+After Question:
+└── Path Confirmed: Do X (5 min)
+```
+
+If a question doesn't reduce implementation paths → **DELETE IT**.
+
+### 4. Questions Generate Data, Not Assumptions
+
+```markdown
+❌ ASSUMPTION: "User probably wants Stripe for payments"
+✅ QUESTION: "Which payment provider fits your needs?
+
+   Stripe → Best documentation, 2.9% + $0.30, US-centric
+   LemonSqueezy → Merchant of Record, 5% + $0.50, global taxes
+   Paddle → Complex pricing, handles EU VAT, enterprise focus"
+```
+
+---
+
+## 📋 Question Generation Algorithm
+
+```
+INPUT: User request + Context (greenfield/feature/refactor/debug)
+│
+├── STEP 1: Parse Request
+│   ├── Extract domain (ecommerce, auth, realtime, cms, etc.)
+│   ├── Extract features (explicit and implied)
+│   └── Extract scale indicators (users, data volume, frequency)
+│
+├── STEP 2: Identify Decision Points
+│   ├── What MUST be decided before coding? (blocking)
+│   ├── What COULD be decided later? (deferable)
+│   └── What has ARCHITECTURAL impact? (high-leverage)
+│
+├── STEP 3: Generate Questions (Priority Order)
+│   ├── P0: Blocking decisions (cannot proceed without answer)
+│   ├── P1: High-leverage (affects >30% of implementation)
+│   ├── P2: Medium-leverage (affects specific features)
+│   └── P3: Nice-to-have (edge cases, optimization)
+│
+└── STEP 4: Format Each Question
+    ├── What: Clear question
+    ├── Why: Impact on implementation
+    ├── Options: Trade-offs (not just A vs B)
+    └── Default: What happens if user doesn't answer
+```
+
+---
+
+## 🎯 Domain-Specific Question Banks
+
+### E-Commerce
+
+| Question | Why It Matters | Trade-offs |
+|----------|----------------|------------|
+| **Single or Multi-vendor?** | Multi-vendor → Commission logic, vendor dashboards, split payments | +Revenue, -Complexity |
+| **Inventory Tracking?** | Needs stock tables, reservation logic, low-stock alerts | +Accuracy, -Development time |
+| **Digital or Physical Products?** | Digital → Download links, no shipping | Physical → Shipping APIs, tracking |
+| **Subscription or One-time?** | Subscription → Recurring billing, dunning, proration | +Revenue, -Complexity |
+
+### Authentication
+
+| Question | Why It Matters | Trade-offs |
+|----------|----------------|------------|
+| **Social Login Needed?** | OAuth providers vs. password reset infrastructure | +UX, -Control |
+| **Role-Based Permissions?** | RBAC tables, policy enforcement, admin UI | +Security, -Development time |
+| **2FA Required?** | TOTP/SMI infrastructure, backup codes, recovery flow | +Security, -UX friction |
+| **Email Verification?** | Verification tokens, email service, resend logic | +Security, -Sign-up friction |
+
+### Real-time
+
+| Question | Why It Matters | Trade-offs |
+|----------|----------------|------------|
+| **WebSocket or Polling?** | WS → Server scaling, connection management | Polling → Simpler, higher latency |
+| **Expected Concurrent Users?** | <100 → Single server, >1000 → Redis pub/sub, >10k → specialized infra | +Scale, -Complexity |
+| **Message Persistence?** | History tables, storage costs, pagination | +UX, -Storage |
+| **Ephemeral or Durable?** | Ephemeral → In-memory, Durable → Database write before emit | +Reliability, -Latency |
+
+### Content/CMS
+
+| Question | Why It Matters | Trade-offs |
+|----------|----------------|------------|
+| **Rich Text or Markdown?** | Rich Text → Sanitization, XSS risks | Markdown → Simple, no WYSIWYG |
+| **Draft/Publish Workflow?** | Status field, scheduled jobs, versioning | +Control, -Complexity |
+| **Media Handling?** | Upload endpoints, storage, optimization | +Features, -Development time |
+| **Multi-language?** | i18n tables, translation UI, fallback logic | +Reach, -Complexity |
+
+### Infrastructure/DevOps
+
+| Question | Why It Matters | Trade-offs |
+|----------|----------------|------------|
+| **Which environments needed?** | Dev/Staging/Prod → Isolation, DB separation, secrets management | +Safety, -Cost |
+| **Managed or Self-hosted?** | Vercel/Railway → Simple but less control | VPS → Full control but maintenance |
+| **CI/CD Strategy?** | GitHub Actions → Free, integrated | GitLab CI → More features | Manual → Error prone |
+| **Secrets Management?** | Platform secrets, Vault, .env files, dotenv-vault | +Security, -Complexity |
+| **Monitoring Needed?** | Logs, APM, Uptime checks, Error tracking | +Visibility, -Cost |
+| **Database per Environment?** | Shared → Cheaper but risky | Isolated → Safer but more cost |
+| **Rollback Strategy?** | Git revert, Previous deploy, Blue-green | +Safety, -Complexity |
+| **Budget Constraints?** | Free tier limits, scaling costs, vendor lock-in | +Cost control, -Flexibility |
+
+### Monetization/SaaS
+
+| Question | Why It Matters | Trade-offs |
+|----------|----------------|------------|
+| **Payment Provider?** | Stripe → Best docs | Paddle → MoR | LemonSqueezy → Simple | +Rev, -Fees |
+| **Subscription Model?** | Monthly/Annual, tiered plans, usage-based | +Revenue, -Complexity |
+| **Free Tier Exists?** | Freemium funnel, conversion tracking | +Adoption, -Revenue |
+| **Feature Gating?** | Plan-based access, soft limits, hard limits | +Upsell, -Development |
+| **Trial Period?** | Duration, credit card required, conversion | +Adoption, -Support |
+
+---
+
+## 📐 Dynamic Question Template
+
+```markdown
+Based on your request for [DOMAIN] [FEATURE]:
+
+## 🔴 CRITICAL (Blocking Decisions)
+
+### 1. **[DECISION POINT]**
+
+**Question:** [Clear, specific question]
+
+**Why This Matters:**
+- [Explain architectural consequence]
+- [Affects: cost / complexity / timeline / scale]
+
+**Options:**
+| Option | Pros | Cons | Best For |
+|--------|------|------|----------|
+| A | [Advantage] | [Disadvantage] | [Use case] |
+| B | [Advantage] | [Disadvantage] | [Use case] |
+
+**If Not Specified:** [Default choice + rationale]
+
+---
+
+## 🟡 HIGH-LEVERAGE (Affects Implementation)
+
+### 2. **[DECISION POINT]**
+[Same format]
+
+---
+
+## 🟢 NICE-TO-HAVE (Edge Cases)
+
+### 3. **[DECISION POINT]**
+[Same format]
+```
+
+---
+
+## 🔄 Iterative Questioning
+
+### First Pass (3-5 Questions)
+Focus on **blocking decisions**. Don't proceed without answers.
+
+### Second Pass (After Initial Implementation)
+As patterns emerge, ask:
+- "This feature implies [X]. Should we handle [edge case] now or defer?"
+- "We're using [Pattern A]. Should [Feature B] follow the same pattern?"
+
+### Third Pass (Optimization)
+When functionality works:
+- "Performance bottleneck at [X]. Optimize now or acceptable for now?"
+- "Refactor [Y] for maintainability or ship as-is?"
+
+---
+
+## 🎭 Example: Full Question Generation
+
+```
+USER REQUEST: "Build an Instagram clone"
+
+STEP 1: Parse
+├── Domain: Social Media
+├── Features: Photo sharing, engagement (likes/comments), user profiles
+├── Implied: Feed, following, authentication
+└── Scale: Potentially high (social apps go viral)
+
+STEP 2: Decision Points
+├── Blocking: Storage strategy, authentication method, feed type
+├── High-leverage: Real-time notifications, data model complexity
+└── Deferable: Analytics, advanced search, reels/video
+
+STEP 3: Generate Questions (Priority)
+
+P0 (Blocking):
+1. Storage Strategy → Affects architecture, cost, speed
+2. Feed Algorithm → Affects database queries, complexity
+3. Auth Method → Affects dev time, UX, security
+
+P1 (High-leverage):
+4. Real-time Notifications → WebSocket vs polling
+5. Media Processing → Client-side vs server-side optimization
+
+P2 (Deferable):
+6. Story/Reels → Major feature creep, defer to v2
+7. DM/Chat → Separate subsystem, defer to v2
+
+STEP 4: Format Output
+```
+
+---
+
+## 📊 Generated Output (Example)
+
+```
+Based on your Instagram clone request:
+
+## 🔴 CRITICAL DECISIONS (Cannot Proceed Without Answers)
+
+### 1. **Photo Storage Strategy**
+
+**Question:** Where will user photos be stored and served?
+
+**Why This Matters:**
+- Affects: Monthly hosting costs, page load speed, CDN complexity
+- High-volume social apps: 1000 users × 10 photos × 2MB = 20GB storage
+
+**Options:**
+| Option | Cost | Speed | Complexity | Best For |
+|--------|------|-------|------------|----------|
+| **Cloudinary** | $89/mo (25GB) | Fast (CDN) | Low | MVP, rapid launch |
+| **AWS S3 + CloudFront** | $0.023/GB | Fast (CDN) | Medium | Production, cost-optimized |
+| **Supabase Storage** | Free tier 1GB | Medium | Low | Small scale, simple |
+| **Local Storage** | Server cost | Slow | Low | Development only |
+
+**If Not Specified:** Cloudinary (balanced for MVP)
+
+---
+
+### 2. **Feed Algorithm Choice**
+
+**Question:** How should the main feed work?
+
+**Why This Matters:**
+- Affects: Database query complexity, caching strategy, development time
+- Algorithmic feeds require ML infrastructure, ranking signals
+
+**Options:**
+| Option | Complexity | Database Impact | Best For |
+|--------|------------|-----------------|----------|
+| **Chronological** | Low | Simple query | Early stage, transparency |
+| **Follow-Only** | Medium | JOIN with pagination | Most social apps |
+| **Algorithmic** | High | Pre-computed feed tables | Instagram competitor |
+
+**If Not Specified:** Follow-Only (balanced for social app)
+
+---
+
+### 3. **Authentication Approach**
+
+**Question:** How do users sign up and login?
+
+**Why This Matters:**
+- Affects: Development time (2-5 hours), security posture, UX friction
+
+**Options:**
+| Option | Dev Time | Security | UX | Best For |
+|--------|----------|----------|-----|----------|
+| **Email/Password** | 4-5 hrs | High (if 2FA) | Medium | Full control needed |
+| **Social Only** | 1-2 hrs | Provider-dependent | Smooth | B2C, rapid launch |
+| **Magic Link** | 2-3 hrs | Medium | Very smooth | Security-focused |
+| **Clerk/Auth0** | 1 hr | High | Smooth | Fastest to market |
+
+**If Not Specified:** Clerk (fastest for MVP)
+
+---
+
+## 🟡 HIGH-LEVERAGE (Affects Architecture)
+
+### 4. **Real-time Notifications**
+
+**Question:** Do users need instant notifications for likes/comments?
+
+**Why This Matters:**
+- WebSocket adds infrastructure complexity (Redis pub/sub for scaling)
+- Polling is simpler but higher latency
+
+**Options:**
+| Option | Complexity | Scale Cost | Best For |
+|--------|------------|------------|----------|
+| **WebSocket + Redis** | High | $10+/mo | >1000 concurrent users |
+| **Polling (30s)** | Low | DB queries | <1000 users |
+| **No Real-time** | None | None | MVP, validate first |
+
+**If Not Specified:** Polling for MVP (defer WebSocket until validated)
+
+---
+
+## 🟢 NICE-TO-HAVE (Defer to v2)
+
+### 5. **Video/Reels Support**
+- Major complexity (video processing, streaming infrastructure)
+- Recommendation: Launch with photos only, add video after validation
+
+### 6. **Direct Messaging**
+- Separate subsystem (chat infrastructure different from feed)
+- Recommendation: Use Pusher/Stream for real-time or defer entirely
+
+---
+
+## 📋 Summary
+
+| Decision | Recommendation | If Changed |
+|----------|----------------|------------|
+| Storage | Cloudinary | +3 hrs setup |
+| Feed | Follow-only | +2 hrs query optimization |
+| Auth | Clerk | -3 hrs dev time |
+| Real-time | Polling | +5 hrs WebSocket setup |
+| Video | Defer to v2 | N/A |
+| DM | Defer to v2 | N/A |
+
+**Total Estimated MVP Time:** 15-20 hours with recommendations above
+```
+
+---
+
+## 🎯 Principles Recap
+
+1. **Every question = Architectural decision** → Not data gathering
+2. **Show trade-offs** → User understands consequences
+3. **Prioritize blocking decisions** → Cannot proceed without
+4. **Provide defaults** → If user doesn't answer, we proceed anyway
+5. **Domain-aware** → Ecommerce questions ≠ Auth questions ≠ Real-time questions
+6. **Iterative** → More questions as patterns emerge during implementation

package/core/skills/checkpointing-patterns/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: checkpointing-patterns
+description: Sistema de checkpoint/resume para workflows longos. Persistência de estado, retomada de execução, gates de saída por fase.
+---
+
+# Checkpointing Patterns
+
+> **Single Source of Truth** para workflows que precisam persistir estado e retomar execução.
+
+---
+
+## 🎯 PROPÓSITO
+
+Garantir que workflows longos:
+1. **Salvem progresso** a cada fase
+2. **Retomem corretamente** de onde pararam
+3. **Mantenham histórico** de ações
+
+---
+
+## 📁 ESTRUTURA DO ARQUIVO DE CHECKPOINT
+
+**Padrão de nome:** `docs/{WORKFLOW}-PROGRESS.md`
+
+| Workflow | Arquivo |
+|----------|---------|
+| `/new-task` | `docs/NEW-TASK-PROGRESS.md` |
+| `/legacy-project` | `docs/LEGACY-PROGRESS.md` |
+| `/new-project` | `docs/PROJECT-PROGRESS.md` |
+
+---
+
+## 📋 TEMPLATE PADRÃO
+
+```markdown
+# {Workflow} Progress - {nome}
+
+> Arquivo de controle para retomar workflow.
+> ⚠️ NÃO EDITAR MANUALMENTE - Atualizado automaticamente.
+
+## 📊 Status Geral
+
+| Campo | Valor |
+|-------|-------|
+| Nome | {nome} |
+| Iniciado em | {data} |
+| Última atualização | {data} |
+| Status | 🟡 Em Progresso |
+| Fase Atual | {N}/{Total} |
+
+---
+
+## 📝 Fases
+
+### Fase 1: {Nome} ✅
+- [x] Item 1
+- [x] Item 2
+
+### Fase 2: {Nome} 🟡
+- [x] Item 1
+- [ ] Item 2 ← pendente
+
+### Fase 3: {Nome} ⏳
+- [ ] Aguardando
+
+---
+
+## 📜 Histórico de Ações
+
+| Data | Fase | Ação |
+|------|------|------|
+| {data} | 1 | {ação} |
+| {data} | 2 | {ação} |
+```
+
+---
+
+## 🔄 CICLO DE VIDA
+
+```
+┌─────────────┐    ┌─────────────┐    ┌─────────────┐
+│   INICIAR   │───►│   SALVAR    │───►│  ATUALIZAR  │
+│  (Criar)    │    │  (Por fase) │    │    (Loop)   │
+└─────────────┘    └─────────────┘    └──────┬──────┘
+                                             │
+                   ┌─────────────┐           │
+                   │   RETOMAR   │◄──────────┘
+                   │  (--resume) │
+                   └─────────────┘
+```
+
+---
+
+## 📋 OPERAÇÕES PADRÃO
+
+### 1. Criar Checkpoint (Início)
+
+```markdown
+# Ao iniciar workflow:
+1. Verificar se existe `docs/{WORKFLOW}-PROGRESS.md`
+2. Se existe:
+   - Perguntar: "Retomar ou reiniciar?"
+3. Se não existe:
+   - Criar arquivo com template padrão
+   - Registrar data de início
+```
+
+### 2. Salvar Progresso (Por Fase)
+
+```markdown
+# Ao concluir CADA fase:
+1. Atualizar `Fase Atual` no arquivo
+2. Marcar itens como concluídos [x]
+3. Adicionar linha no Histórico
+4. Atualizar `Última atualização`
+```
+
+### 3. Retomar (--resume)
+
+```markdown
+# Ao executar --resume:
+1. Carregar `docs/{WORKFLOW}-PROGRESS.md`
+2. Identificar `Fase Atual`
+3. Identificar itens pendentes na fase
+4. Continuar execução
+```
+
+### 4. Finalizar
+
+```markdown
+# Ao concluir workflow:
+1. Atualizar Status para "✅ Concluído"
+2. Registrar data de conclusão
+3. Opcionalmente: arquivar ou deletar
+```
+
+---
+
+## ⚠️ GATES DE SAÍDA
+
+> [!IMPORTANT]
+> Cada fase deve ter um **Gate de Saída** - checklist que DEVE ser satisfeito antes de prosseguir.
+
+### Formato do Gate
+
+```markdown
+**Gate de Saída - Fase {N}:**
+- [ ] Item obrigatório 1
+- [ ] Item obrigatório 2
+- [ ] Item obrigatório 3
+
+> **BLOQUEADOR:** Não prosseguir até que todos os itens estejam ✅
+```
+
+---
+
+## 🔗 WORKFLOWS QUE USAM ESTA SKILL
+
+| Workflow | Arquivo de Checkpoint |
+|----------|----------------------|
+| `/new-task` | `docs/NEW-TASK-PROGRESS.md` |
+| `/legacy-project` | `docs/LEGACY-PROGRESS.md` |
+| `/new-project` | `docs/PROJECT-PROGRESS.md` |