Sharing a particularly useful CLAUDE.md.

Spec Driven Build System Prompt - Let Claude Code / Gemini CLI design before coding, driving AI development through three phases: requirements → design → tasks.

https://t.co/St6iYirtVW

XiaomingX/systemprompt-CLAUDE

Source: https://github.com/XiaomingX/systemprompt-CLAUDE

Spec Driven Build - Claude Code / Gemini CLI System Prompt

Let AI design before coding, saying goodbye to inefficient development of “generating a bunch of garbage code with one sentence.”

What is this?

A set of Spec Driven Build system prompts for Claude Code and Gemini CLI. AI does not write code directly, but strictly goes through three phases:

Idea → Requirements Document → Architecture Design → Task List → Step-by-Step Coding

Each phase requires your review and confirmation to ensure the AI understands correctly before proceeding to the next step.

Three Steps to Get Started

1. Start Spec Mode

# Claude Code
claude -p "$(< .prompt/cli-spec-agent-system-prompt.md)"

# Gemini CLI
gemini chat --system "$(< .prompt/cli-spec-agent-system-prompt.md)"

2. Tell AI Your Idea

I want to develop a user registration and login feature

3. Review and Confirm Phase by Phase

AI will generate requirements, design, and task list in sequence. In each phase, you can supplement and modify. When satisfied, reply “Confirmed”.

Generated files are stored in the .kiro/specs/{feature_name}/ directory.

Reuse in Other Projects

# Copy prompt files to your project
mkdir -p /your/project/.prompt
cp .prompt/cli-spec-agent-system-prompt.md /your/project/.prompt/

# (Optional) Add shortcut command to ~/.zshrc
alias claude-spec='claude -p "$(< .prompt/cli-spec-agent-system-prompt.md)"'

Use Cases

• New feature development: Produce requirements and design first to avoid rework
• Team collaboration: Unified spec document aligns AI and human understanding
• Complex systems: Break down into actionable task lists, advance step by step

License

MIT