For websites, SaaS products and mobile apps, STAQ gives you an organised starting project: architecture, accounts, data, payments and tests, plus the skills and workflows to adapt it with Codex or Claude Code.
Deliverables announced on the sheet
This is neither a no-code product nor a finished application. It is a development base that you own, understand and adapt to your needs.
Organize the front, server, data and environments.
Registration, sessions, email verification, roles and recovery.
Checkout, Stripe returns, purchase statuses and customer access.
Testing, deployment, documentation and access transfer.
Folders, conventions and environments follow the same AQ method.
Server states and controls are already provided in the base.
Payment, customer area and product access share the same logic.
Tests, documentation, and workflows accompany the code.
Each product sheet specifies its exact content. A STAQ boilerplate is delivered as a development project, with its recovery tools.
You retrieve the project structure and its versions from your client area.
Included features are organized for reading, editing, and extending.
Installation, variables, agreements and delivery steps remain with the deposit.
Skills and workflows tell Codex or Claude how to work in this stack.
Showcase site, SaaS or methods for AI agents: the price, stack and status come directly from the catalog.
Deliverables announced on the sheet
The complete boilerplate with 45 SaaS-focused skills.
A journey counts → purchase → already structured access.
CHF 249.-
View productDeliverables announced on the sheet
A fast Nuxt foundation with 31 focused web skills.
A showcase site consistent with the client’s identity and content.
Price coming soon
View product/aq-init
/aq-story
/aq-ship
Instructions that help coding agents work the way you do.
Reusable instructions for your agents and projects.
CHF 89.-
View productTechnologies are not stacked to decorate a sheet. They each cover a specific product liability.
Web interface, server rendering and page structure.
Data, server functions, tasks and real-time synchronization.
Accounts, sessions, email verification and login providers.
Checkout, payment confirmation and purchase history.
Adaptable style system with light and dark modes.
iOS and Android applications sharing server logic.
Unit checks and browser route before delivery.
STAQ himself uses these routes. The content delivered and commercial availability remain honestly detailed on each product sheet.
Email login, sessions, address confirmation and password recovery share the same journey.
Better Auth + server controlsThe price comes from the server, the payment opens a purchase and the failure returns remain repairable.
Checkout → purchase → accessThe user finds their purchases, indicates their GitHub account and monitors the status of their access.
account / purchases / invitationLoading, empty, error and access denied are predicted and then verified by the project's test suites.
Vitest + Playwright + CIThese captures come from the application you are viewing. They show actually built courses, not models presented as a finished product.
Status, stack and price remain public for frictionless product comparison.
Open catalog
The inclusions, technologies and proposed action adapt to the published or future product.
See STAQ SaaS
Registration, address confirmation, password recovery and customer area share the same logic.
View registrationIt does not replace the boilerplate: it explains to Codex or Claude how to understand the project, follow your conventions, check the result and finish properly.
/aq-init
/aq-story
/aq-ship
STAQ does not promise a magic number of hours. It simply makes visible what you need to rebuild alone and what already exists in the base.
The catalog remains public. The account only intervenes to purchase and regain access to the product.
The catalog shows what each product contains, without counting.
You leave an email, you are notified upon exit.
One-time payment by Stripe. No subscription.
Invitation to private GitHub repository, updates included.
I transform what I learn on my own projects into a clear, maintained and shareable system.
The goal is not to sell isolated files: each product must work with the others and save you time without taking away control.
STAQ remains development code: here is what this actually involves before choosing a product.
A boilerplate provides an already organized architecture, modules and procedures. You still need to create your identity, your content and the functionalities specific to your business.
After a confirmed purchase, you will find the product in your customer area. For boilerplates, access is prepared in the form of an invitation to the corresponding private GitHub repository.
Yes. The products are designed as adaptable development bases. The precise conditions of use and the scope delivered remain indicated on each sheet.
The sheet for each product specifies what is maintained and, when defined, the period concerned. STAQ does not display a generic duration that would not be confirmed for the product.
The delivery status remains visible in the customer area. You can restart the preparation when the action is available or contact support for manual intervention.
Requests are reviewed manually. The legal information and conditions applicable at the time of purchase remain the reference; no automatic refund is promised by the interface.