
edgespark-frontend-design
Design and redesign EdgeSpark frontends with distinctive, production-grade visual direction instead of generic AI-looking UI. Use when building or polishing landing pages, marketing sites, dashboards, auth flows, portfolios, product surfaces, or reusable frontend sections in EdgeSpark, especially when the task mentions design quality, aesthetics, typography, color, layout, motion, art direction, or making the UI feel more premium and original.
- Installs
- 588
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/edgesparkhq/agent-skills --skill edgespark-frontend-design- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads edgespark-frontend-design automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
EdgeSpark Frontend Design
Use this skill to turn safe, average UI into deliberate visual design with strong hierarchy, clearer art direction, and higher content quality.
Consult design-principles.md for doctrine, asset strategy, implementation details, and anti-patterns. Load the sections relevant to your task.
Design Stack
Apply the design standard in layers instead of relying on one vague "make it modern" pass:
- Start with the base web system: context-first framing, 12-column structure, 8-point spacing, semantic tokens, responsive behavior, and WCAG 2.1 AA contrast.
- Add the aesthetic lift: softer neutral or premium palettes, asymmetrical composition, dramatic typography contrast, generous whitespace, refined textures, and stronger motion direction.
- Enforce the anti-generic bans from the reference before shipping.
This layering is what prevents the model from drifting into safe but mediocre frontend output.
Workflow
1. Frame the design
Before touching code, derive:
- user goal
- audience
- primary tasks
- key content types
- success metric
- emotional tone
- one unforgettable visual move
- visual thesis: one sentence describing mood, material, and energy
- content plan: hero, support, detail, final CTA when the task is a landing page or marketing surface
- interaction thesis: 2-3 specific motion ideas that change the feel of the page
Give each section one job, one dominant visual idea, and one primary takeaway or action.
Choose a concrete direction instead of a vague "modern" target. Pick an extreme that fits the product, such as editorial, luxury, industrial, playful, organic, brutalist, or retro-futuristic. Map a minimal user journey and reflect it in layout, hierarchy, and copy.
2. Diagnose weak UI before changing it
For redesign work, inspect the current UI and answer:
- are the colors visually fatiguing, cheap-looking, or too vibrant
- is the layout overly traditional, symmetrical, or monotonous
- what modern design elements are missing
- does the page feel static and need motion to come alive
- what is the current brand positioning and intended emotional experience
3. Rebuild from the reference, not from habit
Load only the sections you need from design-principles.md:
Layout And SpacingTypographyColorVisual TreatmentsMotion And InteractionLanding PagesAppsContent AuthenticityVisual Asset RoleUtility Copy For Product UIResponsive And Accessibility BaselineExecution StyleOptimization OrderAnti-PatternsLitmus Checks
4. Follow the non-negotiables
- Start with composition, not components.
- Prefer CSS animations by default. Use Motion or Framer Motion for React, driven by animation tokens.
- Use intersection observers for scroll-triggered entry rather than ad hoc scroll listeners.
- Default to proactive real-image search for visual surfaces. Use placeholders only in the narrow cases listed in the reference.
- Support token-based light and dark modes when the product needs both.
- Match implementation complexity to the chosen direction instead of flattening every design into the same safe template.
5. Validate the finish
- Confirm mobile and desktop behavior.
- Confirm WCAG 2.1 AA contrast and visible interactive states.
- Confirm that motion, typography, color, and imagery all align with the chosen direction.
- Confirm that the result passes the anti-pattern check in the reference.
EdgeSpark Use
Use this skill for the design layer. Pair it with building-edgespark-apps when the task also needs EdgeSpark-specific implementation guidance.
FAQ
What does the edgespark-frontend-design skill do?
Design and redesign EdgeSpark frontends with distinctive, production-grade visual direction instead of generic AI-looking UI. Use when building or polishing landing pages, marketing sites, dashboards, auth flows, portfolios, product surfaces, or reusable frontend sections in EdgeSpark, especially when the task mentions design quality, aesthetics, typography, color, layout, motion, art direction, or making the UI feel more premium and original.
How do I install edgespark-frontend-design?
Run npx skills add https://github.com/edgesparkhq/agent-skills --skill edgespark-frontend-design in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/edgespark-frontend-design/ (personal) or .claude/skills/edgespark-frontend-design/ (project).
Which AI agents can use edgespark-frontend-design?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is edgespark-frontend-design safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains edgespark-frontend-design?
It is published by edgesparkhq in edgesparkhq/agent-skills. It has 588 recorded installs.
More from edgesparkhq/agent-skills
building-edgespark-apps
edgesparkhq/agent-skills
Build and modify EdgeSpark apps. Use when a project has edgespark.toml, the user mentions EdgeSpark, or work involves the edgespark CLI, server SDK types, storage/auth/database workflows, deployment, or @edgespark/web.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.