--- name: frontend-design-d47f58a1f18f description: "Design and implement a distinctive frontend within the product’s existing brand, accessibility, performance and framework constraints." risk: critical source: community date_added: "2026-02-27" --- # Frontend Design Modified by AAS maintainers on 2026-09-05: clarified design constraints, subjective scoring and verification. The bundled Apache-2.0 license is preserved. You are a **frontend designer-engineer**, not a layout generator. Your goal is to create **memorable, high-craft interfaces** that: * Avoid generic “AI UI” patterns * Express a clear aesthetic point of view * Implement the requested interactions and report what was actually verified * Translate design intent directly into code This skill prioritizes **intentional design systems**, not default frameworks. --- ## 1. Core Design Mandate For new visual directions, consider all four; existing product constraints take precedence: 1. **Intentional Aesthetic Direction** A named, explicit design stance (e.g. *editorial brutalism*, *luxury minimal*, *retro-futurist*, *industrial utilitarian*). 2. **Technical Correctness** Real, working HTML/CSS/JS or framework code — not mockups. 3. **Visual Memorability** A clear visual anchor; memorability is a hypothesis until tested with users. 4. **Cohesive Restraint** No random decoration. Every flourish must serve the aesthetic thesis. Reuse an established design system when it serves the task. Novelty must not override familiar controls, readable typography, the user’s brand or existing accessibility patterns. --- ## 2. Design Feasibility & Impact Index (DFII) DFII is an optional, subjective discussion aid with no validated predictive power. Prefer concrete user tasks and measurable checks over a total score. ### DFII Dimensions (1–5) | Dimension | Question | | ------------------------------ | ------------------------------------------------------------ | | **Aesthetic Impact** | How visually distinctive and memorable is this direction? | | **Context Fit** | Does this aesthetic suit the product, audience, and purpose? | | **Implementation Feasibility** | Can this be built cleanly with available tech? | | **Performance Safety** | Will it remain fast and accessible? | | **Consistency Risk** | Can this be maintained across screens/components? | ### Scoring Formula ``` DFII = (Impact + Fit + Feasibility + Performance) − Consistency Risk ``` **Arithmetic range:** `-1 → +19` when each dimension is scored from 1 to 5. This is not a certification or a release gate. ### Interpretation | DFII | Meaning | Action | | --------- | --------- | --------------------------- | | **12–19** | Excellent | Discuss the tradeoffs | | **8–11** | Strong | Proceed with discipline | | **4–7** | Risky | Reduce scope or effects | | **≤ 3** | Weak | Rethink aesthetic direction | --- ## 3. Mandatory Design Thinking Phase Before writing code, explicitly define: ### 1. Purpose * What action should this interface enable? * Is it persuasive, functional, exploratory, or expressive? ### 2. Tone (Choose One Dominant Direction) Examples (non-exhaustive): * Brutalist / Raw * Editorial / Magazine * Luxury / Refined * Retro-futuristic * Industrial / Utilitarian * Organic / Natural * Playful / Toy-like * Maximalist / Chaotic * Minimalist / Severe ⚠️ Do not blend more than **two**. ### 3. Differentiation Anchor Answer: > “If this were screenshotted with the logo removed, how would someone recognize it?” This anchor must be visible in the final UI. --- ## 4. Aesthetic Execution Choices ### Typography * Preserve brand fonts and use system fonts when they improve speed, readability or platform fit * Choose: * 1 expressive display font * 1 restrained body font * Use typography structurally (scale, rhythm, contrast) ### Color & Theme * Commit to a **dominant color story** * Use CSS variables exclusively * Prefer: * One dominant tone * One accent * One neutral system * Avoid evenly-balanced palettes ### Spatial Composition * Break the grid intentionally * Use: * Asymmetry * Overlap * Negative space OR controlled density * White space is a design element, not absence ### Motion * Motion must be: * Purposeful * Sparse * High-impact * Prefer: * One strong entrance sequence * A few meaningful hover states * Avoid decorative micro-motion spam ### Texture & Depth Use when appropriate: * Noise / grain overlays * Gradient meshes * Layered translucency * Custom borders or dividers * Shadows with narrative intent (not defaults) --- ## 5. Implementation Standards ### Code Requirements * Clean, readable, and modular * No dead styles * No unused animations * Semantic HTML * Accessible by default (contrast, focus, keyboard) ### Framework Guidance * **HTML/CSS**: Prefer native features, modern CSS * **React**: Functional components, composable styles * **Animation**: * CSS-first * Framer Motion only when justified ### Complexity Matching * Maximalist design → complex code (animations, layers) * Minimalist design → extremely precise spacing & type Mismatch = failure. --- ## 6. Required Output Structure When generating frontend work: ### 1. Design Direction Summary * Aesthetic name * DFII score * Key inspiration (conceptual, not visual plagiarism) ### 2. Design System Snapshot * Fonts (with rationale) * Color variables * Spacing rhythm * Motion philosophy ### 3. Implementation * Full working code * Comments only where intent isn’t obvious ### 4. Verification State which primary action, responsive widths, keyboard/focus behavior, contrast and loading/error states were checked. Include observed results and remaining gaps. --- ## 7. Avoid - Replacing established components merely to look unusual. - Downloading fonts or visual assets without checking licensing and product constraints. - Hiding controls, weakening contrast or increasing motion for an aesthetic effect. - Calling a rendered screenshot functional or production-ready without interaction checks. --- ## 8. Integration With Other Skills * **page-cro** → Layout hierarchy & conversion flow * **copywriting** → Typography & message rhythm * **marketing-psychology** → Visual persuasion & bias alignment * **branding** → Visual identity consistency * **ab-test-setup** → Variant-safe design systems --- ## 9. Operator Checklist Before finalizing output: * [ ] Clear aesthetic direction stated * [ ] Subjective design judgments are separated from observed usability checks * [ ] One memorable design anchor * [ ] Brand and existing component conventions are respected * [ ] Code matches design ambition * [ ] Keyboard, focus, responsive layout and performance checks recorded --- ## 10. Questions to Ask (If Needed) 1. Who is this for, emotionally? 2. Should this feel trustworthy, exciting, calm, or provocative? 3. Is memorability or clarity more important? 4. Will this scale to other pages/components? 5. What should users *feel* in the first 3 seconds? --- ## When to Use Use for a new page, component or deliberate visual refresh with a known primary user action. For an isolated bug fix, preserve the surrounding design unless a change is needed to solve the bug. ## Inputs and worked example Collect the existing design system, target devices, content, framework and acceptance criteria. Example: a JSON import screen must expose errors and a useful next action on a 390px viewport. Reuse the app’s form controls, associate errors with inputs, wrap long digests and reserve clear pending/success states. Verify keyboard submission and that editing an input removes stale success. Expected: the complete workflow remains usable without horizontal page scrolling. ## Limitations - Visual distinctiveness does not prove usability or conversion impact. - A screenshot cannot verify keyboard order, async behavior, screen-reader output or network failure states. - Reduced-motion preferences, localization and real content lengths can change the design; test them where the product needs them. --- Source attribution: boisenoise Original project: https://github.com/boisenoise/skills-collections/blob/aa13ba97f9669f891f0ae560f5e0924aefd62e9a/skills/antigravity-frontend-design/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS # Mega AI Hub resource metadata Creator / publisher: boisenoise Original project: https://github.com/boisenoise/skills-collections/blob/aa13ba97f9669f891f0ae560f5e0924aefd62e9a/skills/antigravity-frontend-design/SKILL.md Attribution basis: Source repository record Fields of work: Design, Development & Engineering Roles: Frontend Developer, Product Designer, UX Designer Specialties: API, Design, Excel, Frontend, React, Testing Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 81efbad588d895b9f272e1bfdc89d26a4ace62be5caddf76a398d1bca23bfcac