skills.rest
voxel51
voxel51OFFICIAL
Explore all skills by this author →
WebsiteGitHub

fiftyone-code-style

Standardize Python code to FiftyOne's official conventions.

37|8|Updated Dec 18, 2025
Search Tags:#python#code-style#module-template#google-docstrings#lazy-imports#fiftyone#import-organization
One-click install
npx skills add https://github.com/voxel51/fiftyone-skills --skill fiftyone-code-style
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fiftyone-code-style
Source: https://github.com/voxel51/fiftyone-skills/tree/main/skills/fiftyone-code-style
Command: npx skills add https://github.com/voxel51/fiftyone-skills --skill fiftyone-code-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes Python code following FiftyOne's official conventions. Use when contributing to FiftyOne, developing plugins, or writing code that integrates with FiftyOne's codebase.

Core Features & Use Cases

  • Enforces module template structure according to FiftyOne guidelines.
  • Standardizes import organization and Google-style docstrings.
  • Supports lazy imports, guard patterns, and robust error handling.
  • Use cases include plugin development, API integration, and contributing to the core codebase.

Quick Start

Create a new Python module following the template shown in this skill's body. Include a standard header, four grouped import blocks, a public function, and a private helper, all aligned with FiftyOne's coding conventions. No code fences needed.

Frequently Asked Questions about fiftyone-code-style

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

FAQPage Schema
How do I structure Python modules for FiftyOne plugin development?▼

Structure FiftyOne modules using a standard template with a header, four grouped import blocks, public functions, and private helpers to ensure maintainable, plugin-ready contributions.

What import organization does FiftyOne require for core codebase contributions?▼

FiftyOne requires organizing imports into four grouped blocks and applying lazy imports to standardize code structure and ensure maintainable, plugin-ready contributions.

Does FiftyOne use Google-style docstrings for Python API integration?▼

Yes, FiftyOne uses Google-style docstrings to standardize Python code conventions, ensuring consistent documentation for core contributions, plugin development, and API integrations.

What's the best way to handle errors in code that integrates with FiftyOne?▼

Handle errors by applying FiftyOne's guard patterns and robust error handling conventions to ensure plugin-ready, maintainable Python code that integrates smoothly with the FiftyOne codebase.

When do I need lazy imports in FiftyOne-compliant Python code?▼

Use lazy imports when contributing to FiftyOne or developing plugins to standardize import organization, reduce module load times, and maintain consistent code structure across the codebase.

Can I use this code style guide for FiftyOne API integration projects?▼

Yes, the FiftyOne code style conventions apply to API integration, plugin development, and core contributions, enforcing standard imports, module templates, and Google-style docstrings for maintainable code.

Related Skills

Explore More Software Engineering Skills→
voxel51voxel51
37

fiftyone-dataset-import

Automate dataset imports into FiftyOne with automatic format detection.

Official
Intermediate
sunLeeesunLeee

check-python-style

Validate Python code style, type hints, and Google-style docstrings.

Community
Intermediate
voxel51voxel51
37

fiftyone-develop-plugin

Design and implement custom FiftyOne plugins with Python backends and JavaScript frontends.

Official
Advanced
hughdbrownhughdbrown

Code Like hughdbrown (Python)

Standardize Python module structure with shebangs, docstrings, and import groups.

Community
Basic