Run business analysis for a new product or for a medium/large change to an existing product. Elicit goals, map problems, propose solutions, identify risks, define scope, and update the Stage 2 artifacts. For existing products, treat the work as a delta against the canonical product analysis graph unless the human explicitly asks for a separate exploratory artifact. Use when starting new work or when change-assessment routes here.
Initialize a new project or initiative. Establish artifact strategy, classify project type, set predictability expectations, and scaffold the methodology starter structure before Stage 1 product definition begins.
Assess any code change request before implementation. Classifies scale (trivial/small/medium/large), applies a sniff test, and routes to the appropriate process depth. Use before accepting any implementation instruction.
Design and architecture review. Decompose approved business-analysis solutions into components, interfaces, ADRs, and technology choices. Use after business analysis is approved and before implementation begins.
Help the user surface methodology-level feedback about GRACE — unclear guidance, missing capability, friction in a skill, ideas for improvement, or bugs in the plugin itself. Walks the user through articulating the issue, applies a data-sensitivity check, and delivers the feedback as a Gmail draft to [email protected] (falls back to a copy-ready markdown block if Gmail tools are unavailable). Use when the user says things like "I want to flag something about GRACE", "the methodology could be better at X", "send feedback", or invokes `/grace:feedback`.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
GRACE is a methodology for disciplined AI-assisted software development. This repository is the Claude Code plugin that distributes the methodology to consuming projects: skills, slash commands, methodology rules, and the templates each stage uses.
Status: under development. GRACE is being actively designed and refined. The methodology, skill set, and plugin layout may change without notice. Anyone who picks this up before a stable release should expect breaking changes — including renamed skills, restructured rule files, and altered install behavior. There is no commitment to backwards compatibility at this stage and no obligation to early users.
/grace:* slash commands in Claude Code: project-start, project-setup, project-definition, business-analysis, change-assessment, design-review, testing-strategy, implementation, validation, operations, retirement, release-planning, risk-management, feedback, and install.GRACE.md and six rule files) that the /grace:install skill writes into a consuming project so they load into every conversation.Add the marketplace, then install:
/plugin marketplace add https://github.com/grace-method/grace-marketplace.git
/plugin install grace@grace-marketplace
After installation, run /grace:install once in any project where you want the methodology rules loaded into every conversation. The skill writes GRACE.md, the rule files, and ensures a single @.claude/GRACE.md anchor line in the project's .claude/CLAUDE.md.
/plugin marketplace update grace-marketplace
After updating, re-run /grace:install in any project where you want the latest rules.
After /grace:install:
| Path in your project | Owner | Update behavior |
|---|---|---|
.claude/GRACE.md | GRACE | Overwritten on every /grace:install. |
.claude/rules/*.md | GRACE | Overwritten on every /grace:install. |
.claude/CLAUDE.md | You | Only the anchor line is managed; everything else is yours. |
Run /grace:feedback in any project where the plugin is installed. It walks you through articulating what's unclear, missing, or working poorly, applies a quick data-sensitivity check, and drafts an email to the methodology author. You review and send. Use it for anything about GRACE itself — a confusing rule, a skill that asks the wrong questions, a missing capability, or just an idea.
MIT. See LICENSE.
The plugin source is built from the GRACE development repository. This repository contains only the built plugin contents; methodology development happens elsewhere.
npx claudepluginhub grace-method/grace-marketplace --plugin graceComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls