slack-message-formatter
Slack Message Formatter
When the user asks you to parse, format, organize, or do anything with a message, always ask if this is for Slack before proceeding.
If yes, format the message following these rules:
Slack Formatting Rules
Text Formatting
- Bold: Single asterisk
*bold*(NOT double**) - Italic: Underscore
_italic_ - Strikethrough: Tilde
~strike~ - Code: Backticks
`code` - Code block: Triple backticks
- Quote: Prefix line with
>
Structure
- Minimal line breaks: Don't break lines excessively. Keep paragraphs flowing naturally like human conversation
- No markdown separators: Never use
---or===
More from yurifrl/cly
charm-stack
Build terminal UIs with Bubbletea v2, Bubbles v2, Lipgloss v2, and Huh v2. Use when creating TUI applications, interactive forms, styled terminal output, or when user mentions Bubbletea, Bubbles, Lipgloss, Huh, Charm, or TUI development.
59cobra-modularity
Build modular CLI applications with Cobra framework. Use when structuring CLI commands, implementing modular command architecture, handling flags and arguments, or when user mentions Cobra, CLI modularity, command registration, or spf13/cobra.
15go-specialist
Go language consultant providing guidance on best practices, testing with testify, concurrency patterns, error handling, and technology stack recommendations. Use when answering Go questions, reviewing Go code, or advising on Go implementation approaches.
13add-module
Create new demo or utility modules following CLY project patterns. Use when adding TUI demonstration modules to modules/demo/ or utility modules to modules/, following Bubbletea/Bubbles conventions with proper Cobra CLI integration.
12cli-config
Manage CLI application configuration with Cobra and Viper. Use when implementing config files, environment variables, flags binding, or when user mentions Viper, configuration management, config files, or CLI settings.
10testing
Write tests using TDD principles with integration tests as default and minimal mocking. Use when writing code, fixing bugs, or when user mentions tests, TDD, unit tests, integration tests, or testing strategy.
5