logging
Logging Guidelines
This project follows the Wide Events pattern. Logs are optimized for querying, not writing.
Core Principle
Emit one comprehensive event per request per service containing all contextual information. Do not scatter log statements throughout your code.
Wrong mental model: Log what your code is doing Correct mental model: Log what happened to this request
Wide Event Structure
Each event should include:
More from lukevella/rallly
devmoji
Devmoji commit message emoji conventions. Use when writing git commit messages, formatting commit descriptions, or choosing the right emoji prefix for a commit. Triggers on "commit message", "git commit", "commit emoji", "devmoji".
17create-auth-skill
Skill for creating auth layers in TypeScript/JavaScript apps using Better Auth.
1email-and-password-best-practices
This skill provides guidance and enforcement rules for implementing secure email and password authentication using Better Auth.
1organization-best-practices
This skill provides guidance and enforcement rules for implementing multi-tenant organizations, teams, and role-based access control using Better Auth's organization plugin.
1two-factor-authentication-best-practices
This skill provides guidance and enforcement rules for implementing secure two-factor authentication (2FA) using Better Auth's twoFactor plugin.
1better-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
1