monomind 1.10.0 → 1.10.1

package/.claude/skills/mastermind/project-workspace.md

@@ -1,244 +0,0 @@
----
-name: mastermind-project-workspace
-description: Mastermind project-workspace — configure a project-level workspace (not an execution workspace). Manages source type, visibility, repo URL/ref, branch, cwd, setup/cleanup commands, remote provider, remote workspace ref, runtime config JSON, and shared workspace key. Mirrors ProjectWorkspaceDetail.tsx.
-type: domain-skill
-default_mode: confirm
----
-
-# Mastermind Project Workspace
-
-This skill is invoked by `mastermind:project-workspace` or directly via `/mastermind:project-workspace`.
-
----
-
-## Inputs
-
-- `brain_context`: BRAIN CONTEXT block (injected by command, or loaded below if standalone)
-- `org_name`: org the project belongs to (required)
-- `project_id`: project id (required)
-- `workspace_id`: workspace id within the project (required)
-- `action`: show | config | runtime | provision | teardown
-- `name`: display name for workspace (for config)
-- `source_type`: local_path | non_git_path | git_repo | remote_managed (for config)
-- `visibility`: default | advanced (for config)
-- `cwd`: absolute local path (for config; required if source_type is local_path/non_git_path)
-- `repo_url`: remote repository URL (for config)
-- `repo_ref`: git ref/commit (for config)
-- `default_ref`: default branch name (for config)
-- `setup_command`: command to run after workspace creation (for config)
-- `cleanup_command`: command to run before workspace teardown (for config)
-- `remote_provider`: remote provider identifier (for config; use with remote_managed)
-- `remote_workspace_ref`: remote workspace reference ID (for config; use with remote_managed)
-- `shared_workspace_key`: key to share this workspace across agents (for config)
-- `runtime_config`: JSON string with workspaceRuntime config overrides (for runtime)
-- `caller`: command | master
-
----
-
-## Source Types
-
-| Type | Label | Required fields |
-|------|-------|----------------|
-| `local_path` | Local git checkout | `cwd` (absolute path) |
-| `non_git_path` | Local non-git path | `cwd` (absolute path) |
-| `git_repo` | Remote git repo | `repo_url` |
-| `remote_managed` | Remote-managed workspace | `remote_workspace_ref` or `repo_url` |
-
-## Visibility
-
-| Value | Description |
-|-------|-------------|
-| `default` | Shown to all agents in the project |
-| `advanced` | Hidden by default; shown only when explicitly selected |
-
----
-
-## Step 0 — Brain Load (standalone only)
-
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
-
----
-
-## Step 1 — Load Workspace
-
-```bash
-orgFile=".monomind/orgs/${org_name}.json"
-[ ! -f "$orgFile" ] && { echo "ERROR: Org '${org_name}' not found."; exit 1; }
-
-projectsFile=".monomind/orgs/${org_name}-projects.json"
-[ ! -f "$projectsFile" ] && { echo "ERROR: No projects file for org '${org_name}'."; exit 1; }
-
-# Find project
-projDef=$(jq -r --arg pid "$project_id" '.projects[] | select(.id == $pid or .name == $pid)' "$projectsFile")
-[ -z "$projDef" ] && { echo "ERROR: Project '$project_id' not found."; exit 1; }
-
-# Load project workspaces file
-pwsFile=".monomind/orgs/${org_name}-project-workspaces.json"
-[ ! -f "$pwsFile" ] && echo '{"workspaces":[]}' > "$pwsFile"
-
-wsDef=$(jq -r --arg wid "$workspace_id" --arg pid "$project_id" \
-  '.workspaces[] | select(.id == $wid and (.project_id == $pid or .projectId == $pid))' \
-  "$pwsFile")
-```
-
----
-
-## Step 2 — Execute Action
-
-### show (default)
-
-```bash
-echo "PROJECT WORKSPACE — $workspace_id @ $project_id ($org_name)"
-echo "────────────────────────────────────────────────────────"
-
-if [ -z "$wsDef" ]; then
-  echo "  Workspace '$workspace_id' not found in project '$project_id'."
-  echo "  List workspaces: /mastermind:workspaces --org $org_name"
-  exit 0
-fi
-
-echo "$wsDef" | jq -r '
-  "  ID:                \(.id)",
-  "  Name:              \(.name // "(unnamed)")",
-  "  Source type:       \(.sourceType // .source_type // "local_path")",
-  "  Visibility:        \(.visibility // "default")",
-  "  CWD:               \(.cwd // "(none)")",
-  "  Repo URL:          \(.repoUrl // .repo_url // "(none)")",
-  "  Repo ref:          \(.repoRef // .repo_ref // "(default)")",
-  "  Default ref:       \(.defaultRef // .default_ref // "(default branch)")",
-  "  Setup command:     \(.setupCommand // .setup_command // "(none)")",
-  "  Cleanup command:   \(.cleanupCommand // .cleanup_command // "(none)")",
-  "  Remote provider:   \(.remoteProvider // .remote_provider // "(none)")",
-  "  Remote ws ref:     \(.remoteWorkspaceRef // .remote_workspace_ref // "(none)")",
-  "  Shared key:        \(.sharedWorkspaceKey // .shared_workspace_key // "(none)")"
-'
-
-rtConfig=$(echo "$wsDef" | jq -r '.runtimeConfig.workspaceRuntime // null')
-echo ""
-echo "RUNTIME CONFIG: $([ "$rtConfig" = "null" ] && echo '(none)' || echo "$rtConfig" | jq -c .)"
-```
-
-### config
-
-```bash
-if [ -z "$wsDef" ]; then
-  echo "ERROR: Workspace '$workspace_id' not found."
-  exit 1
-fi
-
-ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
-tmp="${pwsFile}.tmp"
-jq \
-  --arg wid "$workspace_id" \
-  --arg pid "$project_id" \
-  --arg name "${name:-}" \
-  --arg st "${source_type:-}" \
-  --arg vis "${visibility:-}" \
-  --arg cwd_ "${cwd:-}" \
-  --arg repoUrl "${repo_url:-}" \
-  --arg repoRef "${repo_ref:-}" \
-  --arg defaultRef "${default_ref:-}" \
-  --arg setupCmd "${setup_command:-}" \
-  --arg cleanupCmd "${cleanup_command:-}" \
-  --arg remoteProvider "${remote_provider:-}" \
-  --arg remoteRef "${remote_workspace_ref:-}" \
-  --arg sharedKey "${shared_workspace_key:-}" \
-  --arg ts "$ts" \
-  '.workspaces = [.workspaces[] | if (.id == $wid and (.project_id == $pid or .projectId == $pid)) then
-    (if $name != "" then .name = $name else . end) |
-    (if $st != "" then .sourceType = $st else . end) |
-    (if $vis != "" then .visibility = $vis else . end) |
-    (if $cwd_ != "" then .cwd = $cwd_ else . end) |
-    (if $repoUrl != "" then .repoUrl = $repoUrl else . end) |
-    (if $repoRef != "" then .repoRef = $repoRef else . end) |
-    (if $defaultRef != "" then .defaultRef = $defaultRef else . end) |
-    (if $setupCmd != "" then .setupCommand = $setupCmd else . end) |
-    (if $cleanupCmd != "" then .cleanupCommand = $cleanupCmd else . end) |
-    (if $remoteProvider != "" then .remoteProvider = $remoteProvider else . end) |
-    (if $remoteRef != "" then .remoteWorkspaceRef = $remoteRef else . end) |
-    (if $sharedKey != "" then .sharedWorkspaceKey = $sharedKey else . end) |
-    .updatedAt = $ts
-  else . end]' \
-  "$pwsFile" > "$tmp" && mv "$tmp" "$pwsFile"
-
-echo "Project workspace '$workspace_id' config updated."
-```
-
-### runtime
-
-```bash
-[ -z "$runtime_config" ] && { echo "ERROR: --runtime-config (JSON string) required."; exit 1; }
-
-# Validate JSON
-parsed=$(echo "$runtime_config" | python3 -c "import json,sys; d=json.load(sys.stdin); print(json.dumps(d))" 2>&1) || {
-  echo "ERROR: --runtime-config must be valid JSON: $parsed"
-  exit 1
-}
-
-ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
-tmp="${pwsFile}.tmp"
-jq --arg wid "$workspace_id" --arg pid "$project_id" --argjson rt "$parsed" --arg ts "$ts" \
-  '.workspaces = [.workspaces[] | if (.id == $wid and (.project_id == $pid or .projectId == $pid)) then
-    .runtimeConfig = {"workspaceRuntime": $rt} | .updatedAt = $ts
-  else . end]' \
-  "$pwsFile" > "$tmp" && mv "$tmp" "$pwsFile"
-
-echo "Runtime config updated for workspace '$workspace_id'."
-echo "  Keys: $(echo "$parsed" | python3 -c "import json,sys; d=json.load(sys.stdin); print(', '.join(d.keys()))")"
-```
-
-### provision
-
-```bash
-setupCmd=$(echo "$wsDef" | jq -r '.setupCommand // .setup_command // ""')
-wsPath=$(echo "$wsDef" | jq -r '.cwd // ""')
-
-echo "PROVISION — $workspace_id"
-echo "────────────────────────────────────────────────────────"
-if [ -z "$setupCmd" ]; then
-  echo "  No setup command configured."
-  echo "  Set one: --action config --setup-command 'npm install'"
-else
-  echo "  Command: $setupCmd"
-  echo "  CWD:     ${wsPath:-(none)}"
-  if [ -d "$wsPath" ] && [ -n "$setupCmd" ]; then
-    echo "  Executing…"
-    (cd "$wsPath" && eval "$setupCmd") && echo "  Provision complete." || echo "  Provision command exited with error."
-  fi
-fi
-```
-
-### teardown
-
-```bash
-cleanupCmd=$(echo "$wsDef" | jq -r '.cleanupCommand // .cleanup_command // ""')
-wsPath=$(echo "$wsDef" | jq -r '.cwd // ""')
-
-echo "TEARDOWN — $workspace_id"
-echo "────────────────────────────────────────────────────────"
-if [ -z "$cleanupCmd" ]; then
-  echo "  No cleanup command configured."
-else
-  echo "  Command: $cleanupCmd"
-  [ -d "$wsPath" ] && (cd "$wsPath" && eval "$cleanupCmd") && echo "  Teardown complete." || echo "  No path or teardown error."
-fi
-```
-
----
-
-## Step 3 — Return Output
-
-```yaml
-domain: ops
-status: complete
-action: <action>
-org: <org_name>
-project_id: <project_id>
-workspace_id: <workspace_id>
-```
-
----
-
-## Step 4 — Brain Write (standalone only)
-
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.

package/.claude/skills/mastermind/projects.md

@@ -1,164 +0,0 @@
----
-name: mastermind-projects
-description: Mastermind projects — create and manage scoped project workspaces within an org. Group tasks under named projects, assign agents to projects, and track project-level status.
-type: domain-skill
-default_mode: confirm
----
-
-# Mastermind Projects
-
-This skill is invoked by `mastermind:projects` or directly via `/mastermind:projects`.
-
----
-
-## Inputs
-
-- `brain_context`: BRAIN CONTEXT block
-- `org_name`: org to manage projects for
-- `action`: list | add | archive | assign | status
-- `project_name`: display name (for add)
-- `project_id`: slug (for archive/assign/status)
-- `agent_id`: role id to assign as project lead
-- `description`: project description
-- `caller`: command | master
-
----
-
-## Step 0 — Brain Load (standalone only)
-
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
-
----
-
-## Step 1 — Load Projects State
-
-Projects are stored in `.monomind/orgs/<org_name>-projects.json`:
-
-```bash
-projectsFile=".monomind/orgs/${org_name}-projects.json"
-[ ! -f "$projectsFile" ] && echo '{"projects":[]}' > "$projectsFile"
-```
-
----
-
-## Step 2 — Execute Action
-
-### list (default)
-
-```bash
-jq -r '
-  .projects[] |
-  "[\(.id)] \(.name)  lead=\(.lead_agent // "unassigned")  status=\(.status // "active")  tasks=\(.task_count // 0)\n  \(.description // "")"
-' "$projectsFile" 2>/dev/null || echo "No projects yet."
-```
-
-Render as:
-```
-PROJECTS — org: <org_name>
-──────────────────────────────────────────────────────
-[homepage-redesign] Homepage Redesign
-  Lead: content-writer  |  Status: active  |  Tasks: 7
-  A full redesign of the company homepage with new copy and visuals.
-
-[q2-seo-push] Q2 SEO Push
-  Lead: seo-specialist  |  Status: active  |  Tasks: 12
-  Target 10 high-volume keywords for Q2.
-```
-
-### add
-
-```bash
-project_id=$(echo "$project_name" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | tr -s '-')
-tmp="${projectsFile}.tmp"
-jq --arg id "$project_id" \
-   --arg name "$project_name" \
-   --arg desc "${description:-}" \
-   --arg lead "${agent_id:-}" \
-   '.projects += [{"id":$id,"name":$name,"description":$desc,"lead_agent":($lead|if .=="" then null else . end),
-     "status":"active","task_count":0,"created_at":(now|todate)}]' \
-   "$projectsFile" > "$tmp" && mv "$tmp" "$projectsFile"
-echo "Project created: $project_id"
-```
-
-Emit `org:project:created` event to dashboard.
-
-### assign
-
-Set the lead agent for a project:
-
-```bash
-tmp="${projectsFile}.tmp"
-jq --arg id "$project_id" --arg agent "$agent_id" \
-   '.projects = [.projects[] | if .id == $id then .lead_agent = $agent | .updated_at = (now|todate) else . end]' \
-   "$projectsFile" > "$tmp" && mv "$tmp" "$projectsFile"
-echo "Assigned $agent_id as lead for project $project_id"
-```
-
-### archive
-
-```bash
-tmp="${projectsFile}.tmp"
-jq --arg id "$project_id" \
-   '.projects = [.projects[] | if .id == $id then .status = "archived" | .archived_at = (now|todate) else . end]' \
-   "$projectsFile" > "$tmp" && mv "$tmp" "$projectsFile"
-echo "Project $project_id archived."
-```
-
-### status
-
-Show project summary with linked tasks from the board:
-
-```bash
-project=$(jq --arg id "$project_id" '.projects[] | select(.id == $id)' "$projectsFile")
-echo "$project" | jq .
-
-# If board exists, count tasks tagged with this project
-orgFile=".monomind/orgs/${org_name}.json"
-board_id=$(jq -r '.board_id // empty' "$orgFile")
-if [ -n "$board_id" ]; then
-  todo_col=$(jq -r '.todo_col_id // empty' "$orgFile")
-  doing_col=$(jq -r '.doing_col_id // empty' "$orgFile")
-  done_col=$(jq -r '.done_col_id // empty' "$orgFile")
-  echo "Tasks on board tagged project:$project_id:"
-  for col in "$todo_col" "$doing_col" "$done_col"; do
-    monotask card list $board_id --col $col --json 2>/dev/null | \
-      jq -r --arg p "project:$project_id" '[.[] | select((.labels // []) | index($p))] | length' 2>/dev/null
-  done
-fi
-```
-
----
-
-## Using Projects in Task Management
-
-When creating tasks with `/mastermind:tasks`, tag them to a project:
-
-```bash
-monotask card label add $board_id $CARD_ID "project:<project_id>"
-```
-
-When running org agents, include the project context in task prompts:
-
-```
-This task belongs to project "<project_name>": <description>
-Report your output tagged with project_id: <project_id>
-```
-
----
-
-## Step 3 — Return Output
-
-```yaml
-domain: ops
-status: complete
-action: <action>
-org: <org_name>
-project_id: <project_id if applicable>
-projects_file: .monomind/orgs/<org_name>-projects.json
-```
-
----
-
-## Step 4 — Brain Write (standalone only)
-
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.

package/.claude/skills/mastermind/references/copywriting-frameworks.md

@@ -1,181 +0,0 @@
-# Copywriting Frameworks Reference
-
-Headline formulas, page structure templates, CTA patterns, and writing principles for marketing pages. Use when writing or reviewing landing pages, homepages, pricing pages, feature pages, or any conversion-focused surface.
-
----
-
-## Writing Principles
-
-### The Hierarchy
-1. **Clarity over cleverness** — If you have to choose, choose clear
-2. **Benefits over features** — Features: what it does. Benefits: what that means for the customer
-3. **Specificity over vagueness** — "Cut weekly reporting from 4 hours to 15 minutes" beats "Save time on your workflow"
-4. **Customer language over company language** — Mirror words from reviews, interviews, support tickets
-5. **Active over passive** — "We generate reports" not "Reports are generated"
-6. **Confident over qualified** — Remove "almost", "very", "really", "quite"
-7. **One idea per section** — Each section advances one argument; build a logical flow down the page
-
-### Quick Quality Check
-- Jargon that could confuse an outsider?
-- Sentences trying to do too much?
-- Passive voice constructions?
-- Exclamation points? (remove them)
-- Marketing buzzwords without substance? (streamline, optimize, innovative, leverage)
-- "We/our" dominating over "you/your"?
-
----
-
-## Headline Formulas
-
-### Outcome-Focused
-- `{Achieve outcome} without {pain point}` → "Understand how users experience your site without drowning in numbers"
-- `{Achieve outcome} by {how product makes it possible}` → "Generate more leads by seeing which companies visit your site"
-- `Turn {input} into {outcome}` → "Turn your hard-earned sales into repeat customers"
-- `[Achieve outcome] in [timeframe]` → "Get your tax refund in 10 days"
-
-### Problem-Focused
-- `Never {unpleasant event} again` → "Never miss a sales opportunity again"
-- `{Question highlighting the main pain point}` → "Hate returning stuff to Amazon?"
-- `Stop [pain]. Start [pleasure].` → "Stop chasing invoices. Start getting paid on time."
-
-### Audience-Focused
-- `{Key feature} for {target audience}` → "Advanced analytics for Shopify stores"
-- `{Key feature} for {target audience} to {outcome}` → "An online whiteboard for teams to ideate together"
-- `You don't have to {skill} to {achieve outcome}` → "You don't have to be an SEO pro to rank higher"
-
-### Differentiation-Focused
-- `The {opposite of usual} way to {achieve outcome}` → "The easiest way to turn your passion into income"
-- `The [category] that [key differentiator]` → "The CRM that updates itself"
-
-### Proof-Focused
-- `[Number] [people] use [product] to [outcome]` → "50,000 marketers use Drip to send better emails"
-- `{Key benefit of your product}` → "Sound clear in online meetings"
-
-### Additional Formulas
-- `The simple way to {outcome}` → "The simple way to track your time"
-- `Finally, {category} that {benefit}` → "Finally, accounting software that doesn't suck"
-- `{Outcome} without {common pain}` → "Build your website without writing code"
-- `What if you could {desirable outcome}?` → "What if you could close deals 30% faster?"
-- `Everything you need to {outcome}` → "Everything you need to launch your course"
-- `The {adjective} {category} built for {audience}` → "The lightweight CRM built for startups"
-- `{Action verb} your {thing} like {admirable example}` → "Market your SaaS like a Fortune 500"
-
----
-
-## Page Structure
-
-### Above the Fold
-**Headline** — Single most important message. Core value prop. Specific > generic.
-**Subheadline** — Expands headline. Adds specificity. 1-2 sentences max.
-**Primary CTA** — Action-oriented. Communicate what they get: "Start Free Trial" > "Sign Up"
-**Supporting element** — Social proof count, trust badge, or hero image
-
-### Core Section Types
-| Section | Purpose | Notes |
-|---|---|---|
-| Social Proof | Build credibility | Logos near CTA, stats, specific testimonials |
-| Problem / Pain | Show you understand | Mirror customer language, not company framing |
-| Solution / Benefits | Connect to outcomes | 3-5 key benefits, not feature list |
-| How It Works | Reduce complexity | 3-4 numbered steps |
-| Objection Handling | Remove hesitation | FAQ, comparison, guarantee |
-| Final CTA | Recap + action | Restate value, repeat CTA, risk reversal |
-
-### Page Templates
-
-**Compact Landing Page** (single offer, cold traffic):
-Above fold → Social proof strip → Problem → Solution/benefits → How it works → Testimonials → CTA
-
-**Feature-Heavy Product Page**:
-Above fold → Social proof → Core value → Feature 1 (problem → feature → benefit) → Feature 2 → Feature 3 → Testimonials → FAQ → CTA
-
-**Enterprise / B2B Landing Page**:
-Above fold (value + credibility) → Problem/stakes → Solution overview → Proof (logos + case study) → How it works → Security/compliance → Testimonials → CTA + Demo request
-
-**Product Launch Page**:
-Above fold (bold announcement) → Why now → What it is → Key capabilities → Social proof from beta → Pricing → FAQ → CTA
-
----
-
-## CTA Copy Guidelines
-
-### Weak CTAs (avoid)
-Submit, Sign Up, Learn More, Click Here, Get Started, Download
-
-### Strong CTAs (use)
-- "Start Free Trial"
-- "Get [Specific Thing]" → "Get the Complete Checklist"
-- "See [Product] in Action"
-- "Create Your First [Thing]"
-- "[Action] for Free"
-
-### Formula
-`[Action Verb] + [What They Get] + [Qualifier if needed]`
-- "Start My Free Trial"
-- "See Pricing for My Team"
-- "Download the 2025 Report"
-
----
-
-## Page-Specific Copy Guidance
-
-### Homepage
-- Serve multiple audiences without being generic
-- Lead with broadest value proposition
-- Provide clear paths for different visitor intents ("I'm a designer" / "I'm an engineer")
-- Don't try to close — guide toward the right next page or CTA
-
-### Landing Page
-- Single message, single CTA — remove navigation if possible
-- Match headline exactly to the ad or email that sent traffic here
-- Complete the argument on one page; don't assume they'll come back
-
-### Pricing Page
-- Help visitors choose the right plan — answer "which is right for me?"
-- Make recommended plan obvious (badge, highlight, preselected)
-- Address the top 3-4 objections in an FAQ
-- Annual toggle with savings stated in dollars and percentage
-
-### Feature Page
-- Connect: feature → benefit → outcome (not feature → feature → feature)
-- Show use cases and examples, not just capabilities
-- Clear path to try or buy at the bottom
-
-### About Page
-- Tell the story of why this exists (founding insight or problem)
-- Connect mission to customer benefit
-- Still include a CTA — this is often a high-intent page
-
----
-
-## Writing for Trust
-
-### Social Proof Placement
-- Customer logos: above the fold (strip) and near primary CTA
-- Testimonials: specific quote + name + title + company + photo; near the claim they validate
-- Numbers: exact figures beat vague ("10,247 teams" not "thousands of teams")
-- Reviews: third-party star ratings add credibility you can't self-claim
-
-### Objection Handling
-Name the objection directly, then resolve it:
-- "What if it's not right for us?" → Money-back guarantee / free trial
-- "How long does setup take?" → "Live in 10 minutes, no IT required"
-- "Is my data secure?" → SOC 2 Type II, encryption at rest, specific certifications
-
-### Risk Reversals
-- "Free 14-day trial, no credit card required"
-- "Cancel anytime — no questions asked"
-- "30-day money-back guarantee"
-- "Free migration assistance"
-
----
-
-## Copy Anti-Patterns
-
-Never:
-- Start a CTA with "Click here" or "Learn more" — be specific about the outcome
-- Use passive voice in problem statements ("An error was encountered")
-- Hedge: "This might help", "You may want to", "Perhaps consider"
-- Restate the heading in the first sentence of body copy
-- Write "Successfully saved" when "Saved" says the same in half the words
-- Use em dashes — use commas, colons, or periods instead
-- Open with "We are pleased to announce..." or "We are excited to share..."