Personas work in Claude Code, Cursor and Codex, too. See how
  1. Home
  2. Industries
  3. Software development

Your conventions, in every pull request.

Keep coding conventions, review checklists and what each client project needs as playbooks. Claude Code, Cursor and Codex load them over MCP while your developers work.

Probably AI-generatedConventions · loaded in Claude Code
Start 14-day free trialSee pricing
  • EU-hosted
  • No training on your content
  • Your own keys

One library for every project.

What changes when your engineering rules live in sqemes instead of in wikis and single prompts.

Your library

Conventions, checklists, project context.

Write down how you build software as skills: conventions, review checklists, architecture notes, one skill per client project. Skills load step by step: the outline first, a file only when the task needs it.

About skills
Probably AI-generated

Engineering library

Coding conventionsSkillReady

Review checklistSkillReady

Project: NorthwindSkillReady

Every tool

Claude Code, Cursor, Codex, one source.

Each developer connects sqemes over MCP once. The coding agent finds the right playbook mid-task without anybody picking it, and a change in sqemes reaches every developer the next time it loads.

How MCP works
Probably AI-generated

Claude Code · sqemes MCP

Coding conventionsSkillLoaded

Project: NorthwindSkillLoaded

Control

Project knowledge for the project team.

Restrict a client project's playbooks to its team, decide separately who may edit them, and switch on review so that a change to shared conventions waits before everyone gets it.

How governance works
Probably AI-generated

Who can see "Project: Northwind"

Everyone in the workspace

RestrictedTeam Northwind

A persona for every role in the project.

Pick a task and see what the Project Lead loads.

Try it: pick a task
  • Works in sqemes Chat and in AI tools connected over MCP.
Probably AI-generated

Project Lead

Coding conventionsSkillLoaded

Project: NorthwindSkillLoaded

Review checklistSkillLoaded

What a software team does with it.

Work between ticket and release, with your rules already in it. Examples of what you can keep in sqemes.

Coding conventions

Naming, structure and patterns as a skill your coding agent loads.

Review checklists

What every pull request has to meet, applied while the code is written.

Client projects

Each client project keeps its own context, restricted to its team.

Technical concepts

Concepts and estimates as Word or PDF in your document style.

Onboarding

New developers find the project's rules in one place, and so do their agents.

Skills with files

Scripts and references travel with a skill. The tool that loads it runs them, sqemes only stores them.

For developers and their agents.

Questions, answered.

What software teams ask.

Still unsure?

Write to us. A real person answers.

Contact us
01How is this different from the page for engineering teams?
The engineering page is about the developers of one company. This page is about teams that build software for clients: one skill per client project, restricted to its team.
02Which coding tools work with sqemes?
Claude Code, Codex, Cursor, VS Code and any other client that supports MCP. Each person connects once under Settings, API & MCP.
03Does sqemes run our scripts?
No. sqemes stores script files with a skill. The tool that loads the skill runs them.
04Do changes reach every developer?
Yes. A playbook is loaded from sqemes when it is used, so a change applies the next time.
05Can we run sqemes on our own servers?
Yes. The self-host version runs on your own servers with your own AI keys and is free for internal use under a fair-code license.