myconotification-system-operationslisted
Install: claude install-skill goondocks-co/myco
# Myco Notification System: Configuration, Wiring, and Debugging
This skill covers the operational semantics of the Myco notification system — the gotchas, configuration rules, and debug protocols a developer needs when extending, configuring, or diagnosing notification domains. For the mechanical wiring steps (registry → emission → display → React hook), see `extend-myco-daemon`. This skill is additive: it documents what goes wrong, how to configure correctly, and how to diagnose failures.
## Prerequisites
- The daemon is running and accessible.
- You understand basic notification domain wiring (see `extend-myco-daemon`).
- You have access to `src/daemon/` and `src/ui/` source trees.
## Procedure 1: Domain Registration and Defaults
Register a new notification domain using the self-registration API. The registry entry establishes the **lowest-priority fallback** defaults for the domain.
```typescript
// src/daemon/notifications/registry.ts (or domain-specific file)
notificationRegistry.register({
domain: 'version_sync',
defaultMode: 'banner', // 'banner' | 'summary' | 'none'
defaultTitle: 'Version Sync',
defaultIcon: '🔄',
description: 'Notifies when a version sync event occurs',
});
```
**Critical constraint:** Registry defaults are the LOWEST-priority fallback. Set `defaultMode` to a safe last-resort value. The mode resolution chain (Procedure 2) means users can override your defaults through config — but only if registry values don't accidentally win