Rhay427

D.StandarDev — Development skill for Claude Code

Development community

An opinionated, portable Claude Code setup — engineering rules, five domain skills, and a tiered plugin install in one command.

How to install D.StandarDev

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Rhay427/D.StandarDev and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What D.StandarDev does

An opinionated, portable Claude Code setup — engineering rules, five domain skills, and a tiered plugin install in one command.

Alternatives in Development

README

D.StandarDev

D.StandarDev

**An opinionated, portable Claude Code setup — one script, one standard, every machine.**

[![Claude Code](https://img.shields.io/badge/Claude%20Code-setup-8A63D2)](https://claude.com/claude-code) [![Skills](https://img.shields.io/badge/skills-6-1f6feb)](#skills) [![Plugins](https://img.shields.io/badge/plugins-20-1f6feb)](#plugins) [![Tokens](https://img.shields.io/badge/agent%20tokens-%E2%88%9247%25-1baf7a)](#benchmark-default-vs-dstandardev) [![License](https://img.shields.io/badge/license-MIT-green)](LICENSE)


What this is

`D.StandarDev` is the whole Claude Code configuration I actually work with — global engineering rules, domain skills, and the plugin set — packaged so a fresh machine goes from *default Claude* to *my Claude* with a single command.

It is not a prompt collection. It is a **standard**: the same guardrails, the same review discipline, and the same tooling on every project you open.

**This is a personal setup, not a generic one.** Every skill and plugin here is one I actually use day to day, tuned to the stack I build on. It is shared as-is — if your stack differs, treat this as a starting point and swap the parts that do not fit.

git clone https://github.com/Rhay427/D.StandarDev.git
cd D.StandarDev
./install.sh

The idea

Most Claude configs are a pile of rules that make Claude do *more*: more checks, more planning, more files. That is why they feel slow and why people turn them off.

This one is built on the opposite bet — **the win is in what Claude decides not to do.**

Three rules carry almost all of it:

**1. Small tasks stay small.** Every skill opens with a gate before anything else happens:

**Fast path (most tasks)** — a copy tweak, a style change, wiring an existing prop, a small bug fix. Read only the file(s) you're touching and make the change directly. If you want to confirm a c