foliko 1.0.80 → 1.0.81

package/.agent/skills/frontend-design/visual-effects.md

@@ -1,383 +0,0 @@
-# Visual Effects Reference
-
-> Modern CSS effect principles and techniques - learn the concepts, create variations.
-> **No fixed values to copy - understand the patterns.**
-
----
-
-## 1. Glassmorphism Principles
-
-### What Makes Glassmorphism Work
-
-```
-Key Properties:
-├── Semi-transparent background (not solid)
-├── Backdrop blur (frosted glass effect)
-├── Subtle border (for definition)
-└── Often: light shadow for depth
-```
-
-### The Pattern (Customize Values)
-
-```css
-.glass {
-  /* Transparency: adjust opacity based on content readability */
-  background: rgba(R, G, B, OPACITY);
-  /* OPACITY: 0.1-0.3 for dark bg, 0.5-0.8 for light bg */
-  
-  /* Blur: higher = more frosted */
-  backdrop-filter: blur(AMOUNT);
-  /* AMOUNT: 8-12px subtle, 16-24px strong */
-  
-  /* Border: defines edges */
-  border: 1px solid rgba(255, 255, 255, OPACITY);
-  /* OPACITY: 0.1-0.3 typically */
-  
-  /* Radius: match your design system */
-  border-radius: YOUR_RADIUS;
-}
-```
-
-### When to Use Glassmorphism
-- ✅ Over colorful/image backgrounds
-- ✅ Modals, overlays, cards
-- ✅ Navigation bars with scrolling content behind
-- ❌ Text-heavy content (readability issues)
-- ❌ Simple solid backgrounds (pointless)
-
-### When NOT to Use
-- Low contrast situations
-- Accessibility-critical content
-- Performance-constrained devices
-
----
-
-## 2. Neomorphism Principles
-
-### What Makes Neomorphism Work
-
-```
-Key Concept: Soft, extruded elements using DUAL shadows
-├── Light shadow (from light source direction)
-├── Dark shadow (opposite direction)
-└── Background matches surrounding (same color)
-```
-
-### The Pattern
-
-```css
-.neo-raised {
-  /* Background MUST match parent */
-  background: SAME_AS_PARENT;
-  
-  /* Two shadows: light direction + dark direction */
-  box-shadow: 
-    OFFSET OFFSET BLUR rgba(light-color),
-    -OFFSET -OFFSET BLUR rgba(dark-color);
-  
-  /* OFFSET: typically 6-12px */
-  /* BLUR: typically 12-20px */
-}
-
-.neo-pressed {
-  /* Inset creates "pushed in" effect */
-  box-shadow: 
-    inset OFFSET OFFSET BLUR rgba(dark-color),
-    inset -OFFSET -OFFSET BLUR rgba(light-color);
-}
-```
-
-### Accessibility Warning
-⚠️ **Low contrast** - use sparingly, ensure clear boundaries
-
-### When to Use
-- Decorative elements
-- Subtle interactive states
-- Minimalist UI with flat colors
-
----
-
-## 3. Shadow Hierarchy Principles
-
-### Concept: Shadows Indicate Elevation
-
-```
-Higher elevation = larger shadow
-├── Level 0: No shadow (flat on surface)
-├── Level 1: Subtle shadow (slightly raised)
-├── Level 2: Medium shadow (cards, buttons)
-├── Level 3: Large shadow (modals, dropdowns)
-└── Level 4: Deep shadow (floating elements)
-```
-
-### Shadow Properties to Adjust
-
-```css
-box-shadow: OFFSET-X OFFSET-Y BLUR SPREAD COLOR;
-
-/* Offset: direction of shadow */
-/* Blur: softness (larger = softer) */
-/* Spread: size expansion */
-/* Color: typically black with low opacity */
-```
-
-### Principles for Natural Shadows
-
-1. **Y-offset larger than X** (light comes from above)
-2. **Low opacity** (5-15% for subtle, 15-25% for pronounced)
-3. **Multiple layers** for realism (ambient + direct)
-4. **Blur scales with offset** (larger offset = larger blur)
-
-### Dark Mode Shadows
-- Shadows less visible on dark backgrounds
-- May need to increase opacity
-- Or use glow/highlight instead
-
----
-
-## 4. Gradient Principles
-
-### Types and When to Use
-
-| Type | Pattern | Use Case |
-|------|---------|----------|
-| **Linear** | Color A → Color B along line | Backgrounds, buttons, headers |
-| **Radial** | Center → outward | Spotlights, focal points |
-| **Conic** | Around center | Pie charts, creative effects |
-
-### Creating Harmonious Gradients
-
-```
-Good Gradient Rules:
-├── Use ADJACENT colors on wheel (analogous)
-├── Or same hue with different lightness
-├── Avoid complementary (can look harsh)
-└── Add middle stops for smoother transitions
-```
-
-### Gradient Syntax Pattern
-
-```css
-.gradient {
-  background: linear-gradient(
-    DIRECTION,           /* angle or to-keyword */
-    COLOR-STOP-1,        /* color + optional position */
-    COLOR-STOP-2,
-    /* ... more stops */
-  );
-}
-
-/* DIRECTION examples: */
-/* 90deg, 135deg, to right, to bottom right */
-```
-
-### Mesh Gradients
-
-```
-Multiple radial gradients overlapped:
-├── Each at different position
-├── Each with transparent falloff
-├── **Mandatory for "Wow" factor in Hero sections**
-└── Creates organic, colorful effect (Search: "Aurora Gradient CSS")
-```
-
----
-
-## 5. Border Effects Principles
-
-### Gradient Borders
-
-```
-Technique: Pseudo-element with gradient background
-├── Element has padding = border width
-├── Pseudo-element fills with gradient
-└── Mask or clip creates border effect
-```
-
-### Animated Borders
-
-```
-Technique: Rotating gradient or conic sweep
-├── Pseudo-element larger than content
-├── Animation rotates the gradient
-└── Overflow hidden clips to shape
-```
-
-### Glow Borders
-
-```css
-/* Multiple box-shadows create glow */
-box-shadow:
-  0 0 SMALL-BLUR COLOR,
-  0 0 MEDIUM-BLUR COLOR,
-  0 0 LARGE-BLUR COLOR;
-
-/* Each layer adds to the glow */
-```
-
----
-
-## 6. Glow Effects Principles
-
-### Text Glow
-
-```css
-text-shadow: 
-  0 0 BLUR-1 COLOR,
-  0 0 BLUR-2 COLOR,
-  0 0 BLUR-3 COLOR;
-
-/* Multiple layers = stronger glow */
-/* Larger blur = softer spread */
-```
-
-### Element Glow
-
-```css
-box-shadow:
-  0 0 BLUR-1 COLOR,
-  0 0 BLUR-2 COLOR;
-
-/* Use color matching element for realistic glow */
-/* Lower opacity for subtle, higher for neon */
-```
-
-### Pulsing Glow Animation
-
-```css
-@keyframes glow-pulse {
-  0%, 100% { box-shadow: 0 0 SMALL-BLUR COLOR; }
-  50% { box-shadow: 0 0 LARGE-BLUR COLOR; }
-}
-
-/* Easing and duration affect feel */
-```
-
----
-
-## 7. Overlay Techniques
-
-### Gradient Overlay on Images
-
-```
-Purpose: Improve text readability over images
-Pattern: Gradient from transparent to opaque
-Position: Where text will appear
-```
-
-```css
-.overlay::after {
-  content: '';
-  position: absolute;
-  inset: 0;
-  background: linear-gradient(
-    DIRECTION,
-    transparent PERCENTAGE,
-    rgba(0,0,0,OPACITY) 100%
-  );
-}
-```
-
-### Colored Overlay
-
-```css
-/* Blend mode or layered gradient */
-background: 
-  linear-gradient(YOUR-COLOR-WITH-OPACITY),
-  url('image.jpg');
-```
-
----
-
-## 8. Modern CSS Techniques
-
-### Container Queries (Concept)
-
-```
-Instead of viewport breakpoints:
-├── Component responds to ITS container
-├── Truly modular, reusable components
-└── Syntax: @container (condition) { }
-```
-
-### :has() Selector (Concept)
-
-```
-Parent styling based on children:
-├── "Parent that has X child"
-├── Enables previously impossible patterns
-└── Progressive enhancement approach
-```
-
-### Scroll-Driven Animations (Concept)
-
-```
-Animation progress tied to scroll:
-├── Entry/exit animations on scroll
-├── Parallax effects
-├── Progress indicators
-└── View-based or scroll-based timeline
-```
-
----
-
-## 9. Performance Principles
-
-### GPU-Accelerated Properties
-
-```
-CHEAP to animate (GPU):
-├── transform (translate, scale, rotate)
-└── opacity
-
-EXPENSIVE to animate (CPU):
-├── width, height
-├── top, left, right, bottom
-├── margin, padding
-└── box-shadow (recalculates)
-```
-
-### will-change Usage
-
-```css
-/* Use sparingly, only for heavy animations */
-.heavy-animation {
-  will-change: transform;
-}
-
-/* Remove after animation if possible */
-```
-
-### Reduced Motion
-
-```css
-@media (prefers-reduced-motion: reduce) {
-  /* Disable or minimize animations */
-  /* Respect user preference */
-}
-```
-
----
-
-## 10. Effect Selection Checklist
-
-Before applying any effect:
-
-- [ ] **Does it serve a purpose?** (not just decoration)
-- [ ] **Is it appropriate for the context?** (brand, audience)
-- [ ] **Have you varied from previous projects?** (avoid repetition)
-- [ ] **Is it accessible?** (contrast, motion sensitivity)
-- [ ] **Is it performant?** (especially on mobile)
-- [ ] **Did you ask user preference?** (if style open-ended)
-
-### Anti-Patterns
-
-- ❌ Glassmorphism on every element (kitsch)
-- ❌ Dark + neon as default (lazy AI look)
-- ❌ **Static/Flat designs with no depth (FAILED)**
-- ❌ Effects that hurt readability
-- ❌ Animations without purpose
-
----
-
-> **Remember**: Effects enhance meaning. Choose based on purpose and context, not because it "looks cool."

package/.agent/skills/i18n-localization/SKILL.md

@@ -1,154 +0,0 @@
----
-name: i18n-localization
-description: Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
-allowed-tools: Read, Glob, Grep
----
-
-# i18n & Localization
-
-> Internationalization (i18n) and Localization (L10n) best practices.
-
----
-
-## 1. Core Concepts
-
-| Term | Meaning |
-|------|---------|
-| **i18n** | Internationalization - making app translatable |
-| **L10n** | Localization - actual translations |
-| **Locale** | Language + Region (en-US, tr-TR) |
-| **RTL** | Right-to-left languages (Arabic, Hebrew) |
-
----
-
-## 2. When to Use i18n
-
-| Project Type | i18n Needed? |
-|--------------|--------------|
-| Public web app | ✅ Yes |
-| SaaS product | ✅ Yes |
-| Internal tool | ⚠️ Maybe |
-| Single-region app | ⚠️ Consider future |
-| Personal project | ❌ Optional |
-
----
-
-## 3. Implementation Patterns
-
-### React (react-i18next)
-
-```tsx
-import { useTranslation } from 'react-i18next';
-
-function Welcome() {
-  const { t } = useTranslation();
-  return <h1>{t('welcome.title')}</h1>;
-}
-```
-
-### Next.js (next-intl)
-
-```tsx
-import { useTranslations } from 'next-intl';
-
-export default function Page() {
-  const t = useTranslations('Home');
-  return <h1>{t('title')}</h1>;
-}
-```
-
-### Python (gettext)
-
-```python
-from gettext import gettext as _
-
-print(_("Welcome to our app"))
-```
-
----
-
-## 4. File Structure
-
-```
-locales/
-├── en/
-│   ├── common.json
-│   ├── auth.json
-│   └── errors.json
-├── tr/
-│   ├── common.json
-│   ├── auth.json
-│   └── errors.json
-└── ar/          # RTL
-    └── ...
-```
-
----
-
-## 5. Best Practices
-
-### DO ✅
-
-- Use translation keys, not raw text
-- Namespace translations by feature
-- Support pluralization
-- Handle date/number formats per locale
-- Plan for RTL from the start
-- Use ICU message format for complex strings
-
-### DON'T ❌
-
-- Hardcode strings in components
-- Concatenate translated strings
-- Assume text length (German is 30% longer)
-- Forget about RTL layout
-- Mix languages in same file
-
----
-
-## 6. Common Issues
-
-| Issue | Solution |
-|-------|----------|
-| Missing translation | Fallback to default language |
-| Hardcoded strings | Use linter/checker script |
-| Date format | Use Intl.DateTimeFormat |
-| Number format | Use Intl.NumberFormat |
-| Pluralization | Use ICU message format |
-
----
-
-## 7. RTL Support
-
-```css
-/* CSS Logical Properties */
-.container {
-  margin-inline-start: 1rem;  /* Not margin-left */
-  padding-inline-end: 1rem;   /* Not padding-right */
-}
-
-[dir="rtl"] .icon {
-  transform: scaleX(-1);
-}
-```
-
----
-
-## 8. Checklist
-
-Before shipping:
-
-- [ ] All user-facing strings use translation keys
-- [ ] Locale files exist for all supported languages
-- [ ] Date/number formatting uses Intl API
-- [ ] RTL layout tested (if applicable)
-- [ ] Fallback language configured
-- [ ] No hardcoded strings in components
-
----
-
-## Script
-
-| Script | Purpose | Command |
-|--------|---------|---------|
-| `scripts/i18n_checker.py` | Detect hardcoded strings & missing translations | `python scripts/i18n_checker.py <project_path>` |