Why use 'app_pages/' instead of the default 'pages/' directory?

Using 'app_pages/' prevents conflicts with Streamlit's legacy auto-discovery API, giving you full programmatic control via the modern st.navigation and st.Page APIs.

How do I maintain state when a user switches between pages?

You should initialize global state in your main entry point file (streamlit_app.py) using st.session_state, which persists as the user navigates through the app.

Where should shared UI elements like sidebars or titles be defined?

Shared elements should be placed in the main entry point file before the page.run() call. This ensures they appear consistently across all individual page modules.

Can I show different navigation options based on user roles?

Yes, this skill provides patterns for building your page list dynamically before passing it to st.navigation, allowing you to show or hide pages based on session_state or user permissions.

Building Multi-page Streamlit Apps

Name: Building Multi-page Streamlit Apps
Author: Aaron-Tawil

byAaron-Tawil

0•

Data Science & ML

Guides the development of organized, multi-page Streamlit applications using modern navigation APIs and shared state management.

This skill provides a standardized framework for building complex Streamlit applications by leveraging the latest navigation and page management features. It establishes a robust directory structure using 'app_pages/' to avoid legacy conflicts, demonstrates how to manage global versus page-specific session states, and implements dynamic navigation patterns. Whether building role-based dashboards or multi-step data tools, this skill ensures developers can create scalable, maintainable, and professional-grade interfaces with clean programmatic navigation and shared UI components.

Key Features

01Modern st.navigation and st.Page API implementation

020 GitHub stars

03Shared UI element patterns across the navigation lifecycle

04Global and page-specific session state management

05Conflict-free directory structure using app_pages/

06Conditional page rendering based on authentication or roles

Use Cases

01Building internal tools with role-based access control for admin and user views

02Creating complex data dashboards with distinct views for analytics, settings, and reports

03Developing multi-step data processing pipelines with clear navigation states

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add aaron-tawil/super-order-automation building-streamlit-multipage-apps

For use in Claude.ai and ChatGPT

Key Features

01Modern st.navigation and st.Page API implementation

020 GitHub stars

03Shared UI element patterns across the navigation lifecycle

04Global and page-specific session state management

05Conflict-free directory structure using app_pages/

06Conditional page rendering based on authentication or roles

Use Cases

01Building internal tools with role-based access control for admin and user views

02Creating complex data dashboards with distinct views for analytics, settings, and reports

03Developing multi-step data processing pipelines with clear navigation states

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add aaron-tawil/super-order-automation building-streamlit-multipage-apps

For use in Claude.ai and ChatGPT