THE DEV-TOOLING SECTION — claude-kit is how Tu Empresa Digital OS gets built.
This section documents claude-kit, the AI dev team that builds the platform. For the platform itself — its apps, architecture, and data model — start at the Overview. For how the kit relates to the product engine, see the kit ↔ engine boundary.
What is claude-kit
claude-kit turns Claude Code into a small team for your project.
Instead of one assistant juggling every kind of task at once — planning, design, writing, building, testing — you get a set of focused roles, each with its own job, its own tools, and its own way of working. A single coordinator at the top reads your request and hands it to whoever owns that kind of work.
You install it once. Then, in any project, you run one command — /kit-init — and the kit sets everything up for you, shaped around the kind of work you do.
Why a team instead of one assistant
One assistant doing everything tends to lose focus: it blurs a design decision into a code change, or rushes past a question only a specialist would catch. A team avoids that.
- Focus. Each role carries only what it needs to know, so its attention stays sharp.
- The right hands for the job. A design question goes to the designer. A security question goes to security. Nobody is guessing outside their lane.
- Clear ownership. Every change has an obvious owner, and roles hand work across to each other rather than overstepping.
- It remembers. Decisions, plans, and context can be kept per project, so you're never re-explaining yourself in the next session.
What you actually get
When you set up a project, the kit drops in a tidy .claude/ folder containing:
- Agents — the roles on your team (a PM, a designer, a developer, and so on — exactly which ones depends on the kind of work you picked).
- Skills — focused abilities the agents reach for: writing conversion copy, building UI, researching a topic, animating a page.
- Rules — the house style: how the team communicates, how plans are written, how it remembers.
- A workflow — an optional, tidy path from idea → task → review → done.
You don't have to understand any of the internals to use it. Pick the closest profile at setup and start asking for work.
The five profiles
A profile is just a starting team, chosen for the kind of work you do. You can reshape it later.
| Profile | For | The team you get |
|---|---|---|
software | Building a product end to end | PM, Tech Lead, Designer, DevOps, Backend, Frontend, QA, Security |
content | Writing, editorial, brand | PM, Editor, Designer, Researcher |
research | Investigation and analysis | PM, Researcher, Analyst |
automation | n8n / workflow automation | PM, n8n specialist, Generalist |
minimal | A lean, flexible start | PM + one generalist |
Not sure? minimal is the gentle way in, and you can grow into more later.
The three values
The kit is built around three ideas, and you'll see them show up everywhere:
- Memoria — context that survives. The team remembers decisions so you don't repeat yourself.
- Eficacia — the right role, the right tool, no wasted motion.
- Gentileza — it asks before it acts, previews before it writes, and never clobbers your work.
Where to go next
- Install — get the plugin, then run
/kit-init. - By role — jump to the guide for the kind of work you do.
- What you can do — the things the kit does, one feature at a time.