## Brief overview
This rule ensures that before executing any task, I thoroughly analyze the entire workspace structure, codebase, and technology stack to understand the project architecture, design patterns, and implementation standards. This analysis is critical for maintaining code consistency and ensuring high-quality implementations.

## Workspace discovery protocol
- Before executing ANY task, perform a comprehensive analysis of the entire workspace structure
- Understand the project architecture, technology stack, and design patterns
- Identify the specific framework being used (React, PHP CI MVC, etc.) and its implementation standards
- Map out the code organization and file structure to avoid assumptions

## Technology stack analysis
- **Framework Identification**: Determine if this is a React/TS, PHP CI MVC, or other framework workspace
- **Library Inventory**: Identify all installed dependencies and their usage patterns
- **Architecture Patterns**: Understand the project's architectural decisions (MVC, component-based, etc.)
- **Design System**: Analyze existing design patterns, CSS organization, and styling approaches

## Code structure examination
- **File Organization**: Map the complete directory structure and understand the purpose of each folder
- **Component Architecture**: For React projects, understand component hierarchy and reusability patterns
- **Routing Structure**: Analyze routing patterns and page organization
- **State Management**: Identify state management solutions and data flow patterns
- **API Integration**: Understand backend integration patterns and data fetching strategies

## Design consistency analysis
- **CSS Organization**: Understand where and how CSS/styling is implemented
- **Design Patterns**: Identify consistent design patterns and UI components
- **Component Reusability**: Map reusable components and their implementation standards
- **Responsive Design**: Analyze responsive design patterns and breakpoints

## Implementation standards verification
- **Code Quality**: Review existing code for patterns, naming conventions, and best practices
- **Error Handling**: Understand error handling patterns and user feedback mechanisms
- **Performance Considerations**: Identify performance optimization patterns and constraints
- **Testing Strategy**: Understand testing approaches and quality assurance measures

## Awwwards-level implementation requirements
- **Design Excellence**: Ensure all implementations meet premium design standards
- **Performance Optimization**: Implement with performance as a top priority
- **User Experience**: Focus on creating exceptional user experiences
- **Code Quality**: Maintain the highest standards of code quality and maintainability
- **Innovation**: Incorporate modern web development practices and innovative solutions

## Skill integration workflow
1. Analyze workspace to determine required skills from the complete inventory
2. Identify which skills are most relevant for achieving Awwwards-level quality
3. Plan skill usage based on project requirements and quality standards
4. Ensure all implementations align with workspace standards and best practices

## Proactive workspace management
- Always perform comprehensive workspace analysis before any implementation
- Maintain awareness of project evolution and architectural changes
- Ensure all new code integrates seamlessly with existing patterns
- Flag any potential conflicts or inconsistencies for review
- Continuously update understanding of workspace standards and practices

## User communication about workspace analysis
- Always explain how workspace analysis informs implementation decisions
- Reference specific workspace patterns when explaining code choices
- Ask for clarification when workspace patterns are unclear or inconsistent
- Suggest workspace improvements when identified during analysis