design/curator

Instantiate a validated Rune into a project-specific Design Contract file.

Updated Aug 23, 2026

Search Tags:#automation #design #curation #project-setup #rune #design-builder #contract-generation

Ready to run

npx skills add https://github.com/f-campana/bifrost --skill design-curator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design/curator
Source: https://github.com/f-campana/bifrost/tree/main/skills/design/design-curator
Command: npx skills add https://github.com/f-campana/bifrost --skill design-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reading a selected Rune and turning it into a project-specific Design Contract to accelerate design work without manual drafting.

Core Features & Use Cases

Read the selected Rune and the project brief.
Resolve project naming and contract metadata.
Write DESIGN_[PROJECT].md at the project root.
Keep the contract self-contained for the design-builder process.

Quick Start

Provide the selected Rune and project brief, then run the design-curator to generate the DESIGN_[PROJECT].md at the project root.

Frequently Asked Questions about design/curator

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

FAQPage Schema

How do I generate a design contract from a Rune automatically?▼

To generate a design contract from a Rune, provide the selected Rune and a project brief. The automation reads these inputs, applies project naming rules, and writes a validated DESIGN_[PROJECT].md file at the project root.

What is a Rune used for in project setup and contract generation?▼

A Rune serves as the foundational template for contract generation. By reading the Rune alongside your project brief, the system instantiates a project-specific Design Contract to accelerate design work without manual drafting.

What inputs do I need to provide for design curation?▼

Design curation requires two mandatory inputs: a selected Rune and a project brief. The process enforces the presence of both to resolve naming conventions and assemble contract metadata accurately.

How does the design-builder process handle naming conflicts?▼

The design-builder process handles naming conflicts by enforcing project naming rules and resolving human-chosen names during contract assembly. This ensures the resulting DESIGN_[PROJECT].md maintains Rune and brief fidelity.

Why does my generated design contract drift from the original project brief?▼

Contract drift occurs when inputs lack validation. This curation process avoids drift by strictly enforcing the presence of both the Rune and brief, maintaining fidelity throughout the contract metadata assembly.

Where is the instantiated Design Contract file placed after generation?▼

The instantiated Design Contract is placed directly at the project root as a self-contained DESIGN_[PROJECT].md file. This location ensures immediate accessibility for the downstream design-builder process.