Brand kit · logo · a month of posts

A month of posts, and not one over the limit.

Describe a business and get a brand kit, a vector logo, and a dated calendar of posts written separately for each platform — the same idea said differently, not one caption pasted five times. Approve what you want, bin what you don't, export the rest.

The captions are measured in code against the real limits before you ever see them. A 340-character X post reads perfectly well and is rejected by the API — and finding that out across thirty scheduled posts is a bad afternoon. Every date is computed too, because a month worked out by a language model is right almost every time.

The business

Your brief is used to write the plan and then discarded. Nothing is stored and the text is never logged.

The more specific you are — scale, place, what you actually make — the less generic the writing. Mention anything it must never say.

Where it posts

The schedule

What is written, and what is counted

The model writes

Positioning, voice, pillars, hooks, captions, hashtags, media briefs, and the logo as vector SVG — crisp at any size and editable, because that is what a logo should be.

Code counts

Every caption measured against its platform's real limit with hashtags included, because that is how the platforms count them. Over the limit is flagged, not shipped.

Code schedules

Dates and times are computed, spread across the week, and weekday-only means weekday-only. Times vary so a month does not all land at 09:00.

Nothing is projected

No reach estimates, no engagement predictions, no best-time-to-post. Those would be invented, and a plan that opens with a fabricated number is one you cannot trust the rest of.

The logo is vector because SVG stays sharp at any size and needs no image service. Photographic images and video for the posts are a separate, paid capability that needs a generation engine connected — worth a conversation if you want the whole pipeline rather than the plan.