library

Document Faebryk component library conventions and _F barrel generation.

9|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/mawildoer/atopile-agent-skill --skill library-mawildoer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library
Source: https://github.com/mawildoer/atopile-agent-skill/tree/main/skills/library
Command: npx skills add https://github.com/mawildoer/atopile-agent-skill --skill library-mawildoer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Faebryk's component library documentation explains how the Faebryk library is structured, how the _F.py barrel is generated, and the conventions for adding new modules.

Core Features & Use Cases

  • Centralizes reusable components, traits, and interfaces that form Faebryk's standard library.
  • Provides a generated barrel module (faebryk.library._F) for convenient imports across projects.
  • Guides conventions for adding modules, updating the generator, and ensuring consistent exports.

Quick Start

Inspect the library layout and the generator workflow, then add a new component following the documented conventions.

Frequently Asked Questions about library

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

FAQPage Schema
What is the Faebryk component library and how does its barrel module work?

The Faebryk component library centralizes reusable components, traits, and interfaces, providing a generated barrel module (faebryk.library._F) for convenient imports across projects.

How do I add a new component to the Faebryk library?

To add a new component to the Faebryk library, inspect the library layout and generator workflow, then add the module following documented frontmatter metadata and description formatting conventions.

How do I regenerate the _F barrel after updating the component library?

You regenerate the _F barrel by running the library generator, which updates the faebryk.library._F export surface to reflect newly added modules and traits across projects.

What conventions must I follow when extending Faebryk's library modules?

Extending Faebryk's library modules requires following conventions for frontmatter metadata, description formatting, documentation structure, and maintaining the library's export surface.

Does the Faebryk library generator support adding custom traits?

Yes, the Faebryk library generator supports adding custom traits by applying the documented conventions for updating the generator and maintaining the library's export surface across projects.

What is the best way to maintain the export surface across multiple Faebryk projects?

The best way to maintain the export surface is to use the generator to regenerate the _F barrel, ensuring consistent exports of reusable components and traits across all Faebryk projects.