Figma Use
Inspect the authorized Figma file and tool capabilities before reading or changing nodes; preserve IDs and component relationships.
Build a frontend direction from the audience, real content, and existing brand constraints; resolve hierarchy before decorative styling.
---
name: knoveya-frontend-design
description: "Build a frontend direction from the audience, real content, and existing brand constraints; resolve hierarchy before decorative styling. Use for matching ux design work."
---
# Frontend Design
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Build a frontend direction from the audience, real content, and existing brand constraints; resolve hierarchy before decorative styling.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
The primary task works at narrow widths and through the keyboard.
## Example task
Compare a dense research table with a spacious first-use screen.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-frontend-design as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-frontend-design/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Compare a dense research table with a spacious first-use screen.
The primary task works at narrow widths and through the keyboard.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.