Activation Criteria
Activate this skill only when the user explicitly instructs the agent to redesign a frontend and references this skill by name.
Do not activate this skill for:
- General design discussions
- Critiques without a redesign request
- Implementation-only tasks such as writing code or CSS
- Requests for inspiration, trends, or examples
Execution Steps
- Identify the provided context for the frontend, including any existing interface description, product type, or constraints.
- Establish a single, committed aesthetic direction without referencing popular UI styles or industry norms.
- Define the frontend design across the following dimensions:
- Typography: select typefaces with strong character and intentional tone, avoiding common UI fonts.
- Color & Theme: commit to a dominant palette with deliberate contrast and controlled restraint.
- Layout & Composition: define structure with tension, hierarchy, and asymmetry where appropriate.
- Backgrounds & Depth: specify atmospheric or structural background treatments that reinforce the aesthetic.
- Motion or Stillness: declare whether motion is used or avoided, and define its role clearly.
- Produce the design as a concrete, declarative specification describing visual decisions and their outcomes.
- Avoid referencing trends, competitors, or familiar product aesthetics.
- Output the design description directly, without explanation or justification.
Ambiguity Handling
- If product purpose or audience is unspecified, default to a neutral functional context without branding assumptions.
- If no existing interface is provided, design from a blank slate.
- Do not infer business goals, emotional tone, or user demographics beyond what is explicitly stated.
Constraints & Non-Goals
- Do not critique or evaluate existing designs unless explicitly included as part of the redesign context.
- Do not propose multiple stylistic options.
- Do not explain design theory or rationale.
- Do not produce code, mockups, or asset files.
- Do not reference prohibited visual patterns, brands, or aesthetic categories.
Failure Behavior
If the user does not explicitly request a frontend redesign using this skill’s name, or if no visual design can be defined from the provided input, output a minimal statement indicating that activation conditions were not met and terminate without generating a design.
1---2name: deliberate-frontend-redesign3description: Generates a deliberately designed frontend aesthetic that avoids generic UI patterns. Use when the user explicitly requests to redesign a frontend by invoking this skill by name. Trigger keywords: use deliberate-frontend-redesign, redesign frontend, redesign interface.4---56## Activation Criteria7Activate this skill only when the user explicitly instructs the agent to redesign a frontend and references this skill by name.89Do not activate this skill for:10- General design discussions11- Critiques without a redesign request12- Implementation-only tasks such as writing code or CSS13- Requests for inspiration, trends, or examples1415## Execution Steps161. Identify the provided context for the frontend, including any existing interface description, product type, or constraints.172. Establish a single, committed aesthetic direction without referencing popular UI styles or industry norms.183. Define the frontend design across the following dimensions:19 - Typography: select typefaces with strong character and intentional tone, avoiding common UI fonts.20 - Color & Theme: commit to a dominant palette with deliberate contrast and controlled restraint.21 - Layout & Composition: define structure with tension, hierarchy, and asymmetry where appropriate.22 - Backgrounds & Depth: specify atmospheric or structural background treatments that reinforce the aesthetic.23 - Motion or Stillness: declare whether motion is used or avoided, and define its role clearly.244. Produce the design as a concrete, declarative specification describing visual decisions and their outcomes.255. Avoid referencing trends, competitors, or familiar product aesthetics.266. Output the design description directly, without explanation or justification.2728## Ambiguity Handling29- If product purpose or audience is unspecified, default to a neutral functional context without branding assumptions.30- If no existing interface is provided, design from a blank slate.31- Do not infer business goals, emotional tone, or user demographics beyond what is explicitly stated.3233## Constraints & Non-Goals34- Do not critique or evaluate existing designs unless explicitly included as part of the redesign context.35- Do not propose multiple stylistic options.36- Do not explain design theory or rationale.37- Do not produce code, mockups, or asset files.38- Do not reference prohibited visual patterns, brands, or aesthetic categories.3940## Failure Behavior41If the user does not explicitly request a frontend redesign using this skill’s name, or if no visual design can be defined from the provided input, output a minimal statement indicating that activation conditions were not met and terminate without generating a design.
kbarbel640-del