developing-with-streamlit
Skill512 starsChanged 7 months agoMITView on GitHub
**[REQUIRED]** Use for ALL Streamlit tasks: creating, editing, debugging, beautifying, styling, theming, optimizing, or deploying Streamlit applications. Also required for building custom components (inline or packaged), using st.components.v2, or any HTML/JS/CSS component work. Triggers: streamlit, st., dashboard, app.py, beautify, style, CSS, color, background, theme, button, widget styling, custom component, st.components, packaged component, pyproject.toml, asset_dir, CCv2, HTML/JS component.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- pp6235024-bit/claude-skillsedited, first seen Oct 11, 2026
- sid-git-repo/claude-skillsedited, first seen Aug 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- pp6235024-bit/claude-skills★ 012% same
- sid-git-repo/claude-skills★ 012% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- implement_yourself/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- implement_yourself/CLAUDE.mdCLAUDE.md
- research-and-writeSkill
- researchSkill
- write-postSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 82
Use this routing table to select sub-skill(s).
- Very specific: line 123
When creating a new dashboard app, prefer starting from a template in templates/apps/:
- Distinctive: line 124
If a template closely matches the request, copy it and adapt:
- Very specific: line 131
If no template is a close match, start from scratch but borrow relevant patterns from the templates (e.g., caching with @st.cache_data, …
- Distinctive: line 134
When editing an existing app, use templates as reference for best practices:
- Very specific: line 135
Check templates/apps/ for caching patterns, layout structure, and Snowflake integration
- Very specific: line 138
When applying a custom theme, use a template from templates/themes/:
- Distinctive: line 192
Step 2: If multiple sub-skills seem relevant, ask user which aspect to focus on first
- Distinctive: line 193
Step 4: Ask before starting the Streamlit app
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Developing with Streamlit
This is a routing skill that directs you to specialized sub-skills for Streamlit development.
When to Use
Invoke this skill when the user's request involves:
- Creating a new Streamlit app
- Editing or modifying an existing Streamlit app
- Debugging Streamlit issues (errors, session state bugs, performance problems)
- Beautifying or improving the visual design of a Streamlit app
- Optimizing Streamlit performance (caching, fragments, reruns)
- Deploying Streamlit apps (locally or to Snowflake)
- Styling widgets (button colors, backgrounds, CSS customization)
- Any question about Streamlit widgets, layouts, or components
Trigger phrases: "streamlit", "st.", "dashboard", "app.py", "beautify app", "make it look better", "style", "CSS", "color", "background", "theme", "button", "slow rerun", "session state", "performance", "faster", "cache", "deploy"
Workflow
Step 1: Locate the Streamlit source code
↓
Step 2: Identify task type and load appropriate sub-skill(s)
↓
Step 3: Apply guidance from sub-skill to edit code
↓
Step 4: Check if app is running and offer to run itStep 1: Locate the Streamlit Source Code (if needed)
Goal: Identify the app file(s) to edit. Skip this step if already clear from context.
When to skip:
- User mentioned a specific file path (e.g., "edit
src/app.py") - User has file(s) already in conversation context
- Working directory has an obvious single entry point (
app.py,streamlit_app.py)
When to search:
- User says "my streamlit app" without specifying which file
- Multiple Python files exist and it's unclear which is the entry point
If searching is needed:
- Quick scan for Streamlit files:
find . -name "*.py" -type f | xargs grep -l "import streamlit\|from streamlit" 2>/dev/null | head -10 - Apply entry point heuristics (in priority order):
streamlit_app.pyat root → this is the entry point (canonical name)app.pyat root → likely entry point- File using
st.navigation→ entry point for multi-page apps - Single
.pyfile at root with streamlit import → entry point - Files in
pages/orapp_pages/subdirectory → NOT entry points (these are sub-pages)
If entry point is obvious → use it, no confirmation needed
Example: Found
streamlit_app.pyandpages/metrics.py→ usestreamlit_app.py- Only ask if genuinely ambiguous (e.g., multiple root-level candidates, none named
streamlit_app.py):Found multiple potential entry points: - dashboard.py - main.py Which is your main app?
Output: Path to the main Streamlit source file(s)
Step 2: Identify Task Type and Route to Sub-Skill
Goal: Determine what the user needs and load the appropriate guidance.
Use this routing table to select sub-skill(s). Always read the sub-skill file before making changes:
| User Need | Sub-skill to Read |
| Performance issues, slow apps, caching | read skills/optimizing-streamlit-performance/SKILL.md |
| Building a dashboard with KPIs/metrics | read skills/building-streamlit-dashboards/SKILL.md |
| Improving visual design, icons, polish | read skills/improving-streamlit-design/SKILL.md |
| Choosing widgets (selectbox vs radio vs pills) | read skills/choosing-streamlit-selection-widgets/SKILL.md |
| Styling widgets (button colors, backgrounds, CSS) | read skills/creating-streamlit-themes/SKILL.md |
| Layouts (columns, tabs, sidebar, containers) | read skills/using-streamlit-layouts/SKILL.md |
| Displaying data (dataframes, charts) | read skills/displaying-streamlit-data/SKILL.md |
| Multi-page app architecture | read skills/building-streamlit-multipage-apps/SKILL.md |
| Session state and callbacks | read skills/using-streamlit-session-state/SKILL.md |
| Markdown, colored text, badges | read skills/using-streamlit-markdown/SKILL.md |
| Custom themes and colors | read skills/creating-streamlit-themes/SKILL.md |
| Comprehensive theme design and brand alignment | read skills/creating-streamlit-themes/SKILL.md |
| Chat interfaces and AI assistants | read skills/building-streamlit-chat-ui/SKILL.md |
| Connecting to Snowflake | read skills/connecting-streamlit-to-snowflake/SKILL.md |
| Building or packaging a custom component, triggering events back to Python from JS/HTML, custom HTML/JS with event handling (CCv2), OR any UI element that doesn't exist as a native Streamlit widget (e.g., drag-and-drop, custom interactive visualization, canvas drawing) | read skills/building-streamlit-custom-components-v2/SKILL.md — IMPORTANT: st.components.v1 is deprecated. Never use v1 for new components; always use st.components.v2.component(). |
| Third-party components | read skills/using-streamlit-custom-components/SKILL.md |
| Code organization | read skills/organizing-streamlit-code/SKILL.md |
| Environment setup | read skills/setting-up-streamlit-environment/SKILL.md |
| CLI commands | read skills/using-streamlit-cli/SKILL.md |
Fallback — "this widget doesn't exist in Streamlit":
If the user asks for a UI element or interaction that has never been part of Streamlit's API and cannot be built with any combination of native widgets (e.g., drag-and-drop, canvas drawing, custom interactive visualizations), route to the CCv2 sub-skill (skills/building-streamlit-custom-components-v2/SKILL.md). Do not route to CCv2 for features that exist in newer Streamlit versions (e.g., st.connection, st.segmented_control) — suggest upgrading instead.
Common combinations:
For beautifying/improving an app, read in order:
skills/improving-streamlit-design/SKILL.mdskills/using-streamlit-layouts/SKILL.mdskills/choosing-streamlit-selection-widgets/SKILL.md
For building a dashboard, read:
skills/building-streamlit-dashboards/SKILL.mdskills/displaying-streamlit-data/SKILL.md
IMPORTANT - Use templates:
When creating a new dashboard app, prefer starting from a template in templates/apps/:
- If a template closely matches the request, copy it and adapt:
dashboard-metrics/dashboard-metrics-snowflake— KPI cards with time-series chartsdashboard-companies— company/entity comparisondashboard-compute/dashboard-compute-snowflake— resource/credit monitoringdashboard-feature-usage— feature adoption trackingdashboard-seattle-weather— public dataset exploration (local only)dashboard-stock-peers/dashboard-stock-peers-snowflake— financial peer analysis
- If no template is a close match, start from scratch but borrow relevant patterns from the templates (e.g., caching with
@st.cache_data,filter_by_time_range(),st.set_page_config(), chart utilities, layout structure) - See
templates/apps/README.mdfor template descriptions
When editing an existing app, use templates as reference for best practices:
- Check
templates/apps/for caching patterns, layout structure, and Snowflake integration - Apply consistent patterns from templates to improve the existing code
When applying a custom theme, use a template from templates/themes/:
- Copy a theme directory (snowflake, dracula, nord, stripe, solarized-light, spotify, github, minimal)
- Themes use Google Fonts for easy setup
- See
templates/themes/README.mdfor theme previews
For performance optimization, read:
skills/optimizing-streamlit-performance/SKILL.md
Step 3: Apply Guidance to Edit Code
Goal: Make changes to the Streamlit app following sub-skill best practices.
Actions:
- Apply the patterns and recommendations from the loaded sub-skill(s)
- Make edits to the source file(s) identified in Step 1
- Preserve existing functionality while adding improvements
Step 4: Check Running Apps and Offer to Run
Goal: Help the user see their changes by checking if their app is running.
Actions:
- Check for running Streamlit apps on ports 850*:
lsof -nP -iTCP -sTCP:LISTEN 2>/dev/null | grep -i python | awk '{print $2, $9}' | grep ':85' || echo "No Streamlit apps detected on ports 850*" Present findings to user:
If app is running:
Found Streamlit app running: - PID: [pid] at http://localhost:[port] Your changes should be visible after a page refresh (Streamlit hot-reloads on file save).If no app is running:
No Streamlit app detected on ports 850*. Would you like me to run the app? I can start it with: streamlit run [app_file.py]- If user wants to run the app, start it:
streamlit run [path/to/app.py] --server.port 8501
Stopping Points
- Step 2: If multiple sub-skills seem relevant, ask user which aspect to focus on first
- Step 4: Ask before starting the Streamlit app
Skill map
| Skill | Covers |
| building-streamlit-chat-ui | Chat interfaces, streaming responses, message history |
| building-streamlit-dashboards | KPI cards, metrics, dashboard layouts |
| building-streamlit-multipage-apps | Page structure, navigation, shared state |
| building-streamlit-custom-components-v2 | Streamlit Custom Components v2 (inline and template-based packaged), bidirectional state/trigger callbacks, bundling, theme CSS variables |
| choosing-streamlit-selection-widgets | Selectbox vs radio vs segmented control vs pills vs multiselect |
| connecting-streamlit-to-snowflake | st.connection, query caching, credentials |
| creating-streamlit-themes | Theme configuration, colors, fonts, light/dark modes, professional brand alignment, CSS avoidance |
| displaying-streamlit-data | Dataframes, column config, charts |
| improving-streamlit-design | Icons, badges, colored text, visual polish |
| optimizing-streamlit-performance | Caching, fragments, forms, static vs dynamic widgets |
| organizing-streamlit-code | When to split into modules, separating UI from logic |
| setting-up-streamlit-environment | Python environment, dependency management |
| using-streamlit-custom-components | Third-party components from the community |
| using-streamlit-cli | CLI commands, running apps |
| using-streamlit-layouts | Sidebar, columns, containers, tabs, expanders, dialogs, alignment, spacing |
| using-streamlit-markdown | Colored text, badges, icons, LaTeX, and all markdown features |
| using-streamlit-session-state | Session state, widget keys, callbacks, state persistence |
Resources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

