A finished site, not a shell
Sitify is an agent skill and a website template in one folder. You say what the site is for. The agent reads the manual, copies the template, brands it, composes the pages from a catalogue of finished sections, writes the copy in every language, draws the social cards and ships it.
A working copy, not a library
The template is copied, never installed as a dependency. Two sites built from it diverge, and that is the point: a fix in one is a deliberate copy into the other, never an automatic upgrade that breaks a live client site at 3am.
Sections in the catalogue
Finished, not sketched
Categories
Openers, content, data, maps, schemes, brand
References
Intake, branding, copy, media, search, deploy, upgrade
Tools covered
Claude Code, Cursor, Codex, Windsurf, Antigravity
The order it gets built in
The skill walks the agent down a fixed route rather than guessing. Composing pages before the colour is set means rebuilding every section against a palette that changed underneath it. So the steps are numbered, and they run in order.
Interview
One batch: what the site is for, who reads it, the domain, the colour, the fonts, the languages. Everything but purpose and audience has a default.
/02Copy and run
The template is copied and renamed in four places. Then confirm the homepage renders, before touching anything at all.
/03Brand
Seven colour tokens, four font variables, the logotype and the icon. Nothing else in the source names a colour or a typeface.
/04Shape
One page or several, how many languages, which one sits at the root. Redoing this later is the most expensive change there is.
/05Compose
Pages come out of the catalogue. A section is taken whole, every prop with it, and only the strings change.
/06Write
Every string in every language. No invented figures, no full stop ending a display heading, no lone last word in a line break.
/07Media and search
Images compressed by one command, one hue per section. Then meta, sitemap, llms.txt and the social cards.
/08Verify and ship
Types, build, both themes, three widths, contrast, console, tab order. Then a push to main, and one machine on Fly serves the site.
Twelve references, read one at a time
The skill is not one long prompt. The entry file holds the route and the detail sits in separate documents, loaded only when the step needs them. The agent does not spend context on deployment while it is writing a headline.
Intake and route
What to ask the client, in what order, and what to take as the default when no answer arrives
Brand and type
Colour tokens, four font roles per writing script, the logotype and the favicons
Sections and shape
Page shape, the rhythm of light and dark blocks, and five rules that have each been broken
Copy
Voice, density, the ban on invented figures, and the cure for a lone last word in a heading
Search and deploy
Meta, sitemap, llms.txt, social cards drawn from real titles, and a deploy on one machine
Between a builder and a studio
A site builder is fast and its ceiling is low. A studio will build anything, in months and for a different budget. Sitify sits where the speed of a template meets code you can open and edit.
The top left is empty
Fast and fully open at once is rare, because speed is usually paid for with a closed platform. Here you get a folder of files rather than an account.
The template knows what a correctly built section looks like, and the skill knows what order to put them in and what to write in them
Grid and layout
Four columns
The guides are drawn on screen and everything sits on them: a half-width zone is two columns, and every cell pads inward. An arbitrary width is visible immediately.
Light and dark
Sections alternate tone on purpose: a dark block marks a change of subject. It is the house language, not a fault to flatten into one tone.
Hover everywhere
A card, row or step that does not react to the cursor reads as unfinished. Everything in the catalogue reacts.
Languages
One registry, one truth
Add a language to the registry and the type check lists every remaining hole as an error. That list is the translation checklist.
Right to left
Sections use logical properties, so an Arabic locale flips the whole layout. Arabic and Chinese are pre-wired and only need switching on.
A locale is not a fallback
An untranslated page 404s in its own language instead of showing English. A half-translated site is a site with holes.
Search and shipping
Cards from real titles
A script walks every route, takes the title that route actually sends and draws the picture. A card cannot show a title the page no longer carries.
llms.txt
One screen: what the company does, the key pages, the contacts. An assistant reads it instead of crawling the site.
One machine
A push to main deploys to Fly, and the workflow refuses to deploy while the app still carries the template name.
The week of work that usually follows a launch
Everything below works the moment the template is copied. This is not a roadmap: each line is built and checked on a live site rather than described in a README.
Dark theme
Both themes plus system, with no wrong colour flashing on load
Two languages
One at the root, one under a prefix, a switcher and a cookie that remembers
Meta and sitemap
Canonicals, hreflang, sitemap, robots and JSON-LD
Social cards
Static PNGs, one per route per language, in the brand colour and mark
Self-hosted fonts
Woff2 in the repository: the build does not fail when a CDN does
Image pipeline
One command resizes, strips metadata and skips what is already current
Request form
In the footer, so on every page: every call to action scrolls to it
Deploy to Fly
Dockerfile, workflow, and one machine instead of the two Fly starts by default
One payment, no subscription
Fifty per cent off until the end of the month. The timer starts again on the 1st. Prices are in US dollars; taxes and payment methods depend on your country.
Fifty per cent off until the end of the month
The clock counts down to the 1st
One person building sites for themselves and their clients
One time payment
- The skill and the template in full, around 390 files
- A catalogue of 62 sections across 13 categories
- Twelve references: intake, brand, sections, copy, media, search, deploy, upgrade
- Install steps for Claude Code, Cursor, Codex, Windsurf and Antigravity
- English and Russian out of the box, Arabic and Chinese pre-wired
- The social card generator and the image pipeline
- Dockerfile and the deploy workflow for Fly
A team or a studio shipping client sites one after another
One time payment
- Everything in Personal
- A team licence; the number of seats is set in the contract
- A written review of one build of yours
- How to generate your own edition under a different name and domain
- The procedure for syncing the template between sites
- Priority on questions about a build
The product is delivered as an archive over a link. What is included, the licence terms, and how refunds work are set in the contract; ask before paying and the answer comes in writing.
What people ask first
Both, and neither half works alone. The template is a finished Next.js site with a catalogue of sections. The skill is the manual that tells an agent how to turn that template into one specific site: what to ask the client, what to change first, what to check before calling it done.
Where to write
Questions about what is included and about the licence get a written answer. If you are not sure your project counts as a marketing site, describe what you need. Hearing "not our case" is faster than asking for a refund.
Buying
( Email )
buy@sitify.ru
( Tell us )
The plan and the country to invoice
Questions
( Email )
hello@sitify.ru
( Blog )
www.sitify.ru/en/resources