genkidama37

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.

genkidama37

Keybase proof

I hereby claim:

• I am genkidama37 on github.
• I am genkidama37 (https://keybase.io/genkidama37) on keybase.
• I have a public key ASC6Mi5sDzWAWSvaG4EpMDhoZxQApj8FWwmzJT03jEHGVAo

To claim this, I am signing this object:

genkidama37

Large Font Terminal Setup for Omarchy Users

Problem Statement

The default Alacritty terminal font size in Omarchy can be too small for comfortable reading during extended coding sessions. However, simply increasing the global font size breaks TUI applications like btop, lazydocker, and other monitoring tools that rely on compact layouts.

Solution Overview

This guide implements a dual-configuration approach that gives you the best of both worlds: