{"_id":"@adobe-thillai/aio-cli-plugin-ccca","name":"@adobe-thillai/aio-cli-plugin-ccca","dist-tags":{"latest":"1.0.0"},"versions":{"1.0.0":{"name":"@adobe-thillai/aio-cli-plugin-ccca","version":"1.0.0","description":"Claude Code commands, hooks, and SDLC workflow for Adobe Commerce / Magento 2 module development — phase-driven lifecycle from requirements to production-ready module.","type":"module","scripts":{"setup:project":"node scripts/setup-project.mjs","setup:project:self":"node scripts/setup-project.mjs --project .","setup:project:developer":"node scripts/setup-project.mjs --role developer","setup:project:self:developer":"node scripts/setup-project.mjs --project . --role developer"},"keywords":["claude-code","claude","anthropic","adobe-commerce","magento","magento2","commerce-development","module-development","ai-tools","sdlc","mcp"],"author":{"name":"Trajendran"},"license":"Apache-2.0","publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/OneAdobe/project-ccca.git"},"bugs":{"url":"https://github.com/OneAdobe/project-ccca/issues"},"homepage":"https://github.com/OneAdobe/project-ccca#readme","dependencies":{"fs-extra":"^11.2.0"},"engines":{"node":">=18.0.0"},"_id":"@adobe-thillai/aio-cli-plugin-ccca@1.0.0","gitHead":"42be3ebdf0fd961c2b80dbdfd84677422ebd5dfa","_nodeVersion":"22.14.0","_npmVersion":"10.9.2","dist":{"integrity":"sha512-/FUnF9zqXRONEUu2VuTYBWYobdFV7kFTh2lyUhfVlDu3MCjA5NGmVesmf2hKAJhpntvzR5OB1cp5t/ZK/DsVUA==","shasum":"f05e64e340cf2c3fbe88cc9d8854d05958b6d2c3","tarball":"https://registry.npmjs.org/@adobe-thillai/aio-cli-plugin-ccca/-/aio-cli-plugin-ccca-1.0.0.tgz","fileCount":82,"unpackedSize":427736,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEQCIFxKRGwvqeY9rTCu/wKVOqP2ALb2hMMtxch8DpUyOcNsAiAbh0aCb6xcd3c/SVCCMf7UjY15yhNZij1AIxDkKHNP1w=="}]},"_npmUser":{"name":"trajendran","email":"trajendran@adobe.com"},"directories":{},"maintainers":[{"name":"trajendran","email":"trajendran@adobe.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/aio-cli-plugin-ccca_1.0.0_1785678391949_0.8719720846649661"},"_hasShrinkwrap":false}},"time":{"created":"2026-08-02T13:46:31.852Z","1.0.0":"2026-08-02T13:46:32.116Z","modified":"2026-08-02T13:46:32.387Z"},"maintainers":[{"name":"trajendran","email":"trajendran@adobe.com"}],"description":"Claude Code commands, hooks, and SDLC workflow for Adobe Commerce / Magento 2 module development — phase-driven lifecycle from requirements to production-ready module.","homepage":"https://github.com/OneAdobe/project-ccca#readme","keywords":["claude-code","claude","anthropic","adobe-commerce","magento","magento2","commerce-development","module-development","ai-tools","sdlc","mcp"],"repository":{"type":"git","url":"git+ssh://git@github.com/OneAdobe/project-ccca.git"},"author":{"name":"Trajendran"},"bugs":{"url":"https://github.com/OneAdobe/project-ccca/issues"},"license":"Apache-2.0","readme":"# Adobe Commerce AI Toolkit\n\nClaude Code commands, hooks, and SDLC workflow for **Adobe Commerce / Magento 2** module development. Enforces a phase-gated lifecycle — requirements → structure → implementation → validation — using the **[adobe-commerce-mcp](https://github.com/OneAdobe/adobe-commerce-mcp)** execution server for all scaffolding, quality checks, and `bin/magento` operations.\n\n---\n\n## How it works\n\n**`CLAUDE.md`** is loaded by Claude Code on every conversation. It contains all domain knowledge, coding standards, SDLC phase procedures, architecture decision rules, and skill implementations in one file — 17 numbered sections (§0–§17) that slash commands reference explicitly.\n\n**`.claude/commands/`** provides eight slash commands that drive the SDLC. Each command creates TodoWrite tasks, calls the right MCP tools, validates results, and gates progression to the next phase.\n\n**`.claude/settings.json`** pre-authorizes all 24 adobe-commerce MCP tools and git commands so they run without per-call approval prompts. Three PostToolCall hooks write quality and scaffold events to an audit log. A Stop hook persists the current phase for fast status retrieval.\n\n---\n\n## Slash commands\n\n| Command | When to use |\n|---|---|\n| `/commerce-init` | First time on a project — detects environment, verifies MCP, shows phase status |\n| `/commerce-status` | Any time — phase dashboard, memory summary, next recommended command |\n| `/phase1` | Start requirements gathering — creates and fills REQUIREMENTS.md |\n| `/phase2` | Scaffold module skeleton and validate DI configuration |\n| `/phase3` | Implement all components with per-step PHPCS + DI validation |\n| `/phase4` | Run full quality suite (parallel) and commit on pass |\n| `/commerce-docs <topic>` | Live Adobe docs lookup + OOTB pattern reference |\n| `/commerce-validate-quick` | Fast PHPCS + DI check during Phase 3 development |\n| `/review-before-commit` | Pre-commit review — ObjectManager, typed exceptions, hardcoded IDs, commit format, App Builder response shape |\n\n---\n\n## SDLC phases\n\n```\n/commerce-init          verify environment and MCP connectivity\n\nPhase 0  (auto)         ensure REQUIREMENTS.md has Project Information\nPhase 1  /phase1        requirements → REQUIREMENTS.md complete\nPhase 2  /phase2        module skeleton + DI validation\nPhase 3  /phase3        implement components, validate each\nPhase 4  /phase4        quality suite (parallel) → git commit on pass\n                              └── fix → re-validate loop\n\n/commerce-status        reorient at any point\n/commerce-docs          look up any Adobe Commerce pattern\n/commerce-validate-quick  fast check during Phase 3\n```\n\n**Phase gates:** Each phase requires the previous one to be marked complete in REQUIREMENTS.md. No phase skipping. Completion markers written automatically by each phase command.\n\n---\n\n## Natural language prompts\n\nYou don't have to use slash commands — Claude Code understands goal-based prompts and routes them to the right phase automatically. The agent proposes an approach, waits for your confirmation, then executes.\n\n### Starting a new module\n\n```\nI need to build a Vendor_LoyaltyPoints module that tracks customer reward\npoints, exposes a REST API for the storefront, and has an admin grid to\nmanage point balances.\n```\n\n```\nBuild a new Adobe Commerce module for B2B quote approvals — managers need\nto approve or reject quotes above $10,000 before they can be submitted.\n```\n\n```\nWe need a module that listens to the order placement event, calculates\ncashback based on order total, and stores it in a custom table.\n```\n\n### Requirements phase\n\n```\nLet's gather requirements for the new inventory reservation module.\nStart Phase 1.\n```\n\n```\nI have a new module to plan — it syncs product data to an external PIM\nvia a REST API. Can you help me document the requirements?\n```\n\n### Scaffolding\n\n```\nRequirements are done. Generate the module skeleton for Vendor_PimSync.\n```\n\n```\nSet up the module structure — we need a custom table, a REST endpoint,\nand an observer on catalog_product_save_after.\n```\n\n### Implementation\n\n```\nImplement the data layer — Model, ResourceModel, Collection, and Repository\nfor the loyalty_points table.\n```\n\n```\nBuild the REST endpoint for /V1/loyalty/balance/:customerId. Make it\ncustomer-authenticated and return points balance and expiry date.\n```\n\n```\nI need an observer on sales_order_place_after that calculates cashback\nand queues a message to process it async. Implement it.\n```\n\n```\nAdd a plugin on Magento\\Catalog\\Model\\Product::getPrice that applies\na B2B tier discount for company customers.\n```\n\n```\nImplement the GraphQL query for fetching loyalty point balance —\nauthenticated customer context, secure resolver, ACL-protected.\n```\n\n```\nCreate the admin grid for managing loyalty point balances — sortable,\nfilterable, with export to CSV.\n```\n\n### Mid-development checks\n\n```\nRun a quick quality check on the current module.\n```\n\n```\nCheck if the DI configuration is valid after the last changes.\n```\n\n```\nPHPCS is failing — show me the errors and fix them.\n```\n\n### Validation\n\n```\nThe implementation is done. Run the full quality suite and tests.\n```\n\n```\nPhase 4 — validate everything and commit when all checks pass.\n```\n\n```\nRun just the unit tests for now.\n```\n\n### Documentation and reference\n\n```\nHow do I implement a custom GraphQL resolver with ACL in Adobe Commerce?\n```\n\n```\nShow me the OOTB pattern for declarative schema foreign keys.\n```\n\n```\nWhat's the right approach — plugin or observer — for modifying order totals\nbefore saving?\n```\n\n```\nHow does Magento handle store-scoped configuration? Show me the OOTB example.\n```\n\n### Pre-commit review\n\n```\nReview my staged changes before I commit.\n```\n\n```\nCheck the staged files for ObjectManager usage and hardcoded store IDs.\n```\n\n```\nI'm about to commit — validate the changes and suggest a commit message.\n```\n\n### Status and reorientation\n\n```\nWhere are we in the module development? What's left to do?\n```\n\n```\nI just joined this project. What phase are we in and what's been done?\n```\n\n```\nShow me the full status — all phases.\n```\n\n---\n\n## Prerequisites\n\n- [Claude Code](https://claude.ai/code) installed\n- [adobe-commerce-mcp](https://github.com/OneAdobe/adobe-commerce-mcp) built and accessible\n- Node.js ≥ 18\n- An Adobe Commerce / Magento 2 project (Docker recommended: Warden or markshust/docker-magento)\n\n---\n\n## Setup\n\n```bash\n# Install into your Commerce project\nnpm run setup:project -- --project /path/to/your/magento-project\n\n# Developer role — Phase 3 + 4 only (for developers, not architects)\nnpm run setup:project -- --project /path/to/your/magento-project --role developer\n\n# Self-setup (use this repo as the workspace)\nnpm run setup:project:self\n```\n\nAfter setup:\n\n1. Copy `.claude/mcp.json.example` → `.claude/mcp.json` and fill in paths:\n```json\n{\n  \"mcpServers\": {\n    \"adobe-commerce\": {\n      \"command\": \"node\",\n      \"args\": [\"/path/to/adobe-commerce-mcp/dist/index.js\"],\n      \"env\": { \"MAGENTO2_ROOT_DIR\": \"/path/to/magento-project\" }\n    }\n  }\n}\n```\n\n2. Open Claude Code in your project root and run `/commerce-init`.\n\n**What setup copies into your project:**\n\n| File | Behaviour |\n|---|---|\n| `.claude/commands/` | Always copied (role-filtered) |\n| `.claude/settings.json` | Copied only if not already present |\n| `.claude/mcp.json.example` | Always copied |\n| `.claude/hooks/` | Always copied |\n| `CLAUDE.md` | Copied only if not already present |\n\n---\n\n## Role-based setup\n\n| Role | Commands installed | For |\n|---|---|---|\n| `full` (default) | All 8 commands | Architects, tech leads, module owners |\n| `developer` | `/phase3`, `/phase4`, `/commerce-status`, `/commerce-docs`, `/commerce-validate-quick` | Developers implementing a pre-structured module |\n\n---\n\n## Native tool equivalents by phase\n\n| Phase | Commands used |\n|---|---|\n| Any | Environment detection from project files (§2 in CLAUDE.md) |\n| Phase 1 | `find app/code`, Read tool on module files |\n| Phase 2 | Claude writes skeleton from OOTB patterns; `bin/magento setup:di:compile`, `bin/magento module:enable`, `bin/magento setup:upgrade` |\n| Phase 3 | Claude writes components from OOTB patterns + skills; `vendor/bin/phpcs`, `bin/magento setup:di:compile` |\n| Phase 4 | `vendor/bin/phpcs`, `vendor/bin/phpstan`, `vendor/bin/phpunit`, `vendor/bin/phpmd`, `bin/magento setup:upgrade` |\n| General | `bin/magento *`, `warden *`, `magento-cloud *` |\n\nThe toolkit is MCP-free. Docker environment is detected by reading project files (`.warden/warden-env.yml`, `docker-compose.yml`). All CLI commands must be run inside the appropriate container when using Warden or markshust.\n\n---\n\n## Claude Code-native features\n\n| Feature | Detail |\n|---|---|\n| **TodoWrite sprint board** | Each phase command creates one todo per component/step — visible in real time as work progresses |\n| **Project memory** | Phase milestones (module name, environment, quality results) saved cross-conversation |\n| **Parallel Phase 4** | Four background agents run quality checks simultaneously — ~3× faster than sequential |\n| **Git phase commits** | Phase 4 auto-commits REQUIREMENTS.md with a structured commit message on full pass |\n| **Live docs** | `/commerce-docs` queries `developer.adobe.com` via WebSearch |\n| **Quality audit log** | Every PHPCS, DI compile, and quality run appended to `.claude/quality-log.jsonl` |\n\n---\n\n## License\n\nMIT\n","readmeFilename":"README.md","_rev":"1-77192f8cd150ae62b8a6a70241b5fe24"}