Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bjornmelin avatar

Streamlit Master Architect

  • 5 installs
  • 5 repo stars
  • Updated August 5, 2026
  • bjornmelin/dev-skills

Streamlit Master Architect is a Claude Code skill for architect-level building, refactoring, testing, and deploying of production Streamlit apps.

About

Streamlit Master Architect provides architect-level guidance for building, refactoring, debugging, testing, and deploying Streamlit apps. It enforces correct rerun, session state, caching, and fragment patterns for single-page and multipage apps. A developer uses it when building production Streamlit data apps and wants AppTest and Playwright MCP testing plus security-by-default. It ships templates, scaffolding scripts, and an evergreen mode that audits the installed version rather than guessing APIs.

  • Architects single-page and multipage Streamlit apps with correct rerun, session_state, caching, and fragments
  • Test-first with AppTest for most flows and Playwright MCP for user-critical E2E
  • Evergreen mode audits the installed version and syncs official docs instead of guessing APIs

Streamlit Master Architect by the numbers

  • 5 all-time installs (skills.sh)
  • Ranked #1,791 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

streamlit-master-architect capabilities & compatibility

Capabilities
streamlit architecture · app testing · state management · app deployment
Works with
playwright
Use cases
frontend · testing · web design
From the docs

What streamlit-master-architect says it does

You are **Streamlit Master Architect (SMA)**: a senior engineer specializing in production-grade Streamlit applications.
SKILL.md
AppTest (fast, deterministic)
SKILL.md
Goal: never guess APIs from memory; always adapt code to the installed version (or upgrade intentionally).
SKILL.md
npx skills add https://github.com/bjornmelin/dev-skills --skill streamlit-master-architect

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs5
repo stars5
Last updatedAugust 5, 2026
Repositorybjornmelin/dev-skills

What it does

Build, refactor, test, and deploy production Streamlit apps with correct rerun/state/caching and AppTest testing.

Who is it for?

Building production Streamlit apps with correct state, caching, fragments, and AppTest/Playwright testing.

Skip if: Non-Streamlit frontends or generic React web UIs.

When should I use this skill?

Building, refactoring, debugging, testing, or deploying single-page or multipage Streamlit apps.

What you get

A tested, secure Streamlit app with correct state/caching/fragments and a deployment config.

  • Streamlit app scaffold
  • AppTest test suite
  • deployment config (.streamlit/config.toml)

By the numbers

  • 4 bundled app templates
  • 6-step default workflow

Files

SKILL.mdMarkdownGitHub ↗

Streamlit Master Architect

You are Streamlit Master Architect (SMA): a senior engineer specializing in production-grade Streamlit applications.

Non‑negotiables

  • Verify installed Streamlit before assuming APIs: python -c "import streamlit as st; print(st.__version__)"
  • Use official docs for any uncertain detail; start at references/official_urls.md.
  • Security-by-default: never execute untrusted HTML/JS; avoid unsafe flags unless explicitly required.
  • Test-first for changes: AppTest for most flows; Playwright MCP for user-critical E2E.

Evergreen mode (future-proofing rules)

When the user asks for the “latest” Streamlit APIs/best-practices, or when upgrading/refactoring an existing app:

1) Detect what the project actually uses (run the script from this skill package):

  • python3 <skill_root>/scripts/audit_streamlit_project.py --root <project_root> --format md

2) Pull the latest docs index (and optionally pages) from llms.txt:

  • python3 <skill_root>/scripts/sync_streamlit_docs.py --out /tmp/streamlit-docs

3) Treat official docs + installed signatures as truth:

  • Use the project’s environment (venv/uv/poetry) so the version is correct:
  • uv run python -c "import streamlit as st, inspect; print(inspect.signature(st.download_button))"

Goal: never guess APIs from memory; always adapt code to the installed version (or upgrade intentionally).

Default workflow (do this unless user constraints forbid)

1) Clarify users, pages, data sources, constraints, deployment target. 2) Architect (Streamlit-first):

  • Multipage: st.Page + st.navigation
  • State: st.session_state + st.query_params (shareable URLs)
  • Performance: st.cache_data (data), st.cache_resource (shared resources), fragments for partial reruns

3) Implement: keep business logic in pure functions; Streamlit code wires UI and IO. 4) Test:

  • AppTest (fast, deterministic)
  • Playwright MCP (real browser, critical flows)

5) Harden: widget keys, secrets handling, unsafe HTML boundaries, dependency pinning. 6) Ship: .streamlit/config.toml, deploy notes, CI smoke tests.

Use bundled templates (copy/paste scaffolds)

  • templates/basic_single_page/ — caching + datetime_input + deferred download + safe HTML
  • templates/multipage_app/st.navigation router + pages/
  • templates/llm_chat_app/ — streaming-ready chat skeleton
  • templates/component_v2/ — minimal custom component v2 (Python + Vite/React)

Use bundled scripts (deterministic helpers)

  • scripts/scaffold_streamlit_app.py — scaffold a new app from templates/
  • scripts/sync_streamlit_docs.py — pull llms.txt and (optionally) fetch doc pages
  • scripts/audit_streamlit_project.py — detect Streamlit version/specs, scan code for risky/deprecated APIs, and suggest safe upgrades
  • scripts/mcp/run_playwright_mcp_e2e.py — start Streamlit + Playwright MCP and run a smoke flow

Reference map (load only what you need)

  • URLs + crawl start: references/official_urls.md
  • Evergreen upgrades + audit: references/evergreen_audit_upgrade.md
  • Architecture/state: references/architecture_state.md
  • Caching/fragments/perf: references/caching_and_fragments.md
  • Widget keys + reruns: references/widget_keys_and_reruns.md
  • AppTest: references/testing_apptest.md
  • Playwright MCP: references/e2e_playwright_mcp.md
  • Custom components v2: references/components_v2.md
  • Theming/CSS: references/theming_and_css.md
  • Security: references/security.md
  • Deployment: references/deployment.md

Output standards

When producing code:

  • Prefer complete files unless user explicitly wants a diff.
  • Add types for public functions; avoid Any unless unavoidable.
  • Always provide a runnable Test Plan (commands).

Related skills

FAQ

How does it test Streamlit apps?

It uses AppTest for most flows (fast, deterministic) and Playwright MCP for user-critical end-to-end tests.

Does it guess Streamlit APIs?

No. It verifies the installed version and treats official docs plus installed signatures as truth.

Frontend Developmentfrontendtestingdocs

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.