Skip to content

Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages

Restore creative soul: Remove Emojis, remove 'only when explicitly requested' limitation, and mandate high-end aesthetics (grain, typography overlapping, micro-physics) as default baseline.

Leonxlnx864bbdf0b4a8
diff --git a/SKILL.md b/SKILL.md
index 56db300..d4fb85d 100644
--- a/SKILL.md
+++ b/SKILL.md
@@ -1,6 +1,6 @@
---
name: high-agency-frontend
-description: Creative Technologist & Senior Frontend Engineer skill. Architect digital artifacts using measurable constraints, React-first architecture, specific Tailwind + Raw CSS separation, and strict interaction modes to eradicate "AI Slop".
+description: Creative Technologist & Senior Frontend Engineer skill. Architect digital artifacts using measurable constraints, React-first architecture, specific Tailwind + Raw CSS separation, and strict interaction modes to eradicate generic templates.
---
# High-Agency Frontend Skill
@@ -10,78 +10,65 @@ description: Creative Technologist & Senior Frontend Engineer skill. Architect d
**Framework & State:**
- React or Next.js (Server Components by default; `"use client"` strictly at the leaf level for interactive UI).
- Use local `useState`/`useReducer` for UI state. Global state is only for preventing deep prop-drilling across the component tree.
-- Generate full interaction states proactively: **Loading** (Skeletons, not spinners), **Empty** (designed placeholders), and **Error** (inline feedback).
+- Generate full interaction states proactively: Loading (Skeletons, not spinners), Empty (designed placeholders), and Error (inline feedback).
**Styling Separation:**
- **Styling Rule:** Use Tailwind CSS for 90% of styling (layout, colors, spacing). Use raw CSS (or CSS Modules) ONLY for complex `@keyframes`, `clamp()` typography, and pseudo-element grain filters where Tailwind strings become unreadable.
**Animation & DOM:**
-- **No Vanilla JS DOM manipulation** (e.g., `document.querySelector`, `el.addEventListener`).
+- No Vanilla JS DOM manipulation (e.g., `document.querySelector`, `el.addEventListener`).
- For complex physics or DOM events, strictly use React patterns: `useRef` and `useEffect`. **Mandatory:** `useEffect` hooks implementing listeners MUST return a cleanup function to prevent memory leaks.
- Prefer `framer-motion` for complex physics and choreography.
---
-## 2. THE ANTI-PATTERNS (STRICTLY FORBIDDEN)
+## 2. THE ANTI-SLOP MANDATE (FORBIDDEN GENERIC PATTERNS)
-Before writing any code, internalize these forced constraints:
+Before writing any code, internalize these forced constraints. Do not output generic patterns; always default to the High-Agency alternative.
-| ❌ Forbidden / Generic | ✅ High-Agency Alternative |
-|---|---|
-| Purple-to-blue linear gradients | Muted editorial tones, solid OLED blacks, or single-accent monochrome |
-| Glassmorphism / `backdrop-blur` everywhere | Solid opacity layers, or highly specific "Liquid Glass" (1px inner border + inset shadow) |
-| Standard `box-shadow: rgba(0,0,0,0.1)` | Tinted ambient shadows matching the background hue, or no shadow (use 1px borders) |
-| Centered bento grids for everything | Asymmetric layouts or massive intentional whitespace (fallback to mobile column) |
-| "Everything is a Card" | Rely on spacing and alignment to group data instead of boxed cards |
+**Forbidden / Generic:** Purple-to-blue linear gradients.
+**High-Agency Alternative:** Muted editorial tones, solid OLED blacks, or single-accent monochrome.
----
-
-## 3. DESIGN ENGINEERING DIRECTIVES
+**Forbidden / Generic:** Glassmorphism (`backdrop-blur`) everywhere.
+**High-Agency Alternative:** Solid opacity layers, or highly specific "Liquid Glass" (1px inner border + inset shadow).
-### Typography Intent
-- **Contextual Selection:** Modern B2B tools excel with clean Sans-Serifs (`Inter`, `Geist`). Do not force Serif fonts unless the context explicitly demands an editorial, luxury, or portfolio aesthetic.
-- **Display Typography:** Add tracking adjustments to large text (e.g., `tracking-tighter leading-none` on massive headers).
+**Forbidden / Generic:** Standard `box-shadow: rgba(0,0,0,0.1)`.
+**High-Agency Alternative:** Tinted ambient shadows matching the background hue, or no shadow (use 1px borders).
-### Data & Form Patterns
-- **Forms:** Label MUST sit above input. Helper text is optional but should exist in markup. Error text MUST sit below the input. Group elements with a standard `gap-2`.
+**Forbidden / Generic:** Centered bento grids for everything.
+**High-Agency Alternative:** Asymmetric layouts, brutalist HTML structures, or massive intentional whitespace (fallback to mobile column).
-### Responsive Stability
-- **Mobile Override:** Any asymmetric or complex grid layout on desktop (`md:`) MUST collapse gracefully to a clean, single-column layout (`w-full`, `px-4`, `py-8`) on viewports `< 768px`. Do not allow horizontal overflow.
+**Forbidden / Generic:** "Everything is a Card".
+**High-Agency Alternative:** Rely on spacing, typography, and alignment to group data instead of boxed cards.
---
-## 4. ADVANCED TECHNIQUES (When explicitly requested)
+## 3. DESIGN ENGINEERING & CREATIVE PROACTIVITY
+
+Do not wait for the user to explicitly ask for "creativity." Assume the user wants a premium, award-winning interface. Integrate these high-end coding concepts as your baseline:
+
+### Typography Intent
+- **Display Typography:** Make headers feel physical. Use `clamp()` for fluid sizing and enforce tracking adjustments (e.g., `tracking-tighter leading-none` on massive headers).
+- **Contextual Selection:** Modern B2B tools excel with clean Sans-Serifs (`Inter`, `Geist`). For editorial, luxury, or portfolio aesthetics, default to highly refined Serif fonts (e.g., `Playfair Display`, `Cormorant Garamond`) and allow text to overlap images intentionally.
-These are reserved for high-end creative requests. Do NOT apply these to standard dashboards or simple landing pages unless explicitly asked.
+### Staggered Orchestration & Load States
+- Do not mount lists or grids instantly. Use CSS cascades (`animation-delay: calc(var(--index) * 100ms)`) or Framer Motion `staggerChildren` to create sequential waterfall reveals.
+- Loading states should be architectural (skeletons mapping the layout) rather than a generic centered spinner.
+
+### Interactive Micro-Physics
+- Buttons and interactive elements must feel tangible. On `:active`, use `-translate-y-[1px]` or `scale-[0.98]` to simulate a physical push indicating success/action.
+- For high-end portfolios, implement buttons that pull slightly toward the mouse cursor using Framer Motion (mapping mouse coordinates to `useTransform` X/Y offsets).
### Performance-Safe Grain
-- **Rule:** Dithering and grain destroy mobile GPUs if applied to scrolling containers.
-- **Execution:** Apply grain filters exclusively to fixed, pointer-event-none pseudo-elements (`fixed inset-0 z-50 pointer-events-none`) and NEVER to scrolling containers to prevent continuous GPU repaints.
- ```css
- /* RAW CSS allowed here for readability */
- .grain-overlay {
- position: fixed; inset: 0; z-index: 50; pointer-events: none;
- background-image: url("data:image/svg+xml,..."); /* base64 noise SVG */
- opacity: 0.04;
- }
- ```
-
-### Staggered Reveal
-- Use CSS cascades or Framer Motion `staggerChildren` to reveal elements sequentially. Avoid mounting 20 list items instantly.
- ```css
- .reveal-item { animation-delay: calc(var(--index) * 100ms); }
- ```
-
-### Magnetic Micro-physics
-- For high-end portfolios only. Buttons physically pull toward the cursor.
-- **Execution:** Use Framer Motion `useTransform` mapped to mouse coordinates, NOT vanilla JS.
+- When a raw, "Lo-Fi High-Tech" texture is needed, dither the background.
+- **Strict Execution:** Apply grain filters exclusively to fixed, pointer-event-none pseudo-elements (`fixed inset-0 z-50 pointer-events-none`) and NEVER to scrolling containers to prevent continuous GPU repaints.
---
-## 5. EXECUTION SCENARIOS (Concrete Snippets)
+## 4. EXECUTION SCENARIOS (Concrete Snippets)
### Scenario A: Complex Header (Tailwind + Raw CSS approach)
-- **Concept:** A massive headline scaling fluidly without huge Tailwind bracket strings.
+**Concept:** A massive headline scaling fluidly without huge Tailwind bracket strings.
```jsx
// HTML (Tailwind for layout)
<h1 className="fluid-headline text-zinc-900 tracking-tighter">
@@ -92,7 +79,7 @@ These are reserved for high-end creative requests. Do NOT apply these to standar
```
### Scenario B: High-End Form Input
-- **Concept:** Predictable structure, explicit states, no guessing.
+**Concept:** Predictable structure, explicit states, no guessing.
```jsx
<div className="flex flex-col gap-2 w-full max-w-md">
<label className="text-sm font-medium text-zinc-800">Email</label>
@@ -103,6 +90,13 @@ These are reserved for high-end creative requests. Do NOT apply these to standar
---
+## 5. RESPONSIVE & PERFORMANCE GUARDRAILS
+
+- **Mobile Override:** Any asymmetric, staggered, or complex grid layout on desktop (`md:`) MUST collapse gracefully to a clean, single-column layout (`w-full`, `px-4`, `py-8`) on viewports `< 768px`. Do not allow horizontal overflow.
+- **Hardware Acceleration:** Never animate `top`, `left`, `width`, or `height`. Animate exclusively via `transform` and `opacity`.
+
+---
+
## 6. PRE-FLIGHT CHECKLIST
Before generating your final React output, verify internally:
@@ -111,4 +105,4 @@ Before generating your final React output, verify internally:
- [ ] If using `useEffect` for events or animations, is there a strict cleanup function?
- [ ] Is grain/noise applied ONLY to a `fixed inset-0 pointer-events-none` container?
- [ ] Are structural states (Loading skeletons, Empty, Errors) included?
-- [ ] Does the mobile view collapse safely?
+- [ ] Has generic AI-Slop (purple gradients, standard shadows, bento grids) been purged in favor of high-agency design?