weidwonder

Dw System — AI skill for Claude Code

AI community

The methodology layer your AI coding stack is missing.

How to install Dw System

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

What Dw System does

The methodology layer your AI coding stack is missing. Prompting harder doesn't make AI coding reliable — engineering does.

Alternatives in AI

  • BHIL AI First Development Toolkit — A production-grade methodology repository for building AI-native applications using iterative sprints, where A 131 ★
  • Artemis — ARTEMIS turns natural-language instructions into reliable Android automation 101 ★
  • Prompting Skill — Portable skill for building reliable LLM prompts 59 ★

README

dw-system — Ship With AI, Reliably

**English** | [中文](./README_zh.md)

![Node ≥20](https://img.shields.io/badge/Node-%E2%89%A520-brightgreen) ![Zero runtime dependencies](https://img.shields.io/badge/dependencies-zero-blue) ![Claude Code · Codex](https://img.shields.io/badge/works%20with-Claude%20Code%20%C2%B7%20Codex-8A2BE2) ![Cross platform](https://img.shields.io/badge/platform-macOS%20%C2%B7%20Linux%20%C2%B7%20Windows-lightgrey)

**The methodology layer your AI coding stack is missing.** Prompting harder doesn't make AI coding reliable — engineering does. dw-system decomposes a raw requirement, layer by layer, into tasks so well-specified that **a zero-context AI agent can execute them dependably** — through Triage, top-level design, engineering specs, coding plans, coding, and tests.

This is not a whiteboard framework. It is distilled from an AI-assisted development system **proven in real production across 50–60 brownfield repositories under bi-weekly, high-velocity iteration**, condensed into eight single-purpose skills that load only when the workflow reaches their step.

The whole system follows **two governing principles**, which are also what it teaches your project: **every fact has exactly one home — everywhere else only links to it**; **normative text has a size budget — when over budget, relocate first, condense second, raise the ceiling last**.

Every project that installs it maintains one **mandatory foundation**: the `engineering-context/` **code-fact layer** (a capability registry + one map card per repo + one domain card per business domain). No tiers, no switch, regardless of project size or headcount. Initialization scaffolds it; from then on the rule is *need a fact about a module? Check the card first. No card? Read the source, then write the card on the spot* — committed with the same task branch, never deferred.

On top of that foundation, exactly two things vary:

  • Collaboration surface (asked once, stored in config) — is anyone e