v0.15.0

.claude/commands/issues/discover.md

@@ -122,7 +122,7 @@ gh issue list --milestone "v0.14.0" --state open
   - Patterns: User-facing feature limitations
   - Suggestion: Audit all limitation messages for issue tracking
 
-- "throw new Error" without handleApiError
+- "throw new Error" without error handling context
   - Locations: domain layer violations
   - Suggestion: Architecture review for error handling
 ```
@@ -205,7 +205,7 @@ Creates structured discovery report and suggests next actions:
 ## Integration with Project Standards
 
 - **Clean Architecture:** Identifies layer violations during discovery
-- **Error Handling:** Finds missing `handleApiError` usage patterns  
+- **Error Handling:** Finds missing error feedback patterns using `showError` and `logging`  
 - **Import Standards:** Validates absolute import usage in discovered files
 - **Quality Gates:** Ensures discoveries align with `pnpm check` standards
 - **Solo Workflow:** Optimized for single developer context and decisions

.claude/commands/quality/review.md

@@ -72,7 +72,7 @@ Each generated review file contains:
 ### Code Quality
 - **Clean Architecture:** Layer separation and dependencies
 - **Type Safety:** TypeScript usage and null checks
-- **Error Handling:** Proper `handleApiError` usage
+- **Error Handling:** Proper `showError` and `logging` usage
 - **Testing:** Test coverage and quality
 - **Performance:** Efficiency and optimization opportunities
 

.claude/commands/refactor/clean-architecture.md

@@ -53,15 +53,15 @@ This command performs comprehensive refactoring to ensure clean architecture com
 
 **Rules:**
 - **Pure logic only** - No side effects
-- **Never call `handleApiError`** - Only throws pure errors
+- **Never use side-effect utilities** - Only throws pure errors with context via `cause`
 - **No external dependencies** - Framework-agnostic code
 - **Business rules** - Core business logic and entities
 
 **Refactoring Actions:**
 ```typescript
 // Before: Domain with side effects
 export function updateDayDiet(dayDiet: DayDiet) {
-  handleApiError(new Error('Invalid'), { component: 'domain' }) // ❌
+  showError(new Error('Invalid'), { context: 'domain' }) // ❌
   toast.success('Updated') // ❌
   return dayDiet
 }
@@ -80,7 +80,7 @@ export function updateDayDiet(dayDiet: DayDiet): DayDiet {
 **Rules:**
 - **Orchestrates domain logic** - Coordinates between layers
 - **Handles all side effects** - API calls, error handling, toasts
-- **Catches domain errors** - Always calls `handleApiError` with context
+- **Catches domain errors** - Uses `showError` for toasts and `logging` for telemetry
 - **State management** - SolidJS signals and effects
 
 **Refactoring Actions:**
@@ -94,6 +94,9 @@ export function useDayDietUpdater() {
 }
 
 // After: Proper application orchestration
+import { showError } from '~/modules/toast/application/toastManager'
+import { logging } from '~/shared/utils/logging'
+
 export function useDayDietUpdater() {
   const updateDayDiet = async (dayDiet: DayDiet) => {
     try {
@@ -102,11 +105,11 @@ export function useDayDietUpdater() {
       toast.success('Day diet updated successfully')
       return result
     } catch (e) {
-      handleApiError(e, {
+      logging.error('updateDayDiet failed', e, {
         component: 'DayDietUpdater',
-        operation: 'updateDayDiet',
         additionalData: { dayDietId: dayDiet.id }
       })
+      showError(e, { context: 'user-action' })
       throw e
     }
   }
@@ -181,7 +184,8 @@ export function MealEditor() {
       await mealRepository.save(meal())
       toast.success('Meal saved')
     } catch (e) {
-      handleApiError(e, { component: 'MealEditor' })
+      logging.error('saveMeal failed', e, { component: 'MealEditor' })
+      showError(e, { context: 'user-action' })
     } finally {
       setLoading(false)
     }
@@ -190,6 +194,9 @@ export function MealEditor() {
 
 // After: Extracted hook
 // ~/modules/diet/meal/application/useMealEditor.ts
+import { showError } from '~/modules/toast/application/toastManager'
+import { logging } from '~/shared/utils/logging'
+
 export function useMealEditor() {
   const [meal, setMeal] = createSignal<Meal>()
   const [loading, setLoading] = createSignal(false)
@@ -200,11 +207,11 @@ export function useMealEditor() {
       await mealRepository.save(meal())
       toast.success('Meal saved')
     } catch (e) {
-      handleApiError(e, {
+      logging.error('saveMeal failed', e, {
         component: 'MealEditor',
-        operation: 'saveMeal',
         additionalData: { mealId: meal()?.id }
       })
+      showError(e, { context: 'user-action' })
     } finally {
       setLoading(false)
     }
@@ -253,11 +260,11 @@ export function groupWeightsByPeriod(weights: Weight[]) {
 ```typescript
 // Before: Relative imports
 import { DayDiet } from '../../domain/dayDiet' // ❌
-import { handleApiError } from '../../../shared/error/errorHandler' // ❌
+import { showError } from '../../../toast/application/toastManager' // ❌
 
 // After: Absolute imports
 import { DayDiet } from '~/modules/diet/day-diet/domain/dayDiet' // ✅
-import { handleApiError } from '~/shared/error/errorHandler' // ✅
+import { showError } from '~/modules/toast/application/toastManager' // ✅
 ```
 
 ### Static Import Enforcement
@@ -283,7 +290,6 @@ const Component = lazy(() => import('./Component')) // ✅
 
 2. **Verify success message:**
    - Must see "COPILOT: All checks passed!"
-   - Check with `.scripts/cat1.sh`, `.scripts/cat2.sh`, `.scripts/cat3.sh`
 
 3. **Architecture validation:**
    - No cross-layer violations

.claude/commands/session/end.md

@@ -130,8 +130,8 @@ export interface SessionLearning {
 - **Data access patterns:** Efficient database and API usage
 
 ### Error Handling Strategies
-- **Domain layer purity:** Maintaining clean error throwing
-- **Application layer coordination:** Effective `handleApiError` usage
+- **Domain layer purity:** Maintaining clean error throwing with context via `cause`
+- **Application layer coordination:** Effective `showError` and `logging` usage
 - **User feedback patterns:** Toast and notification strategies
 - **Recovery mechanisms:** Graceful error recovery approaches
 
@@ -236,7 +236,7 @@ export interface SessionLearning {
 - **Performance:** Sliding window algorithm for period grouping
 - **Architecture:** Clean separation of domain and application concerns
 - **Testing:** Effective mock patterns for Supabase integration
-- **Error Handling:** Consistent `handleApiError` usage patterns
+- **Error Handling:** Consistent `showError` and `logging` usage patterns
 
 ## Process Improvements
 - **Quality Validation:** Streamlined npm run copilot:check workflow

.claude/commands/workflow/context.md

@@ -117,7 +117,7 @@ interface WorkflowContext {
 {
   phase: 'implementation',
   modifiedFiles: ['RecipeEditModal.tsx', 'recipe.ts'],
-  architecturalDecisions: ['use domain validation', 'add handleApiError'],
+  architecturalDecisions: ['use domain validation', 'use showError and logging'],
   testPatterns: ['mock validation', 'test error scenarios'],
   suggestedActions: ['run quality checks', 'update related tests']
 }

.claude/commands/workflow/orchestrate.md

@@ -253,7 +253,7 @@ const qualityIntegration = {
 
   contextualGates: {
     architectureCompliance: 'verify clean architecture adherence',
-    errorHandling: 'confirm proper handleApiError usage',
+    errorHandling: 'confirm proper showError and logging usage',
     testCoverage: 'validate test updates for changes'
   },
 

.env.example

@@ -26,6 +26,10 @@ VITE_OTEL_EXPORTER_OTLP_ENDPOINT=
 # Example: VITE_SENTRY_DSN=https://abc123@o123456.ingest.sentry.io/123456
 VITE_SENTRY_DSN=
 
+# Debug CWD for VSCode links in error stack traces (optional)
+# Set this to your local development folder path to enable clickable links
+VITE_DEBUG_CWD=
+
 # Sentry Build Configuration (for CI/CD and source map upload)
 # Get these from: https://sentry.io → Settings → Developer Settings → Auth Tokens
 SENTRY_ORG=

.github/COPILOT_SETUP_VALIDATION.md

@@ -0,0 +1,147 @@
+# GitHub Copilot Setup Validation
+
+This document validates that the macroflows repository follows GitHub Copilot coding agent best practices.
+
+## ✅ Completed Setup Checklist
+
+### Core Configuration Files
+
+- [x] **`.github/copilot-instructions.md`** - Main instruction file with frontmatter (`applyTo: "**"`)
+  - Contains comprehensive coding standards for TypeScript, SolidJS, and Clean Architecture
+  - Includes project-specific rules (barrel file ban, import conventions)
+  - Defines error handling patterns for Domain and Application layers
+  - Specifies testing, validation, and commit message requirements
+  - References label usage and search feature requirements
+
+- [x] **`.github/copilot-commit-message-instructions.md`** - Commit message generation guidelines
+  - Enforces Conventional Commits standard
+  - Defines commit types and scoping conventions
+  - Includes quality rules to avoid vague language
+  - Provides examples of correct and incorrect commit messages
+
+### Instruction Files
+
+- [x] **`.github/instructions/`** directory exists
+  - Contains 1 scoped instruction file:
+    - `copilot/copilot-customization.instructions.md` - Applies to `.github/**/*.md` files
+    - Contains VS Code Copilot customization documentation
+
+### Prompt Files
+
+- [x] **`.github/prompts/`** directory exists
+  - Contains 28 reusable prompt templates (`.prompt.md` files)
+  - Organized by task type:
+    - GitHub Issue creation (bug, feature, refactor, sub-issue, task, etc.)
+    - Code review and PR management
+    - Development workflows (refactoring, fixing, implementation)
+    - Project management (milestone management, prioritization)
+
+### Documentation
+
+- [x] **`.github/README.md`** - Comprehensive documentation of Copilot setup
+  - Describes directory structure
+  - Documents main configuration files
+  - Provides usage guidelines for developers and Copilot
+  - Includes validation instructions and best practices
+  - Lists project tech stack and architectural principles
+
+## Best Practices Alignment
+
+### ✅ Well-Defined Instructions
+
+- Instructions are clear, specific, and actionable
+- Each instruction addresses a specific aspect of code generation
+- Instructions avoid generic or vague guidelines
+- Project-specific patterns are well-documented
+
+### ✅ Scoped Configuration
+
+- Main instructions apply globally (`applyTo: "**"`)
+- Scoped instructions exist for specific file patterns (`.github/**/*.md`)
+- Instructions can be extended with more scoped files as needed
+
+### ✅ Reusable Prompts
+
+- 28 prompt templates available for common tasks
+- Prompts are organized by category
+- Prompts can reference other prompts and instruction files
+
+### ✅ Quality Standards
+
+- Commit message quality is enforced through specific instructions
+- Code validation process is documented (`pnpm run copilot:check`)
+- Testing requirements are clearly defined
+- Error handling patterns are specified
+
+### ✅ Project Context
+
+- Architecture principles are documented (Clean Architecture, DDD)
+- Tech stack is clearly specified (SolidJS, TypeScript, Supabase)
+- Domain-specific patterns are explained
+- Solo project adaptations are included
+
+## Additional Recommendations Implemented
+
+### Documentation
+
+- [x] Created comprehensive README explaining the Copilot setup
+- [x] Documented directory structure and file purposes
+- [x] Provided usage guidelines for both developers and Copilot
+- [x] Included validation procedures
+
+### Organization
+
+- [x] Instructions are organized by topic and scope
+- [x] Prompts are categorized by task type
+- [x] File naming conventions are consistent
+
+## Future Enhancements (Optional)
+
+While the current setup is comprehensive and follows best practices, here are potential future enhancements:
+
+### Custom Agents (Advanced)
+
+- [ ] Consider creating `.github/agents/` directory for custom agent configurations
+  - Custom agents can be tuned for specific workflows
+  - Agents can have specialized context and tools
+  - Requires Model Context Protocol (MCP) server setup
+
+### Additional Scoped Instructions
+
+- [ ] Consider adding more scoped instruction files for different areas:
+  - `instructions/frontend.instructions.md` for SolidJS components
+  - `instructions/backend.instructions.md` for Supabase integration
+  - `instructions/testing.instructions.md` for test-specific guidelines
+
+### Enhanced Prompts
+
+- [ ] Add more specialized prompts as patterns emerge:
+  - Component generation templates
+  - Migration scripts
+  - Performance optimization workflows
+
+## Validation Results
+
+**Status**: ✅ **PASSED**
+
+The macroflows repository successfully implements GitHub Copilot coding agent best practices:
+
+1. ✅ Main instruction file exists and is comprehensive
+2. ✅ Commit message generation is properly configured
+3. ✅ Scoped instruction files are available
+4. ✅ Extensive prompt library exists (28 prompts)
+5. ✅ Setup is documented for contributors
+6. ✅ Project context and architecture are clearly defined
+7. ✅ Quality standards and validation procedures are specified
+
+## References
+
+- [GitHub Copilot Best Practices](https://docs.github.com/en/copilot/tutorials/coding-agent/get-the-best-results)
+- [Custom Instructions Documentation](https://code.visualstudio.com/docs/copilot/copilot-customization)
+- [Onboarding GitHub Copilot Coding Agent](https://github.blog/ai-and-ml/github-copilot/onboarding-your-ai-peer-programmer-setting-up-github-copilot-coding-agent-for-success/)
+
+---
+
+**Last Updated**: 2025-11-04  
+**Validated By**: GitHub Copilot Coding Agent  
+**Repository**: marcuscastelo/macroflows