Eagle Sight

The Pre-Build Vision Process

Before writing a single line of code, the elite vibecoder establishes complete strategic clarity. Like an eagle surveying the landscape before diving, you must see the entire terrain before execution.

The Linear Path

┌─────────────────────────────────────────────────────────────────────────────────────┐
│                                                                                     │
│   💡 IDEA  ──▶  🔍 RESEARCH  ──▶  🧠 BRAINLIFT  ──▶  📋 PRD  ──▶  🗺️ GAMEPLAN      │
│                                                                                     │
└─────────────────────────────────────────────────────────────────────────────────────┘
                                        │
                                        ▼
                                   ⚡ BUILD

Step	What It Is	Time Investment
💡 Idea	The spark — what and why	5 minutes
🔍 Research	Landscape scan — what exists	30-60 minutes
🧠 Brainlift	Your edge — what AI doesn't know	15-30 minutes
📋 PRD	Requirements — what exactly to build	30-60 minutes
🗺️ Gameplan	Strategy — how to build it	15-30 minutes

Total pre-build time: 2-3 hours → Saves 20-40 hours of confused building

Visual: The Eagle's View

                                    🦅
                                   /   \
                                  /     \
                                 /       \
                                /  EAGLE  \
                               /   SIGHT   \
                              /             \
                             /               \
                            ▼                 ▼
    ┌─────────────────────────────────────────────────────────────────┐
    │                                                                 │
    │    STEP 1         STEP 2         STEP 3        STEP 4    STEP 5│
    │   ┌──────┐       ┌──────┐       ┌──────┐      ┌─────┐   ┌─────┐│
    │   │ 💡   │  ───▶ │ 🔍   │  ───▶ │ 🧠   │ ───▶ │ 📋  │───▶│ 🗺️ ││
    │   │ IDEA │       │RSRCH │       │BRAIN │      │ PRD │   │PLAN ││
    │   └──────┘       └──────┘       └──────┘      └─────┘   └─────┘│
    │      │              │              │             │          │  │
    │      ▼              ▼              ▼             ▼          ▼  │
    │   What &         Market        Contrarian    Concrete   Phased │
    │    Why           Context       Insights      Specs      Tasks  │
    │                                                                 │
    └─────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
                        ┌───────────────────────┐
                        │   ⚡ BUILD WITH       │
                        │   TOTAL CLARITY       │
                        └───────────────────────┘

The Pipeline Breakdown

    ╔═══════════════════════════════════════════════════════════════╗
    ║                     EAGLE SIGHT PIPELINE                      ║
    ╠═══════════════════════════════════════════════════════════════╣
    ║                                                               ║
    ║    💡 IDEA ─────────────────────────────────────────────────▶ ║
    ║       "I want to build X because Y"                           ║
    ║                                                               ║
    ║    🔍 RESEARCH ─────────────────────────────────────────────▶ ║
    ║       Market, competitors, tech options, constraints          ║
    ║                                                               ║
    ║    🧠 BRAINLIFT ────────────────────────────────────────────▶ ║
    ║       Your unique insights that AI doesn't have               ║
    ║       (Second Brain = Contrarian Edge)                        ║
    ║                                                               ║
    ║    📋 PRD ──────────────────────────────────────────────────▶ ║
    ║       Goals, non-goals, user stories, success metrics         ║
    ║                                                               ║
    ║    🗺️  GAMEPLAN ────────────────────────────────────────────▶ ║
    ║       Tech stack, architecture, phased tasks, risks           ║
    ║                                                               ║
    ╠═══════════════════════════════════════════════════════════════╣
    ║    ⚡ BUILD ── Now you're ready to vibecode with precision    ║
    ╚═══════════════════════════════════════════════════════════════╝

Stage 1: 💡 Idea

The spark. What are you building and why?

# Idea Template
 
## What
[One sentence describing the product/feature]
 
## Why  
[The problem it solves]
 
## For Whom
[Target user]
 
## Success Looks Like
[Measurable outcome]

Stage 2: 🔍 Research

Explore the landscape. What already exists? What works? What doesn't?

Research Area	Questions to Answer
Market	Who else has built this? What's their approach?
Technical	What tech stack makes sense? Any gotchas?
User	How do users currently solve this problem?
Constraints	Budget? Timeline? Technical limitations?

Stage 3: 🧠 Brainlift (Second Brain)

This is your competitive edge.

The Brainlift contains information that LLMs don't have:

Your contrarian insights and takes
Domain knowledge from your experience
Current market conditions the AI can't know
Your specific constraints and context
Lessons from past failures

# Brainlift Template
 
## Contrarian Insights
- [What do YOU know that contradicts conventional wisdom?]
- [What have you learned from experience that AI can't know?]
 
## Domain Knowledge
- [Industry-specific context]
- [User behavior patterns you've observed]
- [Market dynamics not in training data]
 
## Hard-Won Lessons
- [What NOT to do based on past experience]
- [Hidden gotchas in this space]
 
## Current Context
- [Recent market changes]
- [Competitor moves]
- [Technology updates post-training-cutoff]

Why Brainlift matters: AI generates based on patterns in its training data. Your unique perspective, recent information, and contrarian takes are what separate a generic AI output from a breakthrough product.

Stage 4: 📋 PRD (Product Requirements Document)

Transform your vision into concrete requirements.

# PRD Template
 
## Overview
[Product name and one-paragraph description]
 
## Goals
1. [Primary goal]
2. [Secondary goal]
3. [Tertiary goal]
 
## Non-Goals (Equally Important!)
- [What you're explicitly NOT building]
- [Scope boundaries]
 
## User Stories
- As a [user type], I want to [action] so that [benefit]
 
## Technical Requirements
- [Performance requirements]
- [Security requirements]
- [Integration requirements]
 
## Success Metrics
- [How you'll measure success]
 
## Timeline
- Phase 1: [scope] - [timeframe]
- Phase 2: [scope] - [timeframe]

Stage 5: 🗺️ Gameplan

Your execution strategy. How will you build this, step by step?

# Gameplan Template
 
## Tech Stack Decision
[Stack choice with brief justification]
 
## Architecture Overview
[High-level system design]
 
## Phase 1: Foundation
- [ ] Task 1
- [ ] Task 2
- [ ] Task 3
 
## Phase 2: Core Features
- [ ] Task 1
- [ ] Task 2
 
## Phase 3: Polish & Launch
- [ ] Task 1
- [ ] Task 2
 
## Risk Mitigation
- Risk: [potential issue] → Mitigation: [how to handle]

Optional Documentation Files

Beyond the core pipeline, consider adding these helper documents to your project for the AI to read and understand:

📐 `aesthetic.md` — Visual Guidelines

# Aesthetic Guidelines
 
## Design Philosophy
[Minimalist? Bold? Playful? Professional?]
 
## Color Palette
- Primary: #HEXCODE
- Secondary: #HEXCODE  
- Accent: #HEXCODE
 
## Typography
- Headings: [Font family]
- Body: [Font family]
 
## Component Style
- Buttons: [Rounded? Sharp? Ghost?]
- Cards: [Shadows? Borders? Glassmorphism?]
- Spacing: [Tight? Comfortable? Generous?]
 
## Inspiration
- [Reference sites/designs]

⚡ `technical.md` — Performance & Efficiency

# Technical Guidelines
 
## Performance Targets
- Page load: <[X]ms
- API response: <[X]ms
- Bundle size: <[X]KB
 
## Algorithms & Patterns
- [Specific algorithms to use/avoid]
- [Caching strategies]
- [State management approach]
 
## Database Patterns
- [Query optimization rules]
- [Indexing strategy]
 
## Security Requirements
- [Auth approach]
- [Data handling rules]

🏗️ `architecture.md` — System Design

# Architecture Guidelines
 
## Folder Structure
[Your preferred organization]
 
## Naming Conventions
- Components: [PascalCase]
- Functions: [camelCase]
- Files: [kebab-case]
 
## Code Patterns
- [Preferred patterns]
- [Anti-patterns to avoid]
 
## Dependencies Policy
- [Allowed libraries]
- [Banned libraries]

📝 `context.md` — Project-Specific Context

# Project Context
 
## Business Context
[What the AI needs to know about your business]
 
## User Context
[Who your users are and how they think]
 
## Technical Debt
[Known issues to work around]
 
## Integration Points
[External systems and their quirks]

The Eagle Sight Advantage

    WITHOUT EAGLE SIGHT              WITH EAGLE SIGHT
    ══════════════════               ════════════════
    
    Vague idea                       Crystal clear vision
         │                                  │
         ▼                                  ▼
    Start coding                     Research landscape
         │                                  │
         ▼                                  ▼
    Hit roadblocks                   Document insights
         │                                  │
         ▼                                  ▼
    Pivot repeatedly                 Define requirements
         │                                  │
         ▼                                  ▼
    Scope creep                      Plan execution
         │                                  │
         ▼                                  ▼
    Burnout / Abandon                Build with confidence
         │                                  │
         ▼                                  ▼
    ❌ Failed project                ✅ Shipped product

When to Use Each Document

Document	When to Create	Who Benefits
Brainlift	Every project	You + AI
PRD	Features with multiple requirements	Team + AI
Gameplan	Multi-phase projects	You + AI
aesthetic.md	UI-heavy projects	AI (consistent styling)
technical.md	Performance-critical apps	AI (optimization)
architecture.md	Large codebases	AI (consistency)
context.md	Domain-specific projects	AI (understanding)

Quick Start

For a new project, at minimum create:

mkdir docs
touch docs/brainlift.md    # Your unique insights
touch docs/prd.md          # What you're building
touch docs/gameplan.md     # How you'll build it

Then tell the AI:

Read docs/brainlift.md, docs/prd.md, and docs/gameplan.md
before we begin building.

The Meta-Principle

Eagle Sight is about strategic altitude.

The higher your vantage point before building, the straighter your path to completion. Time spent in pre-build clarity is always returned 10x during execution.

Ready to see the full development process? Continue to Oneshot Paradigm →

Core Philosophy Oneshot Paradigm