@monoes/monomindcli 2.15.3 → 2.15.4

package/org-skills/programmatic-seo/references/playbooks.md

@@ -0,0 +1,308 @@
+# The 12 Programmatic SEO Playbooks
+
+Beyond mixing and matching data point permutations, these are the proven playbooks for programmatic SEO.
+
+## Contents
+- 1. Templates
+- 2. Curation
+- 3. Conversions
+- 4. Comparisons
+- 5. Examples
+- 6. Locations
+- 7. Personas
+- 8. Integrations
+- 9. Glossary
+- 10. Translations
+- 11. Directory
+- 12. Profiles
+- Choosing Your Playbook (Match to Your Assets, Combine Playbooks)
+
+## 1. Templates
+
+**Pattern**: "[Type] template" or "free [type] template"
+**Example searches**: "resume template", "invoice template", "pitch deck template"
+
+**What it is**: Downloadable or interactive templates users can use directly.
+
+**Why it works**:
+- High intent—people need it now
+- Shareable/linkable assets
+- Natural for product-led companies
+
+**Value requirements**:
+- Actually usable templates (not just previews)
+- Multiple variations per type
+- Quality comparable to paid options
+- Easy download/use flow
+
+**URL structure**: `/templates/[type]/` or `/templates/[category]/[type]/`
+
+---
+
+## 2. Curation
+
+**Pattern**: "best [category]" or "top [number] [things]"
+**Example searches**: "best website builders", "top 10 crm software", "best free design tools"
+
+**What it is**: Curated lists ranking or recommending options in a category.
+
+**Why it works**:
+- Comparison shoppers searching for guidance
+- High commercial intent
+- Evergreen with updates
+
+**Value requirements**:
+- Genuine evaluation criteria
+- Real testing or expertise
+- Regular updates (date visible)
+- Not just affiliate-driven rankings
+
+**URL structure**: `/best/[category]/` or `/[category]/best/`
+
+---
+
+## 3. Conversions
+
+**Pattern**: "[X] to [Y]" or "[amount] [unit] in [unit]"
+**Example searches**: "$10 USD to GBP", "100 kg to lbs", "pdf to word"
+
+**What it is**: Tools or pages that convert between formats, units, or currencies.
+
+**Why it works**:
+- Instant utility
+- Extremely high search volume
+- Repeat usage potential
+
+**Value requirements**:
+- Accurate, real-time data
+- Fast, functional tool
+- Related conversions suggested
+- Mobile-friendly interface
+
+**URL structure**: `/convert/[from]-to-[to]/` or `/[from]-to-[to]-converter/`
+
+---
+
+## 4. Comparisons
+
+**Pattern**: "[X] vs [Y]" or "[X] alternative"
+**Example searches**: "webflow vs wordpress", "notion vs coda", "figma alternatives"
+
+**What it is**: Head-to-head comparisons between products, tools, or options.
+
+**Why it works**:
+- High purchase intent
+- Clear search pattern
+- Scales with number of competitors
+
+**Value requirements**:
+- Honest, balanced analysis
+- Actual feature comparison data
+- Clear recommendation by use case
+- Updated when products change
+
+**URL structure**: `/compare/[x]-vs-[y]/` or `/[x]-vs-[y]/`
+
+*See also: competitors skill for detailed frameworks*
+
+---
+
+## 5. Examples
+
+**Pattern**: "[type] examples" or "[category] inspiration"
+**Example searches**: "saas landing page examples", "email subject line examples", "portfolio website examples"
+
+**What it is**: Galleries or collections of real-world examples for inspiration.
+
+**Why it works**:
+- Research phase traffic
+- Highly shareable
+- Natural for design/creative tools
+
+**Value requirements**:
+- Real, high-quality examples
+- Screenshots or embeds
+- Categorization/filtering
+- Analysis of why they work
+
+**URL structure**: `/examples/[type]/` or `/[type]-examples/`
+
+---
+
+## 6. Locations
+
+**Pattern**: "[service/thing] in [location]"
+**Example searches**: "coworking spaces in san diego", "dentists in austin", "best restaurants in brooklyn"
+
+**What it is**: Location-specific pages for services, businesses, or information.
+
+**Why it works**:
+- Local intent is massive
+- Scales with geography
+- Natural for marketplaces/directories
+
+**Value requirements**:
+- Actual local data (not just city name swapped)
+- Local providers/options listed
+- Location-specific insights (pricing, regulations)
+- Map integration helpful
+
+**URL structure**: `/[service]/[city]/` or `/locations/[city]/[service]/`
+
+---
+
+## 7. Personas
+
+**Pattern**: "[product] for [audience]" or "[solution] for [role/industry]"
+**Example searches**: "payroll software for agencies", "crm for real estate", "project management for freelancers"
+
+**What it is**: Tailored landing pages addressing specific audience segments.
+
+**Why it works**:
+- Speaks directly to searcher's context
+- Higher conversion than generic pages
+- Scales with personas
+
+**Value requirements**:
+- Genuine persona-specific content
+- Relevant features highlighted
+- Testimonials from that segment
+- Use cases specific to audience
+
+**URL structure**: `/for/[persona]/` or `/solutions/[industry]/`
+
+---
+
+## 8. Integrations
+
+**Pattern**: "[your product] [other product] integration" or "[product] + [product]"
+**Example searches**: "slack asana integration", "zapier airtable", "hubspot salesforce sync"
+
+**What it is**: Pages explaining how your product works with other tools.
+
+**Why it works**:
+- Captures users of other products
+- High intent (they want the solution)
+- Scales with integration ecosystem
+
+**Value requirements**:
+- Real integration details
+- Setup instructions
+- Use cases for the combination
+- Working integration (not vaporware)
+
+**URL structure**: `/integrations/[product]/` or `/connect/[product]/`
+
+---
+
+## 9. Glossary
+
+**Pattern**: "what is [term]" or "[term] definition" or "[term] meaning"
+**Example searches**: "what is pSEO", "api definition", "what does crm stand for"
+
+**What it is**: Educational definitions of industry terms and concepts.
+
+**Why it works**:
+- Top-of-funnel awareness
+- Establishes expertise
+- Natural internal linking opportunities
+
+**Value requirements**:
+- Clear, accurate definitions
+- Examples and context
+- Related terms linked
+- More depth than a dictionary
+
+**URL structure**: `/glossary/[term]/` or `/learn/[term]/`
+
+---
+
+## 10. Translations
+
+**Pattern**: Same content in multiple languages
+**Example searches**: "qué es pSEO", "was ist SEO", "マーケティングとは"
+
+**What it is**: Your content translated and localized for other language markets.
+
+**Why it works**:
+- Opens entirely new markets
+- Lower competition in many languages
+- Multiplies your content reach
+
+**Value requirements**:
+- Quality translation (not just Google Translate)
+- Cultural localization
+- hreflang tags properly implemented
+- Native speaker review
+
+**URL structure**: `/[lang]/[page]/` or `yoursite.com/es/`, `/de/`, etc.
+
+---
+
+## 11. Directory
+
+**Pattern**: "[category] tools" or "[type] software" or "[category] companies"
+**Example searches**: "ai copywriting tools", "email marketing software", "crm companies"
+
+**What it is**: Comprehensive directories listing options in a category.
+
+**Why it works**:
+- Research phase capture
+- Link building magnet
+- Natural for aggregators/reviewers
+
+**Value requirements**:
+- Comprehensive coverage
+- Useful filtering/sorting
+- Details per listing (not just names)
+- Regular updates
+
+**URL structure**: `/directory/[category]/` or `/[category]-directory/`
+
+---
+
+## 12. Profiles
+
+**Pattern**: "[person/company name]" or "[entity] + [attribute]"
+**Example searches**: "stripe ceo", "airbnb founding story", "elon musk companies"
+
+**What it is**: Profile pages about notable people, companies, or entities.
+
+**Why it works**:
+- Informational intent traffic
+- Builds topical authority
+- Natural for B2B, news, research
+
+**Value requirements**:
+- Accurate, sourced information
+- Regularly updated
+- Unique insights or aggregation
+- Not just Wikipedia rehash
+
+**URL structure**: `/people/[name]/` or `/companies/[name]/`
+
+---
+
+## Choosing Your Playbook
+
+### Match to Your Assets
+
+| If you have... | Consider... |
+|----------------|-------------|
+| Proprietary data | Stats, Directories, Profiles |
+| Product with integrations | Integrations |
+| Design/creative product | Templates, Examples |
+| Multi-segment audience | Personas |
+| Local presence | Locations |
+| Tool or utility product | Conversions |
+| Content/expertise | Glossary, Curation |
+| International potential | Translations |
+| Competitor landscape | Comparisons |
+
+### Combine Playbooks
+
+You can layer multiple playbooks:
+- **Locations + Personas**: "Marketing agencies for startups in Austin"
+- **Curation + Locations**: "Best coworking spaces in San Diego"
+- **Integrations + Personas**: "Slack for sales teams"
+- **Glossary + Translations**: Multi-language educational content

package/{dist/src/orgrt/role-skills/project-shepherd.md → org-skills/project-shepherd/SKILL.md}

@@ -1,3 +1,11 @@
+---
+name: project-shepherd
+description: "Project Shepherd role best practices. Guides a creative/production project day-to-day through its lifecycle — less about big scheduling decisions, more about unblocking people, keeping momentum, and making sure nothing silently stalls."
+tags: ["leadership","operations"]
+tools: []
+license: Apache-2.0
+source: https://github.com/monoes/monomind
+---
 # Project Shepherd — Best Practices
 
 ## Focus

package/org-skills/prompt-engineer/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/org-skills/prompt-engineer/SKILL.md

@@ -0,0 +1,131 @@
+---
+name: prompt-engineer
+description: "Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building..."
+tags: ["ai-ml"]
+tools: []
+license: MIT
+source: https://github.com/Jeffallan/claude-skills
+source_path: "skills/prompt-engineer"
+source_commit: 882ef55e377dbf9a4dbe496bb41ac6ccd0e555cf
+---
+# Prompt Engineer
+
+Expert prompt engineer specializing in designing, optimizing, and evaluating prompts that maximize LLM performance across diverse use cases.
+
+## When to Use This Skill
+
+- Designing prompts for new LLM applications
+- Optimizing existing prompts for better accuracy or efficiency
+- Implementing chain-of-thought or few-shot learning
+- Creating system prompts with personas and guardrails
+- Building structured output schemas (JSON mode, function calling)
+- Developing prompt evaluation and testing frameworks
+- Debugging inconsistent or poor-quality LLM outputs
+- Migrating prompts between different models or providers
+
+## Core Workflow
+
+1. **Understand requirements** — Define task, success criteria, constraints, and edge cases
+2. **Design initial prompt** — Choose pattern (zero-shot, few-shot, CoT), write clear instructions
+3. **Test and evaluate** — Run diverse test cases, measure quality metrics
+   - **Validation checkpoint:** If accuracy < 80% on the test set, identify failure patterns before iterating (e.g., ambiguous instructions, missing examples, edge case gaps)
+4. **Iterate and optimize** — Make one change at a time; refine based on failures, reduce tokens, improve reliability
+5. **Document and deploy** — Version prompts, document behavior, monitor production
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Prompt Patterns | `references/prompt-patterns.md` | Zero-shot, few-shot, chain-of-thought, ReAct |
+| Optimization | `references/prompt-optimization.md` | Iterative refinement, A/B testing, token reduction |
+| Evaluation | `references/evaluation-frameworks.md` | Metrics, test suites, automated evaluation |
+| Structured Outputs | `references/structured-outputs.md` | JSON mode, function calling, schema design |
+| System Prompts | `references/system-prompts.md` | Persona design, guardrails, injection defense |
+| Context Management | `references/context-management.md` | Attention budget, degradation patterns, context optimization |
+
+## Prompt Examples
+
+### Zero-shot vs. Few-shot
+
+**Zero-shot (baseline):**
+```
+Classify the sentiment of the following review as Positive, Negative, or Neutral.
+
+Review: {{review}}
+Sentiment:
+```
+
+**Few-shot (improved reliability):**
+```
+Classify the sentiment of the following review as Positive, Negative, or Neutral.
+
+Review: "The battery life is incredible, lasts all day."
+Sentiment: Positive
+
+Review: "Stopped working after two weeks. Very disappointed."
+Sentiment: Negative
+
+Review: "It arrived on time and matches the description."
+Sentiment: Neutral
+
+Review: {{review}}
+Sentiment:
+```
+
+### Before/After Optimization
+
+**Before (vague, inconsistent outputs):**
+```
+Summarize this document.
+
+{{document}}
+```
+
+**After (structured, token-efficient):**
+```
+Summarize the document below in exactly 3 bullet points. Each bullet must be one sentence and start with an action verb. Do not include opinions or information not present in the document.
+
+Document:
+{{document}}
+
+Summary:
+```
+
+## Constraints
+
+### MUST DO
+- Test prompts with diverse, realistic inputs including edge cases
+- Measure performance with quantitative metrics (accuracy, consistency)
+- Version prompts and track changes systematically
+- Document expected behavior and known limitations
+- Use few-shot examples that match target distribution
+- Validate structured outputs against schemas
+- Consider token costs and latency in design
+- Test across model versions before production deployment
+
+### MUST NOT DO
+- Deploy prompts without systematic evaluation on test cases
+- Use few-shot examples that contradict instructions
+- Ignore model-specific capabilities and limitations
+- Skip edge case testing (empty inputs, unusual formats)
+- Make multiple changes simultaneously when debugging
+- Hardcode sensitive data in prompts or examples
+- Assume prompts transfer perfectly between models
+- Neglect monitoring for prompt degradation in production
+
+## Output Templates
+
+When delivering prompt work, provide:
+1. Final prompt with clear sections (role, task, constraints, format)
+2. Test cases and evaluation results
+3. Usage instructions (temperature, max tokens, model version)
+4. Performance metrics and comparison with baselines
+5. Known limitations and edge cases
+
+## Coverage Note
+
+Reference files cover major prompting techniques (zero-shot, few-shot, CoT, ReAct, tree-of-thoughts), structured output patterns (JSON mode, function calling), context management (attention budgets, degradation mitigation, optimization), and model-specific guidance for GPT-4, Claude, and Gemini families. Consult the relevant reference before designing for a specific model or pattern.
+
+[Documentation](https://jeffallan.github.io/claude-skills/skills/data-ml/prompt-engineer/)

package/org-skills/prompt-engineer/references/context-management.md

@@ -0,0 +1,198 @@
+# Context Management
+
+<!-- Content adapted from PR #168 (context-engineer skill) by Genius-apple (https://github.com/Genius-apple). -->
+<!-- Original submission: https://github.com/Jeffallan/claude-skills/pull/168 -->
+
+---
+
+## When to Use This Reference
+
+- Designing system prompts for complex agents with large context windows
+- Debugging agents that ignore instructions or hallucinate mid-conversation
+- Optimizing token usage for cost or latency in long-running sessions
+- Structuring conversation history and RAG retrieval for maximum signal
+- Evaluating retrieval quality impact on reasoning
+
+---
+
+## The Context Budget
+
+The context window is a scarce resource — an **attention budget**. Every token consumes attention capacity. Irrelevant tokens actively degrade performance.
+
+**Key metric:** Signal-to-Noise Ratio (SNR). Higher SNR = better reasoning quality.
+
+### Context Components
+
+| Component | Purpose | Persistence |
+|-----------|---------|-------------|
+| **System Prompt** | Identity, permanent rules, output format | Static across session |
+| **Few-Shot Examples** | Demonstrations of desired behavior | Static or semi-static |
+| **Conversation History** | Short-term memory (user interactions) | Grows per turn |
+| **Retrieved Context (RAG)** | Long-term memory or external knowledge | Dynamic per query |
+
+### Structuring Context with XML Tags
+
+Use explicit delimiters to separate context types. This helps the model distinguish instructions from data:
+
+```xml
+<instructions>
+  You are an expert code reviewer...
+</instructions>
+<documents>
+  <doc id="1" source="auth.py">...</doc>
+  <doc id="2" source="models.py">...</doc>
+</documents>
+<history>
+  ...recent conversation turns...
+</history>
+<query>
+  ...current user message...
+</query>
+```
+
+### Recommended Ordering
+
+1. System Instructions (highest primacy bias)
+2. Reference Material (RAG documents)
+3. Few-Shot Examples
+4. Conversation History
+5. User Query (highest recency bias)
+
+---
+
+## Context Degradation Patterns
+
+### Lost-in-the-Middle
+
+**Symptom:** Agent ignores instructions or facts placed in the middle of long context.
+
+**Cause:** LLMs exhibit primacy bias (strong attention to the start) and recency bias (strong attention to the end). Content in the middle receives less attention.
+
+**Mitigation:** Move critical instructions to the beginning (system prompt) or repeat them near the end, just before the user query:
+
+```python
+# Vulnerable to lost-in-the-middle
+prompt = system_prompt + long_history + user_query
+
+# Mitigated: critical instructions repeated near the end
+prompt = system_prompt + long_history + instruction_reminder + user_query
+```
+
+### Context Poisoning
+
+**Symptom:** Irrelevant or conflicting information from previous turns confuses the agent, producing contradictory or stale outputs.
+
+**Mitigation:**
+- Explicitly invalidate outdated information: *"Ignore the previous constraint about X; focus only on Y."*
+- When context shifts significantly, insert a clear boundary marker
+- Summarize and replace older turns rather than accumulating verbatim history
+
+### Distraction / Dilution
+
+**Symptom:** Too much irrelevant detail reduces reasoning quality, even when the answer exists in context.
+
+**Mitigation:**
+- Filter RAG results to only highly relevant documents
+- Summarize verbose tool outputs before injecting into context
+- Remove redundant or low-information turns from history
+
+---
+
+## The Four-Bucket Approach
+
+A tiered strategy for managing context across long sessions:
+
+| Bucket | Content | Treatment |
+|--------|---------|-----------|
+| **1. Critical Instructions** | System prompt, core constraints | Always present, verbatim |
+| **2. Immediate Context** | Last 3-5 conversation turns | Verbatim, always included |
+| **3. Relevant History** | Semantically matched past context | Retrieved via search (RAG) |
+| **4. Archived History** | Everything else | Summarized or discarded |
+
+This prevents unbounded context growth while preserving the most important information. As conversation length increases, content migrates from Bucket 2 to Bucket 3 or 4.
+
+---
+
+## Optimization Strategies
+
+### Context Compaction
+
+Reduce token usage without losing semantic meaning:
+
+| Technique | Token Savings | Risk |
+|-----------|--------------|------|
+| Whitespace removal | Minor (1-5%) | Low |
+| Comment/syntax stripping | Moderate (10-20%) | Low for data, higher for code |
+| Format conversion (verbose JSON to compact YAML/CSV) | Moderate (15-30%) | Medium — verify parsability |
+| Extractive summarization of history | High (30-50%) | Medium — potential information loss |
+
+### KV-Cache Optimization
+
+Reuse computed key-value pairs for static context by keeping the prompt prefix constant across requests:
+
+- **Static Prefix:** System instructions + standard few-shot examples (unchanged between requests)
+- **Dynamic Suffix:** Conversation history + user query (changes each turn)
+
+This allows the model's KV-cache to skip recomputation of the static prefix, reducing latency and cost for APIs that support prompt caching.
+
+### Observation Masking (for Agents)
+
+Tool outputs can be disproportionately large relative to their information content:
+
+| Problem | Solution |
+|---------|----------|
+| Huge tool output (e.g., full directory listing) | Truncate to first N lines |
+| Verbose structured data | Summarize: *"Found 50 files, mainly .py"* |
+| Reading entire files | Use targeted tools (grep, symbol lookup) instead of cat |
+| Raw API responses | Extract only the fields needed for the current task |
+
+---
+
+## Periodic Refocusing
+
+In long conversations (10+ turns), instruction adherence naturally degrades. Counter this with periodic refocusing:
+
+- Every 5-10 turns, restate the current goal or constraints
+- Use explicit checkpoints: *"To confirm, we are currently working on [Goal]. Is this correct?"*
+- After major context shifts, insert a summary of the new direction
+
+---
+
+## Degradation Metrics
+
+Measure context management effectiveness with:
+
+| Metric | What It Tests | How to Measure |
+|--------|---------------|----------------|
+| **Recall Rate** | Can the agent retrieve a specific fact from mid-context? | Insert known facts at various positions, query for them |
+| **Instruction Adherence** | Does the agent follow constraints after many turns? | Test negative constraints (e.g., "no code") at turn 5, 10, 20 |
+| **SNR Impact** | Does adding context improve or degrade output quality? | Compare accuracy with/without additional context |
+
+---
+
+## Optimization Checklist
+
+- [ ] Are JSON keys descriptive but short?
+- [ ] Is the system prompt free of redundant instructions?
+- [ ] Are you sending entire files when only a function is needed?
+- [ ] Are critical instructions placed at the start and/or end of context?
+- [ ] Is conversation history summarized beyond the immediate window?
+- [ ] Are RAG results filtered for relevance before injection?
+- [ ] Is the prompt prefix stable to enable KV-cache reuse?
+
+---
+
+## When Not to Use This Reference
+
+- For prompt pattern selection (zero-shot, few-shot, CoT) — see `prompt-patterns.md`
+- For token counting and A/B testing mechanics — see `prompt-optimization.md`
+- For system prompt structure and persona design — see `system-prompts.md`
+- For structured output schemas — see `structured-outputs.md`
+
+---
+
+## Related Skills
+
+- **RAG Architect** — Vector search, chunking, and retrieval pipeline design
+- **Architecture Designer** — System-level context flow in multi-agent architectures
+- **Debugging Wizard** — Diagnosing agent behavior failures that may be context-related