100xprism 2.3.1

package/modules/copywriting/references/natural-transitions.md

@@ -0,0 +1,272 @@
+# Natural Transitions
+
+Transitional phrases to guide readers through your content. Good signposting improves readability, user engagement, and helps search engines understand content structure.
+
+Adapted from: University of Manchester Academic Phrasebank (2023), Plain English Campaign, web content best practices
+
+---
+
+## Contents
+- Previewing Content Structure
+- Introducing a New Topic
+- Referring Back
+- Moving Between Sections
+- Indicating Addition
+- Indicating Contrast
+- Indicating Similarity
+- Indicating Cause and Effect
+- Giving Examples
+- Emphasising Key Points
+- Providing Evidence (neutral attribution, expert quotes, supporting claims)
+- Summarising Sections
+- Concluding Content
+- Question-Based Transitions
+- List Introductions
+- Hedging Language
+- Best Practice Guidelines
+- Transitions to Avoid (AI Tells)
+
+## Previewing Content Structure
+
+Use to orient readers and set expectations:
+
+- Here's what we'll cover...
+- This guide walks you through...
+- Below, you'll find...
+- We'll start with X, then move to Y...
+- First, let's look at...
+- Let's break this down step by step.
+- The sections below explain...
+
+---
+
+## Introducing a New Topic
+
+- When it comes to X,...
+- Regarding X,...
+- Speaking of X,...
+- Now let's talk about X.
+- Another key factor is...
+- X is worth exploring because...
+
+---
+
+## Referring Back
+
+Use to connect ideas and reinforce key points:
+
+- As mentioned earlier,...
+- As we covered above,...
+- Remember when we discussed X?
+- Building on that point,...
+- Going back to X,...
+- Earlier, we explained that...
+
+---
+
+## Moving Between Sections
+
+- Now let's look at...
+- Next up:...
+- Moving on to...
+- With that covered, let's turn to...
+- Now that you understand X, here's Y.
+- That brings us to...
+
+---
+
+## Indicating Addition
+
+- Also,...
+- Plus,...
+- On top of that,...
+- What's more,...
+- Another benefit is...
+- Beyond that,...
+- In addition,...
+- There's also...
+
+**Note:** Use "moreover" and "furthermore" sparingly. They can sound AI-generated when overused.
+
+---
+
+## Indicating Contrast
+
+- However,...
+- But,...
+- That said,...
+- On the flip side,...
+- In contrast,...
+- Unlike X, Y...
+- While X is true, Y...
+- Despite this,...
+
+---
+
+## Indicating Similarity
+
+- Similarly,...
+- Likewise,...
+- In the same way,...
+- Just like X, Y also...
+- This mirrors...
+- The same applies to...
+
+---
+
+## Indicating Cause and Effect
+
+- So,...
+- This means...
+- As a result,...
+- That's why...
+- Because of this,...
+- This leads to...
+- The outcome?...
+- Here's what happens:...
+
+---
+
+## Giving Examples
+
+- For example,...
+- For instance,...
+- Here's an example:...
+- Take X, for instance.
+- Consider this:...
+- A good example is...
+- To illustrate,...
+- Like when...
+- Say you want to...
+
+---
+
+## Emphasising Key Points
+
+- Here's the key takeaway:...
+- The important thing is...
+- What matters most is...
+- Don't miss this:...
+- Pay attention to...
+- This is critical:...
+- The bottom line?...
+
+---
+
+## Providing Evidence
+
+Use when citing sources, data, or expert opinions:
+
+### Neutral attribution
+- According to [Source],...
+- [Source] reports that...
+- Research shows that...
+- Data from [Source] indicates...
+- A study by [Source] found...
+
+### Expert quotes
+- As [Expert] puts it,...
+- [Expert] explains,...
+- In the words of [Expert],...
+- [Expert] notes that...
+
+### Supporting claims
+- This is backed by...
+- Evidence suggests...
+- The numbers confirm...
+- This aligns with findings from...
+
+---
+
+## Summarising Sections
+
+- To recap,...
+- Here's the short version:...
+- In short,...
+- The takeaway?...
+- So what does this mean?...
+- Let's pull this together:...
+- Quick summary:...
+
+---
+
+## Concluding Content
+
+- Wrapping up,...
+- The bottom line is...
+- Here's what to do next:...
+- To sum up,...
+- Final thoughts:...
+- Ready to get started?...
+- Now it's your turn.
+
+**Note:** Avoid "In conclusion" at the start of a paragraph. It's overused and signals AI writing.
+
+---
+
+## Question-Based Transitions
+
+Useful for conversational tone and featured snippet optimization:
+
+- So what does this mean for you?
+- But why does this matter?
+- How do you actually do this?
+- What's the catch?
+- Sound complicated? It's not.
+- Wondering where to start?
+- Still not sure? Here's the breakdown.
+
+---
+
+## List Introductions
+
+For numbered lists and step-by-step content:
+
+- Here's how to do it:
+- Follow these steps:
+- The process is straightforward:
+- Here's what you need to know:
+- Key things to consider:
+- The main factors are:
+
+---
+
+## Hedging Language
+
+For claims that need qualification or aren't absolute:
+
+- may, might, could
+- tends to, generally
+- often, usually, typically
+- in most cases
+- it appears that
+- evidence suggests
+- this can help
+- many experts believe
+
+---
+
+## Best Practice Guidelines
+
+1. **Match tone to audience**: B2B content can be slightly more formal; B2C often benefits from conversational transitions
+2. **Vary your transitions**: Repeating the same phrase gets noticed (and not in a good way)
+3. **Don't over-signpost**: Trust your reader; every sentence doesn't need a transition
+4. **Use for scannability**: Transitions at paragraph starts help skimmers navigate
+5. **Keep it natural**: Read aloud; if it sounds forced, simplify
+6. **Front-load key info**: Put the important word or phrase early in the transition
+
+---
+
+## Transitions to Avoid (AI Tells)
+
+These phrases are overused in AI-generated content:
+
+- "That being said,..."
+- "It's worth noting that..."
+- "At its core,..."
+- "In today's digital landscape,..."
+- "When it comes to the realm of..."
+- "This begs the question..."
+- "Let's delve into..."
+
+See the seo-audit skill's `references/ai-writing-detection.md` for a complete list of AI writing tells.

package/modules/copywriting/references/sequence-templates.md

@@ -0,0 +1,168 @@
+# Email Sequence Templates
+
+Detailed templates for common email sequences.
+
+## Contents
+- Welcome Sequence (Post-Signup)
+- Lead Nurture Sequence (Pre-Sale)
+- Re-Engagement Sequence
+- Onboarding Sequence (Product Users)
+
+## Welcome Sequence (Post-Signup)
+
+**Email 1: Welcome (Immediate)**
+- Subject: Welcome to [Product] — here's your first step
+- Deliver what was promised (lead magnet, access, etc.)
+- Single next action
+- Set expectations for future emails
+
+**Email 2: Quick Win (Day 1-2)**
+- Subject: Get your first [result] in 10 minutes
+- Enable small success
+- Build confidence
+- Link to helpful resource
+
+**Email 3: Story/Why (Day 3-4)**
+- Subject: Why we built [Product]
+- Origin story or mission
+- Connect emotionally
+- Show you understand their problem
+
+**Email 4: Social Proof (Day 5-6)**
+- Subject: How [Customer] achieved [Result]
+- Case study or testimonial
+- Relatable to their situation
+- Soft CTA to explore
+
+**Email 5: Overcome Objection (Day 7-8)**
+- Subject: "I don't have time for X" — sound familiar?
+- Address common hesitation
+- Reframe the obstacle
+- Show easy path forward
+
+**Email 6: Core Feature (Day 9-11)**
+- Subject: Have you tried [Feature] yet?
+- Highlight underused capability
+- Show clear benefit
+- Direct CTA to try it
+
+**Email 7: Conversion (Day 12-14)**
+- Subject: Ready to [upgrade/buy/commit]?
+- Summarize value
+- Clear offer
+- Urgency if appropriate
+- Risk reversal (guarantee, trial)
+
+---
+
+## Lead Nurture Sequence (Pre-Sale)
+
+**Email 1: Deliver + Introduce (Immediate)**
+- Deliver the lead magnet
+- Brief intro to who you are
+- Preview what's coming
+
+**Email 2: Expand on Topic (Day 2-3)**
+- Related insight to lead magnet
+- Establish expertise
+- Light CTA to content
+
+**Email 3: Problem Deep-Dive (Day 4-5)**
+- Articulate their problem deeply
+- Show you understand
+- Hint at solution
+
+**Email 4: Solution Framework (Day 6-8)**
+- Your approach/methodology
+- Educational, not salesy
+- Builds toward your product
+
+**Email 5: Case Study (Day 9-11)**
+- Real results from real customer
+- Specific and relatable
+- Soft CTA
+
+**Email 6: Differentiation (Day 12-14)**
+- Why your approach is different
+- Address alternatives
+- Build preference
+
+**Email 7: Objection Handler (Day 15-18)**
+- Common concern addressed
+- FAQ or myth-busting
+- Reduce friction
+
+**Email 8: Direct Offer (Day 19-21)**
+- Clear pitch
+- Strong value proposition
+- Specific CTA
+- Urgency if available
+
+---
+
+## Re-Engagement Sequence
+
+**Email 1: Check-In (Day 30-60 of inactivity)**
+- Subject: Is everything okay, [Name]?
+- Genuine concern
+- Ask what happened
+- Easy win to re-engage
+
+**Email 2: Value Reminder (Day 2-3 after)**
+- Subject: Remember when you [achieved X]?
+- Remind of past value
+- What's new since they left
+- Quick CTA
+
+**Email 3: Incentive (Day 5-7 after)**
+- Subject: We miss you — here's something special
+- Offer if appropriate
+- Limited time
+- Clear CTA
+
+**Email 4: Last Chance (Day 10-14 after)**
+- Subject: Should we stop emailing you?
+- Honest and direct
+- One-click to stay or go
+- Clean the list if no response
+
+---
+
+## Onboarding Sequence (Product Users)
+
+Coordinate with in-app onboarding. Email supports, doesn't duplicate.
+
+**Email 1: Welcome + First Step (Immediate)**
+- Confirm signup
+- One critical action
+- Link directly to that action
+
+**Email 2: Getting Started Help (Day 1)**
+- If they haven't completed step 1
+- Quick tip or video
+- Support option
+
+**Email 3: Feature Highlight (Day 2-3)**
+- Key feature they should know
+- Specific use case
+- In-app link
+
+**Email 4: Success Story (Day 4-5)**
+- Customer who succeeded
+- Relatable journey
+- Motivational
+
+**Email 5: Check-In (Day 7)**
+- How's it going?
+- Ask for feedback
+- Offer help
+
+**Email 6: Advanced Tip (Day 10-12)**
+- Power feature
+- For engaged users
+- Level-up content
+
+**Email 7: Upgrade/Expand (Day 14+)**
+- For trial users: conversion push
+- For free users: upgrade prompt
+- For paid: expansion opportunity

package/modules/data-query/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: data-query
+description: Run analytics queries against any database using plain English — BigQuery (bq CLI), PostgreSQL, MySQL, SQLite, or any DB with a CLI/MCP/API. Use when you need to pull metrics, analyze data, or answer business questions without writing SQL.
+category: data
+tier: on-demand
+slash_command: /query
+allowed-tools: Bash Read
+model: sonnet
+---
+
+# Query — Plain-English Database Analytics
+
+Describe what you want to know — Claude writes and runs the query.
+
+## How to use
+- `/query <business question>` — Claude translates to SQL, runs it, returns analysis
+
+## Supported interfaces
+- **BigQuery**: `bq` CLI — `bq query`, `bq show`, `bq ls`
+- **PostgreSQL**: `psql` CLI
+- **MySQL**: `mysql` CLI
+- **SQLite**: `sqlite3` CLI
+
+---
+
+## Phase 1 — Understand the question
+
+Restate the business question in concrete terms. If the schema is ambiguous, inspect it first:
+
+```bash
+# BigQuery — show table schema
+bq show <dataset>.<table>
+
+# PostgreSQL
+PGPASSWORD="$DB_PASS" psql -h "$DB_HOST" -U "$DB_USER" -d "$DB_NAME" \
+  -c "\d <table_name>"
+```
+
+---
+
+## Phase 2 — Write and run the query
+
+Write the SQL for the business question. Run it using the appropriate CLI. Explain the results in plain English.
+
+---
+
+## Phase 3 — Return results
+
+Return:
+1. The SQL written
+2. A plain-English answer to the original question
+3. A table of key numbers
+
+For recurring queries: offer to save as a named script.
+
+## Scope vs `/db`
+- `/query` = analytics in plain English (you describe a business question)
+- `/db` = execute specific SQL against a named connection (you write the SQL or say "migrate")