dreygur-coding-style

Enforce dreygur's coding style across Go, TypeScript, JavaScript, Rust, Python, and PHP.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/dreygur/dreygur-coding-style --skill dreygur-coding-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dreygur-coding-style
Source: https://github.com/dreygur/dreygur-coding-style/tree/main/skills/dreygur-coding-style
Command: npx skills add https://github.com/dreygur/dreygur-coding-style --skill dreygur-coding-style

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill codifies and enforces dreygur's coding style across Go, TypeScript, JavaScript, Rust, Python, and PHP, reducing stylistic drift and speeding up reviews.

Core Features & Use Cases

  • Architecture-focused guidelines for each language (Layers, naming conventions, typed errors, singleton exports, and structured logging) to keep projects consistent.
  • Provides a central entry point via SKILL.md and supports optional references for language-specific patterns, enabling deterministic tasks and on-demand information.
  • Serves as a reusable playbook for scaffolding new projects, enforcing conventions during code generation, review, and refactoring across the supported languages.

Quick Start

Generate a new Go service that follows the dreygur architecture and naming conventions.

Frequently Asked Questions about dreygur-coding-style

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

FAQPage Schema
How do I enforce consistent coding conventions across Go, TypeScript, and Python projects?

Enforce coding conventions across Go, TypeScript, and Python by applying structured architecture rules, naming conventions, and error handling guidelines during code generation and reviews. This provides a central playbook to reduce stylistic drift and keep projects consistent.

What coding style guidelines should I use for scaffolding a new Rust service?

Scaffold new Rust services using architecture-focused guidelines that define layers, typed errors, singleton exports, and structured logging. This ensures deterministic project setup and consistent naming conventions from the start.

Does this coding style approach support multiple languages or is it language-specific?

This coding style approach supports multiple languages including Go, Rust, TypeScript, JavaScript, Python, and PHP. It provides language-specific patterns and references to maintain consistent architecture across different technology stacks.

How can I standardize error handling and naming conventions during code reviews?

Standardize error handling and naming conventions during code reviews by applying codified rules for typed errors and structured logging. This serves as a reusable playbook to speed up reviews and reduce stylistic drift.

Can I use these architecture guidelines for refactoring existing JavaScript codebases?

Use these architecture guidelines for refactoring existing JavaScript codebases by enforcing structured conventions and language-specific patterns. This ensures consistent architecture and naming conventions are applied during the refactoring process.

What's the best way to maintain structured logging and typed errors across different programming languages?

Maintain structured logging and typed errors across different programming languages by applying codified architecture guidelines. This enforces consistent conventions and reduces stylistic drift across Go, TypeScript, Rust, Python, and PHP projects.