Simple Project
Quick startFor small features and MVPs. Covers scope, core entities, and a lean implementation path without over-engineering.
Architecture-first · CLI-first · IDE-agnostic
ArtQ guides you through concrete questions to clarify scope, constraints, and structure—then generates files your coding agent can actually use.
Think before you build
$ arch init? What are you building?REST API for invoicing with Stripe webhooks? Who are the primary users?Freelancers sending invoices to clients? Key constraints?Must work offline-first, deploy to Vercel✓ handoff/README.md✓ architecture.md✓ implementation-plan.md✓ test-plan.md✓ review-checklist.md
The problem
The approach
How it works
No chat threads. No vague prompts. A structured flow that ends with files you can use.
ArtQ asks the questions you'd skip when rushing to code—users, boundaries, data flow, and constraints.
Receive an implementation-ready handoff package: architecture docs, plans, checklists, and a handoff/ guide for agents or developers.
Use the files with Cursor, Claude Code, Copilot, or your own workflow. No vendor lock-in.
Methods
Each method shapes the questions and artifacts around a different way of building.
For small features and MVPs. Covers scope, core entities, and a lean implementation path without over-engineering.
Structures your project for coding agents with clear boundaries, file conventions, and handoff points.
Defines behavior specs and test boundaries before implementation. Ideal when correctness matters more than speed.
Maps domains, use cases, and adapters explicitly. For projects where maintainability is the primary constraint.
Artifacts
Every session produces markdown files you can commit, share, or hand off to a coding agent.
System boundaries, components, data flow, and key decisions.
# Architecture: invoice-api ## Context REST API for freelancers to create and send invoices. Stripe handles payments; we store invoice metadata. ## Components - API layer (Next.js route handlers) - Domain services (Invoice, Client) - Stripe adapter (webhooks + checkout) ## Decisions - Offline-first: queue sync on reconnect - Auth: Clerk JWT, scoped to user org
Who it's for
Whether you're learning structure or already shipping with agents, ArtQ gives you a clearer starting point.
Learn how to think about structure before jumping into syntax. ArtQ teaches the questions senior devs ask.
Ship faster with less rework. Define your MVP scope clearly so you don't build the wrong thing.
Start client projects with documented architecture and plans you can share and iterate on.
Already using Cursor or Claude Code? Give your agent structured context instead of long chat threads.
Differentiation
Coding agents are great at writing code. ArtQ is for the step before—when decisions still matter.
| AI coding assistants | ArtQ | |
|---|---|---|
| Primary focus | Writing and editing code | Defining architecture and plan |
| Output | Files, diffs, suggestions | Structured markdown artifacts |
| When it helps most | During implementation | Before implementation |
| Workflow | IDE-integrated chat | CLI-first, agent-agnostic |
| Best for | Speeding up coding tasks | Reducing ambiguity and rework |
Pricing
Free for small projects. Pro when you need advanced methods and review workflows.
Docs
Getting started takes a few minutes. Install the CLI, run arch init, and review your generated files.
Preview
CLI walkthrough and generated artifacts—screenshots coming soon.
Install the CLI, answer a few questions, and get an implementation-ready handoff package in minutes—not hours of back-and-forth.