raphi011
36 verified skills
charmbracelet-tui
This skill should be used when the user asks to "build a TUI", "create a terminal UI", "use bubbletea", "add a text input", "add a spinner", "create a progress bar", "style with lipgloss", "test a bubbletea model", "use teatest", or when code imports charm.land or charmbracelet packages. Covers Bubbletea v2, Bubbles v2, Lipgloss v2, tea.Model implementations, keyboard/mouse input, program lifecycle, bubbles components (textinput, progress, spinner, viewport, list), teatest, glamour rendering, inline mode, and tea.Println usage.
development
codecov
This skill should be used when the user asks to "check test coverage", "find untested code", "show coverage gaps", "fetch codecov report", "check codecov", "analyze coverage", "what needs more tests", "coverage on this branch", or when planning coverage improvements. Fetches test coverage data from the Codecov API and identifies coverage gaps for the current repository.
development
github-code-search
This skill should be used when the user asks to "search GitHub for code", "search code on GitHub", "find code across repos", "search for usage examples on GitHub", "find implementations in other repos", "find how other repos use", "look for code examples on GitHub", "gh search code", or when local grep is insufficient because the code lives in other repositories. Covers gh search code patterns, structured output, filtering by language/filename/extension, and cross-repository code discovery.
tools
go-quality
Validates Go code quality, runs tests, and fixes issues using a comprehensive validation script. Use this skill whenever working in a Go codebase and the user asks to "validate Go code", "fix Go issues", "run Go linters", "check Go code", "clean up Go code", or mentions go vet, staticcheck, gofmt, or Go static analysis. Also use when Go builds fail, tests are failing, or the user wants a quality check before committing. This skill should be the first step for any Go code quality concern.
development
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
development
kitty-tui-debug
Use when visually verifying terminal UI rendering, testing TUI interactions, debugging Bubbletea display issues, or when asked to "test the TUI", "screenshot the terminal", "check what the TUI looks like", or "visually verify". Requires Kitty terminal with allow_remote_control and macOS for screencapture.
development
mermaid
Use when the user asks to create a diagram, visualize a process, draw a flowchart, show a sequence diagram, model a state machine, create an ER diagram, visualize architecture, or any request involving Mermaid syntax or diagram generation.
data-ai
pr-review-guide
Generate a narrative PR review guide as a markdown file. Use when the user asks to "review this PR", "generate a review guide", "create a PR walkthrough", "review guide for PR", "pr review file", "guide me through this PR", "narrative review", or wants a structured markdown document that walks through PR changes as a story rather than file-by-file.
documentation
surrealdb
Use whenever working with SurrealDB — writing queries, defining schemas, configuring indexes, debugging errors, handling record IDs, using the Go SDK, or discussing SurrealDB architecture. Activate on any mention of SurrealDB, SurrealQL, HNSW indexes, or surreal-related Go SDK code.
development
pr-go
Validates Go code quality and creates a pull request. Triggered by "create a Go PR", "Go PR pipeline", "run Go validation and PR", or "validate and push Go code".
development
zk
Use when the user asks to "search my notes", "find in knowledge base", "look up my docs", "create a note", "remember this", "what do I know about", "find related notes", "find orphan notes", "list tags", "daily note", "quick note", "maintain knowledge base", "search zk", "search zettelkasten", "browse my vault", "check my notes on", "edit my document", or when interacting with the zk Zettelkasten knowledge base.
testing
tailwind-css
Use when writing Tailwind CSS v4 code, configuring Tailwind v4 with @theme or @variant directives, migrating from Tailwind v3 to v4, setting up CSS-native config (no tailwind.config.js), defining semantic color tokens, implementing dark mode with class-based @variant, creating design system tokens, or styling components with utility classes. Covers @import "tailwindcss", @theme blocks, @variant, @layer, CSS custom properties for colors, and common layout/component patterns.
tools
fix-prodsec-vulnerabilities
Discover vulnerabilities from Jira and automatically fix GitHub Dependabot alerts by applying dependency updates. Use when asked to: fix vulnerabilities, fix Dependabot alerts, remediate security issues, fix VDB tickets, or run /fix-prodsec-vulnerabilities.
testing
charmbracelet-tui
This skill should be used when the user asks to "build a TUI", "create a terminal UI", "use bubbletea", "add a text input", "add a spinner", "create a progress bar", "style with lipgloss", "test a bubbletea model", "use teatest", or when code imports charm.land or charmbracelet packages. Covers Bubbletea v2, Bubbles v2, Lipgloss v2, tea.Model implementations, keyboard/mouse input, program lifecycle, bubbles components (textinput, progress, spinner, viewport, list), teatest, glamour rendering, inline mode, and tea.Println usage.
development
codecov
This skill should be used when the user asks to "check test coverage", "find untested code", "show coverage gaps", "fetch codecov report", "check codecov", "analyze coverage", "what needs more tests", "coverage on this branch", or when planning coverage improvements. Fetches test coverage data from the Codecov API and identifies coverage gaps for the current repository.
development
go-quality
Validates Go code quality, runs tests, and fixes issues using a comprehensive validation script. Use this skill whenever working in a Go codebase and the user asks to "validate Go code", "fix Go issues", "run Go linters", "check Go code", "clean up Go code", or mentions go vet, staticcheck, gofmt, or Go static analysis. Also use when Go builds fail, tests are failing, or the user wants a quality check before committing. This skill should be the first step for any Go code quality concern.
development
kitty-tui-debug
Use when visually verifying terminal UI rendering, testing TUI interactions, debugging Bubbletea display issues, or when asked to "test the TUI", "screenshot the terminal", "check what the TUI looks like", or "visually verify". Requires Kitty terminal with allow_remote_control and macOS for screencapture.
development
pr-review-guide
Generate a narrative PR review guide as a markdown file. Use when the user asks to "review this PR", "generate a review guide", "create a PR walkthrough", "review guide for PR", "pr review file", "guide me through this PR", "narrative review", or wants a structured markdown document that walks through PR changes as a story rather than file-by-file.
documentation
tailwind-css
Use when writing Tailwind CSS v4 code, configuring Tailwind v4 with @theme or @variant directives, migrating from Tailwind v3 to v4, setting up CSS-native config (no tailwind.config.js), defining semantic color tokens, implementing dark mode with class-based @variant, creating design system tokens, or styling components with utility classes. Covers @import "tailwindcss", @theme blocks, @variant, @layer, CSS custom properties for colors, and common layout/component patterns.
tools
zk
Use when the user asks to "search my notes", "find in knowledge base", "look up my docs", "create a note", "remember this", "what do I know about", "find related notes", "find orphan notes", "list tags", "daily note", "quick note", "maintain knowledge base", "search zk", "search zettelkasten", "browse my vault", "check my notes on", "edit my document", or when interacting with the zk Zettelkasten knowledge base.
testing
surrealdb
Use whenever working with SurrealDB — writing queries, defining schemas, configuring indexes, debugging errors, handling record IDs, using the Go SDK, or discussing SurrealDB architecture. Activate on any mention of SurrealDB, SurrealQL, HNSW indexes, or surreal-related Go SDK code.
development
pr-go
Validates Go code quality and creates a pull request. Triggered by "create a Go PR", "Go PR pipeline", "run Go validation and PR", or "validate and push Go code".
development
mermaid
Use when the user asks to create a diagram, visualize a process, draw a flowchart, show a sequence diagram, model a state machine, create an ER diagram, visualize architecture, or any request involving Mermaid syntax or diagram generation.
data-ai
github-code-search
This skill should be used when the user asks to "search GitHub for code", "search code on GitHub", "find code across repos", "search for usage examples on GitHub", "find implementations in other repos", "find how other repos use", "look for code examples on GitHub", "gh search code", or when local grep is insufficient because the code lives in other repositories. Covers gh search code patterns, structured output, filtering by language/filename/extension, and cross-repository code discovery.
tools
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
development
pr-review
Generate a narrative PR review guide as a markdown file. Use when the user asks to "review this PR", "generate a review guide", "create a PR walkthrough", "review guide for PR", "pr review file", "guide me through this PR", "narrative review", or wants a structured markdown document that walks through PR changes as a story rather than file-by-file.
documentation
code-search
This skill should be used when the user asks to "search GitHub for code", "search code on GitHub", "find code across repos", "search for usage examples on GitHub", "find implementations in other repos", "find how other repos use", "look for code examples on GitHub", "gh search code", or when local grep is insufficient because the code lives in other repositories. Covers gh search code patterns, structured output, filtering by language/filename/extension, and cross-repository code discovery.
tools
ship
Validates Go code quality and creates a pull request. Triggered by "create a Go PR", "Go PR pipeline", "run Go validation and PR", or "validate and push Go code".
development
lint
Validates Go code quality, runs tests, and fixes issues using a comprehensive validation script. Use this skill whenever working in a Go codebase and the user asks to "validate Go code", "fix Go issues", "run Go linters", "check Go code", "clean up Go code", or mentions go vet, staticcheck, gofmt, or Go static analysis. Also use when Go builds fail, tests are failing, or the user wants a quality check before committing. This skill should be the first step for any Go code quality concern.
development
db
Use whenever working with SurrealDB — writing queries, defining schemas, configuring indexes, debugging errors, handling record IDs, using the Go SDK, or discussing SurrealDB architecture. Activate on any mention of SurrealDB, SurrealQL, HNSW indexes, or surreal-related Go SDK code.
development
mermaid
Use when the user asks to create a diagram, visualize a process, draw a flowchart, show a sequence diagram, model a state machine, create an ER diagram, visualize architecture, or any request involving Mermaid syntax or diagram generation.
data-ai
tui-debug
Use when visually verifying terminal UI rendering, testing TUI interactions, debugging Bubbletea display issues, or when asked to "test the TUI", "screenshot the terminal", "check what the TUI looks like", or "visually verify". Requires Kitty terminal with allow_remote_control and macOS for screencapture.
development
tui
This skill should be used when the user asks to "build a TUI", "create a terminal UI", "use bubbletea", "add a text input", "add a spinner", "create a progress bar", "style with lipgloss", "test a bubbletea model", "use teatest", or when code imports charm.land or charmbracelet packages. Covers Bubbletea v2, Bubbles v2, Lipgloss v2, tea.Model implementations, keyboard/mouse input, program lifecycle, bubbles components (textinput, progress, spinner, viewport, list), teatest, glamour rendering, inline mode, and tea.Println usage.
development
tailwind
Use when writing Tailwind CSS v4 code, configuring Tailwind v4 with @theme or @variant directives, migrating from Tailwind v3 to v4, setting up CSS-native config (no tailwind.config.js), defining semantic color tokens, implementing dark mode with class-based @variant, creating design system tokens, or styling components with utility classes. Covers @import "tailwindcss", @theme blocks, @variant, @layer, CSS custom properties for colors, and common layout/component patterns.
tools
report
This skill should be used when the user asks to "check test coverage", "find untested code", "show coverage gaps", "fetch codecov report", "check codecov", "analyze coverage", "what needs more tests", "coverage on this branch", or when planning coverage improvements. Fetches test coverage data from the Codecov API and identifies coverage gaps for the current repository.
development
revealjs
Create polished, professional reveal.js presentations. Use when the user asks to create slides, a presentation, a deck, or a slideshow. Supports themes, multi-column layouts, code highlighting, animations, speaker notes, and custom styling. Generates HTML + CSS with no build step required.
development