fynt-landing-design
SKILL.md
Fynt Landing Design
Use this skill to generate or improve landing/marketing frontends in one of three modes.
Invocation Contract
$fynt-landing-design mode=clone$fynt-landing-design mode=adapt$fynt-landing-design mode=upgrade
If mode is missing, default to adapt.
Mode Behavior
clone: stay closest to Fynt visual DNA (editorial lines, node separators, dark canvas, orange accent hierarchy, isometric SVG language).adapt: preserve structure, craft, and motion quality while retheming for another brand.upgrade: transform an existing page or TSX into this quality bar with explicit before/after changes.
Required Output Contract
Always include all of the following before finalizing:
- Section architecture plan.
- Motion plan (entry, hover, transition, reduced-motion path).
- SVG treatment plan (hero composition + separators + bento/card motifs).
- Responsive behavior plan (mobile, tablet, desktop).
- Accessibility and performance checks.
- Rubric scorecard with pass/fail decision.
Do not finalize without a rubric pass from references/quality-rubric.md.
Workflow
- Identify mode and constraints.
- Read references/source-pattern-map.md first to anchor output in concrete source patterns.
- Load only needed references:
- Build output using assets as scaffolds when code is requested:
- Run a strict rubric check and return scores.
Non-Negotiables
- Keep motion restrained and purposeful; avoid animation spam.
- Preserve reduced-motion behavior using both
useReducedMotion()and CSS/media fallback. - Use handcrafted or structured SVG systems, not random icon collages.
- Keep contrast and focus states accessible.
- Keep visual effects performance-safe (avoid heavy filters over large constantly-animating surfaces).
Anti-Patterns To Reject
- Flat SaaS boilerplate without section rhythm or separators.
- Generic gradient hero with stock blob art replacing structural SVG composition.
- Overlong animations, unbounded spring chains, or jittery hover effects.
- No mobile strategy or no reduced-motion fallback.
- Color/token inconsistency across cards, controls, and separators.
Framework Baseline
Default target stack is Next.js + Tailwind CSS + Framer Motion.
Weekly Installs
3
Repository
bhaktofmahakal/…t-skillsFirst Seen
10 days ago
Security Audits
Installed on
cline3
github-copilot3
codex3
kimi-cli3
gemini-cli3
cursor3