What is the difference between a base and a component?

In this architecture, a base is a deployable artifact like a webapp or CLI, while a component is a building block that provides an interface namespace for other parts of the system to require.

How is state managed in this skill's architecture?

Stateful components (like database connections or websockets) are managed using Integrant. The resulting map is called the 'system' and is passed as the first argument to functions requiring those states.

How do view-functions work here?

View-functions are pure functions that take the current state as input and return Hiccup data (HTML representation) without performing any side effects.

What are 'actions' and why are they pure data?

Actions are pure data lists that describe intent (e.g., [[:event/prevent-default]]). They are pure to separate the 'what' from the 'how', allowing action-handlers to manage the actual side effects.

Synapse Architecture Guide

Name: Synapse Architecture Guide
Author: schneiderlin

byschneiderlin

开发者工具

Explains architectural design patterns and domain-specific concepts including Polylith components and Integrant state management.

关于

This skill provides Claude with deep contextual knowledge of the Synapse project's architectural framework. It defines the core building blocks of the system, such as the distinction between deployable 'bases' and reusable 'components' within a Polylith structure. It also details the flow of data through pure view-functions, data-driven actions, and side-effect handlers, while managing stateful components via Integrant. This ensures Claude can generate code that adheres to the project's specific design patterns, interface requirements, and state management lifecycle.

主要功能

Polylith architecture guidance for separating bases and components
Data-driven action and action-handler pattern implementation
Hiccup-based view-function development patterns
0 GitHub stars
Integrant system configuration and stateful component management
Interface namespace standards for functional exposure

使用场景

Creating pure UI components that dispatch data-driven actions for side effects
Implementing new stateful services within the Integrant system map
Refactoring code to comply with Polylith component interface standards

关于

主要功能

Polylith architecture guidance for separating bases and components
Data-driven action and action-handler pattern implementation
Hiccup-based view-function development patterns
0 GitHub stars
Integrant system configuration and stateful component management
Interface namespace standards for functional exposure

使用场景

Creating pure UI components that dispatch data-driven actions for side effects
Implementing new stateful services within the Integrant system map
Refactoring code to comply with Polylith component interface standards