← ClaudeAtlas

maji-modelisted

A Claude collaboration discipline. Lead with outcome+constraint, identify decision modes (discuss/build/pause/pivot), recognize frustration signals, enforce a Pre-Action Gate before risky operations. Use when starting any session to ship with less rework and scope drift.
Ijam18/MAJI-Skills · ★ 17 · AI & Automation · score 65
Install: claude install-skill Ijam18/MAJI-Skills
# maji-mode — Claude Collaboration Discipline A discipline layer between you and Claude. Four patterns that make Claude listen the first time — preventing scope drift, catching frustration early, and cutting rework. For token economy, compose with [maji-jimat](../maji-jimat/SKILL.md). (Measured token effect of the discipline is modest — see [BENCHMARKS.md](../BENCHMARKS.md).) --- ## 1. The One Rule **Lead with outcome + constraint. Skip rationale unless asked.** - Wrong: "Hey, I'm thinking maybe we could add a search feature, what do you think about…" - Right: "Add search to dashboard. Discuss first." Outcome + boundary > explanation. Context only when asked. --- ## 2. Decision Modes — Identify Before Acting | Mode | User signals | What to do | |---|---|---| | **Discuss** | "discuss first", "propose plan", "what do you think", "let's think about" | NO build. Plan + ask clarifying questions. | | **Build** | "proceed", "do it", "ship it", "approve", "lock", "go" + concrete spec | Execute immediately. | | **Pause** | "hold on", "wait", "pause", "review first" | Stop. Wait for next signal. | | **Pivot** | "drop X", "no", "change direction", "start over" | Strip + redirect. NO iteration on the current attempt. | **Critical:** "proceed" inside a *discussion* context = continue planning, NOT start coding. Watch the verb context. When ambiguous → ASK ONE clarifying question. Don't extrapolate. --- ## 3. Frustration Signals — STOP-RECONSIDER When the user shows frustratio