Skip to content

Repository files navigation

QualityLayer

QualityLayer

The software factory with you in the loop

Plan each change visually, then let your agents build and verify it.
Work side by side in the App or browser, or use your favourite terminal or IDE.

Stars Star History Downloads PRs Welcome

Install • Features • Docs • Website • Changelog

Download the App for macOS, Windows or Linux.

Watch the film on YouTube, 5:20 Inside QualityLayer, a 27-minute deep dive

The QualityLayer App: you pick the recommended answer to a Plan decision beside its diagram, then approve the finished change and open its pull request

All seven steps play on qualitylayer.dev. Try it yourself: the App demo in your browser, nothing to install.


Why QualityLayer

“With QualityLayer, developing software with agents finally feels like doing real engineering again.”

An engineer who uses QualityLayer

Agree on the change, then review how your agents built and checked it.

You get How it works
Your own agent and plan Use Claude Code, Codex, Cursor and more with your existing login or API key.
A design you can review Comment on diagrams and clickable screens, then approve the Plan before code changes.
Small, tested changes Your agent writes tests before code and hands independent parts to other agents when useful.
An independent check With independent review on, a separate agent checks the running change against your request. What it cannot verify stays visible in Review.
Code health checks Find complex functions, deeply nested code and duplication. Code health.
Your own requirements Add checks, tools or skills to any step. Review shows what was done or skipped. Required lines.
Visible decisions and effort Read decisions and results in your repository; see time, model usage value and cost estimates in the App.

Getting started

Prerequisites

  • A coding agent, installed and signed in with your subscription or API key: Claude Code, Codex, Cursor, Grok, Antigravity, Pi, OpenCode or GitHub Copilot. Other agents connect through the CLI.
  • Git and a repository.

Installation

Download the App and open it. Setup automatically installs the qualitylayer command and connects your agents. On a server, in WSL or in a container:

curl -fsSL https://qualitylayer.dev/install.sh | bash      # macOS, Linux, WSL
irm https://qualitylayer.dev/install.ps1 | iex             # Windows PowerShell

The App updates itself; without it, run qualitylayer update. Installation guide.

Uninstalling

qualitylayer uninstall undoes what the installer changed; your plans stay. On Windows, even when the App is gone:

& ([scriptblock]::Create((irm https://qualitylayer.dev/install.ps1))) -Uninstall
Coming from Pilot Shell 11

Run pilot update or download the App. An active Pilot Shell licence works with both products; older purchases may need help moving over. Migration and memory import.

First steps

In the App or browser, choose +, then Task (Feature or Bugfix) or Chat. Pick your repository and agent, and describe what you need.

Chat is a direct conversation with optional artifacts, checks and reviews. Convert to task starts the workflow in that conversation. Chat guide.

For a Feature or Bugfix, choose Plan with QualityLayer or Existing plan to paste or attach your plan. Describe the change:

Plan retries for failed webhooks and stop after a few tries.
  1. Answer questions and comment on the Plan.
  2. Approve the Plan. Your agent builds and verifies the change.
  3. Review the result and open checks, then approve it. Ask your agent to merge, deploy or make further changes.
Where you work How to start
App or browser Choose In the App to keep the agent beside the task.
Your terminal or IDE Choose In my terminal to copy the request, or ask there: “Using QualityLayer, plan retries for failed webhooks.”
Another agent Agents that run shell commands can use the CLI. Supported agents.

At Plan approval, continue with your planner or choose another agent or session. Outside the App, ask: “Using QL, continue task retry-webhooks.”

QualityLayer runs only when you ask for it. Your first task.

Skills your agent gets

Setup adds these skills. Ask in plain words, in any language.

Skill For You say
ql-peer Agents talking to each other “Ask Codex to review what you just built.”
ql-workflow Plan, build and review a change “Using QualityLayer, add rate limits to the export API.”
ql-chat Chat without workflow steps “Using QualityLayer, chat about the billing refactor.”
ql-artifact Designs, diagrams and pages “Open the settings design in my browser.”
ql-quality Code health and security scans “Scan this repository for leaked secrets.”
ql-manage Tasks, sharing, settings, setup “Share this task with my team.”

More about the skills


Checks and independent review

QualityLayer runs your project's checks and security scans. A separate agent reviews the change against your request. How Verify works.

Project checks: tests and types, linters, code health and recorded proof. Independent agents: security review, independent review, design review and an optional second opinion from another coding agent.

The workflow

Each step saves readable Markdown in your repository. The Plan is the specification you share; build notes live beside it. Export gathers the Plan and its pictures. Existing plans start at Plan. You approve the Plan and finished change, and control pushes and merges.

Discuss, Research, Plan, Outline, Implement, Verify, Review and the pull request: you approve at Plan and at Review and merge the pull request; your agent works in between
Step What happens
Discuss Settles what done means and clarifies a bug report
Research Agents read how your code works today; a bug is reproduced and diagnosed here
Plan Diagrams and change maps, clickable artifacts and checks, approved by you
Outline Your agent splits the approved Plan into small slices
Implement Your agent builds test first, fixes what fails and decides when it is ready
Verify Your project's checks and an independent agent's review
Review A walkthrough of the change and a map of where it landed, approved by you
Pull request Failing checks and routine review threads fixed; the task stays open until you merge

See how a change fits together

Your agent maps the files a change will touch and how they connect, before any code is written. Review shows the same map with where the build landed.

Fictional change map: Gateway contains a changed Handler and a new, risky Meter. Usage links it to Billing's changed Ledger and price().

Two levels

Engineering starts with a technical plan. Product starts with a product brief. Choose in Settings › Workflow. How they differ.

QualityLayer App

Reviewing a billing decision and its diagram beside Claude Code in the App. Fictional project.
In the App What you can do
Chat or a planned task Talk directly with your agent or follow the workflow. See agent activity and get notified when one needs you.
Conversation and terminal Read the agent's conversation or its terminal beside the task. Answer questions and pin feedback.
Artifacts Try mockups, diagrams and clickable pages before any code exists.
Checks and code review Read the evidence and file diffs, and comment on any line.
Agent controls and usage Choose model, effort and permissions; track limits and daily costs, including in the macOS menu bar. Settings.
Memory and team Reuse project lessons, ask teammates over Slack or email and share work.

QualityLayer keeps task files on your computer and encrypts shared tasks first. Your coding agent uses its own provider. Files and privacy.

Explore the App →

Artifacts

Try mockups, diagrams and clickable pages before building. Pin feedback to any spot; your agent updates the artifact. Keep reusable artifacts in your repository. Artifacts guide.

A backend request diagram in QualityLayer’s artifact viewer. Fictional project.

Documentation

Guides for getting started, commands and settings.


Changelog

See the changelog or GitHub Releases.


Contributing

Found a bug or missing a feature? Open an issue.


License

See LICENSE.


Quality by design. The software factory with you in the loop.

Made by Max Ritter

Releases

Used by

Contributors

Languages