# Development Standards

> Org-internal engineering standards for this organization's projects. Invoke whenever scaffolding a new repo, auditing an existing one, setting up CI, or configuring tooling files like `Cargo.toml`, `rust-toolchain.toml`, `justfile`, `.editorconfig`, `.markdownlint-cli2.yaml`, `tsconfig.json`, `package.json`, `pnpm-lock.yaml`, `bunfig.toml`, `pyproject.toml`, `uv.lock`, `.python-version`, or `*.tf`. Also invoke for work involving `axum`, `utoipa`, `markdownlint-cli2`, `uv`, `ruff`, `pyright`, `pytest`, or Node package-manager setup (pnpm is the org default). Rust and Python are fully documented: Cargo workspace inheritance, MSRV pinning, `just` as task runner, `cargo-llvm-cov` coverage, hermetic-vs-live test split, Axum + utoipa OpenAPI; uv workspaces, packaged `src` layout, ruff, pyright strict, pytest live-marker tiers. TypeScript, Node.js, Bun, Terraform, Rust libraries, and Rust GraphQL are stubs — invoke anyway so the user can define the convention rather than receive an improvised one.

- Skill: `46ki75/development-standards` (Agent Skill, multi-file: 12 files)
- Install (CLI): `npx skillmds@latest add 46ki75/development-standards`
- Raw SKILL.md: https://api.skillmd.com/api/skills/46ki75/development-standards/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: MIT
- Author: 46ki75 (https://skillmd.com/u/46ki75)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/46ki75/development-standards

---


# Development Standards

Org-internal engineering standards. This file is a **router** — load the
reference that matches the task, not the whole tree.

## Routing

### Cross-cutting — `references/general/`

| File                | When to read                                                                                                                                    |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| `git-repository.md` | New repo setup, configuring `.editorconfig`, `markdownlint-cli2`, pnpm as the default package manager, baseline layout, editor recommendations. |

Commit-message conventions live in the separate `conventional-commits`
skill — defer there, not here.

### Rust — `references/rust/`

| File             | When to read                                                                                                                          |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| `general.md`     | Any Rust project: workspace inheritance, `rust-toolchain.toml`, `just` recipes, `cargo-llvm-cov`, integration test tiers.             |
| `web-openapi.md` | HTTP API with `axum` + `utoipa`: `OpenApiRouter`, Controller/UseCase/Repository layering, `ToSchema` DTOs, error mapping, Swagger UI. |
| `web-graphql.md` | _Stub — not yet documented._                                                                                                          |
| `library.md`     | _Stub — not yet documented._                                                                                                          |

### Python — `references/python/`

| File         | When to read                                                                                                                                                             |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `general.md` | Any Python project: uv workspaces, `.python-version` pinning, packaged `src` layout, ruff, pyright strict, stdlib `logging`, pytest hermetic/live tiers, `just` recipes. |

### Planned but unwritten

| Section                  | Status                       |
| ------------------------ | ---------------------------- |
| `references/typescript/` | _Stub — not yet documented._ |
| `references/nodejs/`     | _Stub — not yet documented._ |
| `references/bun/`        | _Stub — not yet documented._ |
| `references/terraform/`  | _Stub — not yet documented._ |

## Handling stubbed sections

The user invoked this skill expecting org conventions. If the matching
reference is a stub, **do not improvise an org standard** — that risks
laundering a one-off decision into apparent policy. Instead:

1. Tell the user the section is not yet documented.
2. Look for a de facto convention in the current repo or in sibling
   projects the user has open. If found, propose it and ask whether to
   adopt it as the standard.
3. If no convention exists, offer a recommendation based on general
   engineering judgment, label it clearly as a suggestion (not policy),
   and offer to write it up into the stub once the user decides.

## When NOT to invoke

- General programming or library tutorials — use language- or library-
  specific skills (`mcp-knowledge`, `ag-ui-knowledge`, `rust-toasty`,
  `conventional-commits`) or upstream docs.
- Debugging business logic.
- Reviewing changes that do not touch tooling, project layout, or the
  architectural seams covered in `references/`.