create-section
Automates the setup and content creation for new sections in the AI Native Developer Workshop.
Install
mkdir -p .claude/skills/create-section && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10488" && unzip -o skill.zip -d .claude/skills/create-section && rm skill.zipInstalls to .claude/skills/create-section
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when creating a new section for the AI Workshop presentation. Guides through title slide setup, layout choices, and content gathering. Activates when user wants to add a new topic section to the slideshow.Key capabilities
- →Setup title slides
- →Choose color themes
- →Gather verified content
- →Update project files
How it works
Guides the user through a structured creation process, including title slide generation and project file updates.
Inputs & outputs
When to use create-section
- →Add a new topic to the workshop
- →Generate a title slide for a new section
- →Research content for a workshop module
About this skill
Create New Section Skill
This skill guides the creation of a new section for the AI Native Developer Workshop presentation.
When to Activate
- User asks to "create a new section"
- User wants to "add slides about [topic]"
- User mentions adding a new topic to the workshop
- User requests a new section file in
src/sections/
Workflow
Step 1: Gather Section Requirements
Before creating any files, ask the user these questions:
- Section Topic: What is the main topic for this section?
- Section Color: Which color fits best?
bluegreenpurpleorangegray- Overview/Introduction topics
- Source Material: Does the user have a URL or reference to pull content from?
Step 2: Content Gathering (Optional)
If the user provides a URL or wants help researching content:
Invoke the Slide Content Creator agent using:
@agent Slide Content Creator [URL or topic]
The Slide Content Creator will:
- Fetch content from the provided URL
- Extract verified facts only
- Propose a structured list of slides
- Validate all claims against sources
Wait for the agent's output before proceeding to implementation.
Step 3: Title Slide Setup
Every section MUST begin with a title slide. Use this template:
import { IconName } from 'lucide-react';
import { SlideType } from './types';
export const {sectionName}Slides: SlideType[] = [
{
title: "",
subtitle: "",
content: (
<div className="flex flex-col items-center justify-center h-full space-y-6">
<IconName className="w-16 h-16 md:w-20 md:h-20 text-{color}-500" />
<h1 className="text-5xl md:text-6xl font-bold text-{color}-900 text-center">
Section Name
</h1>
<p className="text-xl md:text-2xl text-gray-600 text-center max-w-2xl">
Brief tagline describing what this section covers
</p>
<div className="flex space-x-2 mt-4">
<div className="w-3 h-3 bg-{color}-300 rounded-full"></div>
<div className="w-3 h-3 bg-{color}-500 rounded-full"></div>
<div className="w-3 h-3 bg-{color}-300 rounded-full"></div>
</div>
</div>
)
},
// Content slides follow...
];
Recommended Icons by Topic
| Topic | Suggested Icons |
|---|---|
| LLMs/AI | Sparkles, Brain, Cpu |
| Models | Box, Layers |
| Framework | Target, Compass |
| Code/Copilot | Code, Bot |
| Instructions | ScrollText, FileText |
| Skills | Puzzle, Wrench |
| Spaces/Organization | Layout, FolderOpen |
| Windows/UI | Monitor, PanelLeft |
| Multi-Agent | Network, Users |
| Workflows | Repeat, RefreshCw |
| Context | Brain, Database |
| Security | Shield, Lock |
| Privacy | Eye, EyeOff |
| Testing | TestTube, CheckCircle |
Step 4: File Creation Checklist
When creating the section, complete ALL of these:
-
Create section file:
src/sections/{sectionname}.tsx- Include title slide as first slide
- Export slides array:
export const {sectionName}Slides: SlideType[] = [...]
-
Update index.ts: Add to
src/sections/index.tsexport { {sectionName}Slides } from './{sectionname}'; -
Update main.tsx imports: Add to import statement
import { ..., {sectionName}Slides } from './sections'; -
Add to sections array in
src/main.tsx:{ name: 'Section Name', slides: {sectionName}Slides, color: '{color}', icon: IconName }, -
Add to slides spread in main.tsx:
const slides = [...otherSlides, ...{sectionName}Slides]; -
Import icon at top of main.tsx if not already imported
Step 5: Content Slide Patterns
After the title slide, add content slides using these patterns:
Definition Slide (introducing concepts):
{
title: "Concept Name",
subtitle: "Clear context sentence",
content: (
<div className="flex flex-col space-y-6 max-w-3xl mx-auto">
<div className="bg-{color}-50 p-6 rounded-lg border-l-4 border-{color}-500">
<h3 className="text-2xl font-bold text-{color}-900 mb-4">What is [Concept]?</h3>
<p className="text-lg text-gray-700">Definition here.</p>
</div>
{/* Key points, takeaway */}
</div>
)
}
Grid Slide (multiple related items):
{
title: "Overview Title",
subtitle: "Context",
content: (
<div className="grid grid-cols-1 md:grid-cols-2 gap-4 md:gap-6 max-w-3xl mx-auto">
{/* 2-4 cards */}
</div>
)
}
List Slide (step-by-step content):
{
title: "Process/Steps",
subtitle: "Context",
content: (
<div className="flex flex-col space-y-6 max-w-3xl mx-auto">
{/* Header box, bullet lists, takeaway */}
</div>
)
}
Validation Checklist
Before completing, verify:
- Title slide has empty
titleandsubtitlestrings - Icon imported from
lucide-react - Color scheme is consistent throughout section
- All 4 files updated (section file, index.ts, main.tsx imports, main.tsx arrays)
- TypeScript compiles without errors
- Responsive classes used (
md:breakpoints where appropriate)
Example Conversation Flow
User: "Create a new section about prompt engineering"
Response: "I'd like to help you create a new section about prompt engineering. A few questions first:
-
Color scheme: This seems like it fits green - helping users communicate effectively with AI. Does that work, or would you prefer a different color?
-
Source material: Do you have any URLs or documentation you'd like me to pull content from? I can use the Slide Content Creator agent to extract verified facts from sources.
-
Scope: What key topics should this section cover? (e.g., prompt structure, few-shot examples, chain-of-thought, etc.)
Once I have this info, I'll set up the title slide and content structure."
When not to use it
- →When editing existing slides
- →When the workshop structure is finalized
Prerequisites
Limitations
- →Requires manual input for section requirements
- →TypeScript compilation must be verified
How it compares
Enforces a consistent workshop template and automated file updates rather than manual slide creation.
Compared to similar skills
create-section side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| create-section (this skill) | 0 | 7mo | No flags | Beginner |
| paper-2-web | 0 | 2mo | Review | Intermediate |
| html-artifact | 0 | 1mo | No flags | Intermediate |
| ml-paper-writing | 48 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
paper-2-web
bg-szy
This skill should be used when converting academic papers into promotional and presentation formats including interactive websites (Paper2Web), presentation videos (Paper2Video), and conference posters (Paper2Poster). Use this skill for tasks involving paper dissemination, conference preparation, cr
html-artifact
MVPavan
Create polished single-file HTML artifacts as an alternative to markdown for documents meant to be read by humans. Use whenever the user asks for an implementation plan, status report, post-mortem, architecture doc, scaling analysis, capacity dashboard, research explainer, concept walkthrough, PR wr
ml-paper-writing
davila7
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.