Run any Skill in Manus with one click

creative-brief-selector

Produce a creative brief grounded in live reference sites and deliberately distinct from existing demos, for any new brand build. Composes with brand-archetype-system and creative-direction. Use this skill at the start of any brand or microsite build when the result needs to land in a specific aesthetic position and not drift into a default house style. Triggers on creative brief, design brief, build brief, brand direction, where should this brand sit, what should this site look like, reference sites for, archetype for, distinct from our other brands, divergence from prior, not the same as. Also triggers when prior builds have come out as siblings and a systematic divergence approach is needed.

Run Skill in Manus

Stars352

Forks44

UpdatedMay 29, 2026 at 06:23

Source

rampstackco

rampstackco/claude-skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Art DirectorsArts, Design, Entertainment, Sports, and Media Occupations27-1011L4

File Explorer

19 files

SKILL.md

readonly

More from this repository

same repository

evidence-based-reviews

rampstackco/claude-skills

Produce honest product reviews and buying guides without fabricated first-hand experience, using disclosed evidence tiers: verified specs, owner-experience synthesis at scale, expert triangulation, and hands-on only when true. Use this skill whenever the user wants to write product reviews or buying guides without hands-on access, set up a review methodology, add evidence disclosure to review content, align reviews with Google's reviews system or FTC affiliate disclosure expectations, or decide when Review and Product schema are honest to use. Triggers on product review, buying guide, best-of list, review methodology, evidence basis, hands-on testing, we tested, affiliate review site, review disclosure, methodology block, original research, reviews system. Also triggers when review content claims testing that did not happen, or when an affiliate site needs a trust mechanism that survives scrutiny.

2026-06-12352

creative-direction

rampstackco/claude-skills

Walk the user through four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) and produce a structured aesthetic brief that downstream content, copy, design, and art-direction skills consume as required input. The aesthetic depth layer, distinct from `creative-brief` (operational kickoff: scope, audience, deliverables, constraints). Use when a project needs aesthetic coherence across many small decisions and the user has only a vague feeling, or when multiple downstream aesthetic-producing skills need a shared brief. Triggers on creative direction, aesthetic direction, set the aesthetic, define the visual direction, what's the vibe, what's the tone, the four axes. Does NOT fire for a general kickoff brief (use `creative-brief`), tactical single-piece work, already-documented direction, purely functional output, or locked production-stage work.

2026-06-01352

integration-orchestrator

rampstackco/claude-skills

Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's tools (Jira, Linear, Notion, Figma, GitHub) with AI agents via MCP and CLI. A temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates. Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction). Triggers on integration orchestrator, delivery cadence, project orchestration, when does the brief lock, how to phase creative direction, design-development handoff, QA gate, agent-driven QA, and when a creative-direction project is starting, mid-flight with broken cadence, or integrating AI agents into PM workflow. Does NOT fire for project scoping (use `creative-brief`), aesthetic direction (use `creative-direction`), or general project management without a creative-direction throughline.

2026-06-01352

logo-design

rampstackco/claude-skills

Generate logo variants for a brand, producing multiple production-grade marks across different architectures (wordmark, lockup, symbol-only, letterform-as-symbol, monogram) with rationale, application specs, and decision-ready presentation. Distinct from `brand-identity`, which produces the complete system (logo plus color, type, voice, applications). Goes deep on the logo specifically: typographic register, symbol approach, application-context discipline (16px favicon, embroidery, signage, motion), and production specs (SVG-ready, single-color, reverse). Triggers on logo design, design a logo, wordmark, monogram, lockup, mark variants, logo iterations, redesign or refine the logo, logo refresh, letterform-as-symbol, and exploring mark variants for an established brand. Does NOT fire for full brand identity (use `brand-identity`), positioning or strategy (use `brand-discovery`), project-wide creative direction (use `creative-direction`), or one-off illustration.

2026-06-01352

vertical-site-conventions

rampstackco/claude-skills

Compose pages and sites that read as their vertical: ecommerce-catalog storefronts that look like storefronts, hospitality-food sites that look like restaurants, b2b-manufacturer sites that look industrial. Use this skill whenever the user wants to build a site that looks like the vertical it serves, fix a build that reads as generic or off-vertical, build to an experience bar produced by competitor-experience-audit, or compose pages with the merchandising, density, and layout conventions a credible site in the category is expected to carry. Triggers on vertical conventions, storefront layout, ecommerce layout, retail conventions, merchandising layout, category page composition, site composition, build to the experience bar, make it look like the vertical, off-vertical, looks generic, build conventions for a vertical, site grammar. Also triggers when a build that is technically clean reads wrong for its category, and the cause is composition, not visual taste.

2026-05-26352

competitor-experience-audit

rampstackco/claude-skills

Audit the brand, UX, and site design of the leading sites in a vertical as a set of observable cross-site patterns, producing the experience bar a new build must meet or beat. Use this skill whenever the user wants to assess the competitive design field, capture vertical conventions, identify the design and UX bar of a category, or set the experience standard before a build. Triggers on competitor experience audit, UX audit, site design audit, brand audit, design conventions, what makes these sites good, vertical conventions, storefront patterns, merchandising patterns, layout density, primary task, design bar, category conventions, retail vs marketing register, what does the field do. Also triggers when an audit of the competitive field has captured technical signals (SEO, accessibility) but never named the brand, UX, or design conventions, and the build downstream will read as off-vertical without that bar.

2026-05-25352

name	creative-brief-selector
description	Produce a creative brief grounded in live reference sites and deliberately distinct from existing demos, for any new brand build. Composes with brand-archetype-system and creative-direction. Use this skill at the start of any brand or microsite build when the result needs to land in a specific aesthetic position and not drift into a default house style. Triggers on creative brief, design brief, build brief, brand direction, where should this brand sit, what should this site look like, reference sites for, archetype for, distinct from our other brands, divergence from prior, not the same as. Also triggers when prior builds have come out as siblings and a systematic divergence approach is needed.
category	brand
catalog_summary	Live-reference-grounded creative briefs with divergence check against prior builds
display_order	6

Creative Brief Selector

A starting-point selector for brand and microsite builds. Given a business spec (name, vertical, shape, one-line vibe, optional list of shipped demos), produces a creative brief grounded in three things:

An archetype position from brand-archetype-system, picked or composed to be deliberately distinct from the shipped demos.
A small set of live reference sites for that archetype-and-vertical combination, drawn from a curated bank plus optional per-build discovery.
A divergence check against the shipped demos that flags palette, voice, structural pattern, and section-shape overlap before the brief is handed off.

The brief output is concrete tokens, not abstract families, including explicit section-shape choices (hero shape and footer shape) as first-class outputs alongside palette and voice. It is meant to be loaded by downstream build skills as the single creative artifact for the build.

When to use

Starting any new brand or microsite build that should land in a specific aesthetic position.
The first build in a portfolio (no prior builds to diverge from yet, but the divergence schema can be seeded for the next one).
The second through nth build in a portfolio, where the risk of sibling output is real.
After a portfolio audit that surfaced sibling builds: this skill is the systemic fix for the pattern.
When a build's creative direction is being chosen between two adjacent archetypes and the call needs a reference-grounded reason.

When NOT to use

The user wants pure aesthetic methodology guidance (use creative-direction).
The user has a finished archetype and a finished brief and is asking for execution (skip to the downstream build skills).
The user wants a logo or a finished identity (use logo-design, brand-identity).
The user wants to define voice for an existing brand (use brand-voice).
Defining brand strategy from zero positioning (use brand-ideation first, then return to this skill).

How this composes with other skills

This skill works upstream of build-time skills and parallel to the aesthetic methodology layer:

brand-archetype-system (upstream input). The archetype catalog this skill picks from. The skill names the archetype in the rendered brief; it does not redefine the archetype's defaults.
creative-direction (parallel input). The four-axis vocabulary the archetypes reference. If the consumer needs the full axis brief, run creative-direction first; this skill's brief consumes its outputs.
brand-identity (downstream). Once the brief is approved, brand-identity turns it into a finished identity system.
landing-page-copy, content-and-copy, art-direction (downstream). Every downstream skill that produces aesthetic output references this skill's brief.

Direct verbatim copying of an archetype's default palette into a new brand is the failure mode this skill exists to prevent. The brief shifts the archetype's defaults toward the business spec's specifics.

The framework: five steps, three rules, one hybrid bank

Locate the design space. Pick one to two candidate archetypes from brand-archetype-system that fit the vertical and shape.
Run input-side divergence. Read the shipped-demos signatures. Discard candidates that would land sibling to anything shipped. Record what was rejected and why.
Pull references. From the curated reference bank under references/reference-bank/, load the file(s) matching the chosen archetype-and-vertical. Augment with one to two discovered live references if the bank is sparse. Add discovered references back to the bank in the build PR.
Adapt. Shift the chosen archetype's defaults (palette, type, voice, layout, imagery direction) toward the business spec. The brief lands as concrete tokens, not abstract families.
Render and verify. Render the brief using the template in references/02-brief-template.md. Run output-side divergence. Output the brief plus the references list plus the divergence-check result.

Full step-by-step in references/01-process.md. The divergence schema and its three overlap rules are in references/03-divergence-check.md.

The hybrid references model

A curated bank that grows with each build. Each file under references/reference-bank/ covers one archetype-and-vertical combination and holds three to six live reference URLs, each with a one-line why and optional palette or type observations. The bank ships with three seed combinations covering western-boot maker, heritage barbershop, and balloon-ride experience.

When a build draws from a sparse combination, the build is expected to commit the live references it discovered back to the bank as part of its build PR. The bank gets denser with use.

The divergence schema

Each shipped demo carries a signature with seven fields:

slug
archetype (the canonical archetype name from brand-archetype-system)
dominant_hue_family (the recognizable colour family, e.g. leather-bone-saddle, dawn-navy-coral, dark-linen-amber)
voice_register (e.g. story-forward third-person, atmospheric second-person, fitment-first technical)
primary_structural_pattern (e.g. shoppable-grid-product-forward, arc-timeline-hero, fitment-selector-then-rails)
hero_shape (e.g. dual-column-image-and-text, wide-photograph-with-band-below, full-bleed-image-with-overlay; canonical vocabulary in references/05-section-shapes-vocabulary.md)
footer_shape (e.g. single-line-strip, multi-column-sitemap, type-only-no-links; same vocabulary file)

Overlap rules (full set in references/03-divergence-check.md):

Two demos share archetype AND share dominant_hue_family => SIBLING (block).
Two demos share archetype AND share voice_register AND share primary_structural_pattern => SIBLING (block).
Two demos share only dominant_hue_family across different archetypes => WARN.
The candidate's hero_shape matches the hero_shape of two or more shipped demos => WARN.
The candidate's hero_shape matches three or more shipped demos AND any share an archetype family => BLOCK.
The candidate's footer_shape matches three or more shipped demos => WARN.

A worked example file of seven signatures lives at references/04-shipped-demos-signatures-example.md for illustration; the live signatures file for any consuming project lives in that project, not in this skill.

Trademark and attribution

Archetypes are NAMED for aesthetic families, NOT for brands, following the convention of brand-archetype-system. Live reference sites are cited as exemplars using nominative attribution language: "exemplified by [URL]", "characteristic of", "in the register of". This is descriptive and nominative fair use territory, durable across brand redesigns. A brand that pivots its identity does not invalidate the archetype it once exemplified.

Reference files

references/00-overview.md - The case for the skill, the hybrid references model, the two-direction divergence, the trademark posture.
references/01-process.md - The five-step process, each step concrete enough to execute.
references/02-brief-template.md - The fillable brief template with section-by-section guidance.
references/03-divergence-check.md - The signature schema and the overlap rules.
references/04-shipped-demos-signatures-example.md - Worked example signatures file with seven demos.
references/05-section-shapes-vocabulary.md - Canonical open vocabulary of hero and footer section shapes plus archetype affinities.

The curated reference bank lives in a reference-bank/ subdirectory under references/. The bank ships with a README plus three seed archetype-and-vertical files: premium-dtc-maker-western-boots.md, heritage-local-service-barbershop.md, and hospitality-experience-balloon-ride.md. The bank's purpose and extension procedure are documented in its README; the seed files each carry three to four positive live references and one to two negative references for the chosen position. Load the bank file matching the build's archetype-and-vertical at step 3 of the process.