Tagged · 24 notes
Everything tagged Workflow, wherever it's filed, newest first.
Stitch a folder of Markdown or text chapter files into one full manuscript, in the right order, with a title block and a word count that's never out of date.
Thread: Tools for the writing desk ↗When a long back-and-forth with an AI finally lands somewhere good, the method is worth more than the answer. How I pull the method out and turn it into a prompt I can run again.
Thread: Building with Claude and MCP ↗Badges is a small Obsidian plugin by gapmiss that turns a bit of inline code into a colored label. What it does, the few conventions I settled on, and the parts of my setup that are still on the to-do list.
The Truth Prompt pushes a model to stick to what it can support, say "I cannot confirm this" out loud, and check itself for fabrication, which helps most when web search is on.
Thread: Changing how the model answers ↗My DevOps reference note is a stack of prompt cards for everything from repo setup to installers. Condensed: which cards earn their keep for one person, what to watch in each, and the order I'd run them.
Thread: Dev habits for a team of one ↗Get a word count for every chapter file and the whole manuscript, from Markdown, plain text or .docx, with a running total and a progress bar toward your target.
Thread: Tools for the writing desk ↗A widely shared prompt that turns an app idea into a full spec you can hand to a no-code builder, plus the quick version for ideas you just saw in a post.
Thread: Prompts for plans, apps and side hustles ↗What I set up before writing a line of theme or plugin code: a local copy, the debug switches, WP-CLI's scaffolding and a profiler. Condensed from a very long page of old notes.
Thread: The WordPress toolbox ↗Execution Mode is a circulating prompt that cuts the pleasantries, apologies and hedging so every reply starts with the answer and stops when it's done.
Thread: Changing how the model answers ↗A custom slash command is a saved prompt you run with a slash. How they work in Claude Code now that they've been folded into skills, and which of the ones in my notes actually have a job.
Thread: Building with Claude and MCP ↗My old notes had a pipeline that wrote and published WordPress posts on a schedule. What I'd keep from it, what I'd throw out, and how I'd use AI for a client's site copy now.
Thread: Building a site for someone ↗My notes on safe updates were written for a big team with canary releases and approval chains. Here's the same idea cut down for one person with a project that still has to work tomorrow.
Thread: Dev habits for a team of one ↗A small Python script that stitches Markdown chapters into a single clean HTML book with a title page, linked contents, chapter breaks, curly quotes and proper scene breaks.
Thread: Tools for the writing desk ↗My old CLAUDE.md template tried to hold everything. The one that runs this blog is about twenty lines. Here's where the file lives, what earns a line in it, and what doesn't.
Thread: Building with Claude and MCP ↗Move CBZ and CBR files, or whole series folders, into genre or decade folders using a series list you keep in a spreadsheet, then list what didn't match and check nothing went missing.
Thread: Keeping a media library tidy ↗One founder, a Delaware C-Corp, evenings and weekends, and a codebase with more lines of tests than lines of code. Here's what that ratio says about how I build.
Thread: Building G8KEPR ↗The folder layout, the one config file, and the handful of checks I want in a Python project before the first real line of code. Plus where my notes had fallen behind the tools.
Thread: Dev habits for a team of one ↗Write the folders you want as an indented outline, or paste the output of tree, and create the whole structure in one go without moving a single file.
Thread: File wrangling ↗How I keep score on G8KEPR with a feature scorecard graded 0 to 10, why it leaves out anything about clients or partners, and the P0-P4 lists that decide what I work on next.
Thread: Building G8KEPR ↗My build loop for G8KEPR: a plan in Todoist, a tracker page, three DEV briefs, and three Claude Code windows working in parallel while I supervise until it's done and tested.
Thread: Building G8KEPR ↗The seven phases and thirteen milestones I plan a website around, the sign-offs between them, and why I don't put week numbers on any of it until the discovery answers are in.
Thread: Building a site for someone ↗Every G8KEPR task list runs from "P0 — Blocks belief/purchase" down to "P4 — Polish". Why belief is the right word for a security product, and how it keeps a solo founder honest.
Thread: Building G8KEPR ↗The questions I work through before building a site for someone, grouped the way I keep them, with the handful that actually change the build pulled out on their own.
Thread: Building a site for someone ↗The short list of WP-CLI commands worth knowing by heart, the few that bite, and what I fixed in my own old notes after checking them against the current docs.
Thread: The WordPress toolbox ↗