skills.rest
streamlit
streamlitOFFICIAL
Explore all skills by this author →
WebsiteGitHub

implementing-new-features

Coordinate end-to-end Streamlit feature implementation across protobufs, backend, and frontend.

45.5k|4.4k|Updated Aug 24, 2019
Search Tags:#workflow#testing#frontend#backend#implement#new-feature#protobufs
One-click install
npx skills add https://github.com/streamlit/streamlit --skill implementing-new-features
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementing-new-features
Source: https://github.com/streamlit/streamlit/tree/main/.claude/skills/implementing-new-features
Command: npx skills add https://github.com/streamlit/streamlit --skill implementing-new-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end feature implementation across protobufs, backend, and frontend for Streamlit.

Core Features & Use Cases

  • End-to-end planning: Align changes across protobuf definitions, backend logic, and frontend components.
  • Testing & validation: Includes Python unit tests, Vitest tests, and Playwright E2E tests to ensure quality before merge.
  • Deployment readiness: Recommends protobuf generation, code checks, and linting as part of the workflow.

Quick Start

Define a new feature and follow this guide to coordinate protobuf, backend, and frontend changes end-to-end.

Frequently Asked Questions about implementing-new-features

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement new Streamlit features across protobufs, backend, and frontend?▼

Implementing new Streamlit features requires coordinating end-to-end changes across protobuf definitions, backend logic, and frontend components. This workflow aligns model definitions, backend updates, and frontend components to enable new capabilities comprehensively.

What testing scenarios are needed for end-to-end Streamlit feature implementation?▼

End-to-end Streamlit feature implementation requires comprehensive testing scenarios including Python unit tests, Vitest frontend tests, and Playwright E2E validations. Automated tests and linting ensure deployment readiness before merge.

When do I need to regenerate protobufs for a new Streamlit feature?▼

You need to regenerate protobufs when a new Streamlit feature spans model definitions, backend logic, and frontend components. Protobuf generation is a required step to coordinate data structures across the backend and frontend layers.

What is the best way to coordinate frontend and backend updates for a Streamlit feature?▼

The best way to coordinate frontend and backend updates is through end-to-end planning that aligns protobuf changes, backend logic updates, and frontend component modifications, followed by code checks and linting.

Does implementing Streamlit capabilities require linting and automated tests?▼

Yes, implementing Streamlit capabilities requires automated tests and linting as part of the workflow. These code checks are recommended to ensure deployment readiness and validate Python unit tests, Vitest tests, and Playwright E2E tests.

Related Skills

Explore More Software Engineering Skills→
bovinphangbovinphang
21

fec-backend-requirements-handoff

Document frontend data, actions, state, and validation rules for backend review.

Community
Intermediate
Alif-NAlif-N

create-tests

Generate Playwright E2E and Vitest unit tests for DaaS features and API routes.

Community
Advanced
rahul-s-bhattrahul-s-bhatt

building-streamlit-custom-components-v2

Build interactive Streamlit custom components with bidirectional UI communication and reusable architectures.

Community
Advanced
gaganpasupuletigaganpasupuleti

full-stack

Coordinate full-stack features across FastAPI backend and Next.js frontend.

Community
Advanced