skills.rest
ByteLandTechnology
ByteLandTechnologyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

cli-forge-design

Generate a design-contract.yml from a template and require user approval before Plan.

Updated Apr 2, 2026
Search Tags:#workflow#design#planning#handoff#approval#contract#cli-forge
One-click install
npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-forge-design
Source: https://github.com/ByteLandTechnology/cli-forge/tree/main/cli-forge-design
Command: npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Design stage provides a single authoritative description contract for generated skills, ensuring downstream surfaces reuse the approved wording and prevent drift across Cargo.toml, SKILL.md, README, and help text.

Core Features & Use Cases

  • Define or refresh the approved purpose summary and the positioning statement to anchor the skill's identity.
  • Capture and lock surfaces that must stay synchronized across the lifecycle: Cargo.toml, SKILL.md, README.md, help contracts, and release notes when publish is in scope.
  • Generate design-contract.yml from the shared template and present it for explicit user approval before moving to Plan.

Quick Start

Provide an authoritative purpose and positioning, then generate and approve the design-contract.yml for downstream stages.

Frequently Asked Questions about cli-forge-design

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

FAQPage Schema
How do I keep skill descriptions consistent across Cargo.toml, README, and help text?▼

A design contract anchors a skill's identity by locking its purpose summary and positioning statement. This prevents wording drift across generated files like Cargo.toml, SKILL.md, README, and help text.

How do I generate and approve a design contract for a new skill?▼

Provide the authoritative purpose and positioning, then generate the design-contract.yml from the shared template. The workflow requires explicit user approval of this file before moving to the Plan stage.

What surfaces need synchronization during the design contract phase?▼

The design contract captures and locks surfaces that must stay synchronized across the lifecycle: Cargo.toml, SKILL.md, README.md, help contracts, and release notes when publish is in scope.

When do I need to define a high-level design contract?▼

You need a design contract when creating a new skill or refreshing an existing one. It applies an authoritative description contract to ensure consistent downstream wording across both new and refreshed design stages.

Can I use the design contract workflow for an existing skill refresh?▼

Yes, the design contract workflow applies to both new and refreshed design contracts. It re-anchors the skill's identity and purpose to ensure consistent downstream wording before plan approval.

Why does my generated skill have inconsistent wording across SKILL.md and Cargo.toml?▼

Inconsistent wording happens without a locked design contract. Defining a single authoritative description contract prevents drift and forces downstream surfaces to reuse the approved purpose and positioning statement.

Related Skills

Explore More Design & Creative Skills→
eusouwillnuneseusouwillnunes

marca:posicionamento

Construct Onlyness Statements and map diffusion for brand positioning.

Community
Intermediate
ByteLandTechnologyByteLandTechnology

cli-forge-takeover

Reconstruct design-contract.yml and cli-plan.yml for pre-existing Rust CLI projects.

Official
Advanced
ByteLandTechnologyByteLandTechnology

cli-forge-plan

Define and lock a CLI contract for the cli-forge plan stage.

Official
Advanced
jllopisjllopis

telos-purpose-core

Define and govern project changes with four explicit purpose horizons.

Community
Advanced