moicle 2.0.0 → 2.1.0

package/README.md

@@ -16,7 +16,7 @@ A toolkit to bootstrap and accelerate project development with Claude Code throu
 
 - **16 AI Agents** - 6 developer agents + 10 utility agents
 - **4 Commands** - Wizards for bootstrap, brainstorm, documentation, and marketing
-- **20 Skills** - Auto-triggered workflows for the full SDLC (feature, bug, review, release, ops, content)
+- **21 Skills** - Auto-triggered workflows for the full SDLC (feature, bug, review, release, ops, content)
 - **8 Architecture References** - DDD + stack-specific patterns
 
 
@@ -112,9 +112,9 @@ moicle install --target codex --global
 | `/brainstorm` | Brainstorm ideas with 6 frameworks |
 | `/doc` | Scan project and generate documentation |
 
-### Skills (20)
+### Skills (21)
 
-Skills are grouped into 5 namespaces. Type `/<group>:<tab>` in Claude Code to see all skills in a group.
+Skills are grouped into 6 namespaces. Type `/<group>:<tab>` in Claude Code to see all skills in a group.
 
 **`/feature:*` — Build & Change**
 
@@ -151,15 +151,21 @@ Skills are grouped into 5 namespaces. Type `/<group>:<tab>` in Claude Code to se
 | `/research:spike` | Time-boxed prototype to learn / decide |
 | `/research:onboarding` | Get up to speed on a new codebase |
 
-**`/docs:*` — Docs & Content**
+**`/docs:*` — Project Documentation**
 
 | Skill | When to use |
 |-------|-------------|
 | `/docs:write` | Author docs manually (README / API / ARCH / CONTRIB) |
 | `/docs:sync` | Auto-generate structured docs from codebase with review loop |
-| `/docs:content` | Blog posts, social media, newsletters, SEO content |
-| `/docs:logo` | Logo + brand identity specification |
-| `/docs:video` | Video script, storyboard, production plan |
+
+**`/marketing:*` — Brand & Content** (wrapped by the `/marketing` command)
+
+| Skill | When to use |
+|-------|-------------|
+| `/marketing:content` | Multi-post content strategy (pillars, calendar, channels) |
+| `/marketing:seo-blog` | Write ONE evergreen blog post optimized for Search + AI tools |
+| `/marketing:logo` | Logo + brand identity specification |
+| `/marketing:video` | Video script, storyboard, production plan |
 
 ### Skill decision matrix
 

package/assets/architecture/_shared/severity-levels.md

@@ -0,0 +1,34 @@
+# Severity Levels — Canonical Reference
+
+Single source of truth for severity classification across review, hotfix, and incident workflows.
+
+## Code / Architecture Severity (review skills)
+
+| Level | Meaning | Examples |
+|-------|---------|----------|
+| **CRITICAL** | Architecture broken; ship-blocker | Build fails, circular imports, domain imports framework, secrets in code |
+| **HIGH** | DDD violation or correctness risk | Cross-domain import, business logic in wrong layer, no ports dir, N+1 query on main table, missing auth check |
+| **MEDIUM** | Structure issue or test gap | Anemic entity, fat controller, missing events, missing test for new code path, missing JSON tags |
+| **LOW** | Convention issue | File naming, redundant code, DTOs in wrong package, style nits |
+
+**Rule:** all CRITICAL/HIGH must be fixed before merge. MEDIUM allowed with explicit waiver. LOW = nice to fix.
+
+## Incident Severity (incident-response, hotfix)
+
+| Level | Description | First response | Examples |
+|-------|-------------|---------------|----------|
+| **P1** | Critical — complete outage / data loss / security breach | <15 min | Site down, DB corrupted, secret leak, all logins broken |
+| **P2** | High — major degradation, ≥50% users affected | <1 h | Login flow broken for one IdP, checkout fails, key endpoint 5xx |
+| **P3** | Medium — partial degradation, <50% users | <4 h | One feature broken, perf regression on a non-critical path |
+| **P4** | Low — minor issue, no significant impact | <24 h | UI glitch, typo in copy, deprecated warning |
+
+**Ambiguous P2 vs P3?** If revenue impact, security risk, or data integrity in question → P2. Otherwise P3.
+
+## Mapping between scales
+
+| Code severity | If found in PR | If found in production |
+|---------------|---------------|------------------------|
+| CRITICAL | Block merge | P1 incident |
+| HIGH | Request changes | P2 incident |
+| MEDIUM | Comment | P3 incident |
+| LOW | Comment / approve | P4 incident |

package/assets/architecture/_shared/stack-detection.md

@@ -0,0 +1,34 @@
+# Stack Detection — Canonical Reference
+
+Used by skills that need to pick the right stack-specific architecture doc and conventions.
+
+## Detection Rules
+
+Check files in this order. **First match wins.**
+
+| File / Pattern | Stack | Architecture doc |
+|----------------|-------|------------------|
+| `go.mod` | Go + Gin | `go-backend.md` |
+| `package.json` contains `"@nestjs/core"` | NestJS | `nodejs-nestjs.md` |
+| `package.json` + `vite.config.*` (no NestJS) | React + Vite | `react-frontend.md` |
+| `package.json` + `remix.config.*` | Remix | `remix-fullstack.md` |
+| `pubspec.yaml` | Flutter / Dart | `flutter-mobile.md` |
+| `composer.json` | Laravel / PHP | `laravel-backend.md` |
+| Workspace root has `pnpm-workspace.yaml` / `turbo.json` / `nx.json` | Monorepo | `monorepo.md` (plus the per-package stack above) |
+
+## Architecture Files Location (priority order)
+
+```
+.claude/architecture/{name}.md     # Project-specific — highest priority
+~/.claude/architecture/{name}.md   # Global
+```
+
+Always load **two files**:
+1. `ddd-architecture.md` — cross-stack DDD core rules
+2. The stack-specific doc from the table above
+
+## When stack is ambiguous
+
+- Multi-stack monorepo: ask the user which package / app the task targets
+- New project (no lock files yet): ask the user
+- Multiple lock files (e.g., `go.mod` + `package.json` for a hybrid service): both stacks apply; usually backend = primary

package/assets/commands/marketing.md

@@ -30,13 +30,13 @@ Let the user choose which areas to focus on:
 Which marketing areas do you want to plan?
 
 1. Logo & Brand Identity     — Design logo, colors, typography, brand guidelines
-                               Triggers skill: logo-design
+                               Triggers skill: /marketing:logo
 
 2. Video Content Strategy    — Plan video series, scripts, production, publishing
-                               Triggers skill: video-content
+                               Triggers skill: /marketing:video
 
 3. Content Writing Strategy  — Blog posts, social media, SEO, newsletter
-                               Triggers skill: content-writer
+                               Triggers skill: /marketing:content
 
 4. All of the Above          — Complete marketing plan (Recommended)
 
@@ -55,19 +55,19 @@ MARKETING PLAN WORKFLOW
 
 Phase 1: Brand Foundation
 │
-├── Execute: logo-design skill
+├── Execute: /marketing:logo skill
 │   └── Output: Brand guidelines, color palette, typography
 │
 ▼
 Phase 2: Content Strategy
 │
-├── Execute: content-writer skill
+├── Execute: /marketing:content skill
 │   └── Output: Content pillars, blog plan, social media plan, newsletter
 │
 ▼
 Phase 3: Video Content
 │
-├── Execute: video-content skill
+├── Execute: /marketing:video skill
 │   └── Output: Video series, scripts, production specs, calendar
 │
 ▼
@@ -85,7 +85,7 @@ Phase 5: Launch Plan
 
 ### Execution Notes:
 - Run skills sequentially — brand identity informs content and video decisions
-- Pass brand guidelines (colors, voice, tone) from logo-design into content-writer and video-content
+- Pass brand guidelines (colors, voice, tone) from /marketing:logo into /marketing:content and /marketing:video
 - Ensure consistency across all outputs
 
 ## Step 4: Create Unified Calendar