design-frontend
Use when designing or redesigning frontend screens from specs, screenshots, visual references, product direction, or brand direction.
What this skill does
# Design Frontend Use before substantial frontend design or redesign work. ## Workflow 1. Identify the screen job. - Name the user's current goal. - Pick one primary action for the state. - Name the state: empty, loading, normal, error, confirming, or done. 2. Ground the visual direction. - Read named local design docs, screenshots, mockups, or brand references. - Inspect images directly when available. - Extract rhythm, density, hierarchy, typography, spacing, color roles, and component behavior. 3. Build the product surface. - Make the actual app screen, not a landing page unless requested. - Use realistic content and real app states. - Do not show implementation, setup, architecture, provider, database, API, mock, or demo explanations in the UI. 4. Subtract before adding. - Prefer fewer sections, cards, labels, buttons, and explanatory sentences. - Add UI only when it enables the task, clarifies risk, prevents a likely mistake, or shows information needed to decide. - Use familiar controls and compact labels instead of explainer panels. 5. Stabilize the layout. - Define design tokens before styling screens. - Use icons for familiar tool actions. - Keep cards for repeated items, modals, or framed tools only. - Avoid nested cards, decorative blobs, generic gradients, marketing heroes, accidental dashboards, and text that resizes layout. ## Flow Storyboards Create a storyboard before coding when the work spans several states, the input path is unclear, or a single screen mock would hide confirmation/success problems. Use `references/storyboard-flow-prompts.md` for prompt structure. Keep captions outside app screens, keep in-app copy minimal, and split distinct modes into separate boards. ## References Read `references/subtractive-principles.md` when the screen feels cluttered, generic, or too verbose. Read `../../references/modern-ios-app-design.md` for mobile or iOS-style work that needs taste calibration. ## Handoff Standard Rendered screens should show a clear primary action, no implementation-detail copy, no duplicate CTAs, no repeated obvious text, no clipped controls, and visual rhythm traceable to the selected references.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".