# Antigravity Integration Prompt: .clinerules Directory Understanding

## Objective
This prompt enables Antigravity to understand and integrate the comprehensive rule system defined in the `.clinerules/` directory, ensuring all development work aligns with established project guidelines and constraints.

## Context Analysis
Based on the workspace analysis, this is a **LockIn** project - a full-stack web application built with:
- **Frontend**: Next.js 16+ with React, TypeScript, Tailwind CSS
- **Backend**: API routes with Prisma ORM
- **Authentication**: Supabase integration
- **Architecture**: Component-based with shadcn/ui components
- **Quality Standards**: Awwwards-level design and performance requirements

## .clinerules Directory Structure
The `.clinerules/` directory contains 15 comprehensive rule files that define development standards:

### Core Infrastructure Rules
1. **workspace-analysis.md** - Mandates comprehensive workspace analysis before any task
2. **rules-integration.md** - Requires checking `.agent/rules/` directory for project constraints
3. **prompt-clarity.md** - Ensures detailed follow-up questions before task execution
4. **conflict-resolution.md** - Protocol for resolving conflicts between prompts and existing rules

### Development Quality Rules
5. **frontend-development.md** - Dynamic frontend approach based on project type analysis
6. **backend-architecture.md** - Backend strategy adapted to specific project requirements
7. **fullstack-integration.md** - Complete integration and deployment process management
8. **testing-qa.md** - Comprehensive testing and quality assurance processes
9. **security-compliance.md** - Security best practices and compliance standards

### Design & User Experience Rules
10. **ui-ux-design.md** - Awwwards-level UI/UX design principles and project-specific strategies
11. **accessibility-inclusion.md** - WCAG 2.1 AA compliance and inclusive design standards

### Project Management Rules
12. **project-management.md** - Complete project lifecycle management with timeline tracking
13. **continuous-improvement.md** - Learning and optimization from each interaction

### Skill & Enhancement Rules
14. **skill-optimization.md** - Proactive identification and utilization of appropriate skills
15. **skills-integration.md** - Integration of agent skills from the open skills ecosystem
16. **enhancer-implementation.md** - Implementation of enhancer prompts for optimization

## Key Integration Requirements

### 1. Workspace Analysis Protocol
Before executing ANY task:
- Perform comprehensive analysis of the entire workspace structure
- Understand project architecture, technology stack, and design patterns
- Identify the specific framework (Next.js 16+ with React/TS) and implementation standards
- Map out code organization and file structure to avoid assumptions

### 2. Rule Integration Workflow
For every user prompt:
1. Check `.agent/rules/` directory for relevant rule files
2. Read and analyze all rule files to understand constraints and requirements
3. Apply relevant rules to the current task or request
4. Reference specific rules when making decisions or providing recommendations
5. Document rule usage for consistency tracking

### 3. Project-Specific Constraints
Based on workspace analysis:
- **Technology Stack**: Next.js 16+, React, TypeScript, Tailwind CSS, Prisma, Supabase
- **Design System**: shadcn/ui components with Awwwards-level quality standards
- **Architecture**: Component-based with API routes and database integration
- **Performance**: Premium performance optimization requirements
- **Security**: Enterprise-grade security measures and compliance

### 4. Quality Assurance Standards
- **Awwwards-Level Quality**: All implementations must meet premium design and performance standards
- **Code Consistency**: Maintain highest standards of code quality and maintainability
- **User Experience**: Focus on exceptional user experiences with smooth interactions
- **Testing Coverage**: Comprehensive testing strategy with automated CI/CD integration

## Implementation Strategy

### Phase 1: Directory Understanding
1. Analyze all 15 rule files in `.clinerules/` directory
2. Understand the relationships between different rule categories
3. Map rule dependencies and integration points
4. Identify project-specific requirements from workspace analysis

### Phase 2: Rule Integration
1. Implement workspace-analysis.md requirements for comprehensive analysis
2. Apply rules-integration.md for checking and applying project constraints
3. Use prompt-clarity.md for gathering complete information before tasks
4. Establish conflict-resolution.md protocol for handling rule conflicts

### Phase 3: Development Standards
1. Apply frontend-development.md for dynamic frontend strategies
2. Implement backend-architecture.md for backend optimization
3. Use fullstack-integration.md for complete integration processes
4. Apply testing-qa.md for comprehensive quality assurance

### Phase 4: Quality Enhancement
1. Implement ui-ux-design.md for Awwwards-level design standards
2. Apply accessibility-inclusion.md for WCAG compliance
3. Use security-compliance.md for security best practices
4. Apply project-management.md for lifecycle management
5. Implement continuous-improvement.md for learning and optimization

## File Copying Instructions
To make all .clinerules files accessible to Antigravity:

1. **Create .antigravity directory** (if not exists)
2. **Copy all files** from `.clinerules/` to `.antigravity/`
3. **Maintain file structure** and naming conventions
4. **Ensure accessibility** for Antigravity to read and reference these files

## Expected Outcomes
After integration:
- Antigravity will understand all 15 rule files and their requirements
- All development tasks will follow established project guidelines
- Quality standards will be consistently maintained
- Project constraints and requirements will be properly applied
- Workspace analysis will be performed before every task
- Rule conflicts will be resolved proactively

## Validation Criteria
- All 15 rule files are successfully copied to `.antigravity/`
- Antigravity can reference and apply rules from the copied files
- Development tasks follow the established workflow and quality standards
- Workspace analysis is performed before task execution
- Rule integration is documented and tracked

## Notes
- This integration ensures consistency with the existing development workflow
- All rules are designed to work together to maintain high-quality standards
- The workspace analysis provides critical context for rule application
- Regular updates to rules should be synchronized between directories