shiny-bslib
This skill provides patterns and techniques for building modern Shiny dashboards and web applications using bslib's Bootstrap 5 components. Use it when creating new Shiny apps from scratch, modernizing legacy applications that rely on outdated approaches like fluidPage or shinythemes, or implementing specific bslib features including page layouts, grid systems, cards, value boxes, navigation structures, sidebars, theming, and interactive components like accordions, tooltips, and popovers.
git clone --depth 1 https://github.com/posit-dev/skills /tmp/shiny-bslib && cp -r /tmp/shiny-bslib/shiny/shiny-bslib ~/.claude/skills/shiny-bslibSKILL.md
# Modern Shiny Apps with bslib
Build professional Shiny dashboards using bslib's Bootstrap 5 components and layouts. This skill focuses on modern UI/UX patterns that replace legacy Shiny approaches.
## Quick Start
**Single-page dashboard:**
```r
library(shiny)
library(bslib)
ui <- page_sidebar(
title = "My Dashboard",
theme = bs_theme(version = 5), # "shiny" preset by default
sidebar = sidebar(
selectInput("variable", "Variable", choices = names(mtcars))
),
layout_column_wrap(
width = 1/3,
fill = FALSE,
value_box(title = "Users", value = "1,234", theme = "primary"),
value_box(title = "Revenue", value = "$56K", theme = "success"),
value_box(title = "Growth", value = "+18%", theme = "info")
),
card(
full_screen = TRUE,
card_header("Plot"),
plotOutput("plot")
)
)
server <- function(input, output, session) {
output$plot <- renderPlot({
hist(mtcars[[input$variable]], main = input$variable)
})
}
shinyApp(ui, server)
```
**Multi-page dashboard:**
```r
ui <- page_navbar(
title = "Analytics Platform",
theme = bs_theme(version = 5),
nav_panel("Overview", overview_ui),
nav_panel("Analysis", analysis_ui),
nav_panel("Reports", reports_ui)
)
```
## Core Concepts
### Page Layouts
- **`page_sidebar()`** -- Single-page dashboard with sidebar (most common)
- **`page_navbar()`** -- Multi-page app with top navigation bar
- **`page_fillable()`** -- Viewport-filling layout for custom arrangements
- **`page_fluid()`** -- Scrolling layout for long-form content
See [page-layouts.md](references/page-layouts.md) for detailed guidance.
### Grid Systems
- **`layout_column_wrap()`** -- Uniform grid with auto-wrapping (recommended for most cases)
- **`layout_columns()`** -- 12-column Bootstrap grid with precise control
See [grid-layouts.md](references/grid-layouts.md) for detailed guidance.
### Cards
Primary container for dashboard content. Support headers, footers, multiple body sections, and full-screen expansion.
See [cards.md](references/cards.md) for detailed guidance.
### Value Boxes
Display key metrics and KPIs with optional icons, sparklines, and built-in theming.
See [value-boxes.md](references/value-boxes.md) for detailed guidance.
### Navigation
- **Page-level**: `page_navbar()` for multi-page apps
- **Component-level**: `navset_card_underline()`, `navset_tab()`, `navset_pill()` for tabbed content
See [navigation.md](references/navigation.md) for detailed guidance.
### Sidebars
- **Page-level**: `page_sidebar()` or `page_navbar(sidebar = ...)`
- **Component-level**: `layout_sidebar()` within cards
- Supports conditional content, dynamic open/close, accordions
- `resizable = TRUE` by default — users can drag the edge to resize on desktop
See [sidebars.md](references/sidebars.md) for detailed guidance.
### Filling Layouts
The fill system controls how components resize to fill available space. Key concepts: fillable containers, fill items, fill carriers. Fill activates when containers have defined heights.
See [filling.md](references/filling.md) for detailed guidance.
### Theming
- **`bs_theme()`** with Bootswatch themes for quick styling
- **Custom colors**: `bg`, `fg`, `primary` affect hundreds of CSS rules
- **Fonts**: `font_google()` for typography
- **Dynamic theming**: `input_dark_mode()` + `session$setCurrentTheme()`
See [theming.md](references/theming.md) for detailed guidance.
### UI Components
- **Accordions** -- Collapsible sections, especially useful in sidebars
- **Tooltips** -- Hover-triggered help text
- **Popovers** -- Click-triggered containers for secondary UI/inputs
- **Toasts** -- Temporary notification messages
- **Toolbars** -- Compact horizontal strips of buttons, selects, and dividers for card headers and footers
See [accordions.md](references/accordions.md), [tooltips-popovers.md](references/tooltips-popovers.md), [toasts.md](references/toasts.md), and [toolbars.md](references/toolbars.md).
### Icons
**Recommended: `bsicons` package** (Bootstrap Icons, designed for bslib):
```r
bsicons::bs_icon("graph-up")
bsicons::bs_icon("people", size = "2em")
```
Browse icons: https://icons.getbootstrap.com/
**Alternative: `fontawesome` package:**
```r
fontawesome::fa("envelope")
```
**Accessibility for icon-only triggers:** When an icon is used as the sole trigger for a tooltip, popover, or similar interactive element (no accompanying text), it must be accessible to screen readers. By default, icon packages mark icons as decorative (`aria-hidden="true"`), which hides them from assistive technology.
- **`bsicons::bs_icon()`**: Provide `title` — this automatically sets `a11y = "sem"`
```r
tooltip(
bs_icon("info-circle", title = "More information"),
"Tooltip content here"
)
```
- **`fontawesome::fa()`**: Set `a11y = "sem"` and provide `title`
```r
tooltip(
fa("circle-info", a11y = "sem", title = "More information"),
"Tooltip content here"
)
```
The `title` should describe the purpose of the trigger (e.g., "More information", "Settings"), not the icon itself (e.g., not "info circle icon").
### Special Inputs
- **`input_switch()`** -- Toggle switch (modern checkbox alternative)
- **`input_dark_mode()`** -- Dark mode toggle
- **`input_task_button()`** -- Button for long-running operations
- **`input_code_editor()`** -- Code editor with syntax highlighting
- **`input_submit_textarea()`** -- Textarea with explicit submission
See [inputs.md](references/inputs.md) for detailed guidance.
## Common Workflows
### Building a Dashboard
1. Choose page layout: `page_sidebar()` (single-page) or `page_navbar()` (multi-page)
2. Add theme with `bs_theme()` (consider Bootswatch for quick start)
3. Create sidebar with inputs for filtering/controls
4. Add value boxes at top for key metrics (set `fill = FALSE` on container)
5. Arrange cards with `layout_column_wrap()` or `layout_columns()`
6. Enable `full_screen = TRUE` on all visualization cards
7. Add `thematic::thematic>
Create and use brand.yml files for consistent branding across Shiny apps and Quarto documents. Covers: (1) Creating new _brand.yml files, (2) Applying to Shiny (R and Python), (3) Using in Quarto, (4) Modifying existing files, and (5) Troubleshooting. Includes complete specifications and integration guides.
>
>
>
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
>-
Research a codebase and create architectural documentation describing how features or systems work. Use when the user asks to: (1) Document how a feature works, (2) Create an architecture overview, (3) Explain code structure for onboarding or knowledge transfer, (4) Research and describe a system's design. Produces markdown documents with Mermaid diagrams and stable code references suitable for humans and AI agents.