CodeGuide
CodeGuide turns a plain-English project description into a full documentation set, covering product requirements, technical architecture, wireframes and an ordered task list, then feeds it to AI coding tools such as Cursor, Claude Code, Lovable, Bolt and v0.
What is CodeGuide?
CodeGuide presents itself as spec-driven context for AI coding: a specification layer placed upstream of the tools that actually write the code. Its diagnosis, set out in its own FAQ, is that a one-line prompt leaves the model guessing, and guessing produces hallucinations, odd assumptions and missing features that then cost hours to unpick. The site sums this up by calling CodeGuide a translator between your idea and AI coding tools.
The flow shown on the home page has five steps: write a project brief, choose the AI tools you intend to build with, answer the clarifying questions CodeGuide asks back, review the project plan, then create the documents. What comes out is a documentation kit rather than a single file: product requirements, technical architecture, frontend guidelines, backend and database design, wireframes and a task list. The site claims this covers 95% of what AI coding tools need, with custom documents available for the remaining 5%, and the result is meant to serve as a knowledge base the assistant consults at every step.
Compatibility is the second pillar. The specifications can be attached to an IDE or CLI agent in one command, Cursor, Claude Code, Cline, GitHub Copilot, Antigravity and OpenCode among them, and pushed into AI web builders such as Lovable, Replit, Bolt, v0 and AI Studio through a Chrome extension, version 0.3.3, updated on 5 February 2026. Existing projects are covered too: legacy code is a black box to AI, so CodeGuide maps the GitHub repository first, then writes specifications for new features that fit the architecture found there. Six open-source starter kits, built on Next.js, Tailwind and TypeScript and paired with Supabase, Firebase, Clerk, Drizzle ORM, Expo or Vite, exist so that no tokens are burned on scaffolding.
Beyond documentation, the platform advertises Software v2, an autonomous coding agent with a unified interface over CLI tools, a model router, more than 200 announced models, a UI editor with comments and parallel agents, offered in early access on the Founder plan only. Traction claimed on the site is 41,450+ developers on the home page and 40,000+ users in the FAQ; the animated result counters shown alongside them carry no readable value.
What it does
- Turn a project described in plain English into a complete project blueprint.
- Generate product requirements, technical architecture, frontend guidelines, backend and database design, and an ordered build task list.
- Generate screen wireframes and design prototypes.
- Analyse an existing GitHub codebase and produce its documentation.
- Write specifications for new features that respect the architecture already in place.
- Run an autonomous coding agent for hours through Software v2, its unified interface over CLI coding tools.
- Attach the specifications to an IDE or CLI tool in a single command, or sync the blueprint into an AI web builder through the Chrome extension.
When to use CodeGuide / When not to
A quick filter to help you decide if CodeGuide is the right fit.
When to use CodeGuide
- Founders who want an idea turned into a written plan, and then an MVP, without hiring a team first.
- Developers already working inside AI IDEs and CLI agents (Cursor, Claude Code, Cline, GitHub Copilot, Antigravity, OpenCode) who want the assistant to follow a spec instead of guessing.
- Teams inheriting an existing GitHub codebase that AI tools treat as a black box, and who need it mapped before new features are generated.
- Agencies running several client projects at once and needing documentation that stays consistent from one project to the next.
- Non-developers building with AI web builders such as Lovable, Replit, Bolt, v0 and AI Studio, whom the site calls vibe coders.
When not to use CodeGuide
- Companies with a procurement or compliance process: the site publishes no terms of service, no general privacy policy, no GDPR mention, no data processing agreement, no subprocessor list and no security certification.
- Anyone who needs to know where their data is stored: no hosting country, region or jurisdiction is declared anywhere.
- EU buyers relying on consumer protection: the Chrome Web Store listing states that the developer has not identified itself as a trader and that consumer rights do not apply to contracts with it.
- Teams who want to call the service from their own pipeline: there is no public API, no API documentation, and no iOS or Android application.
- High-volume users and non-English speakers: quotas are tight (120 one-time credits and one project on the free plan, 15 projects a month on Pro, 18 on Founder) and the interface, the intake and the generated documents are English only.
How to use CodeGuide
A typical end-to-end flow, from setup to results.
- Create an account through accounts.codeguide.dev, where sign-up and sign-in are handled by Clerk, then open the application at app.codeguide.dev.
- Describe your project in plain English.
- Choose the AI tools you intend to build with.
- Answer the clarifying questions CodeGuide generates, on points such as how a notification should behave, whether users need an onboarding, or whether a user can add friends.
- Review the project plan it returns.
- Launch document creation to get the full set of specifications.
- Read the generated specifications before handing them to a model.
- Connect the specifications to the AI tool of your choice, which takes a single command for an IDE or a CLI agent.
- For an AI web builder, install the Chrome extension and sync the blueprint in one click.
- For an existing project, import the GitHub codebase, let CodeGuide analyse it, then generate the specifications for your new features.
Pros & Cons
Pros
- A permanent free plan with no credit card: 120 credits and one complete project, enough to judge the output.
- Broad coverage of the AI coding landscape, with thirteen tools named or displayed, from IDEs and CLI agents to AI web builders.
- The six starter kits are open source on GitHub under the codeGuide-dev organisation, so the code can be inspected before it is used.
- Existing projects are supported, not only greenfield ones: the repository is mapped before new specifications are written.
- Prices are published in full, with no contact-us tier and no quote to request.
- The gap between Pro at 24 USD per month and Founder at 29 USD per month is small, which makes the richer plan cheap to reach.
- The Chrome extension is published by the verified site owner with no violation history, and bring-your-own-keys on Founder avoids credit top-ups.
Cons
- No terms of service and no general privacy policy: the main policy the extension itself points to, at codeguide.dev/privacy, returns a 404.
- No contact page, no about page and no legal notice; the company name and address appear nowhere on the site and had to be read on the Chrome Web Store developer listing.
- Not a single GDPR mention, no data processing agreement, no subprocessor list and no security certification: neither SOC 2 nor ISO 27001 appears on any page collected.
- Signs of an unfinished site: the blog holds four posts all titled Hello World Release September 29, 2025, and the pricing page still displays a demo account's credit gauge.
- Software v2, one of the strongest arguments on the page, is restricted to early access on the Founder plan.
- No public API and no API documentation, no mobile application, and an English-only interface and processing pipeline.
- Tight quotas and traction figures that are hard to square: 15 then 18 projects a month on the paid plans, and 41,450+ developers claimed on the home page against 121 users and no reviews for the Chrome extension, while the home page result counters render as zero.
Pricing & Plans
A permanent free plan is offered and requires no credit card: 120 one-time credits, one complete project and five LLM models. The lowest paid entry point is the Pro plan at 24.00 USD per month; that figure is the annually billed rate, invoiced as 288 USD per year, and the month-to-month rate without commitment is not public, the page's Monthly/Yearly switch not being rendered in the static HTML. The Founder plan is listed at 29.00 USD per month, invoiced as 348 USD per year. Additional credits may be purchased on Pro once the monthly allowance is exhausted. No refund or cancellation terms are published on the pages collected.
- 120 credits granted one time
- 1 project
- 5 LLM models
- all the specification documents including product requirements and tech stacks
- the 6 starter kits
- the Chrome extension and AI prompt refinement
- with no credit card required.
- 5
- 000 credits per month
- 15 projects per month
- 40+ LLM models
- all the specification documents
- wireframes
- specifications for an existing GitHub codebase
- AI prompt refinement
- 6
- 000 credits per month
- 18 projects per month
- 40+ LLM models
- all the specification documents
- wireframes
- documentation for an existing GitHub codebase
- AI prompt refinement
Data, GDPR & hosting
A consolidated view of how CodeGuide handles your data.
GDPR overview
There is no mention of the GDPR at all. Across the five pages collected, home page, pricing, blog, Chrome Web Store listing and extension privacy policy, a search of both the visible text and the archived HTML returns zero occurrence of GDPR or General Data Protection. No Article 27 EU representative is designated, no data processing agreement is offered, no subprocessor list is published, no legal basis is stated and no retention period is quantified beyond the archiving of projects after six months of inactivity. Named data subject rights are replaced by a generic formula: contact support to exercise additional rights available in your jurisdiction. The Chrome Web Store listing goes further, declaring the publisher a non-trader and stating that EU consumer rights do not apply. The company is registered in Delaware, with no EU establishment declared. Privacy requests go to support@codeguide.dev.
Who owns the data?
No terms of service are published anywhere on the site, so ownership of what you submit and of the documents CodeGuide generates is settled by no contract at all. The only legal text in force is the Chrome extension privacy policy, effective 17 December 2025, whose scope is the extension alone. It states that CodeGuide does not sell or lease your personal information, and that data you submit is shared only with CodeGuide services and the essential infrastructure vendors needed to operate them, none of them named; disclosure stays possible where the law requires it. The Chrome Web Store listing adds that data is not sold to third parties and not used outside the core function. Ownership itself is stated nowhere.
Reuse rights
With no terms of service published, no licence clause governs what you may do with the deliverables, so nothing grants and nothing restricts their reuse in writing. In practice the whole product is built for downstream reuse: the product requirements, technical architecture, frontend and backend guidelines, wireframes and task list are meant to be injected into your own IDE, CLI agent or AI web builder, and the six starter kits are published as open source on GitHub under the codeGuide-dev organisation. On the input side, you can manage or delete your projects in the CodeGuide app and contact support to exercise additional rights available in your jurisdiction, and you can clear the extension's local data or remove it at any time. Until terms are published, treat the question of reuse rights as formally open rather than answered.
Data retention & training
Hosting summary
No hosting information is published: no country, no region, no jurisdiction and no named provider appears on any page collected. What can be observed is purely technical. The product runs on three subdomains, the application at app.codeguide.dev, accounts at accounts.codeguide.dev and the backend at api.codeguide.dev; authentication is handled by Clerk, named in the extension privacy policy; and the public site is served by a Next.js and Vercel deployment. The domain resolves to 216.150.1.1, geolocated in the United States on Amazon's AS16509, but that address is an anycast CDN node: it indicates where a request is answered, not where data is stored, and it must not be read as a hosting location. The extension keeps its local data in chrome.storage.local on the user's own device, and all API communication is encrypted via HTTPS. The company is registered in Delaware, which makes United States jurisdiction the default assumption, but no page declares it as a place of hosting. Anyone with a data-residency requirement will have to ask before signing up.
Things to keep in mind
Risks and trade-offs to weigh before adopting CodeGuide.
- No terms of service exist, so nothing contractually settles ownership of the deliverables, the publisher's liability, or what happens to your documentation if the service stops.
- The general privacy policy announced at codeguide.dev/privacy returns a 404, so the processing carried out by the web application is covered by no readable document; the only policy in force concerns the Chrome extension.
- There is no GDPR mention and no EU representative, and the non-trader declaration on the Chrome Web Store removes EU consumer rights from any contract with the developer.
- Your prompts and project ideas travel to api.codeguide.dev with no storage country or region declared, no named provider behind the phrase essential infrastructure vendors, and nothing stating whether customer data is used to train models or how to opt out.
- The extension asks for the cookies permission, reads authentication cookies and injects scripts into lovable.dev, v0.dev, replit.com, bolt.new and cursor.com, which is a wide surface to grant for a convenience feature.
- Projects may be archived after six months of inactivity, so access is lost unless reactivation is requested, and the documentation of an entire project depends on a supplier whose domain dates only from November 2024.
- The cognitive risk is real: accepting a generated blueprint without reading it means outsourcing the design of your own system, and the numbers on display invite misplaced confidence, since the result counters are unverifiable and the claimed audience is far larger than the extension's user count.
Setup & Integrations
Technical difficulty
Getting started is straightforward. The main product is a web application: create an account, describe the project in plain English, answer the clarifying questions. Nothing has to be installed, and the site explicitly addresses people who build without writing code. The Chrome extension installs in one click from the Chrome Web Store (6.77 MiB). The most technical step is attaching the specifications to an IDE or CLI tool, announced as a single command. Two situations ask more: importing an existing GitHub codebase assumes an accessible repository, and bring-your-own-keys on Founder assumes you manage your own model keys.
Deployment
Integrations
Supported languages
Behind CodeGuide
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement CodeGuide.
Frequently asked questions
What is CodeGuide?
What problem is it meant to solve?
What do I actually get?
Which AI tools does it work with?
Why not just ask ChatGPT or Cursor to build the thing?
Can I use it on a project that already exists?
What kinds of projects can be built with it?
Is there a free plan, and what does the paid version cost?
How do I get started?
What legal documents and support does CodeGuide publish?
Should you pick CodeGuide?
CodeGuide occupies a narrow and clearly drawn niche: the specification layer that AI coding tools lack. Product execution is credible for a tool this young, with thirteen coding tools targeted, six open-source starter kits that anyone can inspect on GitHub, a published Chrome extension, prices shown in full with no sales gate, and a free plan that needs no card, so trying it costs next to nothing.
The legal side lags far behind the product. There are no terms of service. The general privacy policy the extension points to, at codeguide.dev/privacy, returns a 404, which leaves the web application covered by no readable document. GDPR is never mentioned, no data processing agreement is offered, no subprocessor list is published and no security certification appears anywhere. The publisher's identity is equally absent from the site: Kyndom Solutions Inc. and its Dover, Delaware address can only be read on the Chrome Web Store developer listing, corroborated by the affiliate program's subdomain.
Other signals point to youth rather than bad faith. The domain was registered on 24 November 2024 and first archived two days later, the blog holds four placeholder posts under one title, and the pricing page still shows a demo account's credit gauge. The 41,450+ developers claimed on the home page also sit awkwardly next to 121 users and no reviews for the Chrome extension.
The fair reading is a young tool with a genuinely useful idea and a compliance file nobody has written yet. For an individual developer, a founder or a small team, the low price and the free plan make it easy to judge on its merits. For a regulated organisation, or for anyone who must know where their documentation is stored and under what contract, the missing documents are disqualifying until they appear.
- Choosing a selection results in a full page refresh.
- Opens in a new window.