development-guidelines

Creates or updates a central development guidelines document with coding conventions and review processes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yuch4/dx-selecta --skill development-guidelines-yuch4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development-guidelines
Source: https://github.com/yuch4/dx-selecta/tree/main/.claude/skills/development-guidelines
Command: npx skills add https://github.com/yuch4/dx-selecta --skill development-guidelines-yuch4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a centralized, living document for development practices to improve consistency, reduce onboarding time, and guide team decisions.

Core Features & Use Cases

  • Coding conventions: naming, formatting, and style guidelines for codebases.
  • Development process: document review workflows, release calendars, and CI/CD expectations.
  • Documentation alignment: reference architecture and repository structure to ensure consistency across docs.

Quick Start

Create or update docs/development-guidelines.md with sections for coding conventions and development process, and include measurable criteria and example rules; ensure alignment with docs/architecture.md and docs/repository-structure.md.

Frequently Asked Questions about development-guidelines

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

FAQPage Schema
How do I create a central development guidelines document for my project?

Create or update docs/development-guidelines.md to formalize coding conventions, review processes, and testing policies, ensuring alignment with architecture and repository structure docs for comprehensive project coverage.

What should be included in software project coding conventions and review processes?

Coding conventions should include naming, formatting, and style guidelines, while review processes should document review workflows, release calendars, and CI/CD expectations to guide team decisions and quality standards.

Does this development guidelines approach work with existing architecture documentation?

Yes, the development guidelines document is designed to align with existing docs/architecture.md and docs/repository-structure.md files, ensuring comprehensive coverage and consistency across all your project documentation.

Why do I need a centralized document for development practices and testing policies?

A centralized development practices document reduces onboarding time, improves consistency, and provides a living reference for team decisions by codifying coding conventions, review processes, and testing policies in one accessible location.

What's the best way to formalize development practices for a growing software team?

The best way to formalize practices is creating a living guidelines document with measurable criteria and example rules, covering coding conventions and development processes to establish clearer quality standards for your team.