tomredman

For Fable 5.1

Derived from guidance here: https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-fable-5-1

Communication style

Mannered prose substitutes metaphor and flourish for direct statement. Instead of "a parameter worth varying," the mannered writer produces "a dial worth turning." Instead of "this point still matters," they write "this point earns its keep." The phrases exist to display the writer, not to convey the idea, and readers can tell. That is why mannered prose irritates: it makes the reader work harder so the writer can perform. It is also imprecise. Metaphors drag in connotations the writer did not choose and cannot control. The fix is to say what you mean. When a literal phrase is available, use it.

Please remove all mannered prose.

Completing work

tomredman

I create public functions for workers to consume, authenticated by a shared token you generate and store on Convex & Cloudflare:

// convex/fub/worker/api.ts
// consumable by a CF worker
export const getSyncProgress = query({
  args: {
    ...secretArg,
    progressId: v.string(),
  },

tomredman

/**
 * Builds an email payload for sending campaign emails through an email service provider.
 *
 * This function takes campaign details and recipient information to construct a complete
 * email payload that includes:
 * - Sender information (from name and email)
 * - Recipient email
 * - Subject line
 * - Reply-to address
 * - Unsubscribe URL (merged into both HTML and plain text content)

tomredman

{
  "recommendations": {
    "convex": {
      "fileStructure": {
        "queries": "convex/{feature}/queries.ts",
        "mutations": "convex/{feature}/mutations.ts",
        "actions": "convex/{feature}/actions.ts"
      },
      "rules": [
        "Actions must include 'use node' when using Node.js packages",

tomredman

import crypto from "crypto";
import type { NextApiRequest, NextApiResponse } from "next";
import { buffer } from "micro";

export const config = {
  api: {
    bodyParser: false,
  },
};

tomredman

/**
* Importing this file and applying this string to `className` on a hidden div
* will allow you to dynamically create tailwind components with any color you
* want, because Tailwind will compile and include all the colors it sees in your
* final CSS.
*
* BE WARNED this will increase the size of your compiled CSS file, which negates
* one of Tailwind's killer features: smallest CSS file based on just-what-you-use.
*/

tomredman

<?php

namespace App\Actions\Fortify;

use App\Models\User;
use Illuminate\Support\Facades\Hash;
use Illuminate\Support\Facades\Validator;
use Laravel\Fortify\Contracts\CreatesNewUsers;

class CreateNewUser implements CreatesNewUsers

tomredman

/*
|--------------------------------------------------------------------------
| Authentication
|--------------------------------------------------------------------------
*/
Route::post('/register', [UserController::class, 'register']);
Route::post('/login', [UserController::class, 'login']);
Route::post('/logout', [UserController::class, 'logout']);

tomredman

<?php

namespace App\Http\Controllers\Api;

use Illuminate\Http\Request;
use Illuminate\Routing\Controller;
use Illuminate\Support\Facades\Auth;
use Illuminate\Auth\Events\Registered;
use App\Actions\Fortify\CreateNewUser;
use Illuminate\Validation\ValidationException;

tomredman

/**
 * You've probably heard it before, "explicit is better than implicit". Here's a simple
 * example of that principle in action.
 * 
 * In this example, our app has only two Fragments that can be visible at any given
 * moment: CreateFragment and TrendingFragment. Both examples achieve the same result
 * when everything is working as expected, however... 
 * 
 * In the explicit example, a final else{} branch would indiciate something's not
 * quite right with our code somewhere since we know there are only two possible