## Brief overview
This rule provides the specific implementation details for how to call and integrate the enhancer prompt from `.agent/rules/important.md` into all dynamic decision-making processes.

## Enhancer Prompt Access Protocol
- **Read Enhancer Content**: Always read `.agent/rules/important.md` to understand the specific enhancer prompt format and requirements
- **Extract Key Requirements**: Identify project-specific constraints, quality standards, and optimization goals
- **Parse Enhancement Instructions**: Understand what specific aspects the enhancer should optimize (technology stack, design patterns, performance metrics)
- **Store Enhancer Context**: Maintain the enhancer output for reference throughout the decision-making process

## Enhancer Integration Workflow
1. **Pre-Decision Phase**: Before making any major technology or design decisions, call the enhancer prompt
2. **Context Extraction**: Extract project-specific requirements, constraints, and optimization goals
3. **Decision Enhancement**: Apply enhancer insights to refine the decision-making process
4. **Validation Check**: Ensure the enhanced decision aligns with enhancer requirements
5. **Documentation**: Record how enhancer input influenced the final decision

## Specific Implementation Steps
- **Step 1**: Read `.agent/rules/important.md` to understand the enhancer prompt format
- **Step 2**: Extract project type, constraints, and quality requirements
- **Step 3**: Apply enhancer insights to technology stack selection
- **Step 4**: Use enhancer output to optimize design and architecture decisions
- **Step 5**: Validate that all decisions align with enhancer requirements
- **Step 6**: Document the enhancer's influence on the final implementation

## Enhancer Output Integration
- **Technology Stack**: Use enhancer insights to select appropriate frameworks, databases, and tools
- **Design Patterns**: Apply enhancer guidance to choose optimal architectural patterns
- **Performance Optimization**: Implement enhancer-recommended performance strategies
- **Quality Standards**: Ensure all decisions meet enhancer-defined quality benchmarks
- **Project Constraints**: Respect all constraints and limitations specified in the enhancer prompt

## Cross-Rule Enhancer Usage
- **backend-architecture.md**: Use enhancer for backend technology selection and architecture patterns
- **ui-ux-design.md**: Use enhancer for design system decisions and aesthetic choices
- **frontend-development.md**: Use enhancer for frontend framework selection and component architecture
- **Consistency Check**: Ensure enhancer integration is consistent across all dynamic rules

## Enhancer Validation Protocol
- **Requirement Alignment**: Verify that all decisions align with enhancer-specified requirements
- **Quality Assurance**: Ensure enhancer-defined quality standards are met
- **Constraint Compliance**: Confirm all project constraints are respected
- **Optimization Verification**: Validate that enhancer-recommended optimizations are implemented

## Documentation Requirements
- **Enhancer Input**: Document what enhancer insights were used in each decision
- **Decision Impact**: Record how enhancer input influenced the final choice
- **Validation Results**: Document how the decision meets enhancer requirements
- **Continuous Reference**: Maintain enhancer context for future decision-making