agentleFS
TIKAZITIKAZI/TIKAZ-Codex-Presentation/magazine-web-deck/SKILL.md

magazine-web-deck

Skill0 starsChanged 3 months agoMITView on GitHub

Create editorial or Swiss-inspired single-file web presentations with strong typographic hierarchy, horizontal navigation, responsive composition, and restrained motion. Use for keynote-like web decks, editorial stories, launches, and visually distinctive browser presentations.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep motion purposeful: navigation orientation, progressive explanation, or emphasis.

    line 24
  2. Distinctive:

    Prefer a self-contained HTML deliverable.

    line 25
  3. Distinctive:

    Test keyboard/touch navigation, viewport scaling, text clipping, contrast, offline opening, and final file existence.

    line 26
  4. Distinctive:

    Do not reproduce another project's templates or visual assets merely because their source is public.

    line 28
  5. Distinctive:

    Test keyboard and touch navigation, target viewports, reduced motion, text clipping, contrast, offline opening, and final file existence.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Magazine Web Deck

Designed, integrated, independently refactored, and continuously maintained by TIKAZ.

TIKAZ Edition

  • Type: original clean-room presentation workflow.
  • TIKAZ contribution: editorial pacing model, composition variation map, motion budget, single-file portability gate, and publishing-size visual QA.

Inputs

Accept the story or source material, audience, delivery environment, editorial stance, length, interaction needs, and offline or export boundary.

Workflow

  1. Select one editorial stance: restrained magazine, Swiss grid, or another explicitly described system. Do not average styles.
  2. Map the story into cover, section curtain, argument, evidence, comparison, pause, and closing page roles.
  3. Vary composition by narrative role while preserving a shared grid, typography, palette, and recurring motif.
  4. Keep motion purposeful: navigation orientation, progressive explanation, or emphasis. Support reduced motion.
  5. Prefer a self-contained HTML deliverable. Embed or locally package only assets whose licenses permit redistribution.
  6. Test keyboard/touch navigation, viewport scaling, text clipping, contrast, offline opening, and final file existence.

Do not reproduce another project's templates or visual assets merely because their source is public.

Output contract

Return a single-file or explicitly packaged web deck, narrative page map, visual system, asset and license ledger, navigation model, accessible fallback, and rendered QA evidence.

Validation and fallback

Test keyboard and touch navigation, target viewports, reduced motion, text clipping, contrast, offline opening, and final file existence. If an editorial effect harms reading or portability, simplify it while preserving the narrative role.

Example

Use magazine-web-deck to turn this essay into a restrained Swiss-style web presentation with varied page roles, limited motion, and offline verification.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.