Index of every page on this site: llms.txt
All skills
shanraisshan avatar

/presentation-structure

@28a3eb4
Run it yourself

Knowledge about the presentation slide format, weight system, navigation, and section structure

  • 1 file
  • 3.5 KB
  • Updated 9 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/shanraisshan/claude-code-best-practice/presentation-structure

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈30 tokens for metadata: the name and description. ≈851 when used: this file.

Description uses 1.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈120 characters, or 1.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Presentation Structure Skill

Knowledge about how the presentation at presentation/index.html is structured.

File Location

presentation/index.html — a single-file HTML presentation with inline CSS and JS.

Slide Format

Each slide is a div with data-slide (sequential number) and optional data-level (journey level at transition points):

<!-- Regular slide — inherits level from previous data-level slide -->
<div class="slide" data-slide="12">
    <h1>Slide Title</h1>
    <!-- content -->
</div>

<!-- Level transition slide — sets new level for this slide and all following -->
<div class="slide section-slide" data-slide="10" data-level="low">
    <h1>Section Name</h1>
    <p class="section-desc">Level: Low — description of this section</p>
</div>

<!-- Title slide (centered) -->
<div class="slide title-slide" data-slide="1">
    <h1>Presentation Title</h1>
    <p class="subtitle">Subtitle text</p>
</div>

Journey Bar Level System

The presentation uses a 4-level system instead of cumulative percentages:

  • Levels are set via data-level attribute on key transition slides (section dividers)
  • All slides after a data-level slide inherit that level until the next transition
  • The journey bar fills to 25% / 50% / 75% / 100% for Low / Medium / High / Pro respectively
  • The bar is hidden on slide 1 (title slide); from slide 2 onward the bar is shown
  • Slides before the first data-level (slides 2–9) show an empty bar (no level yet set)
  • A .level-badge is JS-injected on the <h1> of slides that carry data-level — do NOT hardcode in HTML

Level Transitions by Section

Section Slide Range data-level Bar Height
Part 0: Introduction Slides 1-4 (none) hidden / empty
Part 1: Prerequisites Slides 5-9 (none) empty
Part 2: Better Prompting Slides 10-17 low 25%
Part 3: Project Memory Slides 18-24 medium 50%
Part 4: Structured Workflows Slides 25-28 (inherits medium) 50%
Part 5: Domain Knowledge Slides 29-33 high 75%
Part 6: Agentic Engineering Slides 34-46 high 75%
Appendix Slides 47+ (inherits high) 75%

Navigation System

  • goToSlide(n) — used in TOC links, must match actual data-slide numbers
  • totalSlides is auto-computed from DOM (document.querySelectorAll('[data-slide]').length)
  • Arrow keys, Space, and touch swipe for navigation
  • Slide counter shows current / total at bottom-left

Renumbering Rules

After adding, removing, or reordering slides:

  1. Renumber ALL data-slide attributes sequentially starting from 1
  2. Update all goToSlide() calls in the TOC/Journey Map slide
  3. The JS totalSlides auto-computes — no manual update needed
  4. Verify no gaps or duplicates exist

Section Divider Format

Section dividers use the section-slide class. Level-transition section dividers carry data-level and show the level name in the description:

<div class="slide section-slide" data-slide="10" data-level="low">
    <p class="section-number">Part 2</p>
    <h1>Better Prompting</h1>
    <p class="section-desc">Level: Low — effective prompting for real results.</p>
</div>

The JS will inject a .level-badge (e.g., "→ Low") into the <h1> at runtime when the level transitions — do not add these manually in HTML.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 28a3eb4. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 1 hour ago.

Activeupdated 9 months ago

README badge

README badge for shanraisshan/claude-code-best-practice/presentation-structure