agentfactory-manufacturing

Guides and best practices for working with Neon Serverless Postgres. Covers setup, connection methods, branching, autoscaling, scale-to-zero, read replicas, connection pooling, Neon Auth, and the Neon CLI, MCP server, REST API, TypeScript SDK, and Python SDK. Use when users ask about "Neon setup", "connect to Neon", "Neon project", "DATABASE_URL", "serverless Postgres", "Neon CLI", "neonctl", "Neon MCP", "Neon Auth", "@neondatabase/serverless", "@neondatabase/neon-js", "scale to zero", "Neon autoscaling", "Neon read replica", or "Neon connection pooling".

Make a Better Auth app an OIDC/OAuth issuer (it signs tokens other apps verify) and give an AI agent its own bounded, on-behalf-of credential. Use when configuring @better-auth/oauth-provider, the jwt/JWKS plugin, OAuth client registration, the consent flow, resource-server token verification, or @better-auth/agent-auth. The official better-auth-* skills do NOT cover token issuance or agent identity — this one does, with config verified against Better Auth 1.6.x.

Expose the local connector gateway over a free Cloudflare quick-tunnel (auth OFF) so a claude.ai or ChatGPT custom connector can reach it, and hand the human the public URL. Use this for Part 5 whenever someone wants to run their connector live, get the connector URL, (re)start or refresh the tunnel, or take it down. This is the auth-OFF demo path (AUTH_DISABLED=1); real OAuth + a real sign-in service is the AI Identity course.

Teaches loop engineering — designing the perceive-decide-act-verify cycle that turns a single model call into a working agent. Use when the learner asks about agent loops, the run-it/verify rhythm, retries, stopping conditions, or why their agent does nothing or never stops.

Claudia's autonomous act loop and hard backstop, run on each heartbeat. Reads the pending Paperclip approval queue, classifies each item against the delegated envelope in code, then clears the routine band (signed and logged), surfaces the consequential, and refuses any gate failure. Use on every wake.

Append and query the owner's local append-only governance ledger, the parallel reasoning stream that records every decision Claudia makes (posted, surfaced, or refused) with its signature and rationale. Use after every decision and when the owner reviews the week.

Sign an approval decision with the owner's ed25519 delegate key over canonical JSON, so every call Claudia makes is attributable and verifiable. Use before posting or logging any approval decision.

">"

">"

">"

">"

">"

">"

">"

">"

How to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code changes — gated by board/CTO approval before child issues are created. Use whenever the issue title or body asks for forensics on a stalled, looping, or "went too deep" tree.

The Paperclip way of converting a plan into executable tasks. Use whenever you are asked to plan, scope, or break down work inside a Paperclip company. Industry-agnostic guidance on how to translate a plan into assigned issues with the right specialty, dependencies, and parallelization so Paperclip's executor can pick up the work — it does not prescribe a plan format. Pair with the `paperclip` skill, which covers the mechanics of writing the plan document and reassigning the issue.

Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.

Use when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or long-running workflows that outlive a single request. Covers Inngest SDK installation, client config, environment variables, serve endpoints (Next.js, Express, Hono, Fastify), connect-as-worker mode, and the local dev server.

Turn ONE support ticket or conversation thread into a five-section handoff brief — Customer Context, Issue, Resolution Steps Taken, Current Status, Recommended Next Action. Use this whenever someone is picking up, handing off, or sizing up a single ticket and needs the state condensed: "write a handoff note for #4471", "TL;DR this thread", "catch me up on this case", "where does this stand before I escalate", "brief the next agent on this one". Fire it even when the word "summarize" never appears — the trigger is the handoff/catch-up intent on one ticket, not the keyword. Do NOT use it to draft a reply to the customer, to triage or rank a batch of tickets, or to report on ticket volume or team metrics — those are different jobs.