fimo 2.10.1-staging.2 → 2.10.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/fimo-cli/SKILL.md +2 -2
- package/assets/skills/fimo-cli/SKILL.studio.md +42 -0
- package/assets/skills/fimo-cli/references/branches.md +43 -106
- package/assets/skills/fimo-cli/references/content/bulk.md +3 -12
- package/assets/skills/fimo-cli/references/content/localized.md +1 -1
- package/assets/skills/fimo-cli/references/content/sql.md +3 -10
- package/assets/skills/fimo-cli/references/deploy.md +35 -126
- package/assets/skills/fimo-cli/references/domains.md +38 -131
- package/assets/skills/fimo-cli/references/init.md +36 -170
- package/assets/skills/fimo-cli/references/projects.md +1 -1
- package/assets/skills/fimo-code/references/design.md +42 -126
- package/assets/skills/fimo-migration/SKILL.md +114 -408
- package/assets/skills/fimo-migration/references/content-delivery.md +67 -0
- package/assets/skills/fimo-migration/references/frameworks/nextjs.md +1 -1
- package/assets/skills/fimo-migration/references/qa/browser.md +41 -0
- package/assets/skills/fimo-migration/references/qa/guardrails.md +95 -0
- package/assets/skills/fimo-migration/references/qa/results.md +78 -0
- package/assets/skills/fimo-migration/references/qa.md +102 -383
- package/assets/skills/fimo-migration/references/questions-and-improvements.md +77 -168
- package/assets/skills/fimo-migration/references/setup.md +90 -0
- package/assets/skills/fimo-migration/references/workers/validator.md +2 -2
- package/assets/skills/fimo-migration/references/workers.md +1 -1
- package/assets/skills/fimo-migration/references/workflow.md +117 -171
- package/assets/skills/fimo-studio/SKILL.md +4 -1
- package/assets/skills/fimo-studio/references/ai-chat/agents.md +46 -0
- package/assets/skills/fimo-studio/references/ai-chat/default-agents.md +57 -0
- package/assets/skills/fimo-studio/references/ai-chat/routines.md +53 -0
- package/assets/skills/fimo-studio/references/ai-chat.md +39 -76
- package/assets/skills/fimo-studio/references/custom-domains.md +2 -2
- package/assets/skills/fimo-studio/references/publish-and-deploy.md +1 -1
- package/dist/cli/bundle.json +2 -2
- package/dist/cli/index.js +32 -11
- package/package.json +8 -8
- package/release.json +2 -2
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -1,142 +1,58 @@
|
|
|
1
1
|
# Design
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Read this before major visual work: the first design of a site, a redesign, a visual overhaul, or a vague request such as "make this look better". Skip it for bug fixes, refactors and copy changes.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
When the user gives exact visual details (fonts, colors, layout), skip the brief and build what they asked. Do not replace their choices with the taste rules below.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Keep the application's styling, routing and component conventions. For tracked React primitives, see `references/ui.md` and the framework reference.
|
|
8
8
|
|
|
9
9
|
## Brief first, code second
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Before you write code, write a short design brief with the sections in [The brief](#the-brief). Then build against it.
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Pick one clear direction and execute it with precision:
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
- **Purpose:** what the interface does, and for whom.
|
|
16
|
+
- **Tone:** one strong direction, for example brutally minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft pastel or industrial.
|
|
17
|
+
- **The one thing:** what a visitor will remember.
|
|
18
|
+
- **Constraints:** framework, performance, accessibility.
|
|
16
19
|
|
|
17
|
-
|
|
18
|
-
- **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. Use these for inspiration but design one true to the aesthetic direction.
|
|
19
|
-
- **Constraints**: Technical requirements (framework, performance, accessibility).
|
|
20
|
-
- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
|
|
20
|
+
Bold maximalism and refined minimalism both work: intention matters, not intensity. Match the code to the vision: maximalism needs elaborate code and motion; minimalism needs precise spacing and type.
|
|
21
21
|
|
|
22
|
-
|
|
22
|
+
## Rules
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
- **Typography:** pair a distinctive display font with a refined body font. Use at most two families. Do not use Inter, Roboto, Arial or system fonts as the design's voice. Vary fonts between sites; do not fall back to a "safe" choice such as Space Grotesk.
|
|
25
|
+
- **Color:** a dominant color with sharp accents, not an even, timid palette. Keep saturated colors for small actionable elements. Keep WCAG AA contrast: 4.5:1 for body text, 3:1 for large text. Put palette values in the project's existing theme tokens (for example Tailwind `@theme` or CSS variables) and use the tokens in components. Do not hard-code colors in components.
|
|
26
|
+
- **Motion:** prefer CSS; use the Motion library in React when the project has it. One orchestrated page load with staggered reveals is better than many small effects. Add scroll reveals and hover states that surprise.
|
|
27
|
+
- **Layout:** asymmetry, overlap, diagonal flow, elements that break the grid. Contrast tight clusters with generous space.
|
|
28
|
+
- **Backgrounds and detail:** give depth and atmosphere (gradient meshes, noise, patterns, layered transparency, strong shadows, decorative borders, grain) instead of flat fills.
|
|
29
|
+
- **Vary:** alternate light and dark themes, fonts and aesthetics between sites.
|
|
25
30
|
|
|
26
|
-
|
|
27
|
-
- **Color & Theme**: Commit to a cohesive aesthetic. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Reserve high-saturation colors for small actionable elements (icons, charts, buttons). Maintain WCAG AA contrast (4.5:1 body, 3:1 large text). Put palette values in the project's existing theme tokens instead of hard-coding colors in components.
|
|
28
|
-
- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions; use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
|
|
29
|
-
- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density. Dramatic whitespace contrast: tight clusters + generous breathing room.
|
|
30
|
-
- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors — gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, grain overlays.
|
|
31
|
-
|
|
32
|
-
NEVER use generic AI-generated aesthetics: overused font families (Inter, Roboto, Arial, system fonts), clichéd color schemes (especially purple gradients on white backgrounds), predictable layouts, cookie-cutter design.
|
|
33
|
-
|
|
34
|
-
Interpret creatively and make unexpected choices. 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.
|
|
35
|
-
|
|
36
|
-
**Match implementation complexity to the aesthetic vision.** Maximalist designs need elaborate code with extensive animations. Minimalist designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
|
|
37
|
-
|
|
38
|
-
---
|
|
31
|
+
**Generic AI patterns to avoid:** everything centered, purple gradients on white, uniform card grids, a generic hero, gray `slate-900` dark mode (use true or warm blacks), emoji decoration, safe blue pill buttons, a 4-column footer, stock blob illustrations, even spacing everywhere, "Welcome to X" headlines. In a brief, do not paste this list: name what would look wrong for this site.
|
|
39
32
|
|
|
40
33
|
## Reference anchors
|
|
41
34
|
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
| Inter / Roboto / Arial everywhere | Display fonts for headings, serif accents, personality in type |
|
|
67
|
-
| Generic hero layout | Editorial, asymmetric, full-bleed, split-screen, video backgrounds |
|
|
68
|
-
| Gray dark mode (slate-900) | True blacks, warm darks (#1A1A1A), tinted backgrounds |
|
|
69
|
-
| Emoji overuse (🚀✨🎉) | Subtle iconography, typography-only, or strategic single emoji |
|
|
70
|
-
| Safe blue pill buttons | Contextual styling, ghost buttons, text links, unusual shapes |
|
|
71
|
-
| Cookie-cutter 4-column footer | Footer as a design moment: personality, newsletter CTAs, minimal |
|
|
72
|
-
| Stock blob illustrations | Photography, 3D renders, custom illustrations, or no illustrations |
|
|
73
|
-
| Evenly distributed spacing | Dramatic whitespace contrast: tight clusters + generous breathing room |
|
|
74
|
-
| Generic "Welcome to X" headlines | Personality, questions, bold statements, single impactful words |
|
|
75
|
-
| Converging on Space Grotesk | Vary font choices across generations — never default to a "safe" pick |
|
|
76
|
-
|
|
77
|
-
When you list "Avoid" items in a design brief, be specific to the project context. Don't paste these generic items — explain what would look bad for THIS site.
|
|
78
|
-
|
|
79
|
-
---
|
|
80
|
-
|
|
81
|
-
## Design brief template
|
|
82
|
-
|
|
83
|
-
Use this structure for the brief produced **before** writing code on a non-trivial visual task. Keep each section short — bullets, not paragraphs.
|
|
84
|
-
|
|
85
|
-
### Vibe
|
|
86
|
-
|
|
87
|
-
One sentence describing the aesthetic direction + 2–3 reference anchors.
|
|
88
|
-
Example: "**Linear meets Stripe** — polished SaaS with premium editorial touches"
|
|
89
|
-
|
|
90
|
-
- Reference 1 (what aspect)
|
|
91
|
-
- Reference 2 (what aspect)
|
|
92
|
-
- Reference 3 (what aspect)
|
|
93
|
-
|
|
94
|
-
### Typography
|
|
95
|
-
|
|
96
|
-
- **Like:** Reference site(s) for typography inspiration
|
|
97
|
-
- **Headings:** Font name (e.g., "Satoshi Bold", "Space Grotesk", "Fraunces")
|
|
98
|
-
- **Body:** Font name (e.g., "Geist", "Source Serif Pro", "IBM Plex Sans")
|
|
99
|
-
- **Hierarchy:** Size contrast notes, weight usage, letter-spacing
|
|
100
|
-
|
|
101
|
-
### Color & Theme
|
|
102
|
-
|
|
103
|
-
- **Like:** Reference site(s) for color inspiration
|
|
104
|
-
- **Background:** Primary background color (hex)
|
|
105
|
-
- **Foreground:** Primary text color (hex)
|
|
106
|
-
- **Accent:** Primary accent color (hex)
|
|
107
|
-
- **Secondary accents:** Additional colors if needed
|
|
108
|
-
- **Dark mode:** Direction for dark mode palette (if applicable)
|
|
109
|
-
|
|
110
|
-
Write these into the project's existing theme tokens and reference the tokens from components.
|
|
111
|
-
|
|
112
|
-
### Motion & Interaction
|
|
113
|
-
|
|
114
|
-
- **Like:** Reference site(s) for motion inspiration
|
|
115
|
-
- **Page load:** Stagger, fade, slide
|
|
116
|
-
- **Scroll:** Parallax, reveals, sticky elements
|
|
117
|
-
- **Hover:** Card lifts, color shifts, micro-animations
|
|
118
|
-
- **Transitions:** Page transitions, state changes
|
|
119
|
-
|
|
120
|
-
### Photography & Media
|
|
121
|
-
|
|
122
|
-
- **Like:** Reference site(s) for media direction
|
|
123
|
-
- **Style:** Cinematic, lifestyle, abstract, illustrated, minimal
|
|
124
|
-
- **Treatment:** Full-bleed, contained, overlays, filters
|
|
125
|
-
- **Hero:** Specific direction for hero imagery
|
|
126
|
-
|
|
127
|
-
If the user hasn't supplied images and one is needed, run `fimo image generate --prompt "..."` and reuse the returned `url` or `id`. Run `fimo image generate --help` for current flags. Upload any image that exists only as a local file before using it (`SKILL.md` § Non-negotiable boundaries). See `references/assets.md`.
|
|
128
|
-
|
|
129
|
-
### Iconography
|
|
130
|
-
|
|
131
|
-
- **Like:** Reference site(s) for icon style
|
|
132
|
-
- **Style:** Line icons, filled, duotone, custom
|
|
133
|
-
- **Library:** the icon set the project already uses, a custom set, or none
|
|
134
|
-
- **Usage:** Sparse and meaningful vs. decorative
|
|
135
|
-
|
|
136
|
-
### Quality Bar
|
|
137
|
-
|
|
138
|
-
Pick the row from the Reference Anchors table that matches this project's category and quote its quality-bar question.
|
|
139
|
-
|
|
140
|
-
### Avoid
|
|
141
|
-
|
|
142
|
-
List 3–5 specific patterns to NOT use for this project. Be specific to this project's context — don't paste generic items from the AI Slop Patterns table.
|
|
35
|
+
Anchor the direction on 2–3 well-known sites, brands or studios that fit the project. Examples per category, with the quality bar:
|
|
36
|
+
|
|
37
|
+
- **Creative / agency:** Awwwards winners, Pentagram, Active Theory. Would it win Awwwards Site of the Day?
|
|
38
|
+
- **SaaS / product:** Linear, Stripe, Raycast, Supabase, Mercury. Is it Linear-polished?
|
|
39
|
+
- **Editorial / blog:** The Verge, Monocle, The Atlantic, Substack. Is it magazine-worthy?
|
|
40
|
+
- **E-commerce:** Apple Store, Glossier, SSENSE, Everlane. Would you trust buying from it?
|
|
41
|
+
- **Documentation:** Stripe Docs, Tailwind Docs, Supabase Docs. Can a developer find what they need in 3 seconds?
|
|
42
|
+
- **Personal / portfolio:** Read.cv, Rauno Freiberg, Josh Comeau. Is it memorable and personal?
|
|
43
|
+
- **Corporate:** Apple, Airbnb, Slack, Intercom. Premium but not flashy?
|
|
44
|
+
- **Dashboard:** Linear, Retool, Airtable. Dense but never cluttered?
|
|
45
|
+
- **Landing page:** Framer templates, Lapa.ninja features. Does it convert and delight?
|
|
46
|
+
|
|
47
|
+
## The brief
|
|
48
|
+
|
|
49
|
+
Keep each section to a few bullets.
|
|
50
|
+
|
|
51
|
+
- **Vibe:** one sentence and 2–3 anchors, each with the aspect you take from it (for example "Linear meets Stripe: polished SaaS with editorial touches").
|
|
52
|
+
- **Typography:** the sites you take type from; heading font; body font; hierarchy (size contrast, weights, letter-spacing).
|
|
53
|
+
- **Color & Theme:** the sites you take color from; background, foreground, accent and secondary colors as hex values; dark mode direction. Write them into the theme tokens.
|
|
54
|
+
- **Motion & Interaction:** the sites you take motion from; page load, scroll, hover and transitions.
|
|
55
|
+
- **Photography & Media:** the sites you take media from; style, treatment and hero direction. When the user has no image and one is needed, run `fimo image generate --prompt "..."` and use the returned `url` or `id` (`fimo image generate --help` lists the flags). Do not generate a real photo of a real thing (the team, a product): ask the user for it. Upload a local image file with `fimo assets upload` before you use it (`SKILL.md` § Non-negotiable boundaries lists the files that stay in the repository; `references/assets.md`).
|
|
56
|
+
- **Iconography:** the sites you take icons from; style (line, filled, duotone, custom); the set (the project's existing set, a custom set, or none); sparse and meaningful, or decorative.
|
|
57
|
+
- **Quality Bar:** the anchor category of this project and its question.
|
|
58
|
+
- **Avoid:** 3–5 patterns that would look wrong for this site.
|