
silvertext.com
Zastosuj style
Wybierz style, które chcesz zastosować na swojej stronie, a następnie skopiuj polecenie.
Od inspiracji do interfejsu
Zobacz, jak język wizualny tej strony staje się oryginalnym interfejsem. Użyj promptu, aby stworzyć własny.
Stwórz coś podobnego
Skopiuj początkowy prompt do agenta programistycznego lub dostosuj go do swojego pomysłu.
Use the silvertext.com design pack from Stylepack so what you build looks and behaves like https://silvertext.com/.
Use the silvertext.com design pack from Stylepack so what you build looks and behaves like https://silvertext.com/.
1. Download https://stylepack.ai/packs/silvertext.com/pack.zip?v=bzs7gpqsruxr and unzip it so the pack sits at `design/silvertext.com-design-pack/` (for example: curl -fsSL --http1.1 --retry 3 --retry-max-time 240 --connect-timeout 15 --max-time 120 --cookie "" 'https://stylepack.ai/packs/silvertext.com/pack.zip?v=bzs7gpqsruxr' -o pack.zip && unzip -oq pack.zip -d design && rm pack.zip).
2. Read `design/silvertext.com-design-pack/START_HERE.md` and follow it: it says which files and screenshots to open, in what order, and how to check the result. Build both themes.
Build: Oryginalna strona docelowa z sekcją główną, kartami funkcji i wezwaniem do działania.
When you are done, compare the result with the desktop and phone screenshots in `design/silvertext.com-design-pack/screenshots/`, fix the biggest visual difference first, and repeat.Kolory
Kolory: 9Komponenty
- przycisk secondary
- tekst #17171c na #ffffff, r 6px, h 31px, 14px/500
- przycisk primary
- tekst #ffffff na #5b4dee, r 10px, h 48px, 16px/500
- przycisk ghost
- tekst #9d90ff na przezroczysty na #090910, r 0px, h 24px, 12.5px/550
- karta
- #ffffff, 1px solid #e7e7ee, r 16px, cień
- link
- #17171c, bez podkreślenia, 450
- nagłówek
- 69px, fixed, linki: 12 po 16px
- nagłówek główny
- 84.96px / 900, wyrównanie: center, maks. 678px
- badge
- "14": #efecfe on #4534c9, 10px/600, 21px tall, radius 3.35544e+07px, padding 2px 7px, uppercase
- badge
- "92% match": #fdeaea on #b93838, 10px/600, 23px tall, radius 3.35544e+07px, padding 3px 8px
- awatar
- Avatar 28px, radius 50%, border 0px rgb(34, 51, 89)
- formularze
- 0 forms, 0 inputs. Required markers: 0. Help texts: 0. Label placement: no labelled inputs.
- ikony
- Icons: 44 inline SVGs, outline/stroke, sizes 12px/14px/13px/15px, stroke 2px/1.7px/2.2px; icon font classes lucide.
Interakcje i animacje
- button primary "Sign upGet started": background #ffffff → #fafafa, gradient changes
- button secondary "Check my writing": background #5b4dee → #574ae4, gradient changes
- nav link "silvertext.": bez zmiany po hover
- focus button primary: outline 2px solid rgb(139, 129, 243), offset 3px
- tooltipy: Tooltip triggers exist (2 × title) but none opened on hover in the first viewport; title attributes fall back to the browser's native tooltip.
- menu: No dropdown menus found in the header.
- animacje: 81 elements carry transitions; typical 0.15s with cubic-bezier(0.4, 0, 0.2, 1), mostly on background-color, color, border-color. 10 running keyframe animations (os-spin 3.2s infinite; os-shine 3.2s infinite; os-twinkle 3.8s infinite). 4 sizable elements sit at opacity 0 before scrolling: scroll-reveal animations are in use (reveal on enter, fade + rise is the usual recipe).
Typografia
Czcionki: 1Odstępy
jednostka 4px- Szerokość treści
- 1080px
- Breakpointy
- 640, 768, 1024, 1280, 1536px
Zaokrąglenia
Cienie
4Ciemny motyw
Dostępny przez data-theme=dark. Jasny → ciemny:
Cienie (tryb ciemny): rgba(30, 25, 90, 0.15) 0px 16px 36px 0px; rgba(20, 20, 30, 0.04) 0px 2px 6px 0px, rgba(20, 20, 30, 0.06) 0px 18px 44px 0px
Logo i ikony
7 odniesieńInwentarz komponentów
17 z 87 rodzajów · 39 wariantów · 29 stanów · 1 overlayówZobacz każdy komponent w kontekście jego oryginalnej strony.













Nie ma na tej stronie: Toggle / segmented control, Button group, Text link, Floating action button, Close / dismiss button, Text input, Search field, Textarea, Select (native), Combobox / custom select, Checkbox, Radio, Switch / toggle, Range slider, File input / dropzone, Date / time input, Input with attached button or addon, Field label, Help / hint text, Validation error text, Fieldset / form section, Menu / dropdown trigger, Breadcrumb, Tabs, Pagination, Stepper / progress steps, Sidebar navigation, Skip link, Back to top, Social icon links, Theme toggle, Language / region switch, Tooltip, Popover, Dropdown menu, Drawer / sheet / off-canvas, Toast / snackbar, Banner / announcement bar, Cookie / consent notice, Lightbox / media viewer, Chip (removable / selectable tag), Alert / callout, Progress bar, Spinner / loader, Counter / notification dot, Empty state, Rating / stars, Pricing card / plan, Testimonial / quote card, Stat / metric, Styled list, List row / menu row, Table, Table row, Accordion / disclosure, Avatar stack, Divider, Code block / inline code, Keyboard key, Blockquote, Image / figure, Video / media embed, Carousel / slider, Logo strip, FAQ block, Call-to-action band, Newsletter / signup form, Search results / listing row, Grid of items, Sticky bar.
Responsywność
1440 / 1024 / 768 / 390 px| Viewport | Treść | Marginesy | Tekst | Nagłówek | Nagłówek | Hero | Siatki | Przyciski |
|---|---|---|---|---|---|---|---|---|
| desktop 1440 | 1080px | 381px | 16px | 85px, 2 lines, center | 69px, 7 links, 1 CTA | media below text | 2→2 col; 2→1 col; 2→1 col | content-width |
| laptop 1024 | 976px | 271px | 16px | 60.4px, 2 lines, center | 69px, 7 links, 1 CTA | media below text | 2→1 col; 2→2 col; 2→2 col | content-width |
| tablet 768 | 720px | 203px | 16px | 45.3px, 2 lines, center | 69px, hamburger (Open menu), 2 CTA | media below text | 2→1 col; 2→2 col; 3→1 col | content-width |
| phone 390 | 342px | 24px | 16px | 44px, 3 lines, center | 69px, hamburger (Open menu), 2 CTA | media below text | 2→1 col; 2→1 col; 2→1 col | content-width |
- H1 goes 85px → 44px (52%), 2 → 3 lines.
- Nav collapses to a hamburger by 390px (first seen at 768px); header 69px → 69px.
- Card grids: 2 columns → 1 column on phones (gap 36px → 20px).
- Body text is 16px at the sampled desktop and phone widths.
- Phone side gutter 24px.
- Section top padding 68px → 68px.
Pliki w pakiecie
Pliki: 138Zacznij od 54 kB tekstu przewodnika. Cały tekst paczki to 1,2 MB; szczegółowe pliki otwieraj w razie potrzeby. Obrazy są osobno.
# Start here: silvertext.com
Observed 2026-11-04T23:06:09.834Z; default light theme. This is a compact handoff, not the full evidence archive: everything you need to start is here, the detailed files are one step away.
## How to use this pack
1. Read `START_HERE.md` and `tokens.css` first: the priority values. Keep observed values; a value marked inferred or fallback is a suggestion to resolve against the screenshots.
2. Open `screenshots/desktop-1440-fold.png` and `screenshots/phone-390-fold.png` and match the composition, density, whitespace and image treatment; the values do not carry those. Treat the inside of an image or canvas as a visual inference, not measured DOM.
3. Read `MEDIA.md` before choosing or generating imagery. Preserve the reference's art direction while adapting the subject to the new product. Inspect actual candidate images against the reference and check their desktop and phone crops in the rendered UI. Photography must not silently become geometric illustration; unresolved assets must be reported.
4. Read `FONTS.md` and load `fonts.css` before `tokens.css`. Keep exact weights and variable-font settings and verify the fonts that actually render. If a font is unavailable, name the substitute and compare its width and apparent weight before touching the type scale.
5. Before drawing any logo or icon, read `BRAND.md` and open `screenshots/brand-logo.png`, `screenshots/brand-symbol.png`, `screenshots/brand-icon-1.png`: for a new product, create an original mark with the observed proportions and treatment; never guess a shape from a label.
6. Before building any control, read `COMPONENTS.md` (every variant and measured state, with a crop of each), use `components.css` for the CSS and `demos/` for a live copy of each component. A component listed as not found was not detected in this capture; do not invent a source measurement.
7. Read `REGIONS.md` and inspect its context, detail and icon crops: reconstruct outer and inner surfaces, per-layer gradients and shadows and group spacing (`regions.css` has the recipes), then check the whole page again.
8. Read `BEHAVIOR.md` for hover, focus, tooltips, menus, motion, scrolling, tables, forms, text and each breakpoint, and reproduce the behaviour, not only the colours. Build both themes; `DESIGN.md` pairs the colours.
9. `layout.html` is a generic page composed only from this pack's measured values, with placeholder copy (`layout-alt.html` in the other theme): open it to see the colours, type, recipes and spacing working together and to check your own wiring of the fonts and tokens against it. It is not the site's composition; the screenshots are.
10. `DESIGN.md` has the whole system when a value is missing above. `evidence.json` is diagnostic data: never in the first read.
11. When done, render at desktop, 390px and 320px, compare with the screenshots, fix the biggest visible mismatch first (usually type size, whitespace or image treatment), recheck keyboard focus, overflow, navigation and forms, and repeat.
12. For another site's design, use the enabled Stylepack MCP tools: query_components for specific controls or get_design_pack for broader visual context. Without MCP, fetch https://stylepack.ai/packs/<host>/pack.zip; one question at a time is at https://stylepack.ai/packs/<host>/fonts, /colors and /buttons. Preserve explicit source pages and report missing evidence.
## Priority values and evidence
Values labeled fallback were not observed for that role; inferred-role means a visible heading was mapped to a display role. Keep observed values, but treat fallbacks as suggestions.
Keep measured sizes, tracking, radii and colors unless the new content requires an explicit adaptation. Do not enlarge the headline simply to fill a different line length.
Content width: 1080px. Inferred spacing base: 4px; sampled scale: 4, 8, 12, 16, 20, 24, 28, 32, 40px. Observed CSS breakpoints: 640, 768, 1024, 1280, 1536px.
Colors: background=#ffffff; surface=#efecfe; surface-2=#faefe1; foreground=#17171c; muted-foreground=#3a3a44; primary=#5b4dee; on-primary=#ffffff; secondary=#16a34a; border=#e7e7ee.
- primary: Selected from measured button, link, text, painted-area and theme colors. It is not proof of a filled primary button; follow the observed component recipes.
Radii: button 6px, card 16px, input 6px, image 9999px.
Shadows: rgba(30, 25, 90, 0.15) 0px 16px 36px 0px; rgba(20, 20, 30, 0.04) 0px 2px 6px 0px, rgba(20, 20, 30, 0.06) 0px 18px 44px 0px; rgba(91, 77, 238, 0.35) 0px 2px 8px 0px, rgba(167, 139, 250, 0.26) 0px 0px 16px 0px.
## Typography
Load fonts.css before applying tokens.css. FONTS.md contains the observed face/weight inventory and rendered-font checks. A CSS family name alone does not load a font.
Copy the supplied @font-face sources verbatim; do not replace a captured face with Google Fonts merely because its name looks similar. Keep fonts.css linked (or inline it verbatim for a single HTML deliverable). It includes measured semantic font defaults; tokens.css supplies scale and spacing. Use each role as a complete recipe: family, exact numeric weight, size, line height, tracking, font-feature-settings (including cv/ss stylistic sets), optical sizing and variable-font settings. A font shorthand resets feature settings; reapply the supplied longhands after it. Do not round 510 to 500/600, or turn a measured light style into a bold heading.
Use the captured family first. Self-hosted is a hosting location, not an availability verdict. An unverified probe is not evidence of failure; do not choose the optional fallback merely because it is familiar. Substitute only after an actual failed destination request or missing licensed source; record that reason and the replacement. A transient network error merits a retry before redesigning the typography.
Fallback roles are unmeasured suggestions. If a role is absent, start from the nearest observed text treatment; do not assume headings must be bold.
- mulishLatin: observed weights 450, 550, 600, 650, 900; source loading recipe in fonts.css.
- mulishLatin delivery by face: confirmed 200 1000 normal; failed none; unverified none. Confirmation is from one isolated-origin check, not every deployment. Keep confirmed faces; attempt unverified faces. A failed unused face does not invalidate a working regular/bold face.
After loading, inspect the browser's Rendered Fonts for the headline, body and button. Computed font-family/font-weight and document.fonts.check() alone do not prove which face drew the glyphs.
- headline-display: mulishLatin; 84.96px/84.96px; weight 900; tracking -3.8232px; observed, source h1.
- headline-lg: mulishLatin; 51.84px/58.0608px; weight 650; tracking -1.296px; observed, source h2.
- headline-md: mulishLatin; 18px/28px; weight 650; tracking -0.27px; observed, source h3.
- body-md: mulishLatin; 12.5px/23.75px; weight 450; tracking -0.08px; observed, source body.
- label-md: mulishLatin; 12px/1.5; weight 600; tracking -0.08px; observed, source label.
- button: mulishLatin; 12.5px/12.5px; weight 550; tracking -0.08px; observed, source button.
- Font mulishLatin: self-hosted; use its captured loader first. Self-hosted does not imply unavailable or licensed for reuse; substitution is conditional, not a second design choice.
## Regional composition
Read REGIONS.md and open the referenced context, detail and icon crops before drawing complex previews. Build outer shell, inset content panel and internal groups as distinct layers where observed. Preserve which surface owns each gradient, border and shadow; do not apply one generic card treatment to every layer.
For images, canvas, video and external SVG, use the rendered crops to infer visible internal groupings. Keep those inferences separate from measured DOM facts. Do not treat an illustration as a functional app or paste the screenshot as the finished UI. Return to the whole-page screenshots to match scale and placement.
- r1: 1440×1300px at page (0, 0); 24 measured layers, 7 icon samples, 0 opaque media layers. screenshots/region-r1-context.jpg, screenshots/region-r1-detail.png, screenshots/region-r1-icons.png
- r2: 1440×896.5px at page (0, 1210); 20 measured layers, 8 icon samples, 0 opaque media layers. screenshots/region-r2-context.jpg, screenshots/region-r2-detail.png, screenshots/region-r2-icons.png
- r3: 1440×1257.4px at page (0, 2106.5); 23 measured layers, 12 icon samples, 0 opaque media layers. screenshots/region-r3-context.jpg, screenshots/region-r3-detail.png, screenshots/region-r3-icons.png
## Component recipes
- secondary button: bg #ffffff; text #17171c; border 1px solid #18181b1a; radius 6px; height 31px; padding 6px 13px; type 14px/500; shadow rgba(255, 255, 255, 0.7) 0px 1px 0.5px 0px inset, rgba(24, 24, 27, 0.05) 0px 2px 2px -1px, rgba(24, 24, 27, 0.05) 0px 4px 4px -2px.
- primary button: bg #5b4dee; text #ffffff; border 1px solid #493ebe; radius 10px; height 48px; padding 0px 28px; type 16px/500; shadow rgba(255, 255, 255, 0.12) 0px 1px 0px 0px inset, rgba(24, 24, 27, 0.08) 0px 1px 1px 0px.
- ghost button: bg transparent; text #9d90ff; border none; radius 0px; height 24px; padding 0px 37px; type 12.5px/550; shadow none.
- Card: {"bg":"#ffffff","border":"1px solid #e7e7ee","radius":"16px","padding":"0px","shadow":"rgba(0, 0, 0, 0) 0px 0px 0px 0px, rgba(0, 0, 0, 0) 0px 0px 0px 0px, rgba(0, 0, 0, 0) 0px 0px 0px 0px, rgba(0, 0, 0, 0) 0px 0px 0px 0px, rgba(20, 20, 30, 0.05) 0px 2px 6px 0px, rgba(20, 20, 30, 0.09) 0px 22px 50px 0px","w":320,"h":250}.
## Responsive and interaction evidence
- desktop 1440px: content 1080px, gutter 381px, H1 85px, 2 lines, center, header 69px, 7 links, 1 CTA, grids 2→2 col; 2→1 col; 2→1 col.
- laptop 1024px: content 976px, gutter 271px, H1 60.4px, 2 lines, center, header 69px, 7 links, 1 CTA, grids 2→1 col; 2→2 col; 2→2 col.
- tablet 768px: content 720px, gutter 203px, H1 45.3px, 2 lines, center, header 69px, hamburger (Open menu), 2 CTA, grids 2→1 col; 2→2 col; 3→1 col.
- phone 390px: content 342px, gutter 24px, H1 44px, 3 lines, center, header 69px, hamburger (Open menu), 2 CTA, grids 2→1 col; 2→1 col; 2→1 col.
H1 goes 85px → 44px (52%), 2 → 3 lines.
Nav collapses to a hamburger by 390px (first seen at 768px); header 69px → 69px.
Card grids: 2 columns → 1 column on phones (gap 36px → 20px).
Body text is 16px at the sampled desktop and phone widths.
- Hover button-primary: background #ffffff → #fafafa, gradient changes.
- Hover button-secondary: background #5b4dee → #574ae4, gradient changes.
- Hover nav-link: no visible change.
- Focus button-primary: outline 2px solid rgb(139, 129, 243), offset 3px.
81 elements carry transitions; typical 0.15s with cubic-bezier(0.4, 0, 0.2, 1), mostly on background-color, color, border-color. 10 running keyframe animations (os-spin 3.2s infinite; os-shine 3.2s infinite; os-twinkle 3.8s infinite).
Alternate dark theme observed; use DESIGN.md for paired colors.
## Logo and icons
Logo lockup: 121×31px, outline/stroke. See BRAND.md and its crops for shape evidence.
Icon: 13×13px; outline/stroke; stroke 2px, caps round.
Icon: 16×16px; outline/stroke; stroke 2px, caps round.
## First images to open
- screenshots/desktop-1440-fold.png: Desktop 1440, above the fold
- screenshots/brand-logo.png: primary logo lockup
- screenshots/brand-symbol.png: possible standalone brand symbol
- screenshots/phone-390-fold.png: Phone 390, above the fold
## Verify the build
Render at desktop, 390px and 320px. Inspect the result, compare against the supplied references, fix the largest visible mismatch, and recheck keyboard focus, overflow, navigation and form behavior. Match the visual language while following the requested product content.
















































