Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cowboy.lat/llms.txt

Use this file to discover all available pages before exploring further.

​
Introduction

This style guide ensures consistency, clarity, and professionalism across all Cowboy documentation. Follow these guidelines when contributing documentation, blog posts, or technical specifications.
Goal: Make complex blockchain technology accessible without sacrificing technical accuracy.

​
Formatting Conventions

​
Capitalization

Protocol Name
  • “Cowboy” (always capitalized, never “cowboy” except in code)
  • “the Cowboy protocol” (lowercase “protocol”)
Technical Terms
  • Actor (capitalized when referring to Cowboy Actors)
  • Runner (capitalized when referring to off-chain compute nodes)
  • Cycles and Cells (capitalized when referring to gas units)
  • CBY (all caps, the token symbol)
Standard Terms (lowercase):
  • blockchain, smart contract, validator, transaction, block
Headings
  • Sentence case: “How to deploy an actor” ✅
  • Not title case: “How To Deploy An Actor” ❌

​
Abbreviations & Numbers

  • On first use, spell out then add abbreviation in parentheses; later use the abbreviation. Example: “Proof-of-Stake (PoS)” → “PoS”.
  • Prefer concise, common abbreviations only when helpful (API, SDK, VM, CIP, PoS, DoS).
  • Numbers: spell out one to nine; use numerals for 10+ and for technical units (“3 MB”, “8 cycles”).
  • Use comma separators for large values (“1,000,000”). Write percentages without a space (“85%”).

​
Terminology Standards

​
Required Terms

Use these specific terms consistently:
Concept✅ Use This❌ Not This
Compute unitActorcontract, smart contract, agent
Off-chain workerRunneroracle, worker, node
Compute gasCyclesgas, compute units
Data gasCellsbytes, data units
Native tokenCBYCowboy token, COWBOY
Message passingsend messagecall, invoke
State storagestoragestate, database
Scheduled executiontimercron, scheduled task
Fee burningburndestroy, remove

​
Technical Term Guidelines

  • Define a term on first use or link to the glossary.
  • Keep definitions to one short sentence; avoid duplicating glossary content.

​
Code Examples

​
Code Block Formatting

Always Specify Language 
```python
def handler():
    return "Hello"
```
Not: 
```
def handler():
    return "Hello"
```
Language Tags:
  • python - Actor code
  • bash - CLI commands
  • json - Configuration files
  • yaml - Config/data
  • solidity - Comparison examples
  • rust - Core protocol code

​
Code Style (Essentials)

  • Follow PEP 8 for Python; keep functions short and purposeful.
  • Use type hints for public APIs; prefer descriptive names over abbreviations.
  • Write comments only for non-obvious rationale; avoid restating code.

​
Inline Code

Use backticks for:
  • Function names: storage.get()
  • Variables: max_cycles
  • File names: actor.py
  • Commands: cowboy deploy
  • Class names: Actor
  • Values: True, None, 0x1234
Don’t use for:
  • Emphasis (use bold)
  • Quotation marks (use “regular quotes”)

​
Callouts (Keep It Light)

  • Use callouts sparingly for key takeaways, warnings, or tips.
  • Keep to 1–2 short sentences; prefer regular text for details.

​
Images & Diagrams (Essentials)

  • Prefer SVG for diagrams; use PNG for screenshots.
  • Store diagrams under docs/assets/diagrams/; images under docs/images/.
  • Always include descriptive alt text; keep it to one sentence.

​
Common Mistakes (Quick Fixes)

  • Capitalization: write “the Cowboy protocol”; capitalize proper terms like Actor, Runner, Cycles, Cells, CBY.
  • Terminology: use Cowboy terms (Actor, Runner, Cycles, Cells) instead of generic contract/oracle/gas.
  • Voice: prefer active voice (“Validators sign the block”).
  • Links: avoid “here” links; use descriptive anchors (e.g., “See Actor VM overview”).