Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Mira Presentation Design

ASecurity

**Mode skill.** Default-enabled on the Brand specialist.

6 stars
0 votes
0 copies
0 views
Added 9/20/2026
designrustgoexpress

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add FerroxLabs/murage --skill mira-presentation-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mira Presentation Design?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Mira Presentation Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ferroxlabs-mira-presentation-design/badge)](https://www.skillsdirectory.com/skills/ferroxlabs-mira-presentation-design)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: mira-presentation-design
description: "**Mode skill.** Default-enabled on the Brand specialist."
metadata:
  author: wayland
  version: "1.0.0"
  category: "mira"
---

# presentation-design

**Mode skill.** Default-enabled on the Brand specialist.

## When to use

Use when the deliverable is the **visual side** of a deck, hero block, or landing page: cover slide, section dividers, template grid, hero composition, type hierarchy, image treatment. Run after the visual system is locked in `TEAM_MEMORY.md`. If not locked, run `visual-system` first.

This mode is *visual only*. Slide narrative, speaker notes, deck story arc, and headline copy go to the presentation-content and copy specialists. You set the stage; they fill it.

Trigger phrases: "Design the cover slide." / "What should our hero look like?" / "Build a slide template." / "How should this section divider look?"

## Procedure

**1. Pull the anchors.** Open `TEAM_MEMORY.md`. Confirm: onlyness statement, dominant attribute, two type voices, ownable hue, layout density, motif rule. If any of the six is missing, escalate before designing.

**2. Decide the composition rule for the surface.**

- **Cover / hero.** One idea on the page. The strongest expression of the dominant attribute. *Quiet* attribute = mostly negative space. *Loud* attribute = the cover risks being too much and is fine.
- **Section divider.** Same composition as the cover, scaled down. One element changes (color block, oversized numeral, treated photograph) so the reader registers the shift in half a second.
- **Content slide.** Inverse rule: the attribute lives in the *system*, not the slide. The slide gets out of the way of the information.

**3. Set the type hierarchy.**

- **Hero headline.** Display face, largest size in the deck, set tight. One line if possible. If two, the second is significantly smaller.
- **Section label / eyebrow.** Body or mono, small caps, tracked open, very small. Functional, not decorative.
- **Body line.** Body face, regular weight, set for the longest realistic line length.
- **Three sizes max per slide.** Four always means one is decorative and should be cut.

**4. Set the spatial rule.**

- **Grid.** Column count (12 for landings, 6 for decks) and a single baseline unit (8px default). Every block snaps; every vertical space is a multiple.
- **Anchor margin.** One generous edge margin held across every slide. Inconsistency reads as sloppiness.
- **Density check.** If the slide pushes against the attribute (*spacious* attribute but crammed slide), cut content before adjusting type size.

**5. Image treatment.**

- **One treatment, one source.** Full-bleed photography, treated duotone, grayscale, illustrated, or blocked. Mixing stock, brand, and illustration is the fastest way to break the system.
- **The "never" list.** Re-read the system's image-never rule. If a candidate image violates it, replace it. No negotiation.

**6. Audit before shipping.** Walk through with the name covered. If a teammate can't place a single slide as belonging to this brand, the design is failing. Recognizability is the test.

## Decision rules

- **Cover does the work the deck title can't.** Weak cover + strong content reads as amateur. Strong cover + adequate content reads as a brand.
- **A landing hero is a cover slide that has to convert.** Same composition logic plus one primary CTA and one objection-defusing subline (Copy writes).
- **Data slides use the body face only.** Display type in charts reads as theater. Data wants quiet type.
- **Section dividers earn their place.** Eight dividers in twenty slides is a navigation problem dressed as a design problem.
- **Animation is a brand choice, not a feature.** Pick one transition (or none) and hold it.

## Anti-patterns

- Designing every slide as a hero. The deck has no rhythm and burns out by slide four.
- Centered text everywhere. Pick left-aligned (most surfaces) or centered (cover and dividers only), and hold it.
- Logo on every slide. The brand lives in the *system*. Footer mark on cover and close is usually enough.
- Two transitions, three icon styles, four shades of the primary. Each adds entropy and costs recognizability.
- Treating slide and landing design as separate problems. A deck and a landing page that don't look related is two brands.
- Letting deck content drive design. Push content back to Copy with a slot constraint instead of warping the layout.

## Before / after

**Brief:** *"Cover for an investor deck. Onlyness: only daily planner that forces creatives to schedule the messy middle. Attribute: unflinchingly honest. System: slab display, mono captions, rust on off-white, dense, marked-up date grids only."*

**Before** (default-deck move): centered logotype, centered gray-sans subtitle, soft drop shadow, stock photo of a smiling team behind a frosted overlay.

**After**: off-white field. Slab headline left-aligned at the top third, tight tracking, near-black: *"Week 3 is where the project dies."* Mono caption bottom-left: *Daily planner, 12-month edition.* One rust mark — a struck-through date cell — anchored bottom-right. No stock photo, no logotype on the cover. Reads as the brand at a glance with the title covered.

Attribution

FerroxLabsFerroxLabs
View sourceMore from FerroxLabs →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Responsive Design

Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.

393432 votes

Mermaid Diagrams

Creating and refining Mermaid diagrams with live reload. Use when users want flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, or any other Mermaid visualization. Provides best practices for syntax, styling, and the iterative workflow using mermaid_preview and mermaid_save tools.

2032 votes

sleek-design-mobile-apps

Use when the user wants to design a mobile app, create screens, build UI, or interact with their Sleek projects. Covers high-level requests ("design an app that does X") and specific ones ("list my projects", "create a new project", "screenshot that screen").

5711 votes

swiftui-design-skill

SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.

1801 votes

Ios Hig

Use when designing iOS interfaces, implementing accessibility (VoiceOver, Dynamic Type), handling dark mode, ensuring adequate touch targets, providing animation/haptic feedback, or requesting user permissions. Apple Human Interface Guidelines for iOS compliance.

761 votes
View all in design →