core-architect

Establishes a transport-agnostic core API architecture for the bnto project.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Develonaut/bnto --skill core-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-architect
Source: https://github.com/Develonaut/bnto/tree/main/.claude/skills/core-architect
Command: npx skills add https://github.com/Develonaut/bnto --skill core-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coupled frontend components with backend implementations are hard to evolve; the Core Architect persona defines a transport-agnostic core API layer to decouple UI from backend specifics.

Core Features & Use Cases

  • Defines core API surface: clients (public API), services (domain logic), adapters (backend bridges), transforms (doc -> API types), and hooks (React bindings).
  • Enables backend swapping without breaking consumers; supports multiple backends like Convex and Tauri IPC.
  • Supports consistent contracts, dependency direction rules, and robust testing strategies across the core boundary.

Quick Start

Initialize a core client and execute a sample service call to verify public API wiring.

Frequently Asked Questions about core-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decouple React UI from backend implementations in TypeScript?

Backend swapping without breaking consumers requires defining a core API surface with adapters acting as backend bridges. This setup supports multiple backends like Convex and Tauri IPC behind consistent public client contracts.

How do I structure integration tests across a core API boundary?

Structuring integration tests across a core API boundary requires an imperative-first core logic approach. You define robust testing strategies that validate the public clients and services without coupling tests to specific backend transport layers.

Does this core API architecture support both Convex and Tauri IPC backends?

Yes, the core API architecture supports both Convex and Tauri IPC backends. It uses adapters as backend bridges and transforms to map document types to API types, enabling backend swapping without impacting consuming React hooks.

What is the dependency direction for a transport-agnostic core API layer?

The dependency direction for a transport-agnostic core API layer flows from public clients and React hooks down to services and adapters. Imperative-first core logic resides in services, ensuring domain rules remain independent of backend transport specifics.

When do I need to use transforms in a core API architecture?

You need to use transforms in a core API architecture when mapping backend documents to public API types. They ensure the core boundary exposes consistent contracts, allowing services to process normalized data regardless of the underlying backend format.