docs-guidelines

Guide documentation of OpenFirma code, docs, and contributor material.

106|5|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Firma-AI/openfirma --skill docs-guidelines-firma-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-guidelines
Source: https://github.com/Firma-AI/openfirma/tree/main/.skills/docs-guidelines
Command: npx skills add https://github.com/Firma-AI/openfirma --skill docs-guidelines-firma-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides comprehensive guidelines to ensure OpenFirma's documentation is clear, concise, and user-friendly, improving the developer experience and maintainability.

Core Features & Use Cases

  • Documentation Best Practices: Offers a set of standards for writing code comments, docstrings, README text, and the docs-site pages.
  • Task-Oriented: Focuses on documenting the user's perspective, emphasizing the why, constraints, and invariants.
  • Placement Model: Directs users on where to document specific types of information for the best accessibility and maintainability.
  • Update Guidance: Provides instructions for updating documentation when changes occur to major behavior, CLI, configuration, or public API.

Quick Start

Follow the guidelines in the 'docs-guidelines' skill to write clear and consistent documentation for your OpenFirma project.

Frequently Asked Questions about docs-guidelines

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

FAQPage Schema
What are the best practices for writing OpenFirma code comments and docstrings?▼

OpenFirma documentation guidelines direct you to write clear, concise code comments and docstrings that explain the why, constraints, and invariants from a task-oriented user perspective. This structured approach ensures contributor-facing material remains highly maintainable.

How do I structure OpenFirma documentation for better developer experience?▼

You structure OpenFirma documentation by following a specific placement model that directs where to document specific types of information, such as README text and docs-site pages, ensuring best accessibility and maintainability for developers. This structured approach ensures contributor-facing material remains highly maintainable.

When should I update OpenFirma documentation after changing a public API?▼

You should update OpenFirma documentation when changes occur to major behavior, CLI, configuration, or public API. The documentation guidelines provide specific instructions for updating contributor-facing material to reflect these code modifications accurately.

Does the OpenFirma documentation guide cover what to include in README text and docs-site pages?▼

Yes, the OpenFirma documentation guide covers standards for writing README text and docs-site pages. It offers a comprehensive set of standards for documenting code and contributor-facing material, ensuring all documentation is user-friendly and task-oriented.

What is the best way to document OpenFirma constraints and invariants?▼

The best way to document OpenFirma constraints and invariants is by adopting a task-oriented approach that focuses on the user's perspective. The guidelines emphasize documenting the why behind the code to improve clarity and maintainability for contributors.