Yorby Logging
Packages PostHog's official logging best-practices guide into a skill so Claude implements consistent, high-quality logging without the developer needing deep logging expertise.
About this skill
name: yorby-logging description: Use when Packages PostHog's official logging best-practices guide into a skill so Claude implements consistent, high-quality logging without the developer needing deep logging expertise.
Yorby Logging
Built by copying PostHog's official logging best-practices guide directly into a skill definition. The creator, who describes himself as more of a product engineer than a logging expert, uses this so that any time the app needs new logs, Claude references the codified guide instead of inventing ad hoc logging patterns. A pattern he also notes mirrors Supabase's own official Postgres best-practices skill set.
What you get
- Consistent logging implementation across the codebase, sourced from an official PostHog best-practices guide, no need for the developer to be a logging expert, reusable across every new feature.
Customize your output
- Swap in the best-practices guide from your own observability provider (Sentry, Datadog, etc.) instead of PostHog.
Example output
New feature added — Claude automatically applied PostHog-recommended structured logging with proper event naming and context, matching the rest of the codebase.
Best for
Product-focused developers who want expert-level logging practices without personally researching or being opinionated about logging architecture.
Source: Yorby Founder · https://www.youtube.com/watch?v=QFDku45b_EQ Category: Development / Observability · Priority: Standard
SKILL.md preview
---
name: yorby-logging
description: Use when Packages PostHog's official logging best-practices guide into a skill so Claude implements consistent, high-quality logging without the developer needing deep logging expertise.
---
# Yorby Logging
Built by copying PostHog's official logging best-practices guide directly into a skill definition. The creator, who describes himself as more of a product engineer than a logging expert, uses this so that any time the app needs new logs, Claude references the codified guide instead of inventing ad hoc logging patterns. A pattern he also notes mirrors Supabase's own official Postgres best-practices skill set.
## What you get
- Consistent logging implementation across the codebase, sourced from an official PostHog best-practices...