MemStack Documentation

The memstack-content-email-sequence skill is designed for writing automated email campaigns. It provides a structured protocol for planning, designing, and writing multi-email sequences to achieve specific marketing goals.

At its base level (Lv.1), the skill covers:

• Campaign Planning: Defining goals, cadence, and the narrative arc.
• 5-Email Structure: A standard sequence consisting of Welcome, Story, Value, Soft Pitch, and Hard Pitch.
• Copywriting Elements: Subject lines (optimized for ~50 chars), preview text, and P.S. lines.
• Optimization: A/B test suggestions and platform setup notes.
• Output: A complete, ready-to-use sequence.

The Level 1 (Base) Site Audit skill provides the following SEO analysis capabilities:

• Meta tag scanning: Verifies presence and correctness of meta tags.
• Heading hierarchy: Analyzes the structure of H1-H6 tags.
• Broken link detection: Identifies dead links.
• Image optimization: Checks for optimized image assets.
• Core Web Vitals code patterns: Scans for code patterns affecting performance metrics.
• Robots.txt/Sitemap.xml: Validates SEO configuration files.
• Page performance: Evaluates loading speeds and efficiency.
• Structured data presence: Checks for Schema.org or other structured data.
• Scored output: Provides a page-by-page score with a prioritized list of recommended fixes.

The memstack-security-csp-headers skill is used to audit existing HTTP security headers, identify overly permissive directives (like unsafe-inline or unsafe-eval), and generate a production-ready Content-Security-Policy (CSP) along with companion security headers.

When to use this skill:

• When you need to audit, generate, or fix HTTP security headers for a web application.
• When you need to address unsafe-inline, unsafe-eval, or wildcard directives.
• When you need to configure HSTS, X-Frame-Options, or Permissions-Policy.

When NOT to use this skill:

• Do not use this for API route audits (use api-audit).
• Do not use this for dependency scanning.
• Do not use this for full OWASP security audits (use owasp-top10).
• Do not use this for scanning secrets in code (use secrets-scanner).

The API Designer skill focuses on designing robust routes, validation logic, and handler patterns. It covers the full lifecycle of API development, from initial route structure to generating TypeScript interfaces.

Key components include:

• Route Structure: Designing logical endpoint hierarchies.
• Auth Guard Pattern: Implementing security chains using getAuthContext and verifyOrgAccess.
• Input Validation: Using Zod for schema-based validation.
• Response Consistency: Ensuring a uniform response format and correct HTTP status codes.
• Advanced Patterns: Implementing rate limiting, webhook signature verification, and webhook endpoint design.
• Type Safety: Generating TypeScript interfaces from API definitions.

Git-Guard is an installer and verifier for machine-wide secret-blocking setups. It is NOT a secret scanner itself; it ensures that the necessary protection layers (git hooks, .gitignore, and gitleaks configuration) are present, correctly wired, and actually 'armed' to catch secrets during a commit.

When to use Git-Guard:

• When asking "is this repo protected?"
• When running "set up / install git-guard"
• When verifying gitleaks or git hooks
• On a new repository before the first commit

When NOT to use Git-Guard:

• For deep secret or history audits (use secrets-scanner instead).
• When mid-commit and simply trying to bypass a block (do not loosen protection to unblock).

The OWASP Top 10 skill supports two distinct scan modes depending on the required scope and speed:

Deep scan (Default)

• Scope: All 10 OWASP categories.
• Use Case: Pre-launch reviews, formal security audits, or compliance checks.

Quick scan

• Scope: Limited to A01 (Broken Access Control/Auth), A05 (Security Misconfiguration/Headers), and A06 (Vulnerable and Outdated Components).
• Use Case: Fast pre-deploy checks, CI pipeline gates, or initial triage.
• Trigger: Triggered by phrases like "quick OWASP", "quick security check", or "fast scan".
• Behavior: The scorecard will display the 3 targeted categories and mark the remaining 7 as ⏭️ SKIPPED (quick mode).

To ensure effective SEO, avoid these common mistakes:

• Targeting only high volume keywords: High volume often means high competition. Focus on long-tail keywords with lower volume but higher intent for faster ranking.
• One keyword per page: Each page should have one primary keyword and 3-5 semantically related keywords to build topic clusters.
• Treating research as a one-time task: Revisit keyword research at least quarterly to account for shifting trends and new competitors.
• Focusing on brand terms: You will rank for your brand naturally. Focus research on non-brand terms to attract new visitors.
• Relying solely on volume: A keyword with lower volume but high purchase intent is often more valuable than a high-volume informational keyword.

The Level 1 Refactor Planner provides a systematic framework for planning code improvements. It includes:

• Code Smell Categories: 4 categories (bloaters, couplers, dispensables, change preventers) covering 16 specific smells.
• Risk Assessment: A 5-factor risk matrix.
• Refactoring Patterns: 12 patterns organized into 3 groups (extraction, simplification, structural).
• Execution Framework: A phased execution plan template, a rollback strategy with defined abort criteria, and a system for tracking before/after metrics.

To create persuasive copy, avoid listing technical specifications (features) in isolation. Instead, transform every feature into a customer benefit that triggers an emotional outcome.

Conversion Formula: [Feature] → so you can → [Benefit] → which means → [Emotional outcome]

Examples: