newsletter-visuals
Audit a newsletter draft for visual opportunities and generate on-brand visual assets. Use when enhancing a newsletter draft with visuals, when a draft has [screenshot] placeholders, or when the user says 'add visuals', 'create images for this issue', 'make this more visual', or 'add diagrams to the newsletter'.
optimize-newsletter
Optimize a newsletter draft or write a full issue from an outline. Use when asked to 'optimize this draft', 'polish this newsletter', 'write from this outline', 'improve this issue', or when transforming an existing draft or outline into a publication-ready issue. Distinct from plan-newsletter which starts from a topic — this starts from existing content.
write
Generalized writing skill that produces written content for any platform and format. Use when asked to write, draft, or create a newsletter, YouTube script, guide, sales page, Twitter thread, LinkedIn post, Substack Note, or community post. Also use when the user says "write this up", "draft a post", "create content about", or needs any written output.
youtube-data
Retrieve YouTube data using the YouTube Data API. Use when you need to search videos, get video or channel details, fetch transcripts, read comments, find trending or related content, or when the user mentions 'YouTube data', 'video stats', 'transcript', or 'channel info'.
write-note
Create high-engagement Substack Notes. Use when asked to write a Substack Note, create a note for Substack, share an insight on Notes, promote a newsletter issue via Notes, or post between newsletter issues. Also use when the user mentions "note", "Substack Note", or "short-form Substack content".
manage
Manage scheduled Claude Code tasks — add (recurring or one-off), list, pause, resume, remove, view results, and test execution of skills, prompts, and scripts with safety controls and notifications. Use when the user mentions scheduling, cron, automated tasks, recurring tasks, background tasks, running something on a schedule, periodic execution, or wants a skill/prompt/script to run automatically at a set time. Cross-platform (macOS, Linux, Windows).
update-context
Update the context system based on our conversation so far.
skill-retro
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
upgrade-plugin
Upgrade a plugin's skills, hooks, and patterns to align with latest Claude Code capabilities and best practices. Use when a plugin needs modernization, after Claude Code updates, or when the user says "upgrade plugin", "modernize plugin", or "update plugin to latest patterns".
test-skill
Run or generate test suites for any skill. Use when testing a skill before deployment, after making changes, before/after plugin upgrades, when validating skill behavior, or when the user says "test skill", "run skill tests", "generate tests for skill", or "check for regressions".
analyze-team-session
Use when reviewing an agent team session export for quality, when asked to "analyze this team session", "review my agent team run", "what went wrong with this session", "how can I improve my agent team usage", or when provided a markdown team session transcript and asked for feedback on agent teams effectiveness.
migrate
Migrate your Elle installation between versions. Handles any version-to-version upgrade path with sequential, idempotent steps. Use when updating Elle, when prompted by a version mismatch, or when the user says "migrate Elle" or "upgrade Elle".
evolve
Research-driven self-upgrade pipeline for the Elle personal assistant. Fetches latest Claude Code features, audits Elle's architecture, plans upgrades, executes them, and verifies results. Use after Claude Code updates, when exploring new features, or periodically. Also use when the user says "let's modernize Elle", "evolve Elle", or "what Claude Code features are we missing".
view-team-session
Generate a self-contained HTML viewer for any Claude Code session, including agent team sessions with full inter-agent DM timelines. Use whenever the user asks to "view a session", "visualize a conversation", "show me what happened in session X", "generate a session viewer", "replay a session", "show me what my agents did", "session replay", "team timeline", or references viewing/inspecting Claude Code JSONL logs. Also use when the user provides a session ID and wants to see the conversation.
brand-guidelines
Define, codify, or update brand identity and connect it to design systems. Use when the user wants to create brand guidelines, define their brand, update brand identity, or when the user mentions "brand", "brand guidelines", "brand identity", "brand voice", or "brand compliance".
community-post
Create YouTube community posts that drive views and audience engagement. Use when asked to create a community post, promote a video on the community tab, run a poll, or engage the YouTube audience between uploads. Also use when the user mentions 'community tab', 'YouTube poll', or 'post to community'.
setup
Set up the personal assistant plugin. Run this once after installing the plugin.
sync-context
Regenerate ~/.claude/rules/elle-core.md from your context files. Run after significant context updates to keep your session rules current. Use when context feels stale, after /update-context changes rules/preferences/identity, or after /upgrade.
voice
Apply Kenny Liao's authentic writing voice to any written content. This is a PERSONALITY skill invoked by other skills that produce written output — it handles parenthetical asides, sentence rhythm, fragments, counterpoint patterns, and raw-over-polished quality.
title
Generate optimized titles, headlines, and subject lines for any content type. Use when asked to create a title, headline, subject line, or when the user says "title ideas", "what should I call this", "subject line options", or needs engagement-optimized naming for videos, newsletters, or social posts.
thumbnail
Create high-performing thumbnails and cover images optimized for click-through rate. Use when asked to create a thumbnail, design a cover image, generate a YouTube thumbnail, or when the user mentions "thumbnail", "cover image", "CTR", or needs a visual asset for video or course content.
social-graphic
Create social media graphics and visual assets for any platform. Use when asked to create a social media image, newsletter header, blog feature image, OG image, profile banner, or when the user mentions 'social graphic', 'header image', 'banner', or needs a platform-specific visual asset (not thumbnails — use creator-stack:thumbnail for those).
research
Conduct topic and competitor research for any content type. Use when researching a topic before creating content, analyzing the competitive landscape, identifying content gaps, or when the user says "research this", "what's out there on", "analyze competitors", or needs to understand a content landscape before writing.
repurpose-video
Repurpose a completed YouTube video into newsletter issues, social media posts, and other content formats. Use when the user says 'repurpose this video', 'turn this video into a newsletter', 'create social posts from my video', 'distribute this content', or wants to maximize reach of existing video content across platforms.
onboard
Get to know the user through a guided conversation to personalize Elle's context.
design-system
Create, update, or refresh a visual design system or art style guide. Use when the user wants to define a visual style, create a design system, build a style guide, or when they mention "design system", "art style", "style guide", "visual identity", or "color palette".
retrospective
Use when ending a working session to capture lessons learned, when the user corrects Claude or asks to redo work, when the user expresses frustration with output quality, or when user triggers /retrospective
jta
Translate JSON i18n files to multiple languages with AI-powered quality optimization. Use when user mentions translating JSON, i18n files, internationalization, locale files, or needs to convert language files to other languages.
laravel:writing-plans
Create an actionable Laravel implementation plan—bite-sized tasks with TDD-first steps, migrations, services, jobs, and validation points
laravel:api-resources-and-pagination
Use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly
laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
laravel:bootstrap-check
Detect Sail/non‑Sail and print the right command pairs for your environment; verify dependencies and key services are reachable
laravel:brainstorming
Interactive design refinement tailored to Laravel projects; clarify domain, data, interfaces, testing, and quality gates while accounting for Sail/non‑Sail environments
laravel:code-review-requests
Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions
laravel:api-surface-evolution
Evolve APIs safely using versioned DTOs/transformers, deprecations, and compatibility tests
laravel:complexity-guardrails
Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches
laravel:config-env-storage
Portable storage configuration across S3/R2/MinIO with optional CDN—env toggles, path-style endpoints, and URL generation
laravel:using-laravel-superpowers
Read first in Laravel repos; explains runner selection (Sail vs non-Sail), core workflows, and how to apply superpowers skills in Laravel projects without platform lock-in
laravel:constants-and-configuration
Replace hardcoded values with constants, enums, and configuration for maintainability; use PHP 8.1+ enums and config files
laravel:controller-cleanup
Reduce controller bloat using Form Requests for auth/validation, small Actions/Services with DTOs, and resource/single-action controllers
laravel:controller-tests
Write focused controller tests using HTTP assertions; keep heavy logic in Actions/Services and unit test them
laravel:using-examples-in-prompts
Provide concrete examples—existing code patterns, style samples, input/output pairs—to guide AI toward your project's conventions
laravel:transactions-and-consistency
Wrap multi-write operations in transactions; use dispatchAfterCommit and idempotency patterns to ensure consistency
laravel:template-method-and-plugins
Stabilize workflows with Template Method or Strategy; extend by adding new classes instead of editing core logic
laravel:tdd-with-pest
Apply RED-GREEN-REFACTOR with Pest or PHPUnit; use factories, feature tests for HTTP, and parallel test runners; verify failures before implementation
laravel:task-scheduling
Schedule tasks with safety; use withoutOverlapping, onOneServer, and visibility settings for reliable cron execution
laravel:strategy-pattern
Use the Strategy pattern to select behavior at runtime; bind multiple implementations to a shared interface
laravel:specifying-constraints
Define clear constraints—performance, security, testing, architecture, dependencies—so AI generates code that meets your project standards
laravel:runner-selection
Choose Sail automatically when available, fall back cleanly to host PHP/Composer/Node; paired command map for both environments
laravel:custom-helpers
Create and register small, pure helper functions when they improve clarity; keep them organized and tested
Page 438 of 1360 · 67970 results
