PersonIndependent

Emerson Tosin

GitHub@etosinlast push

Capabilities2

Provides 2
Agent guidanceBTPAgent guidancecapabilityPackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.Architecture diagramsBTPArchitecture diagramscapabilityDrawing the architecture and components of a solution so another person can understand their responsibilities and connections. Shared notation makes diagrams readable across teams.

Entries1

Group by
EntrySignals
Maintains1
ARC-DRAW
Functional boundary

MCP server drawing BTP solution diagrams on a draw.io canvas

Details

History2
  • ARC-DRAWdescription.when_not_to_use → Any run nobody is watching: the drawing tools work only while the draw.io canvas at `http://localhost:3000/` is open and connected, so there is no diagram to produce on a build agent or a server. Nothing checks the result either, because the maintainer keeps a diagram linter on the [roadmap](https://github.com/etosin/arc-draw#-roadmap) rather than in the release. The maintainer marks the status early at v0.x, installs it from source, and records testing with Claude Code alone.The README declares the status early (v0.x), installation from source and testing with Claude Code alone, and the entry carried none of it. The maturity label is the maintainer's own, dated here, and the live-canvas requirement is what separates this option from the ones that write a file.
  • First entry seenDiscovered via Added by hand.
For your agent