Update to Knock

{
  "name": "knock-notification-best-practices",
  "description": "Comprehensive guidelines for designing, writing, and implementing effective notification systems across email, push, SMS, in-app, and chat channels.",
  "included_files": [
    {
      "relative_path": "rules/channel-specific-notifications-guidelines.md",
      "size_in_bytes": 6558
    },
    {
      "relative_path": "rules/notification-copy-best-practices.md",
      "size_in_bytes": 4826
    },
    {
      "relative_path": "rules/notification-system-implementation.md",
      "size_in_bytes": 10673
    },
    {
      "relative_path": "rules/notification-template-examples.md",
      "size_in_bytes": 9293
    },
    {
      "relative_path": "rules/transactional-email-best-practices.md",
      "size_in_bytes": 8605
    },
    {
      "relative_path": "rules/welcome-email-best-practices.md",
      "size_in_bytes": 8546
    }
  ],
  "skill_md_contents": "---\nname: knock-notification-best-practices\ndescription: Comprehensive guidelines for designing, writing, and implementing effective notification systems across email, push, SMS, in-app, and chat channels.\n---\n\n# Notification best practices skill\n\nThis skill provides comprehensive guidelines and best practices for designing, writing, and implementing effective notification systems across all channels.\n\n## Overview\n\nThe notification best practices skill includes six detailed rule sets covering:\n\n1. **Channel-specific notification guidelines** - Specifications for email, push, SMS, in-app, and chat notifications\n2. **Notification copy best practices** - Core principles for writing effective notification copy\n3. **Notification system implementation rules** - Technical implementation guidelines including timing, preferences, error handling, and compliance\n4. **Notification template examples** - Ready-to-use templates for common notification use cases\n5. **Transactional email best practices** - Deliverability, templates, localization, and dynamic content for transactional emails\n6. **Welcome email best practices** - Guidelines for crafting effective SaaS welcome emails\n\n## How to use this skill\n\n### For writing notifications\n\nWhen you need to write notification copy:\n\n1. **Start with copy best practices** (`rules/notification-copy-best-practices.md`)\n   - Follow core principles: be specific, include context, use active voice\n   - Choose the right tone and structure for your notification type\n\n2. **Check channel-specific guidelines** (`rules/channel-specific-notifications-guidelines.md`)\n   - Verify character limits for your target channel\n   - Follow channel-specific formatting requirements\n   - Ensure your message fits the channel's constraints\n\n3. **Reference templates** (`rules/notification-template-examples.md`)\n   - Find similar use cases to your notification\n   - Adapt template structure and variables\n   - Use provided examples as starting points\n\n### For email notifications\n\nWhen working with email notifications:\n\n1. **Review transactional email best practices** (`rules/transactional-email-best-practices.md`)\n   - Follow deliverability guidelines\n   - Use componentized templates and partials\n   - Implement proper localization\n\n2. **For welcome emails specifically** (`rules/welcome-email-best-practices.md`)\n   - Choose the right pattern for your product\n   - Follow timing best practices\n   - Focus on value and clear CTAs\n\n### For system implementation\n\nWhen implementing a notification system:\n\n1. **Follow system implementation rules** (`rules/notification-system-implementation.md`)\n   - Understand channel selection criteria\n   - Implement proper timing and frequency controls\n   - Set up preference management\n   - Handle errors and retries correctly\n   - Ensure compliance with regulations\n\n2. **Use channel-specific guidelines** for technical constraints\n   - Character limits\n   - Formatting requirements\n   - Delivery specifications\n\n## Rule files reference\n\n- `rules/channel-specific-notifications-guidelines.md` - Channel specifications and constraints\n- `rules/notification-copy-best-practices.md` - Writing principles and guidelines\n- `rules/notification-system-implementation.md` - Technical implementation rules\n- `rules/notification-template-examples.md` - Template library with examples\n- `rules/transactional-email-best-practices.md` - Email-specific best practices\n- `rules/welcome-email-best-practices.md` - Welcome email patterns and guidelines\n\n## Quick reference\n\n### Channel selection\n- **Email**: Persistent reference, detailed content, non-time-critical\n- **Push**: Time-sensitive, requires app return, urgent actions\n- **SMS**: Guaranteed delivery, authentication, extreme time-criticality\n- **In-app**: User active in product, can wait until next session\n- **Chat**: Team collaboration, immediate visibility needed\n\n### Copy principles\n- Be specific and actionable\n- Include maximum context\n- Use active voice\n- Maintain consistent terminology\n- Format for each channel\n\n### Common patterns\n- Transactional: Confirm what happened, include identifiers, provide next steps\n- System: Translate technical events to user impact, offer actionable steps\n- Lifecycle: Balance value with frequency, use social proof appropriately\n- Promotional: Lead with benefits, make offers specific and time-bound\n\n## Best practices summary\n\n1. **Always provide context** - Users need enough information to decide whether to act\n2. **Respect channel constraints** - Follow character limits and formatting requirements\n3. **Use appropriate timing** - Consider immediate vs. batched vs. scheduled sends\n4. **Implement preferences** - Give users control over notification types and channels\n5. **Test thoroughly** - Verify across channels, devices, and with real data\n6. **Monitor and optimize** - Track delivery, engagement, and user satisfaction metrics\n"
}