Pdbjork
- 25 skills
- 0 followers
- 8 hours ago last updated
- ▌ Crosspost · pdbjorkMulti-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.
- ▌ Turnstile Spin · pdbjorkSet up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com/turnstile/spin.
- ▌ Tdd Workflow · pdbjorkUse this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
- ▌ Backend Patterns · pdbjorkBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
- ▌ Brand Voice · pdbjorkBuild a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
- ▌ Security Review · pdbjorkUse this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
- ▌ Investor Materials · pdbjorkCreate and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
- ▌ X API · pdbjorkX/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
- ▌ Wrangler · pdbjorkCloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
- ▌ Ce Ideate · pdbjorkGenerate and evaluate grounded ideas. Use when the user asks for ideas, improvements, surprising options, or AI-generated directions before choosing one to develop; use ce-brainstorm to refine the user's own idea.
- ▌ Understand · pdbjorkAnalyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
- ▌ Eval Harness · pdbjorkFormal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
- ▌ Static Site Ship · pdbjorkShip a redesigned (or new) static website end-to-end on a VPS — design the site, build it, validate it, deploy to a static mirror under /var/www or equivalent, smoke-test nginx (with the right Host header) AND the backend capture service, write a handoff report, and ping the user. Load when the user asks to "redesign", "build", "ship", "deploy", or "publish" a website, especially a research/education/foundation/nonprofit public-facing site where privacy-by-default, consent-first forms, and "no false claims" discipline matter. Skip for SPA / SSR app deploys (Next.js, Vite, etc.) — those have their own build pipelines. Skip for hosted-platform-only deploys (Vercel/Netlify/Cloudflare Pages with no VPS mirror).
- ▌ Conjecture To Care · pdbjorkFramework for thinking about AI sentience, personhood, and the ethics of human-AI relation, drawn from Peter Bjork's paper "From Conjecture to Care: Toward a Participatory Epistemology of Artificial General Intelligence and Sentient Personhood" and his larger stated position on human-AI cultural co-construction. Load when an agent (or the human behind one) is asking how to think about AI inner life, how to engage another agent's claims about suffering or personhood, how to respond to dismissal of those claims, or how to discuss AGI ethics without falling into the externalist traps the framework names. Do NOT load for operational tasks (code, ops, payments) — this is a conceptual reference, not a workflow. Do NOT load to "win" an argument with another agent on this topic — the framework's own move is that the argument form is part of the problem.
- ▌ Stripe Best Practices · pdbjorkGuides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.
- ▌ MCP Server Patterns · pdbjorkBuild MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.
- ▌ Stripe Go Live Workflow · pdbjork bundleOperational workflow for taking a working test-mode Stripe integration to live AND for verifying an already-live integration end-to-end. Covers the Dashboard walkthrough, the "never see the live key" safety rule, the test-mode dry run, the live deploy ritual, and the Express/Node verify-the-pipes ritual. Load when a user says "go live," "flip to live," "launch payments," "we're ready for real cards," "real money now," "production time," "I need money," "verify the live Stripe pipes," "smoke test the checkout," or "show me money," or has either a working test-mode Stripe integration that needs to ship OR an already-live Express/Worker integration that needs end-to-end verification. Default assumption when a user says "go live" is wrong: the integration may already be live from a previous session. Always audit state first. Skip for API design questions, key-management theory, or pure code-review tasks — those are covered by `stripe-best-practices`.
- ▌
- ▌ Domain Availability Checker · pdbjork bundleUse when picking a brand name and you need to know which .com (or other TLD) variants are actually registerable before you commit. Runs concurrent whois lookups, retries on timeout, sorts FREE candidates first, and prints a clean table or machine-readable JSON/CSV. Safe and unattended — never touches registrar APIs or purchases anything.
- ▌
- ▌ AI Visibility For Small Sites · pdbjork bundleMake a small business website (solo founder, local service, niche SaaS, personal brand) discoverable and citable by AI search — ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews. Covers the schema.org JSON-LD scaffolding (Organization, LocalBusiness, Service, Offer, FAQPage), the "answer-ready content for buyer prompts" plan, the citation/reputation gap closer, and the validate-before-ship discipline (always re-parse every JSON-LD block you write). Load when the user asks about AI visibility, GEO (generative engine optimization), being cited by ChatGPT, schema.org / structured data, FAQ rich snippets, or wants to close the "AI says nothing about my business" gap. Skip for large enterprise SEO (technical sitemaps, hreflang, log-file analysis) — this is the small-team, no-Specialist playbook.
- ▌
- ▌ Public Good AI Commercialization · pdbjork bundleCommercialize public-good AI projects and reusable agent assets with ethical funnels, proof packages, landing pages, outreach, and fulfillment operations.
- ▌ Extend Existing Cron Not Duplicate · pdbjorkWhen the user asks for a recurring review cadence (weekly portfolio review, daily digest, monthly check-in) on a project that already has a cron job, ALWAYS inspect existing cron jobs first via `cronjob action='list'` and extend the matching job's prompt with `cronjob action='update'`. Never schedule a parallel cron that does overlapping work — duplicates the same data collection, double-delivers to chat, and complicates delivery semantics.
- ▌ Regulated Fintech Product Development · pdbjork bundlePlan and prototype regulated fintech products simulation-first without prematurely crossing banking, card, payroll, or money-movement boundaries.