3.9 KiB

Raw Blame History

Meta-Rule Architecture Overview

Author: Matthew Raymer Date: 2025-01-27 Status: 📋 ACTIVE - Meta-rule organization and relationships

Meta-Rule Structure

Core Always-On Rules (`meta_core_always_on.mdc`)

Purpose: Applied to every single prompt
Scope: Human competence, time standards, version control, application context
Priority: Critical - foundation for all interactions

Enhanced Research Workflows (`meta_research.mdc`) ⭐ NEW

Purpose: Applied to research, investigation, and analysis tasks
Scope: Systematic investigation, evidence collection, root cause analysis
Priority: High - applies to all research tasks
Bundles: Research diagnostic, type safety, version control research, platform context

Feature Development Workflows (`meta_feature_planning.mdc`)

Purpose: Applied to feature planning and development tasks
Scope: Requirements analysis, architecture planning, implementation strategy
Priority: High - applies to feature development

Bug Investigation Workflows (`meta_bug_diagnosis.mdc`)

Purpose: Applied to bug investigation and diagnosis tasks
Scope: Defect analysis, evidence collection, root cause identification
Priority: High - applies to bug investigation

Bug Fixing Workflows (`meta_bug_fixing.mdc`)

Purpose: Applied to bug fixing and resolution tasks
Scope: Fix implementation, testing, validation
Priority: High - applies to bug resolution

Research Meta-Rule Integration

When to Use Research Meta-Rule

The research meta-rule should be applied when:

Investigating bugs - systematic defect analysis
Researching solutions - feasibility and alternative analysis
Analyzing codebases - architecture and dependency research
Collecting evidence - systematic data gathering
Root cause analysis - systematic problem investigation
Impact assessment - scope and consequence evaluation

How It Complements Other Meta-Rules

Core Always-On: Provides foundation (competence, time, context)
Research: Adds systematic investigation methodology
Feature Planning: Guides feasibility research and analysis
Bug Diagnosis: Provides investigation framework
Bug Fixing: Informs fix strategy through research

Research Workflow Phases

Investigation Setup - Scope, context, methodology
Evidence Collection - Systematic data gathering
Analysis & Synthesis - Pattern recognition, root cause
Conclusion & Action - Evidence-based recommendations

Usage Examples

Bug Investigation

Apply: meta_core_always_on + meta_research + meta_bug_diagnosis
Result: Systematic investigation with evidence collection and root cause analysis

Feature Research

Apply: meta_core_always_on + meta_research + meta_feature_planning
Result: Comprehensive feasibility research with platform context

Architecture Analysis

Apply: meta_core_always_on + meta_research
Result: Systematic architecture investigation with evidence-based conclusions

Benefits of Enhanced Research Meta-Rule

Systematic Approach: Structured investigation methodology
Evidence-Based: Comprehensive data collection and validation
Quality Standards: Defined research quality criteria
Integration: Seamless integration with existing workflows
Documentation: Comprehensive research documentation standards

Next Steps

Test Research Meta-Rule - Apply to next research task
Validate Integration - Ensure smooth workflow integration
Collect Feedback - Gather effectiveness ratings
Iterate - Refine based on usage experience

Status: Active documentation Priority: Medium Estimated Effort: Ongoing reference Dependencies: All meta-rules Stakeholders: Development team, Research team

3.9 KiB Raw Blame History