Skip to content
Back to skills

Code Style Guide

ASecurity

Project coding standards and style guidelines. Always follow these conventions when writing or reviewing code.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
documentationpythongodocumentation

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill code-style-guide --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Style Guide?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Style Guide
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-code-style-guide/badge)](https://www.skillsdirectory.com/skills/david-li0406-code-style-guide)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-style-guide
description: >
  Project coding standards and style guidelines. Always follow these
  conventions when writing or reviewing code.
license: MIT
---

# Code Style Guide

Follow these conventions for all code in this project.

## Python

- Use 4 spaces for indentation
- Maximum line length: 88 characters (Black default)
- Use type hints for function signatures
- Prefer f-strings over `.format()` or `%` formatting

## Naming Conventions

- Classes: `PascalCase`
- Functions/variables: `snake_case`
- Constants: `UPPER_SNAKE_CASE`
- Private members: `_leading_underscore`

## Documentation

- All public functions must have docstrings
- Use Google-style docstrings
- Include type information in docstrings when not using type hints

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…