Editorial Portfolio Chapters logo

Editorial Portfolio Chapters

Community
boraoztunc
editorial-portfolio-chapters

Create or redesign creative-studio, agency, photographer, artist, and portfolio websites where project work leads the story. Use for dark editorial shells, full-bleed campaign media, color-coded case-study chapters, oversized service typography, restrained project reveals, and a decisive contact finale.

Overview

Publisherboraoztunc
Repositoryskills
Skill nameeditorial-portfolio-chapters
Stars
422
Forks
63
Bundled files
2
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by boraoztunc on GitHub. Read the source before you install it.

Installation

Install the Editorial Portfolio Chapters AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/boraoztunc/skills/tree/main/editorial-portfolio-chapters
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/boraoztunc/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/editorial-portfolio-chapters .claude/skills/editorial-portfolio-chapters
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Editorial Portfolio Chapters in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Editorial Portfolio Chapters on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Editorial Portfolio Chapters is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Editorial Portfolio Chapters

Build the page as a sequence of distinct editorial chapters. Let the work establish desire before explaining the studio.

Establish the Story

  1. Open with one strong campaign image and a concise positioning line.
  2. Move directly into selected work. Treat each case study as a new magazine cover.
  3. Explain the studio point of view only after the work has earned attention.
  4. Use oversized service typography as the handoff from proof to contact.
  5. End with a high-contrast contact chapter that feels final, not appended.

Replace all source brands, projects, people, claims, images, labels, and links with original or client-provided content. Preserve pacing and hierarchy, not source content.

Build the Visual System

  • Frame the page with near-black, then introduce warm white and one muted color field per project.
  • Use a grotesk display face with a neutral text companion. Keep labels compact and copy readable.
  • Align to a 12-column grid with 40–64px desktop edge margins.
  • Favor square or deliberately cropped media, restrained radii, hairline rules, and almost no shadow.
  • Let the strongest proof change scale. Do not turn every section into a hero or bento grid.
  • Keep full-bleed chapters rare and purposeful.

Compose the Page

  • Header: place compact navigation at the outer edges and keep the identity centered or strongly anchored.
  • Hero: reserve most of the first viewport for one stable image; expose the first project below the fold.
  • Projects: alternate dark framing with muted color panels; show title, role, year, and action without hover.
  • Studio: use an asymmetrical portrait or process composition instead of a generic team-card grid.
  • Services: set capabilities as large semantic headings or links with controlled wrapping.
  • Contact: switch to one unmistakable signal color and one primary action.
  • Footer: resolve navigation, location, social links, and legal text without competing with the contact ask.

Implement the Signature Interactions

Editorial project panel reveal

  • Reserve the panel height before media loads.
  • Clip only the image layer; keep title and metadata selectable.
  • Reveal with a 500–760ms mask or shallow translate.
  • On hover or focus, scale media no more than 1.02 and expose the same project action.
  • Keep every panel understandable when static.

Oversized service handoff

  • Use clamp() for scale and a short edge-aligned text mask.
  • Shift weight, underline, or tone on hover and focus without moving layout.
  • Open optional details with semantic disclosure behavior, Escape support, and focus return.
  • Wrap deliberately on mobile and render immediately under reduced motion.

Motion Defaults

  • Use 160–220ms for control feedback and 500–760ms for section entrances.
  • Stagger direct children by 45–70ms with cubic-bezier(.22,.61,.36,1).
  • Keep parallax below 5% and the hero stable enough to study.
  • Tie navigation or background changes to section boundaries.
  • Pause offscreen media and observers; clean up timelines on route changes.
  • Do not hijack scroll.

Validate

  • Confirm logical heading order, visible focus, useful alt text, and contrast through every color change.
  • Test keyboard, touch, 200% zoom, narrow mobile, slow media, missing media, and reduced motion.
  • Confirm case studies remain readable before animation and no source content was lightly paraphrased.
  • Remove invented awards, clients, outcomes, or claims when evidence is unavailable.

Source-Backed Prompt Pack

Use Mara Voss Interaction Prompt Pack as a worked example for turning one editorial portfolio into portable loader, pinned chapter, archive, inspection, sticky-stack, and footer interaction prompts. Reuse the motion logic, not the reference identity, copy, imagery, or claims.

Avoid

  • Explaining the studio before showing its work.
  • Repeating identical rounded cards across every chapter.
  • Fast card choreography, large parallax, or decorative motion loops.
  • Hiding project titles or actions until hover.
  • Copying source imagery, brand language, project names, or client claims.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Editorial Portfolio Chapters AI skill do?

Create or redesign creative-studio, agency, photographer, artist, and portfolio websites where project work leads the story. Use for dark editorial shells, full-bleed campaign media, color-coded case-study chapters, oversized service typography, restrained project reveals, and a decisive contact finale.

Why use Editorial Portfolio Chapters on TypingMind?

Because you install it once and use it with any model. Editorial Portfolio Chapters is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Editorial Portfolio Chapters in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/boraoztunc/skills/tree/main/editorial-portfolio-chapters. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Editorial Portfolio Chapters?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Editorial Portfolio Chapters?

As many as you like. As long as a model supports skills, you can use Editorial Portfolio Chapters with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Editorial Portfolio Chapters AI skill free?

Yes. It is published on GitHub by boraoztunc under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇