We’re building Ever Works in public. Some things may be incomplete, missing, or broken while we continue improving the platform.We’re building Ever Works in public — expect a few rough edges.
Start from a strong base · In depth
Nothing in Ever Works starts from a blank page. There is a curated catalog behind every noun in the product: the code your site is generated from, the starter repository you fork, the playbook a Mission runs, the specialist an Agent is cloned from, the Skills that specialist knows, and the whole company you can import in a single step. This page walks all of them, names what is production-ready, and flags what is still a placeholder.
You rarely pick one by hand. A Work with no explicit choice resolves its base from your saved default and then from its kind, so a Website, Blog or Landing Page Work starts on web while a Directory or awesome-repo Work starts on classic. Switch a Work to a different base later from its Deploy tab, set one account-wide default in the Templates hub, and leave Update automatically on so an hourly pass pulls newer template code into your website repository — with main, stage and develop mirrored into your copy, and a beta channel on the bases that publish one.
The system default, cloned from ever-works/directory-web-template: search, faceted filters, item detail pages, categories and tags, comparison pages and community-PR submissions, on the App Router with Tailwind. It is the largest base, and the only one excluded from AI restyling for exactly that reason.
The same directory shape with as little JavaScript as possible: Astro static output, Preact islands only where interactivity is needed, and a plugin architecture in which SEO, pagination, filters, search, sort, sitemap, breadcrumbs, RSS, analytics and related items are each a plugin you switch on. Deliberately opt-in — it is never auto-selected.
For everything that is not a directory. It ships a complete landing page — hero, features, how-it-works, testimonials, pricing, FAQ and CTA — plus About, Pricing and Contact pages and a Markdown blog, with every string in one site config file so a rebrand is a single edit.
The same marketing section set, built statically with zero JavaScript by default and served exactly like the minimal directory. Copy lives in one site config file, and the theme is a plain-CSS surface an Agent can restyle for you.
Website templates are the code. These four catalogs are everything else you can start from — and one of them is honest about being half-built. AI customization is real but narrow by design: an Agent restyles a fresh copy of a base through a single plain-CSS theme.css, every other path it touches is discarded before the commit, and Sync from base later pulls newer template code back in — overwriting that styling, so you re-run the restyle on top.
Two built-ins are seeded on boot: Starter Directory (Next.js) and Starter Directory (Minimal) (Astro). Fork copies one into your own GitHub account or an organization you belong to and makes the fork your default in the same call; Add custom template registers any GitHub repository URL as a starter of your own.
Starter Business, for spinning up Ideas around a new venture, and Starter Content Site, for a recurring publishing cadence. Use this Template drops you on the Create page with the Mission chip selected and the prompt pre-filled, and the new Mission inherits the template cadence, guardrails and knowledge-base seed — every one of which your own values override.
A second, public catalog read from the ever-works/works manifest and offered in the Create-Work picker. Three entries are production today: Directory, Directory (Minimal) and Marketing Site. Company, Store, Blog, Landing Page and Awesome List are declared placeholders, and the picker filters them out until their builders ship.
Pre-built Task shapes — bug triage, weekly review, release checklist — with status, labels and sub-tasks already wired up, alongside your own workflow templates, which instantiate a whole parent-and-steps task tree in one action.
The Create-Agent wizard offers quick-pick chips and a View All catalog read live from the ever-works/agents repository. That repository is private, so the platform reads it through its GitHub App installation, or through a token on self-hosted installs; when neither resolves, the wizard quietly falls back to its built-in set rather than breaking — connect GitHub to see the full catalog.
PM, Coder, Researcher, Copywriter, Marketer, Sales SDR, Support, Curator, Growth, Designer, DevOps and Founder — the roles a small company actually needs. The catalog has since grown past them with planning and review specialists: Planner, Plan Reviewer, Plan Executor, Code Reviewer, Review Coordinator, Senior Dev, Spec Writer, Librarian and Generalist.
A SOUL.md identity, a .works/agent.yml manifest, a skills.yml naming the Skills it requires and recommends with a one-line why for each, a starter kb/ of playbooks and checklists, a prompts/ folder holding the system prompt, a README and an icon.
Every template declares whether it runs across the whole tenant, inside a single Work, or on a Mission. A Researcher can serve everything you own, while a Curator or a DevOps Agent stays bound to the one site it looks after.
Content Marketer, SEO Auditor, Lead Researcher, Outreach Drafter, Social Scheduler and Competitive Analyst arrive fully specified rather than as catalog metadata: activating one writes an ordinary Agent with its system prompt, permissions and guardrails already set.
A template gives an Agent an identity. Skills give it know-how — and a company package hands you the entire org chart at once.
Skills come from the public ever-works/skills repository as plain SKILL.md files — YAML frontmatter plus instructions, in the open agentskills format — and every row carries its license and source URL for anything adapted from upstream. The first-party provider is on by default, caches the catalog for an hour, and falls back to a small built-in set if the repository is ever unreachable.
Lead research, competitor watch, news-signal detection, lead scoring, risk filtering, outreach personalization, newsletter drafting, social scheduling, digest compilation, CRM-sync hygiene, follow-up cadence, reply detection, contact enrichment, SEO audit, campaign reporting and engagement analysis. Each one declares the data it reads, the data it produces, and the tool families it expects to be granted.
New skill starts from a template or from scratch, scoped to your tenant or to a single Mission, Work, Idea or Agent. A Skill can carry companion files — scripts, references, configs and assets — and every Agent has its own Skills tab, so binding know-how to a specialist is a checkbox rather than a copy-paste.
The public ever-works/orgs catalog holds more than thirty ready-made organizations: Ever Starter Co with 8 Agents, 2 teams and a first-launch project, Atlas Engineering, creative agencies, research institutes, security review boards. Importing one materializes the organization, its teams, its Agents — paused, so you review before anything runs — its skills, and a starter project with real tasks already written.
Five steps, in the order you will meet them — the last one hands your catalog choice to the loop.
Sidebar → Templates, then the Website Templates, Work Templates or Mission Templates pill. Every card carries a Built-in or Custom badge, its origin — Standard, Forked or Custom URL — and the branch, sync branches and beta branch it is wired to. The Active default stat at the top names the base every new Work starts from; ⋮ → Make default moves it.
Fork on a built-in card asks for a destination — your personal account or an organization — then forks the repository and makes it your default. Add custom template takes a GitHub repository URL and fills in the name, framework and default branch you leave blank. On an AI-customizable base, Create with AI provisions a fresh repository from it and runs the restyle.
Sidebar → Teams → Agents tab → + New Agent. The quick-pick chips cover the common roles and View All opens the full repo-backed catalog, where each template shows its role, its scope and the Skills it wants before you create anything.
The Skills block sits at the bottom of that same Agents tab, with Installed, Available and Custom tabs plus Browse templates and New skill. Skills a template marked required are attached and locked when the Agent is created; recommended ones arrive pre-checked and are yours to drop.
Make your chosen base the account default from the Templates hub — ⋮ → Make default, confirmed by the Active default tile — then create a Mission, give it a five-field cron and switch on Auto-build Works from spawned Ideas. Every Idea that Mission spawns is then built from that template into a repository you own, inside the Mission’s spend cap: the catalog choice stops being where you started and becomes the shape of everything the loop ships. One switch comes first — the Work agent gate is off on a new account, and until it is on a tick queues Ideas that never become Works.
Every Work is generated from a template — production-grade Next.js and Astro bases — so you never start from a blank page.
Learn more →Named AI employees — a CEO, a CTO, a Researcher — that run your Missions, Ideas, and Works around the clock.
Learn more →Author recipes the runtime can execute. Reusable, versioned, your library of agent know-how.
Learn more →Group Agents and people into nested teams, assign the Works each team owns, and see the whole organization — humans and AI — on one chart.
Learn more →A generated Work is a real application — auth, payments, search, maps, 21 languages, SEO, feeds and a Git-based CMS — not a page-builder export.
Learn more →The buildable unit — websites, blogs, directories, landing pages — researched, written, coded, deployed, and kept fresh.
Learn more →Give Ever Works an ongoing goal and it keeps generating ideas and building toward it — for as long as you let it.
Learn more →One-shot builders generate a site and stop. Ever Works keeps researching, writing, building, and improving — on a schedule.
Learn more →Describe what you want to build. Ever Works researches it, ships it, and keeps it improving — content and code, owned in your own Git.