01 — What I Did and Why
The 30-Second Story
I built the Undeniable Claude Skills Library: 36 matching pages on my website, each one sharing a Claude skill I use in my business. I started with 2 pages built by hand and 30+ more sitting in my Claude, already created, already used, just invisible to the world. Building the pages one at a time meant weeks of repeat work. So I spent one day building the system that builds them. Three days later the whole library was live, and it now grows every time I type one line.
The thinking underneath it: there is no difference between me doing it for me, me doing it for my clients, and me doing it for someone who just found me. It is one connected system. I build it for myself first, which is why it works. Then I flip it around and hand it to you.
Why it lives on MY website: I want to own the asset. I watched a 500,000 person AI community get deleted off a platform overnight. Platforms change rules, algorithms shift, and rented land gets taken back. Your library on your domain is yours forever, and every entry stacks authority onto the entity that matters: you.
The Tech Stack I Used
Claude
The thinking partner. Designing, writing, critiquing, deciding.
Claude Code
The builder. Writes the pages, publishes them, verifies they work.
GitHub
Where my website files live.
Cloudflare Pages
Publishes the site automatically every time the files update.
Google Analytics (GA4)
Tracks the clicks that matter on every page.
Your stack can look different. The method works with any AI and any website setup. This is exactly what I used, so you can copy it move for move.
02 — What You Get at the End
Four Assets, One Connected System
Each of these is a standalone win. Together they compound, because the library feeds your authority, your authority feeds your list, and your list feeds your offer.
A Live Library
A hub on your website with matching entries people browse, use, and share. This is your knowledge made visible: every entry is a credibility stack that says this person has receipts.
A Master Template
Your best entry, extracted into a reusable structure. Here is the part I want you to feel: I spent more time on the design of the template than on everything else combined, because if we are going to do something once, we do it into perpetuity forever.
An AI Publisher
A repeatable process that writes, builds, and publishes a new entry from one line of instruction, carrying your standards every time. New knowledge in your world becomes a live page without the build ever touching your calendar.
A Scoreboard
Google Analytics tracking on the clicks that matter, reported to you weekly. I refuse to build parking lots. If it exists, it reports, and the market tells me which entries to build next.
03 — The Five Moves
The Whole Method At A Glance
Design Your Library
→
Build One By Hand
→
Turn It Into A Template
→
Teach AI To Publish
→
Make It Compound
The question that starts everything: where in your business do you have a library of assets you could build once and spin up many times? Client FAQs, onboarding docs, tool guides, teardowns, SOPs, frameworks. You are probably sitting on yours right now, already created, already used, just invisible to the world.
The big version is never one big build. The big version is one, one, one, one, done on the same template, and the system does the counting.
04 — Move 1
Design Your Library
Answer four questions in writing before you build anything. Ten minutes here saves you weeks later.
The Four Questions
•What collection am I building? (skill pages, client playbooks, teardowns, templates, guides)
•Who is it for?
•What does it feed? (your email list, your program, your offer)
•How do people flow through it?
The Four Parts Every Library Has
•Front door — one URL where new people enter and give an email
•Hub — the browsable index of every entry
•Entries — same structure every time, fresh substance every time
•Offer — one call to action on every entry, pointing at the thing you sell
The discernment call on gating: give your best stuff away. Gating everything protects content most people never finish anyway, and it costs you the organic reach and authority that are the whole juice. Gate the front door once, keep every entry open and indexable, and let the 1% who devour everything come find out what working with you is really like.
Nuance: Design the entry so using it takes seconds. Copy, paste, done. Zero downloads, zero zip files, zero Google Drive links. Friction is a tax on every future visitor, and you set the rate on day one. Same with naming and URLs: pick them now, because renaming twelve live entries later is a tax too.
05 — Move 2
Build One By Hand
Build a single entry manually, all the way to live. Full attention, no shortcuts. This one entry sets the standard everything else inherits.
Then Run The Critique Loop
1
Look At It Like An Editor
Look at your live entry like a world-class editor.
2
Say Why Out Loud
Every time something feels off, say WHY out loud.
3
Turn Each Why Into A Rule
Turn each "why" into a written rule ("FAQs answer real questions people search" · "One CTA, written for whoever is on this page" · "Headlines lead with the outcome").
4
Fix And Repeat
Fix the entry, repeat until it feels world class.
Expect 3 to 4 passes. Your rules list is the real asset. The entry is proof the rules work.
Nuance: You cannot automate what you have only done in your head. Building one deliberately, by hand, is what makes everything after this trustworthy.
06 — Move 3
Turn It Into A Template
Split your finished entry into two piles, then extract the template.
Pile 1 — What Repeats
The structure, the design, the section order, the CTA. This becomes the fixed template.
Pile 2 — What Gets Created Fresh
The headline, the substance, the examples, the FAQ. These become fill-in slots.
The Prompt To Run
in Claude Code or Claude, pointed at your best entry
Turn this entry into a reusable template. Keep everything structural exactly as is: layout, design, section order, and CTA. Replace every piece of entry-specific content (headline, body substance, examples, FAQ) with clearly named fill-in slots. Document every slot at the top of the file so a future session knows exactly what to create for each new entry. This template is now the single source of truth for every entry in my library.
Two Rules That Make The Template Work
•The template is the single source of truth. Improve it once, every future entry inherits the improvement.
•Nobody hand-edits a published entry. Change the template (all entries) or change one entry's slot content (one entry), then regenerate.
Design the universal change in from the start. I knew I might want to update all 36 pages someday: a new CTA, a new section. So the template was built so one edit plus one command updates the entire library at once. If we are going to do something once, we do it into perpetuity forever. That is why I spent more time designing the template than on everything else.
Nuance: Save each entry's slot content in a file next to it. Every entry becomes rebuildable, and a change across your whole library costs one edit and one command.
07 — Move 4
Teach AI To Publish
Turn your manual build into a repeatable process AI runs end to end. Your standards go INSIDE the process, so every entry carries them automatically.
The Prompt To Run
I just published an entry to my library manually. Turn that exact process into a repeatable publishing skill. When I say "publish [entry name]," you: write the fresh content for every template slot following my written rules, fill the template, publish the page, add it to the hub, and verify it is live. My rules are law: [paste your rules list from Move 2]. If any step fails, stop and tell me exactly what blocked it.
Then Scale Trust The Way I Did: 1, Then 1, Then 5, Then 8
Where AI fails is when you ask it to write the book overnight. Hand it 50 chapters at once and quality slowly degrades while you sleep. So earn the scale instead:
1
Publish One From The Template
with a review stop before it goes live. Read it like an editor. Every correction becomes a permanent rule.
2
Publish One More
Clean? The template and the rules are proven.
3
Release To Batches
of five to eight, no stops, reviewed after shipping. Each batch earns the next one.
4
Promote Every Catch
When you or the AI finds a miss, add it to the rules immediately. The system publishing entry 30 should be smarter than the one publishing entry 3.
Nuance: Fixes stay cheap because nothing is hand-edited. See something you want changed after shipping? Edit that entry's slot content, regenerate, done.
08 — Move 5
Make It Compound
Four choices, baked into your template once, inherited by every entry forever.
FAQs Answer Real Questions
This is the part that stuck me, and I went through it five times before it clicked: nobody is searching your framework's name on day one. Write the questions a real person deciding to use this would actually ask. How do I know if this applies to me? How long does it take? What do I need before I start? Real questions earn citations from AI answer engines, and your terminology rides along inside the answers.
One CTA, Tuned
Write the call to action for the exact person on that page and what they just did there.
Link Sideways
Every entry points to a related entry. This is internal linking, and it helps with AEO: answer engines and search engines read a connected world instead of orphan pages, and visitors go deeper instead of leaving.
Track The Click That Matters
Find the action that means someone actually used the entry (a copy button, a download, a template grab) and fire a Google Analytics event on it. I track every copy button, Studio click, and related-entry click across all 36 pages in GA4, feeding a weekly report. I refuse to build parking lots. If it exists, it reports.
Nuance: Kill every number you would have to remember to update. A stale "12 entries!" counter reads as neglect. Live numbers or no numbers.
09 — The Nuances That Make It Click
The Small Rules With Big Compounding
Asset First, Sequence Second
People get overwhelmed thinking they need the email automation, the nurture flow, and the funnel before they start. Build the asset first and get it live. Then bolt on a simple three-email value sequence behind the front door. The library works day one. The marketing engine gets added in an afternoon.
Guard Your Private IP
Decide what never publishes: client work, licensed material, your internal systems. Write the list into your publisher as a hard stop, so nothing leaks on an autonomous run.
Brand IP Only On The Front Door
Every entry should be provably yours: your frameworks, your language, your proof. Generic filler dilutes what the library says about you. When in doubt, leave it out.
Batch In Order, Review After
Publish batches one entry at a time so the sideways links build as you go. Review the report after shipping. Post-ship review works because regeneration makes every fix cheap.
Tell The Story
The AI publishes the entries. Only you can tell the story of building it, and the story is the proof that sells everything else. Capture the receipts while they happen.
10 — The Receipt
How Hard Was This? It Was New, And That Is Different From Hard.
I built the entire 36-page library in three days, and here is the honest part: I never got a five-hour block to work on it. I got 10 minutes here, 37 minutes there, 9 minutes between a jungle gym trip and lunch with my wife. The system did the heavy lifting inside those pockets, including publishing 7 entries while I slept.
2 pages became 36. Every one carries the same structure, the CTA, the internal links, the tracking. I impressed myself, and that is the standard I want for you: the moment you look at what you built and say I cannot believe I just did that, your belief ceiling moves.
11 — Where To Start
Your First Library Is Already Started
Find the thing you have made three of by hand. Three client onboarding docs. Three teardown posts. Three proposal templates. The third manual build is the signal: the standard is already in your head, and Move 2 is basically done.
Then run it through this lens: what would the 101, 201, and 301 of your world look like? The questions every brand-new client asks. The systems you install once they start. The advanced plays for the ones going deep. That is a library map, and you already know every answer in it. Run the five moves on it this week.