generate-design

Generates design-spec.json with per-format layout mappings, palettes, and fonts from content.md.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill generate-design-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-design
Source: https://github.com/jokerman89/lintel/tree/main/skills/generate-design
Command: npx skills add https://github.com/jokerman89/lintel --skill generate-design-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning written content into presentations, web pages, and documents requires consistent design decisions across formats. This Skill converts an annotated content.md file into a single design-spec.json that defines shared palettes, fonts, logo placement, and per-format layout mappings, so every downstream format-builder starts from the same design baseline. ## Core Features & Use Cases - Design Spec Generation: Parses content.md sections and HTML-comment annotations to produce a validated design-spec.json with per-format layout mappings for PPT, web, and Word targets. - Brand Consistency: Resolves named palettes and brand templates from ~/.lintel/brand/, applies shared fonts and colors, and enforces validation rules like layout rotation and font size bounds. - Use Case: After generating content.md with the write stage, run this Skill with --target-formats ppt,web to get a design spec that the PPT and web format-builders consume, then re-run with a different --palette to A/B-test brand themes. ## Quick Start Ask the agent to generate a design spec from content.md targeting ppt and web formats using the default palette.

Frequently Asked Questions about generate-design

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

FAQPage Schema
How do I generate a design spec from markdown content?▼

Run the Skill with --content pointing to your content.md and --target-formats listing the outputs you need, such as ppt,web,word. It parses section annotations and writes a design-spec.json with per-format layout mappings, palette, and fonts.

What is design-spec.json used for in a content pipeline?▼

design-spec.json is the shared design baseline consumed by format-builders like generate-ppt, generate-web, and generate-word. Each builder reads the spec and applies its own format-specific design pass named in the design_pass_hook field.

Can I use a custom brand palette for document generation?▼

Yes, pass --palette with a palette name resolved from ~/.lintel/brand/palettes/<name>.json. If the named palette is missing, the Skill falls back to the default palette and flags the substitution.

What happens if a brand template is missing?▼

If a format template is missing from ~/.lintel/brand/<format>-templates/ and --use-defaults is not set, the Skill exits with BLOCKED status and instructs you to drop a template into the brand directory. Templates older than 90 days trigger a staleness warning.

When should I not use a design spec generator?▼

Skip it when you have no content.md yet, when you only need a visual mockup without real content, or when you want format-specific design tweaks. Per-format fidelity adjustments belong in the format-builder's design pass, not the shared baseline.