design-references

design-references

Status: stub. This skill is a placeholder until the designer consolidates Stoïk's brand guidelines in Figma and Notion. It exists so visual-primary output skills (Phase 5) can already declare their dependency on it without breaking.

When this skill will be loaded (in the future)

• output-presentation — for slide layouts, brand colors, typography.
• output-one-pager — for compact visual layout patterns.
• output-landing-page — for hero, section, and CTA patterns.
• output-visual-brief — for component references handed to designers or to Claude Design.
• Any output skill that needs to embed brand visuals.

How this skill will fetch (in the future)

Use the Figma MCP for design tokens, components, and screenshots. Use the Notion MCP for any guideline pages that wrap or annotate Figma references.

Expected Figma resources:

• A "Brand" or "Design System" file containing tokens (color, type, spacing).
• Component libraries for slide layouts, social cards, landing page sections.
• Screenshot frames showing approved past assets as reference.

Expected Notion resources:

• A "Brand Guidelines" page that links to the Figma files.
• Any written do/don't notes accompanying the visual system.

Current behavior (v1 stub)

When invoked in v1, this skill should:

1. Return an explicit status: stub flag.
2. Return a short note: "Design references are not yet consolidated in Figma or Notion. Visual-primary outputs should generate without brand visuals or escalate to the designer."
3. List the future-fetch targets above so the caller can show the user what is expected.
4. Not block. Visual-primary output skills should proceed with structural briefs (text and layout intent) and let Claude Design or a human designer apply visuals downstream.

Output shape (v1)

status: stub
note: <text>
expected_sources:
  figma:
    - <description>
  notion:
    - <description>
escalation_path: contact designer for current references

Gaps and TODOs

• TODO (designer): consolidate brand colors, typography, spacing in a single Figma file and confirm the file ID.
• TODO (designer): tag a stable component library in Figma so this skill can pull from it.
• TODO (designer): write the "Brand Guidelines" Notion page that wraps the Figma references for non-designers.
• TODO (this skill): when the above land, replace this stub with the full fetch logic. The output shape will expand to include tokens, components, examples, and direct Figma/Notion source URLs.

Phase dependency

Phase 5 (visual outputs) is gated on this skill graduating from stub to functional. Surface this dependency in any planning conversation about visual outputs.

Visual codes already defined (from FR Brand Platform)

Until the designer consolidates references, these rules from the team's earlier Brand Platform deck (FR Pitch, captured 2026-05-10) apply by default for any visual-primary output. They are operationally useful even before a full system lands.

Brand signature:

• Two overlapping circles representing Assurance and Cybersécurité, with "stoïk" sitting in the intersection. The intersection is the core idea. Used on cover slides, About sections, brand placements.

Color cues observed in the deck:

• Primary brand blue (saturated mid-blue) for emphasis, headers, and the brand mark.
• Pale blue-tinted backgrounds and card fills.
• Black for the intersection element in the Venn signature.
• Grey for body text and secondary elements.

The designer will codify exact tokens. Until then, do not invent specific hex values — describe colors qualitatively in visual briefs.

Visual do's:

• Imagery that evokes protection and care: shields, locked windows, calm browser interfaces, clean phone/desktop mockups.
• Generous whitespace, sentence-case headings, clean typography.
• Diagrammatic explanations (Venn, three-card layouts, simple flows).

Visual don'ts:

• No skulls, no hoodie-wearing hackers, no anonymous masks, no green-on-black "matrix" code, no ransom-note typography. The cybersecurity press uses these clichés constantly; Stoïk explicitly rejects them.
• No dark, threatening, or anxiety-inducing aesthetics.
• No childish or comedic illustration styles.
• No startup-y illustration styles (over-saturated, overly playful) when the audience is insurance.

Layout patterns from the deck (still in use):

• Three-card horizontal layouts (mission/ambition/promise; broker triptych; do/don't comparisons).
• Title + horizontal subtitle + content area.
• Section divider slides with section number ("01") and section title in white-on-blue.

Pending placeholders (from slide 22 of the deck, "Mise en application"): Brochure / Flyer Stoïk, Stoïk présentation_Broker, Website. These were marked as "lien en attente" and have likely been refreshed; confirm during the next foundation review.

Source: Pitch deck "Brand platform (FR)", URL on file with Maike. Outdated overall but visual codes remain applicable.

Sourcing note

When brand-foundations and this skill diverge on a visual question, this skill wins for visuals. When they diverge on a tonal or messaging question (e.g., how to caption a visual), brand-foundations and tov-en win.