A read-only archive of iterate's former monorepo, kept for reference. The platform, SDK, apps and templates now live in smaller public repos that you can read or self-host from.
Clone the repository
$ git clone https://github.com/iterate/iterate
This was iterate's monorepo from September 2025 to 2026-10-02. It's now a read-only archive: about 3,100 commits, every pull request and issue, and the code as of that day.
iterate is now developed in one private repo, iterate/private, which only the iterate team can see. Parts of it are copied, one way, to two public repos:
core/os), the iterate SDK and CLI (core/lib), and the project templates every build offers (core/configs). Start here to self-host.packages/ui), and the templates that use them (configs/).Paths match: core/os/src/... here is core/os/src/... in iterate/core. The rest (internal-packages/, test/, scripts/, docs/, tasks/, CI) isn't copied, so this archive is its last public version. A few apps have repos of their own, like iterate/kit and iterate/mobile.
We're following a setup to similar to Ryan Dahl's for celld: the public repo is a lean export, and the tests, CI, ops scripts and working notes live in a private repo. Agents running on iterate read iterate/core to understand the platform they run on, and a small repo is easier to read than this one.
https://pkg.pr.new/iterate/iterate/...) stop updating, and pkg.pr.new removes old builds after a while. New builds are at https://pkg.pr.new/iterate/private/....The last commit here renames the CI folders to .depot.archived/ and .github.archived/, so nothing in this repo runs, but you can still read how it was wired. Licenses are unchanged: AGPL-3.0 (LICENSE), except folders with an Apache-2.0 LICENSE of their own (the SDK, the packages and the templates).
Stars on GitHub
Helps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
@mattpocockA development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraGives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
@affaan-mDeveloper tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
@facebookA read-only archive of iterate's former monorepo, kept for reference. The platform, SDK, apps and templates now live in smaller public repos that you can read or self-host from. Install it with the command on its page. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it