marketing-vs-product-system
FeaturedA marketing site and the product it sells share a brand but not a design system. The surfaces differ in density, type scale, radius and weight for good reasons, and those differences are legitimate, but the token layer underneath them must stay single. The same rule covers the other surfaces a brand runs, including documentation, transactional email and a status page. Use when a product app and its public site drift apart, when deciding which values may differ between surfaces, when a signed-in surface needs a theme the marketing site does not have, when a component renders in both, when unifying a token layer that has already forked, or when deciding who owns it.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- dembrandt
- Repository
- dembrandt/dembrandt-skills
- Created
- 5 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
brand-and-design-system
Use when doing brand or design-system work. Covers positioning, verbal identity, color and type scales, tokens, component specs, accessibility, and developer handoff.
layout-paradigms-and-consistency
A layout is not a neutral container — choosing the right layout paradigm (feed, board, table, canvas, master-detail, dashboard, gallery, timeline, map, single-focus, narrative long-scroll) is a design decision that shapes how content is understood. Landing and marketing pages get a product narrative framework — hook, problem, USP, value props, proof points, how it works, stakes, CTA — used to review whether the page carries a visitor to a decision. Once chosen, the same paradigm and page skeleton must be reused consistently across the application so users build one mental model. This is consistency at the macro scale, above component and token consistency. Use when deciding the overall structure of a screen, designing page templates, or reviewing whether screens across a product feel like one coherent application.
design-taste
Anti-slop visual judgment for landing pages, marketing sites, storefronts, portfolios, redesigns. Use for desain landing page, layout LP, homepage or hero design, storefront/PLP/PDP/cart design, design review, redesign, design tokens, visual polish, or UI that looks AI-templated. Choose Brand/Marketing, Storefront/Commerce, or DR/COD Funnel mode; honor existing project tokens over defaults. Defaults to a designed light theme; dark only when genuinely designed, not inverted. Pair with the installed framework skill for implementation. Not for admin/data-dense UI (admin-dashboard), commerce behavior (storefront-ux), copywriting, component installation, or browser evidence (ui-validation).