beyond-entity

Beyond Entity — Data skill for Claude Code

Data community

Persistent architecture memory for AI coding agents via MCP.

How to install Beyond Entity

This entry records only its repository, not the path inside it, so there is no exact command to give. Open beyond-entity/beyond-entity and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Beyond Entity does

Persistent architecture memory for AI coding agents via MCP. Design or reverse-engineer software architecture, explore ERDs and data lineage, and keep processor transformations aligned with code. Includes Claude Code and Codex plugins, skills, and samples.

Alternatives in Data

OpenViking — Self-evolving Context Database for AI Agents 33.3k ★
Archify — Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self 17.2k ★
Skill Content Pipeline — Extract patterns and anatomy from URLs — use to reverse-engineer content strategies from live pages 2.8k ★

README

Beyond Entity — Architecture Memory for AI Coding Agents

[English](README.md) · [한국어](README_ko.md) · [日本語](README_ja.md)

Beyond Entity gives AI agents and engineers a persistent, shared architecture memory: system intent, design decisions, models, data contracts, processor transformations, and implementation context that can be carried from one work session to the next.

The **beyond-entity-mcp** plugin connects this architecture memory to an AI coding workflow through the local Beyond Entity MCP server. Its skill guides an agent to recover context, check the design before changing code, keep architecture aligned with verified implementation changes, and leave a checkpoint for the next agent or human.

Use Beyond Entity for **software architecture modeling**, **architecture diagrams**, **data lineage**, and **design-to-code workflows** with Claude Code or Codex through MCP (Model Context Protocol).

[Download Beyond Entity](https://beyondentity.com/en/download) · [Installation guide](INSTALL.md) · [User guide](docs/USER_GUIDE.md) ([한국어](docs/USER_GUIDE_ko.md) · [日本語](docs/USER_GUIDE_ja.md)) · [Sample projects](samples/README.md) · [Website](https://beyondentity.com) · [GitHub](https://github.com/beyond-entity/beyond-entity)

[![Table Q web, API, and database attribute lineage](assets/screenshots/table-q-workflow.png)](https://canvas.beyondentity.com/viewsample?sample_project_file_id=rXxLCaaJ1nEVN9CKbneL)

*Trace a workflow from web interactions through API transformations to database attributes. Click the image to explore Table Q in the viewer.*

Start from a design or from existing code

You can build architecture memory from either direction:

Start with design. Ask your AI agent to turn your requirements into a design in Beyond Entity through MCP, including system boundaries, entities, data contracts, processors, and transformations. You can also design web and app architectures, ERDs, APIs, ETL/ELT pipelines, and schedulers directly in the Beyond E