dev-rules

Codify universal development rules for comments, module structure, and refactor discipline.

160|8|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/rust-dd/tako --skill dev-rules-rust-dd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-rules
Source: https://github.com/rust-dd/tako/tree/main/.claude/skills/dev-rules
Command: npx skills add https://github.com/rust-dd/tako --skill dev-rules-rust-dd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent coding styles and noisy, hard-to-parse comments slow team velocity and reduce maintainability. This guide codifies universal development rules to ensure clean, readable, and durable code across projects.

Core Features & Use Cases

  • Enforces no decorative banner comments to reduce visual noise and keep diffs readable.
  • Advises against restating code in comments; promotes concise, purpose-driven documentation.
  • Encourages succinct docstrings, sensible module structure, and minimal, durable notes that survive refactors.
  • Serves as a baseline for onboarding new contributors and maintaining consistency across languages and teams.

Quick Start

Apply these rules to every new file or major refactor by auditing comments, structure, and documentation before committing.

Frequently Asked Questions about dev-rules

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

FAQPage Schema
What are the best practices for writing clean code comments?

Clean code comments should provide concise rationale without restating code or using decorative banners. This minimizes noisy, outdated notes and ensures documentation remains readable and maintainable across refactors.

How do I maintain code quality and consistency across different programming languages?

Apply universal development rules to all source files to enforce code quality and consistency across languages. This codifies guidelines for module structure, readable formatting, and refactor discipline to ensure durable code.

When should I refactor code and what documentation should I check?

Refactor code during major updates by auditing module structure, documentation, and comment quality before committing. Ensure docstrings are succinct and remove any noisy, outdated notes that no longer match the code.

Does this coding guidelines standard work for onboarding new contributors?

Yes, these universal coding guidelines serve as a baseline for onboarding new contributors. They establish consistent commenting, module structure, and refactor discipline across the entire team to improve maintainability.

Why avoid banner comments in source files?

Banner comments should be avoided to reduce visual noise and keep diffs readable. Removing decorative banners prevents visual clutter, ensuring the source files remain clean and easy to parse for all contributors.