My File System Was a Disaster. Here's the One I'm Building to Replace It. I want to be upfront about something before I get into this: what follows is not a finished system I've been running for years and am now generously revealing to you. It's the system I'm actively building right now, because the old one finally broke under its own weight. Here's what broke it. I went looking for a cover concept file from an earlier book. It wasn't in the book folder. It was in a "Graphics" folder from eight months ago that also had three other books' covers in it, none labeled clearly enough to tell them apart at a glance. The marketing copy for that same book was in a completely different folder tree, because I'd started using a new tool partway through and never went back to reconcile the old stuff. Fifteen minutes of searching for one file I knew existed. That's the tax you pay for not deciding on a structure up front, and I'd been paying it quietly for a long time. So I sat down and asked the obvious question: what's actually going in these folders, and what's the smallest set of rules that keeps it findable six months from now when I've forgotten the details? The core idea: Projects is the top, then everything nests by type Books aren't the only thing I'm keeping track of. There are coding projects, there's a growing pile of AI prompts and skill files, there are short stories that don't need the full novel treatment, and there's a permanent junk drawer of half-formed ideas that aren't committed to anything yet. Trying to organize all of that around "books" was the first mistake, because a lot of my actual work isn't a book. So the true top level is just **Projects**, full stop. Not around the tool that made something, not around the date, not around whether it's "writing stuff" or "marketing stuff." Whatever kind of thing it is, fiction or code or a stray idea, it lives inside its own project folder, not scattered across whatever pile happened to be open when I made it.

Stop Guessing at Your Comps — Reverse-Engineer Them Instead Topic: Using Book Reporter (CONAN) and Series Reporter (SONJA) to forensically analyze comp titles before you write a word of your own story The problem this solves Most of us pick comp titles the same way: we read a book we loved, we feel something, and we say "I want to write something like that." Then we sit down to plan our own story and realize "like that" was never actually specific. Was it the pacing? The trope execution? The voice? The way the series built across four books instead of one? Vibes aren't a blueprint. If you can't name exactly what a comp title is doing — structurally, at the sentence level, across its beats — you can't reliably reproduce what made it work, and you definitely can't improve on it. That's what Book Reporter and Series Reporter are for. They're the forensic layer of the Professional Writing System — the tools you run before Phase 1 (Story Development Room) to turn "I want something like this" into an actual architecture you can build from. The two tools, and how they're different Book Reporter (CONAN) analyzes one book. He reads it the way a mechanic pulls an engine — not to admire it, but to understand exactly what's load-bearing and what's cosmetic. He produces a Forensic Morphology Report: 15 layers covering structure, character architecture, prose voice, world-building, tropes, emotional design, and hooks, plus: A Beat Rhythm Map — a chapter-by-chapter tension chart that shows you exactly where the book accelerates, where it breathes, and where it stalls (dead zones, flagged by name) Genre Beat Benchmarks — where this book's inciting incident, midpoint, dark night, and climax land as percentages of total length, compared against genre norms A Prose Quality Score Card — eight dimensions scored 1–10, so "the writing is good" becomes "voice distinctiveness is an 8, but foreshadowing/payoff execution is a 4, and here's why" A Reconstruction Brief — the condensed DNA of the book (genre, structure, archetypes, thematic argument, world type, tropes) formatted to drop directly into Story Development Room, plus 2–3 original seed concepts that share the book's structural DNA without copying it

I'm Michael. I built the Professional Writing System and WordCrafter Pro after spending years trying to wrangle AI tools into something that actually helps writers write better stories — not just faster ones. The Professional Writing System is a set of Claude skills to help you as authors get the words out and get published. Each skill has a group of personas who are experts in their field that let you discuss your book not order the AI to do your bidding. They help you work out ideas, build the story Bible & outline, design believable characters, write your story (with help not write for you), and edit the work afterwards. The Merch and Marketing skills step in to help you build products around your story and sell it (the most important part) WordCrafter Pro is the latest in AI Writing Aids that has the entire PWS System baked in. Here in a scrivener styled interface you can organize all of your pieces together, control your context windows, get help when needed and get the stories published! With this system you never have to write alone again. You can even talk to the persona's individually ***** What you've walked into is the community hub for everything PWS: the skill files, the app we're building, the classes, the challenges, and most importantly, the other writers doing this work alongside you. Here's what to do right now: 1. Introduce yourself in the Introductions category. Tell us your name, what you write, and your biggest creative challenge right now. 2. Grab the free PWS Quick-Start Guide at [this link] It explains the four-phase system and shows you exactly where to start. 3. Browse the Start Here posts. The PWS Overview explains all four phases. The Community Rules are short and worth reading. This community is free and always will be. A paid Inner Circle tier is coming for writers who want deeper access, but everything you need to use the system lives here at no cost. the skills themselves and the PWS Studio App I'm developing will have a cost, but if you are reading this there will be a huge discount.