인디 개발자를 위해 새로 추가된 기술을 갖춘 새로운 버전의 Claude-ground

A minimal rule system for Claude Code. Gives Claude the structural discipline it lacks by default — phase tracking, decision logging, honest pushback, debug discipline, language-specific best practices, and reusable skills. Claude Code is capable. But left to its own defaults it tends to: - Lose track of the original plan mid-implementation - Silently simplify or pivot when blocked, without asking - Agree with you when it should push back - Brute-force the same failed approach instead of stopping to think - Modify existing code without understanding it first - Skip tests or write superficial ones - Use inline styles, hardcoded colors, and generic AI aesthetics These aren't model failures — they're defaults that go unchallenged without explicit rules. rules/common/ — Always active, every project: | Rule file | What it does | |---|---| core.md | Phase management, approval gates, honest opposition, time estimates, periodic analysis | decisions.md | Decision log format and rules | git.md | Branch strategy, conventional commits, commit discipline, versioning | testing.md | When to test, naming, structure, mocks vs integration, coverage | debug.md | Two-attempt rule, structured analysis, no error masking | existing-code.md | Read before touch, follow existing patterns, separate refactoring from features | frontend.md | Theme-first, no inline styles, intentional design (UI projects only) | security.md | Input validation, auth, secrets, headers, rate limiting essentials (production) | deploy.md | Server hardening, TLS, systemd, monitoring essentials (production) | observability.md | Structured logging, health checks, external monitoring essentials (production) | oss-hygiene.md | Branch protection, tag immutability, signing, governance (open source) | rules/[language]/ — Language-specific best practices: | Language | Key rules | |---|---| | Go | Goroutine lifecycle, error wrapping, interface design, package structure, table-driven tests | | Swift | MVVM structure, async/await + actors, memory management, error handling, testable ViewModels | | TypeScript | Component granularity, API layer separation, strict types, state discipline, RTL testing | | Kotlin | Coroutine scopes, sealed UI state, Compose theming, repository pattern, coroutine testing | | Flutter | Widget granularity, state management, AppTheme, platform isolation, widget/golden tests | | Rust | Ownership patterns, thiserror/anyhow, tokio consistency, unsafe discipline, proptest | | Python | Type hints, project structure, custom exceptions, dependency management, pytest | | .NET | Constructor DI, layered architecture, async + CancellationToken, Result pattern, Testcontainers | | Spring | Constructor injection, layered architecture, exception handling, transactions, Testcontainers | commands/ — Reusable skills (slash commands): | Skill | What it does | |---|---| cg-mac-release | Build, sign, notarize, and publish a macOS app as a GitHub release with a professional DMG | cg-devplan | Generate structured development plans for Claude Code to follow | cg-store-listing | Generate ASO-optimized App Store / Google Play listing metadata | cg-security-hardening | Full security hardening guide — OWASP-aligned, multi-language, with validation tests | cg-indie-deploy | Deploy to a single VPS — Caddy/nginx, systemd, TLS, backups, rollback | cg-indie-observability | Structured logging, error tracking, uptime monitoring, alerting | cg-oss-git-hygiene | OSS repo setup — rulesets, signing, templates, Dependabot, triage | All rules use MUST / SHOULD / RECOMMENDED severity levels so Claude knows what is a hard rule vs a best practice. templates/ — Starting point for new projects: CLAUDE.md — Project context file. Tech stack, architecture, active rules.DECISIONS.md — Empty decisions log, ready to fill.phases/PHASE-01.md — First phase template. Three things get installed — they go to different places: | What | Where | Effect | |---|---|---| | Rules | ~/.claude/rules/ (global) | Active in every project, every session | | Skills | ~/.claude/commands/ (global) | Slash commands available everywhere | | Templates | Current working directory | CLAUDE.md, DECISIONS.md, phases/ for one project | Rules and skills are always global. Templates are always local to whatever directory you run the command from. npm install -g claude-ground No dependencies — uses only Node.js built-ins. claudeground # interactive — pick languages + skills claudeground install go typescript # non-interactive — specify languages directly This installs common rules + your chosen language rules to ~/.claude/rules/ , and selected skills to ~/.claude/commands/ . Done once, works everywhere. From your project directory: cd your-project claudeground init # interactive — pick languages, skills, UI claudeground init go swift # non-interactive — specific languages This asks if the project has a UI (to enable frontend rules), then creates: your-project/ ├── CLAUDE.md ← fill this in ├── DECISIONS.md ← log your first stack