Menu
Use when asked to fix short descriptions of Python type members.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement a new Flet extension/control that wraps a third-party Flutter package end-to-end, including dependency selection, version pinning, compatibility checks, Python/Flutter integration, docs, examples, tests, and CI updates. Use when adding any flet_* package backed by an external pub.dev package.
Use when adding or changing deprecations for Python controls/APIs in sdk/python/packages/, including V.deprecated fields, deprecated decorators, version lifecycle, and docs admonitions/labels.
Use when asked to prepare new Flet release by bumping versions and author release notes.
Use when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop, browser, and computer-use verification workflows.
Use when writing or reviewing Flet documentation, including Python docstrings (Google style, reST roles, admonitions), Markdown docs (cross-references, images, code examples), and sidebar navigation.
Use when asked to add, revise, or review a changelog or release-notes entry in this repo. Inspect the existing changelog section style and the relevant PR, issue, and commit context first, then write a focused entry in the correct release section without overstating docs, tests, or chores unless they are the primary user-facing change.
| name | fix-members-short-description |
| description | Use when asked to fix short descriptions of Python type members. |
When Flet documentation is generated from docstrings the first sentence of a member docstring is used as a short description, for example:
@dataclass
class MyControl:
property_a: str
"""
Short description of a property.
Full description.
Another line of full description.
"""
Here "Short description of a property." will be used as a short description.
However, when a sentence is broken into multiple lines the lines must be "concatenated" with \, for example:
@dataclass
class MyControl:
property_a: str
"""
Short description of a property which could \
take multiple lines.
Full description.
Another line of full description.
"""
Your goal is to go through all members (properties, methods, etc.) of all types (classes, enums) in input file or directory and ensure the first sentence in their docstrings is broken into multiple lines correctly with \ symbol.
Apply the fix regardless of whether the first sentence starts on the same line as the opening """ or on a following line.
Ensure every docstring line is at most 88 characters long (including any trailing \). If a line cannot be wrapped without breaking a single unbreakable token (e.g., a long URL or Windows registry path like HKEY_LOCAL_MACHINE\\...), add # noqa: E501 to the docstring closing """ line instead of the long line.