ln-design

Generates and compares alternative module shapes and API boundary designs.

7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hashintel/brunch --skill ln-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-design
Source: https://github.com/hashintel/brunch/tree/main/.agents/skills/ln-design
Command: npx skills add https://github.com/hashintel/brunch --skill ln-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Developers often struggle to determine the most effective API boundary and module shape, which can lead to overly complex or inefficient designs.

Core Features & Use Cases

  • Generate Multiple Designs: Produce three or more radically different module shapes based on specified constraints to explore optimal API boundaries.
  • Comparison & Evaluation: Analyze generated designs on criteria like depth, usability, and efficiency to select the best approach.
  • Use Case: When designing a new API, quickly generate and compare different interface shapes to identify the most maintainable and scalable structure.

Quick Start

Provide the module or API boundary you want to explore, and the skill will generate diverse design options for evaluation.

Frequently Asked Questions about ln-design

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

FAQPage Schema
How do I prototype different module boundaries for API design?

Prototyping different module boundaries for API design involves generating multiple module shapes based on your constraints to explore optimal interfaces. This process helps developers compare structural options and select the most maintainable boundary before implementation begins.

What is the best way to compare alternative API interface shapes?

Comparing alternative API interface shapes requires generating three or more radically different module designs and evaluating them on criteria like depth, usability, and efficiency. This analysis identifies the most scalable and maintainable structure for your specific use case.

Do I need external dependencies to analyze module boundary decisions?

Analyzing module boundary decisions requires no external dependencies beyond core scripting capabilities. The evaluation process runs self-contained, allowing you to explore interface shapes and API designs without installing additional frameworks or libraries.

Can I generate multiple API designs from a single module constraint?

Generating multiple API designs from a single module constraint produces three or more radically different module shapes for evaluation. You provide the initial API boundary or module specification, and the system outputs diverse structural options to compare.

When do I need to evaluate module shapes for optimal API boundaries?

Evaluating module shapes for optimal API boundaries is needed when designing a new API or restructuring existing interfaces to avoid overly complex or inefficient designs. It aids developers and architects in identifying the most effective boundary before committing to implementation.

What criteria should I use to select the best API design from generated options?

Selecting the best API design from generated options involves analyzing the prototypes on criteria like depth, usability, and efficiency. This comparative evaluation highlights which module shape delivers the most maintainable and scalable structure for your interface.