agentleFS
fpindejfpindej/netrock/.claude/skills/add-email-template/SKILL.md

add-email-template

Skill234 starsChanged 3 months agoMITView on GitHub

Add a transactional email template using Fluid (Liquid)

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All marked as EmbeddedResource (verify .csproj has <EmbeddedResource Include="Features\Email\Templates\*.liquid" />).

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adds a transactional email template using Fluid (Liquid).

Each email has a 3-file pattern plus a model record.

Steps

1. Create the model record in src/backend/MyProject.Application/Features/Email/Models/EmailTemplateModels.cs:

/// <summary>
/// Model for the order-confirmation template. Exposed as <c>order_number</c> and <c>total</c> in Liquid.
/// </summary>
public record OrderConfirmationModel(string OrderNumber, string Total);

Properties auto-map to snake_case Liquid variables (OrderNumber -> order_number).

2. Create 3 template files in src/backend/MyProject.Infrastructure/Features/Email/Templates/:

  • order-confirmation.liquid - HTML body fragment (injected into _base.liquid via {{ body | raw }}):
    <h2 style="margin: 0 0 20px 0; font-size: 22px; font-weight: 700; color: #333333;">Order Confirmed</h2>
    <p style="margin: 0 0 16px 0;">Your order <strong>{{ order_number }}</strong> totaling {{ total }} has been confirmed.</p>
  • order-confirmation.subject.liquid - Subject line (plain text, no HTML)
  • order-confirmation.text.liquid - Plain text body (optional but recommended)

All marked as EmbeddedResource (verify .csproj has <EmbeddedResource Include="Features\Email\Templates\*.liquid" />).

3. Register the model type in FluidEmailTemplateRenderer.CreateOptions():

options.MemberAccessStrategy.Register<OrderConfirmationModel>();

4. Use in a service:

await templatedEmailSender.SendSafeAsync("order-confirmation",
    new OrderConfirmationModel(order.Number, order.FormattedTotal),
    customer.Email, cancellationToken);

5. Add tests in FluidEmailTemplateRendererTests.cs - test subject rendering, HTML variable injection, and plain text variant.

6. Verify: dotnet test src/backend/MyProject.slnx -c Release

Conventions

  • Template names: kebab-case (order-confirmation, not orderConfirmation)
  • HTML templates: inline styles (email clients ignore <style> blocks in fragments)
  • _base.liquid provides the wrapper (header with {{ app_name }}, card, footer) - fragments provide inner content only
  • HTML body: HtmlEncoder.Default (XSS-safe). Subject/plain text: unencoded
  • Subject: static text or config-sourced variables only - never raw user input
  • {{ app_name }} is automatically available from EmailOptions.FromName

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.