메뉴
Canonical dprint setup — the standard formatter for config and markup files (JSON, Markdown, TOML, YAML). Use when configuring or running formatting for these file types.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write standalone single-file Python scripts using PEP 723 inline metadata and uv. Use when creating a quick CLI script that needs dependencies without a full project.
Canonical Python development stack — uv, Ruff, ty, pytest, scaffolding, Litestar web, Typer scripts, and AI agents via agents-cli. Use for any Python project, library, CLI, or agent.
Cut a versioned release for fmind/dotfiles using the Go dot CLI release command (alias r). Use when shipping a new tagged version of dotfiles.
Build a presentation as one self-contained, zero-dependency HTML file (16:9, keyboard + touch nav), authored directly by the agent. Use when creating slides, a deck, or a talk from notes or a document.
Configure MCP servers for Antigravity, OpenCode, and Claude — stdio or remote transport, workspace or user scope. Use when adding, connecting, or troubleshooting an MCP server.
Bootstrap workspace agent configuration — AGENTS.md, the .agents/ layout, subagents, and skills — for Antigravity, OpenCode, and Claude. Use when initializing or onboarding a repository for agents.
| name | dprint |
| description | Canonical dprint setup — the standard formatter for config and markup files (JSON, Markdown, TOML, YAML). Use when configuring or running formatting for these file types. |
| metadata | {"author":"Médéric HURIER (Fmind)","source":"github.com/fmind/dotfiles/tree/main/skills/dprint","created":"2026-06-29T00:00:00.000Z","updated":"2026-07-06T00:00:00.000Z"} |
Canonical setup for dprint, the primary formatter for configuration and markup languages (JSON, Markdown, TOML, YAML). dprint formats only — linting lives in the language stacks (go-stack, python-stack).
dprint resolves config from the project directory upward and never auto-loads the home config, so every project needs its own resolvable dprint.json/dprint.jsonc. The home file (~/.config/dprint/dprint.jsonc, managed via chezmoi under dot_config/dprint/dprint.jsonc) is only a stored template. Seed a project one of two ways:
"extends" to a single source of truth — a local path or a commit-pinned URL, e.g. "extends": "https://raw.githubusercontent.com/fmind/dotfiles/<commit>/dot_config/dprint/dprint.jsonc". Projects inherit and can still override rules or add plugins.dprint fmt — format in place; the pre-commit hook calls the format:dprint task with {staged_files}.dprint check — verify formatting, non-zero exit on diff; wired into check as check:format.dprint add <plugin> — add and pin a new plugin version.plugins array defines precedence. Ensure generic formatting plugins do not overshadow specialized ones.