Entry point: /faion-net — invoke this skill for automatic routing to the appropriate domain.
Frontend Developer Skill
Frontend development specializing in styling, UI libraries, design systems, and modern frontend patterns.
Purpose
Handles frontend styling, design systems, UI component libraries, accessibility, PWA, and responsive design.
Context Discovery
Auto-Investigation
Detect frontend styling setup:
| Signal |
How to Check |
What It Tells Us |
tailwind.config.* |
Glob("**/tailwind.config.*") |
Tailwind CSS used |
styled-components |
Grep("styled-components", "package.json") |
Styled Components |
emotion |
Grep("@emotion", "package.json") |
Emotion CSS-in-JS |
shadcn components |
Glob("**/components/ui/*.tsx") |
shadcn/ui used |
.storybook/ |
Glob("**/.storybook/*") |
Storybook setup |
| Design tokens |
Glob("**/tokens.*") |
Design system exists |
| PWA manifest |
Glob("**/manifest.json") |
PWA configured |
Read existing patterns:
- tailwind.config for theme/tokens
- Existing components for styling patterns
- Storybook stories for component API
Discovery Questions
Q1: Styling Approach
question: "What styling approach are you using?"
header: "Styling"
multiSelect: false
options:
- label: "Tailwind CSS"
description: "Utility-first CSS framework"
- label: "CSS-in-JS (Styled Components, Emotion)"
description: "JavaScript-based styling"
- label: "CSS Modules"
description: "Scoped CSS files"
- label: "Plain CSS/SCSS"
description: "Traditional stylesheets"
- label: "Not decided / recommend"
description: "I'll suggest based on project"
Q2: UI Component Library
question: "Are you using a UI component library?"
header: "UI Lib"
multiSelect: false
options:
- label: "shadcn/ui"
description: "Copy-paste Radix-based components"
- label: "Material UI"
description: "Google Material Design"
- label: "Chakra UI"
description: "Accessible component library"
- label: "Custom components"
description: "Building from scratch"
- label: "None yet"
description: "Need recommendation"
Q3: Design System Status
question: "Do you have a design system?"
header: "Design"
multiSelect: false
options:
- label: "Yes, with design tokens"
description: "Colors, spacing, typography defined"
- label: "Figma designs exist"
description: "Designs to implement"
- label: "No formal system"
description: "Ad-hoc styling"
- label: "Need to create one"
description: "Want to establish system"
Q4: Accessibility Requirements
question: "What are your accessibility requirements?"
header: "A11y"
multiSelect: false
options:
- label: "WCAG 2.1 AA compliance"
description: "Standard accessibility"
- label: "WCAG 2.1 AAA compliance"
description: "Highest accessibility"
- label: "Basic accessibility"
description: "Semantic HTML, keyboard nav"
- label: "Not a priority yet"
description: "Focus on functionality first"
When to Use
- Tailwind CSS styling and architecture
- Design tokens and design systems
- CSS-in-JS patterns
- UI component libraries (shadcn/ui, etc.)
- Progressive Web Apps (PWA)
- Responsive and mobile design
- Accessibility (a11y)
- SEO for SPAs
- Storybook component development
Methodologies
| Category |
Methodology |
File |
| Tailwind CSS |
|
|
| Tailwind basics |
Setup, utilities, responsive design |
tailwind.md |
| Tailwind architecture |
Component organization, theme config |
tailwind-architecture.md |
| Tailwind patterns |
Best practices, patterns, plugins |
tailwind-patterns.md |
| CSS-in-JS |
|
|
| CSS-in-JS basics |
Styled components, emotion basics |
css-in-js-basics.md |
| CSS-in-JS advanced |
Theme, SSR, performance |
css-in-js-advanced.md |
| Design Systems |
|
|
| Design tokens basics |
Token structure, naming conventions |
design-tokens-basics.md |
| Design tokens implementation |
Token generation, tooling |
design-tokens-implementation.md |
| UI Libraries |
|
|
| shadcn/ui |
Component setup and usage |
shadcn-ui.md |
| shadcn/ui architecture |
Project structure, customization |
shadcn-ui-architecture.md |
| UI lib basics |
Component library patterns |
ui-lib-basics.md |
| UI lib patterns |
Advanced component patterns |
ui-lib-patterns.md |
| Storybook setup |
Storybook configuration, stories |
storybook-setup.md |
| Responsive & Mobile |
|
|
| Mobile responsive |
Responsive design, breakpoints |
mobile-responsive.md |
| PWA |
|
|
| PWA core |
Service workers, caching, offline |
pwa-core.md |
| PWA advanced |
Push notifications, sync, install |
pwa-advanced.md |
| SEO & Accessibility |
|
|
| SEO for SPAs |
SSR, meta tags, structured data |
seo-for-spas.md |
| Accessibility |
ARIA, keyboard nav, screen readers |
accessibility.md |
| Frontend Design |
|
|
| Frontend design |
UI/UX implementation patterns |
frontend-design.md |
Tools
- Styling: Tailwind CSS, CSS-in-JS (styled-components, emotion)
- Design tokens: Style Dictionary, Figma Tokens
- UI libraries: shadcn/ui, Radix UI, Headless UI
- Storybook: Component development and documentation
- Accessibility: axe-core, WAVE, Lighthouse
Related Sub-Skills
| Sub-skill |
Relationship |
| faion-javascript-developer |
React components, Next.js |
| faion-ux-ui-designer |
Design specs and mockups |
| faion-devtools-developer |
Build tools, bundlers |
Integration
Invoked by parent skill faion-software-developer for frontend styling and UI work.
faion-frontend-developer v1.0 | 18 methodologies
1---2name: faion-frontend-developer3description: Frontend: Tailwind, CSS-in-JS, design tokens, UI libraries, PWA, accessibility.4---5> **Entry point:** `/faion-net` — invoke this skill for automatic routing to the appropriate domain.
6
7# Frontend Developer Skill
8
9Frontend development specializing in styling, UI libraries, design systems, and modern frontend patterns.
10
11## Purpose
12
13Handles frontend styling, design systems, UI component libraries, accessibility, PWA, and responsive design.
14
15---
16
17## Context Discovery
18
19### Auto-Investigation
20
21Detect frontend styling setup:
22
23| Signal | How to Check | What It Tells Us |
24|--------|--------------|------------------|
25| `tailwind.config.*` | `Glob("**/tailwind.config.*")` | Tailwind CSS used |
26| `styled-components` | `Grep("styled-components", "package.json")` | Styled Components |
27| `emotion` | `Grep("@emotion", "package.json")` | Emotion CSS-in-JS |
28| `shadcn` components | `Glob("**/components/ui/*.tsx")` | shadcn/ui used |
29| `.storybook/` | `Glob("**/.storybook/*")` | Storybook setup |
30| Design tokens | `Glob("**/tokens.*")` | Design system exists |
31| PWA manifest | `Glob("**/manifest.json")` | PWA configured |
32
33**Read existing patterns:**
34- tailwind.config for theme/tokens
35- Existing components for styling patterns
36- Storybook stories for component API
37
38### Discovery Questions
39
40#### Q1: Styling Approach
41
42```yaml
43question: "What styling approach are you using?"
44header: "Styling"
45multiSelect: false
46options:
47 - label: "Tailwind CSS"
48 description: "Utility-first CSS framework"
49 - label: "CSS-in-JS (Styled Components, Emotion)"
50 description: "JavaScript-based styling"
51 - label: "CSS Modules"
52 description: "Scoped CSS files"
53 - label: "Plain CSS/SCSS"
54 description: "Traditional stylesheets"
55 - label: "Not decided / recommend"
56 description: "I'll suggest based on project"
57```
58
59#### Q2: UI Component Library
60
61```yaml
62question: "Are you using a UI component library?"
63header: "UI Lib"
64multiSelect: false
65options:
66 - label: "shadcn/ui"
67 description: "Copy-paste Radix-based components"
68 - label: "Material UI"
69 description: "Google Material Design"
70 - label: "Chakra UI"
71 description: "Accessible component library"
72 - label: "Custom components"
73 description: "Building from scratch"
74 - label: "None yet"
75 description: "Need recommendation"
76```
77
78#### Q3: Design System Status
79
80```yaml
81question: "Do you have a design system?"
82header: "Design"
83multiSelect: false
84options:
85 - label: "Yes, with design tokens"
86 description: "Colors, spacing, typography defined"
87 - label: "Figma designs exist"
88 description: "Designs to implement"
89 - label: "No formal system"
90 description: "Ad-hoc styling"
91 - label: "Need to create one"
92 description: "Want to establish system"
93```
94
95#### Q4: Accessibility Requirements
96
97```yaml
98question: "What are your accessibility requirements?"
99header: "A11y"
100multiSelect: false
101options:
102 - label: "WCAG 2.1 AA compliance"
103 description: "Standard accessibility"
104 - label: "WCAG 2.1 AAA compliance"
105 description: "Highest accessibility"
106 - label: "Basic accessibility"
107 description: "Semantic HTML, keyboard nav"
108 - label: "Not a priority yet"
109 description: "Focus on functionality first"
110```
111
112---
113
114## When to Use
115
116- Tailwind CSS styling and architecture
117- Design tokens and design systems
118- CSS-in-JS patterns
119- UI component libraries (shadcn/ui, etc.)
120- Progressive Web Apps (PWA)
121- Responsive and mobile design
122- Accessibility (a11y)
123- SEO for SPAs
124- Storybook component development
125
126## Methodologies
127
128| Category | Methodology | File |
129|----------|-------------|------|
130| **Tailwind CSS** |
131| Tailwind basics | Setup, utilities, responsive design | tailwind.md |
132| Tailwind architecture | Component organization, theme config | tailwind-architecture.md |
133| Tailwind patterns | Best practices, patterns, plugins | tailwind-patterns.md |
134| **CSS-in-JS** |
135| CSS-in-JS basics | Styled components, emotion basics | css-in-js-basics.md |
136| CSS-in-JS advanced | Theme, SSR, performance | css-in-js-advanced.md |
137| **Design Systems** |
138| Design tokens basics | Token structure, naming conventions | design-tokens-basics.md |
139| Design tokens implementation | Token generation, tooling | design-tokens-implementation.md |
140| **UI Libraries** |
141| shadcn/ui | Component setup and usage | shadcn-ui.md |
142| shadcn/ui architecture | Project structure, customization | shadcn-ui-architecture.md |
143| UI lib basics | Component library patterns | ui-lib-basics.md |
144| UI lib patterns | Advanced component patterns | ui-lib-patterns.md |
145| Storybook setup | Storybook configuration, stories | storybook-setup.md |
146| **Responsive & Mobile** |
147| Mobile responsive | Responsive design, breakpoints | mobile-responsive.md |
148| **PWA** |
149| PWA core | Service workers, caching, offline | pwa-core.md |
150| PWA advanced | Push notifications, sync, install | pwa-advanced.md |
151| **SEO & Accessibility** |
152| SEO for SPAs | SSR, meta tags, structured data | seo-for-spas.md |
153| Accessibility | ARIA, keyboard nav, screen readers | accessibility.md |
154| **Frontend Design** |
155| Frontend design | UI/UX implementation patterns | frontend-design.md |
156
157## Tools
158
159- **Styling:** Tailwind CSS, CSS-in-JS (styled-components, emotion)
160- **Design tokens:** Style Dictionary, Figma Tokens
161- **UI libraries:** shadcn/ui, Radix UI, Headless UI
162- **Storybook:** Component development and documentation
163- **Accessibility:** axe-core, WAVE, Lighthouse
164
165## Related Sub-Skills
166
167| Sub-skill | Relationship |
168|-----------|--------------|
169| faion-javascript-developer | React components, Next.js |
170| faion-ux-ui-designer | Design specs and mockups |
171| faion-devtools-developer | Build tools, bundlers |
172
173## Integration
174
175Invoked by parent skill `faion-software-developer` for frontend styling and UI work.
176
177---
178
179*faion-frontend-developer v1.0 | 18 methodologies*