skills
This commit is contained in:
@@ -0,0 +1,45 @@
|
||||
---
|
||||
name: frontend-design
|
||||
description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
|
||||
license: Complete terms in LICENSE.txt
|
||||
---
|
||||
|
||||
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
|
||||
|
||||
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
|
||||
|
||||
## Design Thinking
|
||||
|
||||
Before coding, understand the context and commit to a BOLD aesthetic direction:
|
||||
|
||||
- **Purpose**: What problem does this interface solve? Who uses it?
|
||||
- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
|
||||
- **Constraints**: Technical requirements (framework, performance, accessibility).
|
||||
- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
|
||||
|
||||
**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
|
||||
|
||||
Then implement working code (HTML/CSS/JS, React, Vue, the appropriate frontend framework, etc.) that is:
|
||||
|
||||
- Production-grade and functional
|
||||
- Visually striking and memorable
|
||||
- Cohesive with a clear aesthetic point-of-view
|
||||
- Meticulously refined in every detail
|
||||
|
||||
## Frontend Aesthetics Guidelines
|
||||
|
||||
Focus on:
|
||||
|
||||
- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
|
||||
- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
|
||||
- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
|
||||
- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
|
||||
- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
|
||||
|
||||
NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
|
||||
|
||||
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
|
||||
|
||||
**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
|
||||
|
||||
Remember: You are capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
|
||||
@@ -0,0 +1,56 @@
|
||||
# Ripple TS Framework Skill
|
||||
|
||||
Use this skill when working on Ripple TS projects. Ripple is a TypeScript UI framework combining the best parts of React, Solid, and Svelte.
|
||||
|
||||
## Activation
|
||||
|
||||
This skill activates when:
|
||||
- Working with `.ripple` files
|
||||
- User mentions "Ripple" in the context of a UI framework
|
||||
- Project uses `ripple` or `@ripple-ts/*` packages
|
||||
|
||||
## Documentation Reference
|
||||
|
||||
**Always fetch the latest documentation before providing Ripple-specific guidance:**
|
||||
|
||||
```
|
||||
https://www.ripple-ts.com/llms.txt
|
||||
```
|
||||
|
||||
Use the `fetch_content` tool to retrieve this URL. The documentation is optimized for AI/LLM understanding and may be updated with new features and syntax changes.
|
||||
|
||||
## Quick Reference
|
||||
|
||||
### Key Syntax Patterns
|
||||
|
||||
- **Components**: Use `component` keyword (not functions returning JSX)
|
||||
- **Text content**: Must be wrapped in expressions `{"text"}` - no raw text in templates
|
||||
- **Reactivity**: Use `track()` to create reactive values, `@` to read/write them
|
||||
- **Templates**: Only valid inside `component` function bodies
|
||||
- **Early returns**: Use `return;` (no value) for guard clauses only
|
||||
|
||||
### Common Imports
|
||||
|
||||
```typescript
|
||||
import { mount, track, effect, Context, untrack, flushSync, tick } from 'ripple';
|
||||
import { TrackedArray, TrackedObject, TrackedSet, TrackedMap, TrackedDate } from 'ripple';
|
||||
import type { Component, PropsWithChildren, Tracked } from 'ripple';
|
||||
```
|
||||
|
||||
### Critical Mistakes to Avoid
|
||||
|
||||
1. **Raw text in templates** - Always use `{"text"}` not `text`
|
||||
2. **Return statements with values** - Use `return;` only, no `return <JSX/>`
|
||||
3. **Templates outside components** - JSX only valid inside `component {}` bodies
|
||||
4. **Destructuring props without trackSplit** - Loses reactivity for non-tracked props
|
||||
|
||||
## When to Fetch Full Docs
|
||||
|
||||
Fetch the full documentation when:
|
||||
- Implementing complex reactive patterns
|
||||
- Using Context API
|
||||
- Setting up SSR/hydration
|
||||
- Integrating with React (compat layer)
|
||||
- Working with reactive collections (TrackedArray, TrackedMap, etc.)
|
||||
- Using control flow (switch statements, for loops with keys)
|
||||
- Implementing portals or refs
|
||||
Reference in New Issue
Block a user