design/dialogue

Explain Runes, Design Contracts, and design rules in plain language.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/f-campana/bifrost --skill design-dialogue-f-campana
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design/dialogue
Source: https://github.com/f-campana/bifrost/tree/main/skills/design/design-dialogue
Command: npx skills add https://github.com/f-campana/bifrost --skill design-dialogue-f-campana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers and engineers often need concise, grounded explanations of Runes, Design Contracts, and design rules to ensure consistent reasoning and vocabulary across the system.

Core Features & Use Cases

  • Plain-language explanations of Runes, Design Contracts, and design rules, anchored to the Sanctum/Bifrost vocabulary.
  • Contextual examples and references to the system's terminology to support understanding.
  • Use Case: when a team member needs a quick justification or clarification of a rule to align teammates.

Quick Start

Explain the selected Rune or Design Contract in plain language with clear rationale.

Frequently Asked Questions about design/dialogue

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

FAQPage Schema
What is a design contract and how does it work in a design system?

A design contract defines explicit rules and constraints for system components. This Skill explains design contracts and runes in plain language, providing clear rationale anchored to the system vocabulary to ensure consistent reasoning across the team.

How do I explain design rules to align my team on vocabulary?

To explain design rules clearly, you need grounded rationale tied to system terminology. This Skill reads the relevant rune or contract and produces a plain-language explanation that stays within the domain vocabulary to help teammates align.

When do I need plain-language explanations for runes?

You need plain-language explanations for runes when team members require quick justification or clarification of a design rule. This Skill translates domain-specific runes into clear rationale, ensuring everyone understands the system vocabulary consistently.

Can I use this to get contextual examples for design education?

Yes, this Skill provides contextual examples and references to system terminology to support design education. It reads the relevant rune or contract and produces an explanation anchored to the system vocabulary for quick team alignment.

Does explaining design contracts require prior knowledge of system vocabulary?

Explaining design contracts requires reading the relevant rune or contract and understanding the system vocabulary. This Skill handles the translation process, ensuring the explanation stays within the domain vocabulary while providing clear rationale for the team.

What is the best way to justify a design rule without losing context?

The best way to justify a design rule is using plain-language explanations anchored to the system vocabulary. This Skill reads the specific rune or contract and produces grounded rationale with contextual examples, preventing misalignment across the team.