project-conventions

Define Python project code conventions for typing, testing, and module structure.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/deicer/codex-lb --skill project-conventions-deicer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/deicer/codex-lb/tree/main/.agents/skills/project-conventions
Command: npx skills add https://github.com/deicer/codex-lb --skill project-conventions-deicer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code quality and consistency by providing clear guidelines on typing, structure, testing, and avoiding common anti-patterns, leading to more maintainable and robust software.

Core Features & Use Cases

  • Coding Standards: Defines rules for typing, data contracts, and module structure.
  • Anti-Pattern Avoidance: Lists common pitfalls to prevent in development.
  • Testing & DI: Outlines best practices for testing and dependency injection.
  • Use Case: When starting a new feature, consult this Skill to ensure your implementation adheres to the project's established best practices for maintainability and scalability.

Quick Start

Read the conventions file in this skill directory to review the current project coding rules.

Frequently Asked Questions about project-conventions

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

FAQPage Schema
What are the best practices for Python module structure and coding standards?

Python coding standards enforce strict typing, single source of truth, fail-fast principles, and clear domain boundaries to ensure maintainable and robust module structure.

How do I implement dependency injection in Python to improve module testing?

Dependency injection best practices outline clear rules for testing and module design, ensuring components are decoupled and maintainable while facilitating scalable software development.

How do I avoid common anti-patterns when defining data contracts in Python?

Avoiding anti-patterns involves enforcing strict typing and single source of truth principles for data contracts, preventing common development pitfalls that compromise maintainability.

Does this guide cover database migration governance and testing conventions?

Yes, the conventions cover database migration governance alongside strict rules for testing, dependency injection, and typing to enforce clear domain boundaries and robust modules.

When should I consult coding conventions for new Python feature development?

Consult coding conventions when starting a new feature to ensure implementation adheres to established best practices for typing, structure, testing, and overall project maintainability.