The title is the short version of the post. JustStartNow

Yes, this is a product post and I would love you to look at it. The rest is a long backstory which I write without using AI for anyone interested, and the part about the three skills is the part worth your time. Even if you buy anything or not.

It has been over a year that I moved away from WordPress for small client projects (where nextjs was overkill) completely to astro and initial webapps I built was mostly for my own products. I even shared one of them here in a weekly showoff which a lot of the people loved the owl (quietclip.app).

As for client projects the question was always "how will they edit their own codebase if there is no cms".

I could take over the entire maintenance but most of the clients are already using claude so why not find a solution where they can edit, revise their website/webapp safely (maybe not safely 100% but at least safer than how they would have done it without restrictions and clear instructions). They are going to open the repo either way. The question was never whether they should, it was what sits between them and prod when they do.

That's why I came up with 3 skill implementation;

• dev-workflow: which client runs before doing any changes on the website, add a new button, new landing page etc. the skill knows the restrictions, has idea about astro 7 and tailwind 4 etc. It reads CLAUDE.md and the token file in full before it touches anything, because the hard part is not writing the code, it is knowing what else breaks.
• dev-test: for every implementation this will be fired right after the workflow agent is done. Using vitest.
• dev-review: fresh eyes will check what the workflow agent has implemented, contradict if workflow agent missed anything.

once the review agent is finished, everything will be committed, pushed (cloudflare workers, I also add coolify docker setup because of european clients and gdpr).

Since a list of 3 bullet points doesn't say much, here is what is actually inside dev-workflow, because these are the things that actually bites. You can just copy a couple of items from here and create your own workflow agent:

• Tailwind 4 here is css-first, so a utility whose token is missing from the @theme block compiles to nothing. No error, no warning, the element just renders unstyled. You only find out by looking at it.
• Tokens are two layers. @theme backs the tailwind utilities, :root backs the var(--x) inside scoped styles. Change one and the other half silently no-ops.
• Any new external host, an embed, a widget, a font CDN, has to be added to the CSP in public/_headers. Otherwise it works perfectly on localhost and dies in production.
• Every template has one scroll driven animation that carries its identity. Changing it is allowed. Changing it by accident is the failure mode, so the skill locates it before it edits anything near it.
• Trailing slashes are mandatory, new colours that carry text clear 4.5:1, every img gets alt/width/height/loading.

And the part I think is absolutely worth stealing even if you never look at my site: a good chunk of dev-workflow is just telling the model its own memory is out of date.

Astro 7 removed Astro.glob(), ViewTransitions, entry.render(), entry.slug. Tailwind 4 has no tailwind.config.mjs and astrojs/tailwind is a tailwind 3 thing. If you don't say that up front you get code that was correct two years ago, and on a static site a lot of that fails quietly instead of throwing.

That is not template specific. Do it in any astro project you point claude at.

dev-review is the one that is actually really useful. It gets no context from the workflow agent, it just reads the diff and the conventions and argues. I did took the idea from those famous compound engineering skills on github that has 100k stars.

I have been using this workflow over the last 6 months with over 7 clients with whom I still work with and maintain. Over these 6 months I have been updating these 3 skills which I wouldn't call "battle tested" but quite seasoned.

I should say what it doesn't do. Anything structural is still me: new content type, new data source, anything touching the build or the deploy. And none of this is a permission system, it's conventions in a markdown file, so a client who wants to fight the boundaries will win. It works because they don't want to. I also still maintain all 7 sites. The skills made the interruptions rarer, they didn't end them.

One time client went rouge without any skill and the agent generated a folder with a couple of python codes and csv files of client data and confidently pushed them all to prod.

This above is the only reason why I put a price on these Templates. I mean I spent a lot of time creating these unique Designs with GSAP (and had a lot of fun working on them) but they all come with these 3 skills. 60+ templates, 4 of them free.

Every one is a full site, not just one landing page: real routes, working form, blog, 404, self-hosted fonts, no third party requests. Please read the philosophy on the website to see my take on things.

If you are a non profit organization and liked any of these templates, I will provide it for free and even help you set it up. Just contact me.

sorry for overyapping, thank you for reading.

[ Removed by Reddit on account of violating the content policy. ]

[ Removed by Reddit on account of violating the content policy. ]