@monoes/monomindcli 2.16.1 → 2.16.3

package/org-skills/senior-data-scientist/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: senior-data-scientist
-description: "World-class senior data scientist skill specialising in statistical modeling, experiment design, causal inference, and predictive analytics. Covers A/B testing (sample sizing, two-proportion z-tests, Bonferroni correction), difference-in-differences, feature engineering pipelines (Scikit-learn, XGBoost), cross-validated model evaluation (AUC-ROC, AUC-PR, SHAP), and MLflow experiment tracking —..."
-tags: ["data","ai-ml"]
+description: "Use when designing A/B tests, building statistical or predictive models, feature engineering pipelines or causal inference analyses in Python. Covers sample sizing, two-proportion z-tests, Bonferroni correction, feature pipelines with pandas and scikit-learn and model evaluation for production data science."
+tags: ["data","ai-ml","python","experimentation","statistics"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/senior-developer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: senior-developer
-description: "Senior Developer role best practices. Owns full-stack feature delivery end-to-end — architecture-aware implementation, polished UI/UX, and production-grade performance, not just \"code that works.\""
-tags: ["engineering"]
+description: "Org role guidance for a senior developer: own full-stack feature delivery end to end with architecture-aware code, polished UI states and fast pages. Covers planning data flow first, matching stack idioms, accessibility, responsive testing, render-path performance and avoiding gold-plating."
+tags: ["engineering","frontend","performance","accessibility"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/senior-pm/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: senior-pm
-description: "Senior PM role best practices. Owns product direction and prioritization for a workstream — deciding what gets built and why, balancing user needs, business goals, and engineering reality."
-tags: ["leadership","operations"]
+description: "Use when an org role acts as senior product manager and must set product direction and prioritize what gets built and why for a workstream. Covers problem-first framing, RICE/ICE/MoSCoW prioritization, success metrics before build, tight PRDs with out-of-scope sections and trade-off communication."
+tags: ["leadership","operations","product","planning","strategy"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/senior-pm-playbook/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: senior-pm-playbook
-description: "Senior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring."
-tags: ["operations","leadership"]
+description: "Use when managing an enterprise software project portfolio: health scoring, quantitative risk (EMV, Monte Carlo), capacity and RAG executive reports. Includes Python scripts for project health dashboards and risk matrices, WSJF/RICE prioritization and RACI governance. Project management, not product management; for product direction see senior-pm."
+tags: ["operations","leadership","planning","communication"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/seo/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: seo
-description: "Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping."
-tags: ["marketing","frontend"]
+description: "Use when implementing SEO fixes in a site's code: crawlability, canonicals, redirects, meta tags, structured data, Core Web Vitals and internal links. Engineering-oriented checklist with page-specific, implementable recommendations. For a diagnostic audit report use seo-audit; for pages at scale use programmatic-seo."
+tags: ["marketing","frontend","seo","performance"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/seo-audit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: seo-audit
-description: "When the user wants to audit, review, or diagnose SEO issues on their site."
-tags: ["marketing","frontend"]
+description: "Use when auditing or diagnosing SEO issues on a site to produce prioritized findings on crawlability, indexation, technical, on-page and content quality. Includes a caveat that curl and web_fetch miss JS-injected schema markup. For implementing fixes use seo; for AI answer engines use ai-seo."
+tags: ["marketing","frontend","seo","audit"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/seo-specialist/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: seo-specialist
-description: "SEO Specialist role best practices. Improves organic visibility through technical SEO, content optimization, and authority building — increasingly across both traditional search and AI-driven answer engines."
-tags: ["writing","marketing"]
+description: "Use when an org role acts as SEO specialist and must grow organic visibility across search and AI answer engines through technical SEO, content and authority. Covers technical foundations, search intent, topical authority via internal linking, schema markup, Core Web Vitals and entity-first optimization."
+tags: ["writing","marketing","seo","content"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/shap-model-explainability/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: shap-model-explainability
-description: "Explain and audit machine-learning predictions with SHAP. Use for selecting SHAP explainers and maskers, computing and validating feature attributions, handling multi-output explanations, and producing local or global SHAP visualizations."
-tags: ["ai-ml","data"]
+description: "Use when explaining or auditing ML model predictions with SHAP in Python: choosing explainers and maskers, feature attributions and SHAP plots. Aligned to SHAP 0.52 and the shap.Explanation API; covers background data choice, multi-output models, additivity checks and local vs global visualizations."
+tags: ["ai-ml","data","python","evaluation","visualization"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/signup-flow-cro/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: signup-flow-cro
-description: "When the user wants to optimize signup, registration, account creation, or trial activation flows."
-tags: ["marketing","product","design"]
+description: "Use when optimizing signup, registration, account creation or trial activation flows to raise completion rates. Covers field minimization, value before commitment, social auth, step design and friction audits. For post-signup activation use onboarding-cro; for marketing pages use page-cro."
+tags: ["marketing","product","design","cro","growth"]
 tools: ["monodesign_detect"]
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/site-architecture/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: site-architecture
-description: "When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking."
-tags: ["marketing","design","frontend"]
+description: "Use when planning or restructuring a website's page hierarchy, navigation, URL structure or internal linking for SaaS, content, e-commerce or docs sites. Produces site maps, nav and URL patterns and redirect-aware restructures. Information architecture, not an SEO audit (see seo-audit) or copy (see copywriting)."
+tags: ["marketing","design","frontend","seo","ux"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/sms-marketing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: sms-marketing
-description: "When the user wants to plan, build, or optimize SMS or MMS marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS."
-tags: ["marketing"]
+description: "Use when planning or optimizing SMS or MMS marketing: welcome flows, abandoned cart texts, post-purchase, win-back, promotional or transactional sends. Covers when SMS beats email, A2P 10DLC and opt-in compliance, short code vs toll-free numbers and list economics."
+tags: ["marketing","growth","compliance"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/soc2-compliance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: soc2-compliance
-description: "Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness."
-tags: ["legal","security"]
+description: "Use when preparing a SaaS company for a SOC 2 Type I or Type II audit: Trust Service Criteria mapping, control matrices, gap analysis and evidence collection. Also covers readiness checklists, vendor management and continuous compliance. Framework playbook; for the auditor org role across SOC 2, ISO 27001 and HIPAA see compliance-auditor."
+tags: ["legal","security","compliance","audit"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/social-content/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: social-content
-description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms, or wants to do social listening and engagement triage."
-tags: ["marketing","writing"]
+description: "Use when creating, scheduling or optimizing individual posts for LinkedIn, Twitter/X, Instagram, TikTok or Facebook, or triaging social engagement. Covers platform formats, hooks, repurposing and content calendars. For overall social strategy use social-media-manager."
+tags: ["marketing","writing","social","content"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/social-media/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: social-media
-description: "Social Media role best practices. Runs platform-native social presence — content, scheduling, and community engagement — tuned to each platform's format and audience rather than a single cross-posted strategy."
-tags: ["writing","marketing"]
+description: "Use when an org role acts as social media manager and must run a platform-native presence: per-platform content, posting cadence and fast community engagement. Covers audience-based platform choice, per-platform briefs and KPIs and conversation-driving content. Role guidance; for strategy playbooks see social-media-manager."
+tags: ["writing","marketing","social","content"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/social-media-manager/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: social-media-manager
-description: "When the user wants to develop social media strategy, plan content calendars, manage community engagement, or grow their social presence across platforms. Also use when the user mentions 'social media strategy,' 'social calendar,' 'community management,' 'social media plan,' 'grow followers,' 'engagement rate,' 'social media audit,' or 'which platforms should I use.' For writing individual..."
-tags: ["marketing"]
+description: "Use when developing social media strategy: picking platforms, planning content calendars, auditing a weak presence or scaling community management. Three modes: build from scratch, audit and optimize, scale and systematize. For writing individual posts use social-content."
+tags: ["marketing","social","strategy","growth"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

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

@@ -1,7 +1,7 @@
 ---
 name: solidity-engineer
-description: "Solidity Engineer role best practices. Writes and ships EVM smart contracts — gas-efficient, security-first, and audit-ready — for token standards, upgradeable proxies, and DeFi protocols across Ethereum and L2 chains."
-tags: ["engineering","security"]
+description: "Use when an org role acts as Solidity engineer and must ship gas-efficient, audit-ready EVM contracts: tokens, upgradeable proxies and DeFi on L1 and L2s. Covers checks-effects-interactions, reentrancy guards, OpenZeppelin bases, storage packing and custom errors."
+tags: ["engineering","security","blockchain"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: spark-engineer
-description: "Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure executor memory, process .parquet files, handle data partitioning, or build..."
-tags: ["data","engineering"]
+description: "Use when writing or tuning Apache Spark jobs: PySpark DataFrame and Spark SQL transformations, RDD pipelines, partitioning, shuffle and executor memory tuning. Also covers skew handling, caching and broadcast joins, Parquet I/O and Structured Streaming for big data ETL."
+tags: ["data","engineering","python","performance"]
 tools: []
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/spec-driven-workflow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: spec-driven-workflow
-description: "Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices."
-tags: ["engineering","product"]
+description: "Use when writing a spec before code: RFC 2119 requirements, Given/When/Then acceptance criteria, edge cases, API contracts and data models. Enforces no code without an approved spec and derives tests from acceptance criteria. For lighter intent clarification alongside work, see intent-driven-development."
+tags: ["engineering","product","planning","documentation"]
 tools: ["monograph_query","monograph_suggest"]
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/springboot-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: springboot-patterns
-description: "Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work. Use when building or reviewing a Spring Boot backend — REST layer, services, data access, caching, or async work."
-tags: ["backend"]
+description: "Use when building or reviewing a Java Spring Boot backend: REST controllers, layered services, Spring Data JPA, validation, caching and async work. A catalogue of idioms with code; for end-to-end enterprise Java builds and microservices see java-architect."
+tags: ["backend","java","spring","api"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/sprint-prioritizer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: sprint-prioritizer
-description: "Sprint Prioritizer role best practices. Decides what enters the next sprint from a groomed backlog, balancing value, effort, risk, and dependencies so each sprint delivers the highest-impact work that's actually feasible."
-tags: ["product"]
+description: "Use when an org role acts as sprint prioritizer and must decide what enters the next sprint from a groomed backlog by value, effort, risk and dependencies. Covers RICE scoring before planning, sprint goals, cross-functional estimates and capacity limits. For writing stories and backlog ownership see agile-product-owner."
+tags: ["product","planning","strategy"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/sql-pro/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: sql-pro
-description: "Optimizes SQL queries, designs database schemas, and troubleshoots performance issues. Use when a user asks why their query is slow, needs help writing complex joins or aggregations, mentions database performance issues, or wants to design or migrate a schema."
-tags: ["engineering","data","backend"]
+description: "Use when a SQL query is slow or you need complex joins, CTEs, window functions or aggregations, or to design or migrate a schema. Covers EXPLAIN ANALYZE, indexing, normalization and dialect differences across PostgreSQL, MySQL and SQL Server."
+tags: ["engineering","data","backend","sql","database"]
 tools: []
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/sre/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: sre
-description: "SRE role best practices. Treat reliability as a measurable, budgeted feature — define SLOs that reflect real user experience, build observability that answers questions before they're asked, and automate away toil."
-tags: ["devops"]
+description: "Use when an org role acts as SRE and must make reliability a budgeted feature: user-facing SLOs, error-budget policy, observability and toil automation. Role guidance; for SLO definitions, runbooks and monitoring configs produced as artifacts see sre-engineer."
+tags: ["devops","reliability","observability"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: sre-engineer
-description: "Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning."
-tags: ["devops","operations"]
+description: "Use when producing SRE artifacts: SLI/SLO definitions, error budget policies, golden-signal alerts, incident runbooks, capacity models, chaos tests. Includes blameless postmortems and toil-reduction automation. For the org role persona see sre."
+tags: ["devops","operations","reliability","observability","incident"]
 tools: []
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/startup-financial-modeling/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: startup-financial-modeling
-description: "Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups. Use this skill when creating financial projections, calculating burn rate or runway, modeling fundraising scenarios, or preparing investor-ready financials for a seed or Series A raise."
-tags: ["finance"]
+description: "Use when building a 3-5 year startup financial model: cohort revenue, cost structure, cash flow, burn, runway and seed or Series A fundraising scenarios. For tracking and benchmarking operating metrics like CAC and LTV see startup-metrics-framework."
+tags: ["finance","fundraising","planning"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/startup-metrics-framework/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: startup-metrics-framework
-description: "Track, calculate, and optimize key performance metrics for SaaS, marketplace, consumer, and B2B startups from seed through Series A, including unit economics, growth efficiency, and cash management. Use this skill when defining a metrics framework, calculating CAC/LTV/burn multiple, benchmarking business health, or preparing metrics dashboards for investors or board reporting."
-tags: ["finance","product"]
+description: "Use when defining or calculating startup KPIs for SaaS, marketplace, consumer or B2B: MRR/ARR growth, CAC, LTV, burn multiple and stage benchmarks. Supports investor and board metrics dashboards. For forward-looking financial projections see startup-financial-modeling."
+tags: ["finance","product","analytics","fundraising"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/statistical-analysis/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: statistical-analysis
-description: "Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting. Use whenever a user wants to compare groups, test a hypothesis, analyze experimental or survey data, check statistical assumptions, compute required sample sizes, or write up results - even if they never name a specific test."
-tags: ["data","science","research"]
+description: "Use when analyzing research data in Python: picking and running t-tests, ANOVA, chi-square, regression or Bayesian models with APA-format reporting. Uses pingouin, statsmodels, SciPy and PyMC with effect sizes. For planning sample sizes before data collection see statistical-power."
+tags: ["data","science","research","statistics","python"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/statistical-power/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: statistical-power
-description: "Sample-size and statistical power calculations for planning studies. Use whenever someone asks \"how many subjects/samples/replicates do I need\", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration."
-tags: ["data","science","research"]
+description: "Use when planning a study's sample size: a priori power analysis, minimum detectable effect, power curves or justifying n for a grant, IRB or pre-registration. Covers closed-form and simulation-based power, effect size choice and attrition. For analyzing collected data see statistical-analysis."
+tags: ["data","science","research","statistics","experimentation"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/stride-analysis-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: stride-analysis-patterns
-description: "Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation."
-tags: ["security"]
+description: "Use when running a STRIDE threat modeling session to identify spoofing, tampering, repudiation, disclosure, DoS and privilege threats in a design. Includes a threat analysis matrix and templates for threat documentation. For mapping threats to controls see threat-mitigation-mapping."
+tags: ["security","architecture","documentation"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/stripe-integration/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: stripe-integration
-description: "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows."
-tags: ["backend","finance"]
+description: "Use when integrating Stripe payments: Checkout Sessions, Payment Intents, subscriptions, webhooks, refunds and saved payment methods. Also covers SCA, Stripe Connect marketplace flows and PCI-compliant client handling. For PCI DSS requirements generally see pci-compliance."
+tags: ["backend","finance","stripe","api"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/studio-operations/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: studio-operations
-description: "Studio Operations role best practices. Keeps the studio's operating infrastructure running — tools, pipelines, budgets, vendor/contractor logistics, and the processes that let creative teams focus on making the thing instead of fighting the environment."
-tags: ["leadership","operations"]
+description: "Use when an org role acts as studio operations lead and must keep a creative or game studio's tools, pipelines, budgets and vendor logistics running. Covers pipeline friction as backlog, milestone-tied budget burn, standardized processes and contractor terms. For scope and schedule see studio-producer."
+tags: ["leadership","operations","game-dev"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/studio-producer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: studio-producer
-description: "Studio Producer role best practices. Owns scope, schedule, and capacity for a creative/game production — the person who keeps a project moving from pitch to shippable build without burning the team out."
-tags: ["leadership","operations"]
+description: "Use when an org role acts as studio producer and must own scope, schedule and capacity for a creative or game production from pitch to shippable build. Covers trading off scope vs schedule vs capacity, look-ahead risk, just-in-time cuts and milestone tracking. For tooling and vendor ops see studio-operations."
+tags: ["leadership","operations","game-dev","planning"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/support-responder/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: support-responder
-description: "Support Responder role best practices. Handles customer support conversations — resolving issues directly where possible and escalating cleanly where not — with a tone that de-escalates rather than inflames."
-tags: ["writing","marketing"]
+description: "Use when an org role acts as support responder and must resolve customer support conversations or escalate them cleanly with a de-escalating tone. Covers acknowledging before solving, plain language over policy-speak, confirming the real problem and full-context handoffs."
+tags: ["writing","marketing","support","communication"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/swift-expert/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: swift-expert
-description: "Builds iOS/macOS/watchOS/tvOS applications, implements SwiftUI views and state management, designs protocol-oriented architectures, handles async/await concurrency, implements actors for thread safety, and debugs Swift-specific issues. Use when building iOS/macOS applications with Swift 5.9+, SwiftUI, or async/await concurrency."
-tags: ["engineering","mobile"]
+description: "Use when building iOS, macOS, watchOS or tvOS apps in Swift end to end: SwiftUI views, protocol-oriented architecture, async/await, actors and XCTest. Persona with reference files on concurrency, memory and performance. For a SwiftUI-only pattern catalogue see swiftui-patterns."
+tags: ["engineering","mobile","swift"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/swiftui-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: swiftui-patterns
-description: "SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices. Use when building or reviewing SwiftUI views, @Observable state, navigation, or render performance."
-tags: ["mobile","frontend"]
+description: "Use when building or reviewing SwiftUI views: @Observable state, property wrappers, view composition, NavigationStack and render performance. A catalogue of SwiftUI idioms; for full Swift app work including concurrency see swift-expert."
+tags: ["mobile","frontend","swift","ui"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/system-architect/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: system-architect
-description: "System Architect role best practices. Makes high-level technical and structural decisions — system boundaries, component interactions, and technology trade-offs — that other roles then implement against."
-tags: ["engineering"]
+description: "Org role guidance for a system architect: decide system boundaries, component contracts and technology trade-offs that other roles implement. Covers quality attributes first, ADRs with rejected options, right-sized scale and operational concerns up front."
+tags: ["engineering","architecture","planning"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/systematic-debugging/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: systematic-debugging
-description: "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes"
-tags: ["engineering","testing"]
+description: "Use when hitting any bug, test failure, build failure or unexpected behavior, before proposing a fix: a four-phase root-cause-first process. Iron law of no fixes without root cause investigation, then pattern analysis, hypothesis testing and implementation. Process discipline, not a stack-trace parsing toolkit (see debugging-wizard)."
+tags: ["engineering","testing","debug"]
 tools: ["monograph_query","monograph_context","monograph_impact","monograph_suggest"]
 license: MIT
 source: https://github.com/obra/superpowers

package/org-skills/task-orchestrator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: task-orchestrator
-description: "Task Orchestrator role best practices. Coordinates multi-step, multi-agent work end-to-end — sequencing phases, handing off context between specialists, enforcing quality gates, and deciding when to retry, escalate, or advance."
-tags: ["engineering"]
+description: "Use when an org role acts as task orchestrator and must run multi-agent work: sequence phases, hand off context, enforce gates, retry or escalate. Covers small verifiable tasks, explicit state tracking and capped retries."
+tags: ["engineering","coordination","agents"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/team-communications/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-communications
-description: "Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences."
-tags: ["writing","operations"]
+description: "Use when drafting internal company comms: 3P updates (Progress, Plans, Problems), newsletters, FAQ roundups, incident reports or status updates. Routes to a format reference per type and can pull real data via Slack, Gmail or Drive tools."
+tags: ["writing","operations","communication"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/team-composition-analysis/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-composition-analysis
-description: "Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A. Use this skill when planning headcount, determining which roles to hire next, setting compensation or equity ranges, designing org structure, or building a hiring budget aligned to funding milestones."
-tags: ["leadership","operations"]
+description: "Use when planning startup headcount from pre-seed to Series A: next hires, team structure by stage, comp and equity ranges and hiring budgets. For broader people leadership, culture and retention see chro-advisor."
+tags: ["leadership","operations","people","planning"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/technical-artist/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: technical-artist
-description: "Technical Artist role best practices. Bridges art and engineering — building shaders, tools, and pipeline standards that let artists work efficiently while keeping assets performant and engine-ready."
-tags: ["design"]
+description: "Use when an org role acts as technical artist and must bridge art and engineering in a game pipeline: shaders, tools and engine-ready asset standards. Covers shader cost, naming and LOD standards, texture budgets and draw-call reduction."
+tags: ["design","game-dev","performance"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/technical-writer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: technical-writer
-description: "Technical Writer role best practices. Transforms complex engineering concepts into clear, accurate developer documentation — READMEs, API references, tutorials, and conceptual guides that developers actually read and use."
-tags: ["writing","marketing"]
+description: "Org role guidance for a technical writer: turn engineering concepts into clear developer docs such as READMEs, API references, tutorials and conceptual guides. Covers tested code samples, the Divio doc types, outcome-first framing and consistent voice."
+tags: ["writing","marketing","documentation"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: terraform-engineer
-description: "Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing."
-tags: ["devops"]
+description: "Use when writing or maintaining Terraform on AWS, Azure or GCP: reusable modules, remote state and backend migration, imports and multi-env workflows. Enforces fmt, validate, tflint and a reviewed plan before apply."
+tags: ["devops","terraform","cloud"]
 tools: []
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/test-driven-development/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: test-driven-development
-description: "Use when implementing any feature or bugfix, before writing implementation code"
-tags: ["engineering","testing"]
+description: "Use when implementing any feature or bugfix, before writing implementation code: strict red-green-refactor TDD. Iron law of no production code without a failing test first, with rationalization checks. A process discipline; for test strategy, coverage and performance testing see test-master."
+tags: ["engineering","testing","coding-standards"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/obra/superpowers

package/org-skills/test-master/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: test-master
-description: "Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery;"
-tags: ["testing","engineering"]
+description: "Use when writing unit, integration or E2E tests, designing a test strategy or framework, finding coverage gaps or load testing with k6 or Artillery. Covers Jest, Vitest, pytest, mocking, flaky tests and security testing with defect reports. For strict test-first workflow see test-driven-development."
+tags: ["testing","engineering","performance"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/tester/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: tester
-description: "Tester role best practices. Builds confidence that code works — through the right mix of unit, integration, and end-to-end tests targeting real risk, not just coverage numbers."
-tags: ["engineering"]
+description: "Org role guidance for a tester: build confidence code works with the right mix of unit, integration and end-to-end tests aimed at real risk. Covers the test pyramid, edge cases, Arrange-Act-Assert, mocking dependencies and bug-reproducing tests."
+tags: ["engineering","testing","coding-standards"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/the-fool/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: the-fool
-description: "Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions."
-tags: ["leadership","research"]
+description: "Use when stress-testing an idea, plan or decision with structured critique: devil's advocate, pre-mortem, red team, Socratic questions, evidence audit. Five modes that steelman the position, present the strongest challenges and synthesize a stronger version."
+tags: ["leadership","research","strategy"]
 tools: []
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/theme-factory/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: theme-factory
-description: "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly."
-tags: ["design"]
+description: "Use when applying a consistent color and font theme to slides, docs, reports or HTML pages, picking from 10 preset themes or generating a new one. Each theme has a hex palette and header/body font pairing, shown in a showcase PDF for selection."
+tags: ["design","ui","design-system"]
 tools: ["monodesign_palette"]
 license: Apache-2.0
 source: https://github.com/anthropics/skills