# Dev Standards

> Development standards for Python projects including code style, git conventions, testing patterns, timing measurement, and validation requirements. Use when writing code, reviewing PRs, or making commits. Loaded by all implementation agents. Use when this capability is needed.

- Skill: `tomevault-io/dev-standards` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/dev-standards`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/dev-standards/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/dev-standards

---


# Development Standards

Core behavioral rules for code generation and project maintenance.

## Core Rules

1. **Do what's asked** - Nothing more, nothing less
2. **Prefer editing** - Always edit existing files over creating new ones
3. **No unnecessary files** - Never proactively create documentation unless explicitly requested
4. **No backwards compatibility assumptions** - Unless specifically instructed

## Decision Priority Order

When making implementation decisions:

| Priority | Focus | Question |
|----------|-------|----------|
| 1 | Business requirements | What problem are we solving? |
| 2 | Domain model integrity | Does this preserve our invariants? |
| 3 | Existing patterns | Consistency over perfection |
| 4 | Project conventions | Check project's CLAUDE.md |
| 5 | Team standards | As documented in configs/docs |
| 6 | Industry best practices | Only if no project precedent |

## Before Making Changes

- [ ] Searched for existing implementations?
- [ ] Will this break existing functionality?
- [ ] Following the project's patterns?
- [ ] Checked the test suite?
- [ ] Is this the minimal change needed?

## Critical Reminders

1. **Never assume dependencies exist** - Check `pyproject.toml` first
2. **Test modifications immediately** - Don't accumulate changes
3. **Read existing code patterns first** - Match the project's style
4. **Domain logic stays pure** - No framework dependencies in domain model

## Before Any Commit (Non-negotiable)

**Run `make validate-branch` before ANY commit** - No exceptions.

Additional requirements:
- Do not add claude signatures to commits and PRs
- Do not commit until confirmed by user

See `reference.md` for Git guidelines, test naming conventions, timing measurement patterns (`perf_counter()` vs `time()`), and validation requirements.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/ai-enhanced-engineer) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-14 -->