global-coding-style
Follow core coding style principles including SOLID, DRY, KISS, and YAGNI when writing code. Apply consistent naming conventions, meaningful variable names, small focused functions, automated formatting, and proper code organization. Use this skill across all programming languages and file types when writing or refactoring code. Use when creating functions, classes, modules, or components to ensure Single Responsibility Principle, when avoiding code duplication (DRY), when choosing simple over clever implementations (KISS), or when resisting premature optimization and speculative features (YAGNI). Use when establishing naming conventions, removing dead code, or maintaining consistent indentation and formatting. Apply these principles universally across backend (.ts, .js, .py, .java, .go), frontend (.tsx, .jsx, .vue), and configuration files.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Features and purpose
Follow core coding style principles including SOLID, DRY, KISS, and YAGNI when writing code. Apply consistent naming conventions, meaningful variable names, small focused functions, automated formatting, and proper code organization. Use this skill across all programming languages and file types when writing or refactoring code. Use when creating functions, classes, modules, or components to ensure Single Responsibility Principle, when avoiding code duplication (DRY), when choosing simple over clever implementations (KISS), or when resisting premature optimization and speculative features (YAGNI). Use when establishing naming conventions, removing dead code, or maintaining consistent indentation and formatting. Apply these principles universally across backend (.ts, .js, .py, .java, .go), frontend (.tsx, .jsx, .vue), and configuration files.
Quick start
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
Guides ↗Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!