Content & Media
Content creation, media processing, and design skills
18175 skills in this category
github-wrapped
Generate a verifiable GitHub Wrapped year-in-review as a single-file HTML (raw gh API JSON saved, Python-built dataset embedded), with a Bilibili-style narrative, smooth transitions, and mobile-friendly paged mode. Requires gh CLI to be authenticated.
mongodb-atlas
MongoDB Atlas cloud database management including clusters, schemas, aggregation pipelines, and Prisma ORM integration. Activate for MongoDB queries, schema design, indexing, and Atlas administration.
audit-workflow
Bi-directional comparison workflow for config auditing. Compares what agents expect (from templates/standards) against what repositories actually have, presenting differences with remediation options. Use when agents need to audit configs, validate standards compliance, or identify mismatches between expected and actual configurations.
draw-diagram-skill
Expert guidance for creating syntactically correct and well-structured Mermaid diagrams following best practices. Use when creating flowcharts, sequence diagrams, class diagrams, state diagrams, Gantt charts, ER diagrams, data lineage visualizations, or any other Mermaid visualization.
mobile-development
iOS (Swift, SwiftUI), Android (Kotlin, Compose), cross-platform (Flutter, React Native), and game development (Unity, Unreal). Master mobile and games.
change-request-builder
Creates comprehensive ServiceNow change request documentation when users request CR creation, need to generate change requests, ask to prepare deployment documentation, or mention creating release documentation. Automatically analyzes git history, queries functional requirements from BigQuery, generates technical change summaries, and creates properly formatted YAML files for L'Oréal BTDP deployments.
get-youtube-transcript-raw
Capture a YouTube video transcript as raw material using `ytt`, storing it in the raw/ directory with minimal metadata for later distillation.
speck-help
Answer questions about Speck specs, plans, tasks, requirements, progress, architecture, user stories, feature status, and constitution. Interprets spec.md, plan.md, tasks.md files. Use when users ask about feature requirements, implementation status, or Speck workflow artifacts.
ui-ux-principles
Modern UI/UX design principles for minimalist, efficient, and elegant interfaces. Covers keyboard-driven design, command palettes, component architecture, accessibility, and performance. Based on analysis of Linear, Raycast, Arc, and other top-tier developer tools in 2025. Use when designing UI components, planning features, or reviewing interface design decisions.
tdd
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
typescript-shims
Generates TypeScript declaration files (shims-vue.d.ts, shims-svg.d.ts) to enable type-safe imports of Vue components and SVG files.
dockerignore-config
Docker ignore configuration template and validation logic for optimizing Docker build contexts. Includes 5 required standards (build artifacts, development files, CI/CD and testing, logs and temporary files, root-only placement). Use when creating or auditing .dockerignore files to reduce build context size, improve performance, and ensure security.
brand-guidelines
IdeaForge brand identity - colors, typography, and visual guidelines. Use when styling UI components, creating marketing materials, or ensuring brand consistency.
defense-in-depth
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
nextjs-fullstack
Next.js fullstack development guidelines for React 19 and Next.js 15+. Use when building Next.js applications with Feature-Sliced Design, TailwindCSS v4, ShadCN, Jotai, React Query, and Supabase integration. Covers file naming, component architecture, testing with Vitest/Playwright, UI/UX design patterns, and Toss frontend principles.
coaching-materials-creator
This skill should be used when creating coaching guides, peer learning structures, and post-workshop support materials. Use this skill to design coaching conversations using Kolb's cycle, create community of practice frameworks, and enable sustained learning.
hub-news-posts
This skill should be used when creating Galaxy Hub news posts, writing content for galaxyproject.org/news, or converting content to Galaxy Hub markdown format.
skill-developer
Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.
testing-test-writing
Write strategic, behavior-focused tests for core user flows and critical functionality using Vitest for unit tests and Playwright for end-to-end testing. Use this skill when writing test files, testing utilities, or implementing test coverage for critical paths. When working on Vitest test files (.test.ts, .spec.ts), Playwright E2E test suites, test setup and configuration files (vitest.config.ts, test-setup.ts), mock implementations for external dependencies, testing utility functions or test helpers, component test files using React Testing Library, API route test files, or integration tests for Content Collections and data fetching logic.
action-bias
"Am I *doing* or just *describing* that I should do?" - Counters documentation-over-action patterns. Triggers when: (1) about to say "should create", "need to fix", "I recommend" instead of acting, (2) end of work blocks before reporting completion, (3) reporting success while failures exist, (4) creating docs/plans without executing, (5) explaining fixes instead of implementing. Enforces ACT FIRST, DOCUMENT AFTER. Does NOT trigger for: genuine planning phases, user-requested documentation, or blocked situations requiring input.