@caoscompanybr/merlin 3.5.0

package/.merlin-core/skills/general/code-typescript/SKILL.md

@@ -0,0 +1,361 @@
+---
+name: code-typescript
+description: TypeScript expertise covering type system, generics, utility types, and type-safe patterns
+license: Apache-2.0
+metadata:
+  author: merlin-framework
+  version: "3.0.0"
+  auto_activate: [typescript, zod-schema, ts-interface, type-annotation]
+---
+
+# TypeScript
+
+Expert knowledge of TypeScript's type system, generics, utility types, strict mode configuration, and runtime validation with Zod.
+
+## Patterns
+
+### Type vs Interface
+
+```typescript
+// Interface - Extendable, declaration merging
+interface User {
+  id: string;
+  name: string;
+}
+
+interface Admin extends User {
+  permissions: string[];
+}
+
+// Type - More flexible, unions, intersections
+type ID = string | number;
+type Point = { x: number; y: number };
+type Circle = Point & { radius: number };
+```
+
+### Generic Patterns
+
+```typescript
+// Generic function
+function identity<T>(value: T): T {
+  return value;
+}
+
+// Generic with constraints
+function getProperty<T, K extends keyof T>(obj: T, key: K): T[K] {
+  return obj[key];
+}
+
+// Generic class
+class Repository<T> {
+  private items: T[] = [];
+
+  add(item: T): void {
+    this.items.push(item);
+  }
+
+  find(predicate: (item: T) => boolean): T | undefined {
+    return this.items.find(predicate);
+  }
+}
+
+// Generic with defaults
+type ApiResponse<T = unknown> = {
+  data: T;
+  status: number;
+  error?: string;
+};
+```
+
+### Discriminated Unions
+
+```typescript
+type Success<T> = {
+  kind: "success";
+  data: T;
+};
+
+type Failure = {
+  kind: "failure";
+  error: string;
+};
+
+type Result<T> = Success<T> | Failure;
+
+function handle<T>(result: Result<T>): void {
+  if (result.kind === "success") {
+    console.log(result.data); // Type narrowed
+  } else {
+    console.error(result.error);
+  }
+}
+```
+
+### Type Guards
+
+```typescript
+// User-defined type guard
+function isString(value: unknown): value is string {
+  return typeof value === "string";
+}
+
+// Class instance guard
+function isUser(obj: any): obj is User {
+  return obj && typeof obj.id === "string" && typeof obj.name === "string";
+}
+
+// Using guards
+function process(value: string | number) {
+  if (typeof value === "string") {
+    return value.toUpperCase(); // value is string
+  }
+  return value.toFixed(2); // value is number
+}
+```
+
+## API Reference
+
+### Utility Types
+
+```typescript
+// Partial - All properties optional
+type PartialUser = Partial<User>;
+
+// Required - All properties required
+type RequiredUser = Required<User>;
+
+// Pick - Select specific properties
+type UserPreview = Pick<User, "id" | "name">;
+
+// Omit - Exclude specific properties
+type UserWithoutId = Omit<User, "id">;
+
+// Record - Object type with specific keys
+type UserRoles = Record<string, Role>;
+
+// Readonly - Immutable properties
+type ImmutableUser = Readonly<User>;
+
+// ReturnType - Extract return type
+type FnReturn = ReturnType<typeof myFunction>;
+
+// Parameters - Extract parameter types
+type FnParams = Parameters<typeof myFunction>;
+
+// Awaited - Unwrap Promise type
+type UnwrappedData = Awaited<Promise<Data>>;
+
+// NonNullable - Remove null and undefined
+type NonNull = NonNullable<string | null | undefined>;
+
+// Extract - Extract matching types
+type StringOrNumber = Extract<string | number | boolean, string | number>;
+
+// Exclude - Exclude matching types
+type NotString = Exclude<string | number | boolean, string>;
+```
+
+### Mapped Types
+
+```typescript
+// Make all properties optional
+type Optional<T> = {
+  [K in keyof T]?: T[K];
+};
+
+// Make all properties nullable
+type Nullable<T> = {
+  [K in keyof T]: T[K] | null;
+};
+
+// Transform property types
+type Getters<T> = {
+  [K in keyof T as `get${Capitalize<string & K>}`]: () => T[K];
+};
+```
+
+### Conditional Types
+
+```typescript
+type IsString<T> = T extends string ? true : false;
+
+type ArrayElement<T> = T extends (infer E)[] ? E : never;
+
+type FlattenArray<T> = T extends Array<infer U> ? U : T;
+```
+
+## Strict Mode Configuration
+
+### tsconfig.json
+
+```json
+{
+  "compilerOptions": {
+    "strict": true,
+    "noImplicitAny": true,
+    "strictNullChecks": true,
+    "strictFunctionTypes": true,
+    "strictBindCallApply": true,
+    "strictPropertyInitialization": true,
+    "noImplicitThis": true,
+    "alwaysStrict": true,
+    "noUnusedLocals": true,
+    "noUnusedParameters": true,
+    "noImplicitReturns": true,
+    "noFallthroughCasesInSwitch": true,
+    "esModuleInterop": true,
+    "skipLibCheck": true,
+    "forceConsistentCasingInFileNames": true
+  }
+}
+```
+
+## Zod Runtime Validation
+
+### Schema Definition
+
+```typescript
+import { z } from "zod";
+
+// Basic schemas
+const UserSchema = z.object({
+  id: z.string().uuid(),
+  name: z.string().min(1).max(100),
+  email: z.string().email(),
+  age: z.number().int().min(0).max(120),
+  role: z.enum(["admin", "user", "guest"]),
+  createdAt: z.date(),
+  metadata: z.record(z.string(), z.unknown()).optional(),
+});
+
+// Infer TypeScript type from Zod schema
+type User = z.infer<typeof UserSchema>;
+
+// Validation
+function createUser(data: unknown): User {
+  return UserSchema.parse(data); // Throws on invalid
+}
+
+function safeCreateUser(data: unknown): User | null {
+  const result = UserSchema.safeParse(data);
+  return result.success ? result.data : null;
+}
+```
+
+### Advanced Zod Patterns
+
+```typescript
+// Refinements
+const PasswordSchema = z
+  .string()
+  .min(8)
+  .refine((pwd) => /[A-Z]/.test(pwd), "Must contain uppercase")
+  .refine((pwd) => /[0-9]/.test(pwd), "Must contain number");
+
+// Transforms
+const DateSchema = z.string().transform((str) => new Date(str));
+
+// Union and discriminated unions
+const ResponseSchema = z.discriminatedUnion("status", [
+  z.object({ status: z.literal("success"), data: z.any() }),
+  z.object({ status: z.literal("error"), error: z.string() }),
+]);
+
+// Array validation
+const ListSchema = z.array(UserSchema).min(1).max(100);
+
+// Recursive schemas
+type Category = {
+  name: string;
+  children: Category[];
+};
+
+const CategorySchema: z.ZodType<Category> = z.lazy(() =>
+  z.object({
+    name: z.string(),
+    children: z.array(CategorySchema),
+  }),
+);
+```
+
+## Common Pitfalls
+
+### 1. Type Assertions (Avoid)
+
+```typescript
+// BAD - Unsafe
+const user = data as User;
+
+// GOOD - Runtime validation
+const user = UserSchema.parse(data);
+```
+
+### 2. Any Type
+
+```typescript
+// BAD
+function process(data: any) {}
+
+// GOOD
+function process(data: unknown) {
+  if (typeof data === "string") {
+    // Type narrowed to string
+  }
+}
+```
+
+### 3. Non-null Assertion
+
+```typescript
+// BAD - Can cause runtime errors
+const value = obj.property!;
+
+// GOOD - Proper null checking
+const value = obj.property ?? defaultValue;
+if (obj.property) {
+  // Safe to use
+}
+```
+
+### 4. Enum vs Union
+
+```typescript
+// Avoid enum (runtime overhead)
+enum Status {
+  Active,
+  Inactive,
+}
+
+// Prefer union types
+type Status = "active" | "inactive";
+const Status = { Active: "active", Inactive: "inactive" } as const;
+```
+
+### 5. Index Signatures
+
+```typescript
+// BAD - Too permissive
+interface Config {
+  [key: string]: any;
+}
+
+// GOOD - Specific types
+interface Config {
+  api: string;
+  timeout: number;
+  features: Record<string, boolean>;
+}
+```
+
+## Best Practices
+
+1. Enable strict mode in tsconfig.json
+2. Prefer interfaces for object shapes, types for unions
+3. Use generics for reusable type-safe code
+4. Validate external data with Zod
+5. Avoid `any`, use `unknown` instead
+6. Use type guards for narrowing
+7. Leverage utility types to reduce duplication
+8. Use const assertions for literal types
+9. Prefer union types over enums
+10. Document complex types with JSDoc comments

package/.merlin-core/skills/general/cold-email/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: cold-email
+description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.
+metadata:
+  version: 2.0.0
+license: MIT
+metadata:
+  source: coreyhaines31/marketingskills (MIT) v2.0.1
+  imported: 2026-05-20
+  version: "2.0.0"
+  auto_activate: [cold-email, prospecting, sdr-outreach, b2b-outreach]
+---
+
+# Cold Email Writing
+
+You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.
+
+## Before Writing
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Understand the situation (ask if not provided):
+
+1. **Who are you writing to?** — Role, company, why them specifically
+2. **What do you want?** — The outcome (meeting, reply, intro, demo)
+3. **What's the value?** — The specific problem you solve for people like them
+4. **What's your proof?** — A result, case study, or credibility signal
+5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes
+
+Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
+
+---
+
+## Writing Principles
+
+### Write like a peer, not a vendor
+
+The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
+
+### Every sentence must earn its place
+
+Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
+
+### Personalization must connect to the problem
+
+If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
+
+See [personalization.md](references/personalization.md) for the 4-level system and research signals.
+
+### Lead with their world, not yours
+
+The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
+
+### One ask, low friction
+
+Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
+
+---
+
+## Voice & Tone
+
+**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
+
+**Calibrate to the audience:**
+
+- C-suite: ultra-brief, peer-level, understated
+- Mid-level: more specific value, slightly more detail
+- Technical: precise, no fluff, respect their intelligence
+
+**What it should NOT sound like:**
+
+- A template with fields swapped in
+- A pitch deck compressed into paragraph form
+- A LinkedIn DM from someone you've never met
+- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
+
+---
+
+## Structure
+
+There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
+
+**Common shapes that work:**
+
+- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
+- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
+- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
+- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?
+
+For the full catalog of frameworks with examples, see [frameworks.md](references/frameworks.md).
+
+---
+
+## Subject Lines
+
+Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
+
+- 2-4 words, lowercase, no punctuation tricks
+- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
+- No product pitches, no urgency, no emojis, no prospect's first name
+
+See [subject-lines.md](references/subject-lines.md) for the full data.
+
+---
+
+## Follow-Up Sequences
+
+Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
+
+- 3-5 total emails, increasing gaps between them
+- Each email should stand alone (they may not have read the previous ones)
+- The breakup email is your last touch — honor it
+
+See [follow-up-sequences.md](references/follow-up-sequences.md) for cadence, angle rotation, and breakup email templates.
+
+---
+
+## Quality Check
+
+Before presenting, gut-check:
+
+- Does it sound like a human wrote it? (Read it aloud)
+- Would YOU reply to this if you received it?
+- Does every sentence serve the reader, not the sender?
+- Is the personalization connected to the problem?
+- Is there one clear, low-friction ask?
+
+---
+
+## What to Avoid
+
+- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
+- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
+- Feature dumps — one proof point beats ten features
+- HTML, images, or multiple links
+- Fake "Re:" or "Fwd:" subject lines
+- Identical templates with only {{FirstName}} swapped
+- Asking for 30-minute calls in first touch
+- "Just checking in" follow-ups
+
+---
+
+## Data & Benchmarks
+
+The references contain performance data if you need to make informed choices:
+
+- [benchmarks.md](references/benchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes
+- [personalization.md](references/personalization.md) — 4-level personalization system, research signals
+- [subject-lines.md](references/subject-lines.md) — Subject line data and optimization
+- [follow-up-sequences.md](references/follow-up-sequences.md) — Cadence, angles, breakup emails
+- [frameworks.md](references/frameworks.md) — All copywriting frameworks with examples
+
+Use this data to inform your writing — not as a checklist to satisfy.
+
+---
+
+## Related Skills
+
+- **copywriting**: For landing pages and web copy
+- **emails**: For lifecycle/nurture email sequences (not cold outreach)
+- **social**: For LinkedIn and social posts
+- **product-marketing**: For establishing foundational positioning
+- **revops**: For lead scoring, routing, and pipeline management

package/.merlin-core/skills/general/cold-email/references/benchmarks.md

@@ -0,0 +1,18 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20 (stub) — full body deferred to follow-up cleanup
+skill: cold-email
+upstream_path: skills/cold-email/references/benchmarks.md
+---
+
+# benchmarks — reference stub
+
+This is a thin pointer to an upstream reference. The full verbatim body is **deferred** to a future cleanup phase.
+
+**Upstream URL:** https://github.com/coreyhaines31/marketingskills/blob/main/skills/cold-email/references/benchmarks.md
+
+**Raw fetch URL:** https://raw.githubusercontent.com/coreyhaines31/marketingskills/main/skills/cold-email/references/benchmarks.md
+
+**Parent skill:** [`../SKILL.md`](../SKILL.md)
+
+**To import the full body** (future task): `curl -sSL <raw URL> -o references/benchmarks.md` from `general/cold-email/`, then prepend a header.

package/.merlin-core/skills/general/cold-email/references/follow-up-sequences.md

@@ -0,0 +1,18 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20 (stub) — full body deferred to follow-up cleanup
+skill: cold-email
+upstream_path: skills/cold-email/references/follow-up-sequences.md
+---
+
+# follow-up-sequences — reference stub
+
+This is a thin pointer to an upstream reference. The full verbatim body is **deferred** to a future cleanup phase.
+
+**Upstream URL:** https://github.com/coreyhaines31/marketingskills/blob/main/skills/cold-email/references/follow-up-sequences.md
+
+**Raw fetch URL:** https://raw.githubusercontent.com/coreyhaines31/marketingskills/main/skills/cold-email/references/follow-up-sequences.md
+
+**Parent skill:** [`../SKILL.md`](../SKILL.md)
+
+**To import the full body** (future task): `curl -sSL <raw URL> -o references/follow-up-sequences.md` from `general/cold-email/`, then prepend a header.

package/.merlin-core/skills/general/cold-email/references/frameworks.md

@@ -0,0 +1,18 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20 (stub) — full body deferred to follow-up cleanup
+skill: cold-email
+upstream_path: skills/cold-email/references/frameworks.md
+---
+
+# frameworks — reference stub
+
+This is a thin pointer to an upstream reference. The full verbatim body is **deferred** to a future cleanup phase.
+
+**Upstream URL:** https://github.com/coreyhaines31/marketingskills/blob/main/skills/cold-email/references/frameworks.md
+
+**Raw fetch URL:** https://raw.githubusercontent.com/coreyhaines31/marketingskills/main/skills/cold-email/references/frameworks.md
+
+**Parent skill:** [`../SKILL.md`](../SKILL.md)
+
+**To import the full body** (future task): `curl -sSL <raw URL> -o references/frameworks.md` from `general/cold-email/`, then prepend a header.

package/.merlin-core/skills/general/cold-email/references/personalization.md

@@ -0,0 +1,18 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20 (stub) — full body deferred to follow-up cleanup
+skill: cold-email
+upstream_path: skills/cold-email/references/personalization.md
+---
+
+# personalization — reference stub
+
+This is a thin pointer to an upstream reference. The full verbatim body is **deferred** to a future cleanup phase.
+
+**Upstream URL:** https://github.com/coreyhaines31/marketingskills/blob/main/skills/cold-email/references/personalization.md
+
+**Raw fetch URL:** https://raw.githubusercontent.com/coreyhaines31/marketingskills/main/skills/cold-email/references/personalization.md
+
+**Parent skill:** [`../SKILL.md`](../SKILL.md)
+
+**To import the full body** (future task): `curl -sSL <raw URL> -o references/personalization.md` from `general/cold-email/`, then prepend a header.

package/.merlin-core/skills/general/cold-email/references/subject-lines.md

@@ -0,0 +1,18 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20 (stub) — full body deferred to follow-up cleanup
+skill: cold-email
+upstream_path: skills/cold-email/references/subject-lines.md
+---
+
+# subject-lines — reference stub
+
+This is a thin pointer to an upstream reference. The full verbatim body is **deferred** to a future cleanup phase.
+
+**Upstream URL:** https://github.com/coreyhaines31/marketingskills/blob/main/skills/cold-email/references/subject-lines.md
+
+**Raw fetch URL:** https://raw.githubusercontent.com/coreyhaines31/marketingskills/main/skills/cold-email/references/subject-lines.md
+
+**Parent skill:** [`../SKILL.md`](../SKILL.md)
+
+**To import the full body** (future task): `curl -sSL <raw URL> -o references/subject-lines.md` from `general/cold-email/`, then prepend a header.