@discourser/design-system 0.22.2 → 0.22.3
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/dist/figma-codex.json +2 -2
- package/docs/CSS_USAGE.md +235 -0
- package/docs/FIGMA_MAKE_SETUP.md +339 -0
- package/docs/GUIDELINES_REVIEW.md +728 -0
- package/docs/MAINTAINER_CHECKLIST.md +265 -0
- package/docs/TESTING_QUICK_REFERENCE.md +159 -0
- package/docs/TESTING_TOKENS.md +340 -0
- package/docs/active-stories/README.md +29 -0
- package/docs/active-stories/STORY-006a-figma-translation-foundations.md +324 -0
- package/docs/active-stories/STORY-006b-figma-translation-components.md +201 -0
- package/docs/active-stories/STORY-006c-figma-translation-layout-extension.md +258 -0
- package/docs/active-stories/STORY-008-kai-sidecar-fragments.md +137 -0
- package/docs/active-stories/STORY-011-verify-translation-docs.md +182 -0
- package/docs/archive/ARCHITECTURE-discourser-design-system.md +448 -0
- package/docs/claude-feed-back/ARCHITECTURE_DIAGRAM.md +243 -0
- package/docs/claude-feed-back/STYLING_VERIFICATION.md +89 -0
- package/docs/claude-feed-back/TEST_RESULTS.md +182 -0
- package/docs/context-share/ELEVATION_FIX_PLAN.md +903 -0
- package/docs/context-share/STORY-001-VALIDATION-PASSED.md +192 -0
- package/docs/context-share/STORY-002-IMPLEMENTATION-COMPLETE.md +161 -0
- package/docs/context-share/STORYBOOK_MCP_STRATEGY.md +867 -0
- package/docs/context-share/TESTING_GAPS_FILLED.md +353 -0
- package/docs/context-share/TOKEN_TESTING_SUMMARY.md +388 -0
- package/docs/context-share/code-connect-prompt.md +90 -0
- package/docs/context-share/dds-autonomous-pipeline.md +765 -0
- package/docs/context-share/fix-checkbox-radio-tokens.md +145 -0
- package/docs/context-share/icon-component-prompt.md +154 -0
- package/docs/context-share/icons/Audience.svg +3 -0
- package/docs/context-share/icons/AudioSpeaker.svg +3 -0
- package/docs/context-share/icons/BookmarkPlus.svg +3 -0
- package/docs/context-share/icons/ClipBoard.svg +8 -0
- package/docs/context-share/icons/DiscourserLogo.svg +4 -0
- package/docs/context-share/icons/ExitStudio.svg +4 -0
- package/docs/context-share/icons/Microphone.svg +5 -0
- package/docs/context-share/icons/NotebookPen.svg +3 -0
- package/docs/context-share/icons/PausePlay.svg +5 -0
- package/docs/context-share/icons/Play.svg +4 -0
- package/docs/context-share/icons/Record.svg +6 -0
- package/docs/context-share/icons/RepeatQuestion.svg +3 -0
- package/docs/context-share/icons/ScrollText.svg +3 -0
- package/docs/context-share/icons/Sparkles.svg +3 -0
- package/docs/context-share/icons/Speech.svg +3 -0
- package/docs/context-share/icons/StopPlay.svg +4 -0
- package/docs/context-share/icons/Timer.svg +3 -0
- package/docs/context-share/icons/UserProfile.svg +3 -0
- package/docs/context-share/m3-token-pipeline-audit.md +125 -0
- package/docs/context-share/storybook-mcp-kai-agent-revised-summary.md +211 -0
- package/docs/discourser-design-system-prd.md +3698 -0
- package/docs/figma-captures/01-typography.png +0 -0
- package/docs/figma-captures/02-button-iconbutton.png +0 -0
- package/docs/figma-captures/03-form-inputs.png +0 -0
- package/docs/figma-captures/04-form-controls.png +0 -0
- package/docs/figma-captures/05-data-display.png +0 -0
- package/docs/figma-captures/06-feedback.png +0 -0
- package/docs/figma-captures/07-overlays.png +0 -0
- package/docs/figma-captures/08-navigation-layout.png +0 -0
- package/docs/figma-captures/09-custom-components.png +0 -0
- package/docs/figma-captures/10-scenario-queue.png +0 -0
- package/docs/figma-captures/11-icon-library.png +0 -0
- package/docs/figma-make-docs/01-understanding-templates.md +235 -0
- package/docs/figma-make-docs/02-prerequisites.md +266 -0
- package/docs/figma-make-docs/03-creating-template.md +306 -0
- package/docs/figma-make-docs/04-adding-guidelines.md +448 -0
- package/docs/figma-make-docs/05-example-starter-code.md +590 -0
- package/docs/figma-make-docs/06-publishing-template.md +417 -0
- package/docs/figma-make-docs/07-maintenance.md +536 -0
- package/docs/figma-make-docs/08-faq.md +490 -0
- package/docs/figma-make-docs/README.md +95 -0
- package/docs/material-theme.json +418 -0
- package/docs/plans/2026-03-12-figma-token-export-rewrite.md +504 -0
- package/docs/plans/2026-03-12-step7-panda-token-resolution-design.md +119 -0
- package/docs/plans/2026-03-12-step7-panda-token-resolution.md +993 -0
- package/docs/token-name-mapping.json +850 -0
- package/docs/token-name-mapping.md +251 -0
- package/package.json +3 -2
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
@@ -0,0 +1,235 @@
|
|
|
1
|
+
# Understanding Figma Make Templates
|
|
2
|
+
|
|
3
|
+
## What is Figma Make?
|
|
4
|
+
|
|
5
|
+
Figma Make is an AI-powered code generation tool built into Figma that allows you to:
|
|
6
|
+
- Build interactive prototypes using real React code
|
|
7
|
+
- Generate UI components based on text prompts
|
|
8
|
+
- Use your production design system in prototypes
|
|
9
|
+
- Export working code for development
|
|
10
|
+
|
|
11
|
+
## What is a Figma Make Template?
|
|
12
|
+
|
|
13
|
+
A **Figma Make Template** is a pre-configured Figma Make file that serves as a starting point for new projects. Think of it as a "starter kit" that includes:
|
|
14
|
+
|
|
15
|
+
- Pre-installed npm packages (like your design system)
|
|
16
|
+
- Design system guidelines
|
|
17
|
+
- Example/starter code
|
|
18
|
+
- Configuration files (Vite, TypeScript, etc.)
|
|
19
|
+
- Best practices and patterns
|
|
20
|
+
|
|
21
|
+
### Template vs. Regular File
|
|
22
|
+
|
|
23
|
+
| Regular Figma Make File | Figma Make Template |
|
|
24
|
+
|------------------------|---------------------|
|
|
25
|
+
| User starts from scratch | User starts with everything configured |
|
|
26
|
+
| Must install packages manually | Packages pre-installed |
|
|
27
|
+
| Must add guidelines manually | Guidelines already included |
|
|
28
|
+
| No example code | Includes starter examples |
|
|
29
|
+
| Private to creator | Shared with team/organization |
|
|
30
|
+
|
|
31
|
+
## The Three-Part System
|
|
32
|
+
|
|
33
|
+
Understanding how the pieces fit together is crucial:
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
┌─────────────────────────────────────────────────────┐
|
|
37
|
+
│ 1. NPM Package (@discourser/design-system) │
|
|
38
|
+
│ • React components (Button, Card, Input, etc.) │
|
|
39
|
+
│ • Panda CSS styled-system │
|
|
40
|
+
│ • TypeScript definitions │
|
|
41
|
+
│ • Published to npm registry │
|
|
42
|
+
│ • Installed via: npm install │
|
|
43
|
+
└─────────────────────────────────────────────────────┘
|
|
44
|
+
↓ Used by
|
|
45
|
+
┌─────────────────────────────────────────────────────┐
|
|
46
|
+
│ 2. Guidelines (Markdown Documentation) │
|
|
47
|
+
│ • How to use components │
|
|
48
|
+
│ • Design token reference │
|
|
49
|
+
│ • Best practices and patterns │
|
|
50
|
+
│ • DO/DON'T examples │
|
|
51
|
+
│ • Lives in guidelines/ folder │
|
|
52
|
+
└─────────────────────────────────────────────────────┘
|
|
53
|
+
↓ Combined in
|
|
54
|
+
┌─────────────────────────────────────────────────────┐
|
|
55
|
+
│ 3. Figma Make Template (Pre-configured File) │
|
|
56
|
+
│ • Package installed in package.json │
|
|
57
|
+
│ • Guidelines copied to guidelines/ folder │
|
|
58
|
+
│ • Example code in src/ │
|
|
59
|
+
│ • Ready-to-use configuration │
|
|
60
|
+
│ • Published as shareable template │
|
|
61
|
+
└─────────────────────────────────────────────────────┘
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
## How Guidelines Work in Figma Make
|
|
65
|
+
|
|
66
|
+
### The AI Learning Process
|
|
67
|
+
|
|
68
|
+
Figma Make's AI reads guidelines to understand your design system:
|
|
69
|
+
|
|
70
|
+
1. **User asks:** "Create a login form"
|
|
71
|
+
2. **AI reads:** `guidelines/Guidelines.md` → "Read these in order..."
|
|
72
|
+
3. **AI reads:** `guidelines/overview-components.md` → "Available components: Button, Input..."
|
|
73
|
+
4. **AI reads:** `guidelines/components/button.md` → "Button has 5 variants..."
|
|
74
|
+
5. **AI reads:** `guidelines/components/input.md` → "Input requires label prop..."
|
|
75
|
+
6. **AI generates:**
|
|
76
|
+
```tsx
|
|
77
|
+
<form>
|
|
78
|
+
<Input label="Email" type="email" />
|
|
79
|
+
<Input label="Password" type="password" />
|
|
80
|
+
<Button variant="filled">Log In</Button>
|
|
81
|
+
</form>
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
### Why Guidelines Are Essential
|
|
85
|
+
|
|
86
|
+
Without guidelines, the AI will:
|
|
87
|
+
❌ Use native HTML elements instead of design system components
|
|
88
|
+
❌ Use raw color values instead of semantic tokens
|
|
89
|
+
❌ Create inconsistent component usage
|
|
90
|
+
❌ Miss accessibility requirements
|
|
91
|
+
❌ Not follow your design patterns
|
|
92
|
+
|
|
93
|
+
With guidelines, the AI will:
|
|
94
|
+
✅ Use design system components correctly
|
|
95
|
+
✅ Apply semantic tokens (primary, onPrimary, etc.)
|
|
96
|
+
✅ Follow M3 patterns and best practices
|
|
97
|
+
✅ Include proper accessibility attributes
|
|
98
|
+
✅ Generate production-ready code
|
|
99
|
+
|
|
100
|
+
## Where Everything Lives
|
|
101
|
+
|
|
102
|
+
### NPM Package (Published to npm)
|
|
103
|
+
```
|
|
104
|
+
@discourser/design-system/
|
|
105
|
+
├── dist/ # Compiled components
|
|
106
|
+
├── styled-system/ # Panda CSS output
|
|
107
|
+
├── package.json
|
|
108
|
+
└── README.md
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
**Lives:** npm registry (`registry.npmjs.org`)
|
|
112
|
+
**Accessed:** Via `npm install @discourser/design-system`
|
|
113
|
+
|
|
114
|
+
### Guidelines (In Your Repository)
|
|
115
|
+
```
|
|
116
|
+
guidelines/
|
|
117
|
+
├── Guidelines.md
|
|
118
|
+
├── overview-components.md
|
|
119
|
+
├── design-tokens/
|
|
120
|
+
│ ├── colors.md
|
|
121
|
+
│ ├── typography.md
|
|
122
|
+
│ ├── spacing.md
|
|
123
|
+
│ └── elevation.md
|
|
124
|
+
└── components/
|
|
125
|
+
├── button.md
|
|
126
|
+
├── card.md
|
|
127
|
+
├── dialog.md
|
|
128
|
+
├── icon-button.md
|
|
129
|
+
├── input.md
|
|
130
|
+
└── switch.md
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
**Lives:** Your repository (`/guidelines` folder)
|
|
134
|
+
**Accessed:** Manually copied into Figma Make files
|
|
135
|
+
|
|
136
|
+
### Figma Make Template (In Figma Cloud)
|
|
137
|
+
```
|
|
138
|
+
Figma Make File (template)
|
|
139
|
+
├── src/
|
|
140
|
+
│ ├── App.tsx # Example app
|
|
141
|
+
│ └── components/ # Example components
|
|
142
|
+
├── guidelines/ # Copied from repository
|
|
143
|
+
│ ├── Guidelines.md
|
|
144
|
+
│ └── ...
|
|
145
|
+
├── package.json # Lists @discourser/design-system
|
|
146
|
+
├── node_modules/ # Installed packages
|
|
147
|
+
└── vite.config.ts
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
**Lives:** Figma's cloud (figma.com)
|
|
151
|
+
**Accessed:** Via Figma's Resources panel
|
|
152
|
+
|
|
153
|
+
## The User Journey
|
|
154
|
+
|
|
155
|
+
### Without a Template
|
|
156
|
+
1. User creates new Figma Make file
|
|
157
|
+
2. User installs package: `npm install @discourser/design-system`
|
|
158
|
+
3. User manually copies all guidelines files
|
|
159
|
+
4. User creates starter code from scratch
|
|
160
|
+
5. User configures build settings
|
|
161
|
+
6. **Total time:** 1-2 hours of setup
|
|
162
|
+
|
|
163
|
+
### With a Template
|
|
164
|
+
1. User clicks "Use template" in Resources
|
|
165
|
+
2. New file created with everything pre-configured
|
|
166
|
+
3. User can immediately start building
|
|
167
|
+
4. **Total time:** 0 minutes of setup
|
|
168
|
+
|
|
169
|
+
## Key Concepts
|
|
170
|
+
|
|
171
|
+
### Template Publishing
|
|
172
|
+
- Templates are created **inside Figma Make**
|
|
173
|
+
- Templates are published **from Figma Make** to your team/organization
|
|
174
|
+
- Templates **cannot be created outside** Figma Make and imported
|
|
175
|
+
|
|
176
|
+
### Template Scope
|
|
177
|
+
- **Team template:** Available to specific Figma team
|
|
178
|
+
- **Organization template:** Available to entire organization
|
|
179
|
+
- **Public template:** Not available for Make (unlike Figma Community designs)
|
|
180
|
+
|
|
181
|
+
### Template Independence
|
|
182
|
+
- Each user gets their **own copy** of the template
|
|
183
|
+
- Changes to the template **don't affect** existing copies
|
|
184
|
+
- Users can modify their copy however they want
|
|
185
|
+
|
|
186
|
+
### Template Updates
|
|
187
|
+
- You can **update** published templates
|
|
188
|
+
- Updates **don't affect** users who already used the template
|
|
189
|
+
- Users must **create a new file** from the updated template
|
|
190
|
+
|
|
191
|
+
## Why Create a Template?
|
|
192
|
+
|
|
193
|
+
### For Users
|
|
194
|
+
✅ Zero setup time
|
|
195
|
+
✅ Everything pre-configured
|
|
196
|
+
✅ Clear examples to learn from
|
|
197
|
+
✅ Best practices built-in
|
|
198
|
+
✅ Consistent starting point
|
|
199
|
+
|
|
200
|
+
### For Your Team
|
|
201
|
+
✅ Consistency across projects
|
|
202
|
+
✅ Reduced onboarding time
|
|
203
|
+
✅ Design system adoption
|
|
204
|
+
✅ Quality control
|
|
205
|
+
✅ Faster prototyping
|
|
206
|
+
|
|
207
|
+
### For Figma Make AI
|
|
208
|
+
✅ Immediate access to guidelines
|
|
209
|
+
✅ Better code generation
|
|
210
|
+
✅ Proper component usage
|
|
211
|
+
✅ Adherence to design patterns
|
|
212
|
+
✅ Accessibility compliance
|
|
213
|
+
|
|
214
|
+
## What You Cannot Do
|
|
215
|
+
|
|
216
|
+
❌ **Create a template outside Figma Make**
|
|
217
|
+
Templates must be created inside the Figma Make interface.
|
|
218
|
+
|
|
219
|
+
❌ **Include templates in the npm package**
|
|
220
|
+
The npm package contains components, not templates.
|
|
221
|
+
|
|
222
|
+
❌ **Auto-install templates when package is installed**
|
|
223
|
+
Templates must be manually selected/used.
|
|
224
|
+
|
|
225
|
+
❌ **Update user's existing files**
|
|
226
|
+
Once a user creates a file from a template, it's independent.
|
|
227
|
+
|
|
228
|
+
❌ **Publish templates to npm**
|
|
229
|
+
Templates are published within Figma's ecosystem only.
|
|
230
|
+
|
|
231
|
+
## What's Next?
|
|
232
|
+
|
|
233
|
+
Now that you understand what templates are and how they work, let's check if you have everything needed to create one.
|
|
234
|
+
|
|
235
|
+
**Next:** [Prerequisites](./02-prerequisites.md) →
|
|
@@ -0,0 +1,266 @@
|
|
|
1
|
+
# Prerequisites
|
|
2
|
+
|
|
3
|
+
Before creating a Figma Make template, ensure you have the necessary access, tools, and prepared materials.
|
|
4
|
+
|
|
5
|
+
## Required: Figma Account Access
|
|
6
|
+
|
|
7
|
+
### Account Type Requirements
|
|
8
|
+
|
|
9
|
+
✅ **Required:**
|
|
10
|
+
- Figma account with a **Full seat** on a **paid plan**
|
|
11
|
+
- Cannot be an "Editor" or "Viewer" seat
|
|
12
|
+
- Cannot be on a free plan
|
|
13
|
+
|
|
14
|
+
❌ **Not Supported:**
|
|
15
|
+
- Free Figma accounts
|
|
16
|
+
- Viewer-only seats
|
|
17
|
+
- Editor seats (unless on certain plans)
|
|
18
|
+
|
|
19
|
+
### How to Check Your Access
|
|
20
|
+
|
|
21
|
+
1. Go to https://figma.com
|
|
22
|
+
2. Click on your profile (bottom-left)
|
|
23
|
+
3. Go to **Settings** → **Account**
|
|
24
|
+
4. Check your plan type
|
|
25
|
+
|
|
26
|
+
### Need Access?
|
|
27
|
+
|
|
28
|
+
If you don't have the required access:
|
|
29
|
+
- Contact your team admin to upgrade your seat
|
|
30
|
+
- Upgrade your plan to a paid tier
|
|
31
|
+
- Request Full seat access from your organization
|
|
32
|
+
|
|
33
|
+
## Required: Published npm Package
|
|
34
|
+
|
|
35
|
+
✅ **Completed in Phase 6:**
|
|
36
|
+
The `@discourser/design-system` package must be published to npm.
|
|
37
|
+
|
|
38
|
+
**Verify it's published:**
|
|
39
|
+
```bash
|
|
40
|
+
npm view @discourser/design-system
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
**Expected output:**
|
|
44
|
+
```
|
|
45
|
+
@discourser/design-system@0.1.7
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
If not published:
|
|
49
|
+
- Review Phase 6 documentation
|
|
50
|
+
- Run: `pnpm build && pnpm changeset publish`
|
|
51
|
+
|
|
52
|
+
## Required: Complete Guidelines
|
|
53
|
+
|
|
54
|
+
✅ **Completed in Phase 7:**
|
|
55
|
+
All guideline markdown files must be ready.
|
|
56
|
+
|
|
57
|
+
**Verify guidelines exist:**
|
|
58
|
+
```bash
|
|
59
|
+
ls -R guidelines/
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
**Expected structure:**
|
|
63
|
+
```
|
|
64
|
+
guidelines/
|
|
65
|
+
├── Guidelines.md
|
|
66
|
+
├── overview-components.md
|
|
67
|
+
├── design-tokens/
|
|
68
|
+
│ ├── colors.md
|
|
69
|
+
│ ├── typography.md
|
|
70
|
+
│ ├── spacing.md
|
|
71
|
+
│ └── elevation.md
|
|
72
|
+
└── components/
|
|
73
|
+
├── button.md
|
|
74
|
+
├── card.md
|
|
75
|
+
├── dialog.md
|
|
76
|
+
├── icon-button.md
|
|
77
|
+
├── input.md
|
|
78
|
+
└── switch.md
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
If guidelines are missing:
|
|
82
|
+
- Review Phase 7 documentation
|
|
83
|
+
- Ensure all files are in the `/guidelines` folder
|
|
84
|
+
|
|
85
|
+
## Required: Example/Starter Code
|
|
86
|
+
|
|
87
|
+
⚠️ **To Be Created:**
|
|
88
|
+
You'll need example components to showcase the design system.
|
|
89
|
+
|
|
90
|
+
**What to prepare:**
|
|
91
|
+
- Example login form
|
|
92
|
+
- Example dashboard layout
|
|
93
|
+
- Example component showcase
|
|
94
|
+
- Example card grid
|
|
95
|
+
|
|
96
|
+
**We'll create these in:** [Example Starter Code](./05-example-starter-code.md)
|
|
97
|
+
|
|
98
|
+
## Optional but Recommended
|
|
99
|
+
|
|
100
|
+
### Team/Organization Setup
|
|
101
|
+
|
|
102
|
+
**Recommended:**
|
|
103
|
+
- Have team or organization set up in Figma
|
|
104
|
+
- Know who should have access to the template
|
|
105
|
+
- Determine if template should be team-wide or org-wide
|
|
106
|
+
|
|
107
|
+
### Communication Plan
|
|
108
|
+
|
|
109
|
+
**Recommended:**
|
|
110
|
+
- Prepare announcement for template launch
|
|
111
|
+
- Create internal documentation/tutorial
|
|
112
|
+
- Plan training session if needed
|
|
113
|
+
|
|
114
|
+
### Testing Plan
|
|
115
|
+
|
|
116
|
+
**Recommended:**
|
|
117
|
+
- Identify beta testers for the template
|
|
118
|
+
- Create feedback collection process
|
|
119
|
+
- Plan iteration based on feedback
|
|
120
|
+
|
|
121
|
+
## Tools and Environment
|
|
122
|
+
|
|
123
|
+
### Browser Requirements
|
|
124
|
+
|
|
125
|
+
✅ **Supported Browsers:**
|
|
126
|
+
- Google Chrome (recommended)
|
|
127
|
+
- Microsoft Edge
|
|
128
|
+
- Safari
|
|
129
|
+
- Firefox
|
|
130
|
+
|
|
131
|
+
✅ **Recommended:**
|
|
132
|
+
- Latest browser version
|
|
133
|
+
- Stable internet connection
|
|
134
|
+
- Screen resolution: 1280x720 minimum
|
|
135
|
+
|
|
136
|
+
### Local Development Environment
|
|
137
|
+
|
|
138
|
+
While not strictly required for creating the template, having a local development environment helps with:
|
|
139
|
+
- Testing components before adding to template
|
|
140
|
+
- Verifying package installation works
|
|
141
|
+
- Creating and testing example code
|
|
142
|
+
|
|
143
|
+
**Recommended setup:**
|
|
144
|
+
```bash
|
|
145
|
+
# Node.js version
|
|
146
|
+
node --version # Should be v18 or higher
|
|
147
|
+
|
|
148
|
+
# Package manager
|
|
149
|
+
pnpm --version # Or npm/yarn
|
|
150
|
+
|
|
151
|
+
# Code editor
|
|
152
|
+
code --version # VS Code recommended
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
## Knowledge Requirements
|
|
156
|
+
|
|
157
|
+
### Must Know
|
|
158
|
+
- ✅ Basic React concepts (components, props, JSX)
|
|
159
|
+
- ✅ How to use npm packages
|
|
160
|
+
- ✅ Basic Markdown formatting
|
|
161
|
+
- ✅ How to navigate Figma interface
|
|
162
|
+
|
|
163
|
+
### Helpful to Know
|
|
164
|
+
- TypeScript basics
|
|
165
|
+
- Vite build tool
|
|
166
|
+
- Panda CSS (if customizing styles)
|
|
167
|
+
- Git/GitHub (for version control)
|
|
168
|
+
|
|
169
|
+
### Don't Need to Know
|
|
170
|
+
- ❌ How to build a design system from scratch
|
|
171
|
+
- ❌ Advanced React patterns
|
|
172
|
+
- ❌ Complex build configurations
|
|
173
|
+
- ❌ AI/LLM internals
|
|
174
|
+
|
|
175
|
+
## Pre-Creation Checklist
|
|
176
|
+
|
|
177
|
+
Before starting template creation, verify:
|
|
178
|
+
|
|
179
|
+
### Access
|
|
180
|
+
- [ ] Figma account with Full seat on paid plan
|
|
181
|
+
- [ ] Ability to create Figma Make files
|
|
182
|
+
- [ ] Permissions to publish templates to team/org
|
|
183
|
+
|
|
184
|
+
### Materials
|
|
185
|
+
- [ ] `@discourser/design-system` published to npm
|
|
186
|
+
- [ ] All guidelines files completed and reviewed
|
|
187
|
+
- [ ] Example code prepared (or ready to create)
|
|
188
|
+
- [ ] Documentation reviewed
|
|
189
|
+
|
|
190
|
+
### Planning
|
|
191
|
+
- [ ] Decided on template scope (team or organization)
|
|
192
|
+
- [ ] Chosen template name: e.g., "Discourser Design System Starter"
|
|
193
|
+
- [ ] Written template description
|
|
194
|
+
- [ ] Identified target users
|
|
195
|
+
|
|
196
|
+
### Time
|
|
197
|
+
- [ ] Allocated 2-3 hours for initial creation
|
|
198
|
+
- [ ] Additional 30-60 minutes for testing
|
|
199
|
+
- [ ] Time for iterations based on feedback
|
|
200
|
+
|
|
201
|
+
## Verification Commands
|
|
202
|
+
|
|
203
|
+
Run these commands to verify your setup:
|
|
204
|
+
|
|
205
|
+
```bash
|
|
206
|
+
# Check npm package is published
|
|
207
|
+
npm view @discourser/design-system
|
|
208
|
+
|
|
209
|
+
# Verify guidelines exist
|
|
210
|
+
ls -R guidelines/
|
|
211
|
+
|
|
212
|
+
# Check you can install the package locally
|
|
213
|
+
cd /tmp && mkdir test-install && cd test-install
|
|
214
|
+
npm init -y
|
|
215
|
+
npm install @discourser/design-system
|
|
216
|
+
cd - && rm -rf /tmp/test-install
|
|
217
|
+
|
|
218
|
+
# Verify package contents
|
|
219
|
+
npm pack @discourser/design-system
|
|
220
|
+
tar -tzf discourser-design-system-*.tgz
|
|
221
|
+
rm discourser-design-system-*.tgz
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
All commands should complete without errors.
|
|
225
|
+
|
|
226
|
+
## Common Issues
|
|
227
|
+
|
|
228
|
+
### "I don't have Figma Make access"
|
|
229
|
+
|
|
230
|
+
**Solution:**
|
|
231
|
+
- Figma Make requires a paid plan
|
|
232
|
+
- Contact your workspace admin
|
|
233
|
+
- Upgrade your Figma plan if needed
|
|
234
|
+
- Request Full seat access
|
|
235
|
+
|
|
236
|
+
### "Package not found on npm"
|
|
237
|
+
|
|
238
|
+
**Solution:**
|
|
239
|
+
- Verify package is published: `npm view @discourser/design-system`
|
|
240
|
+
- Check package name spelling
|
|
241
|
+
- Ensure you completed Phase 6 (publishing)
|
|
242
|
+
- Verify you have npm access
|
|
243
|
+
|
|
244
|
+
### "Guidelines folder is empty"
|
|
245
|
+
|
|
246
|
+
**Solution:**
|
|
247
|
+
- Verify you completed Phase 7
|
|
248
|
+
- Check the `/guidelines` directory in your repository
|
|
249
|
+
- Ensure all markdown files were created
|
|
250
|
+
- Review Phase 7 documentation
|
|
251
|
+
|
|
252
|
+
### "Can't create Figma Make file"
|
|
253
|
+
|
|
254
|
+
**Solution:**
|
|
255
|
+
- Verify you have Full seat (not Viewer/Editor)
|
|
256
|
+
- Check your Figma plan type
|
|
257
|
+
- Try accessing https://figma.com/make directly
|
|
258
|
+
- Contact Figma support if issues persist
|
|
259
|
+
|
|
260
|
+
## What's Next?
|
|
261
|
+
|
|
262
|
+
Once you've verified all prerequisites are met, you're ready to create your template!
|
|
263
|
+
|
|
264
|
+
**Next:** [Creating Your Template File](./03-creating-template.md) →
|
|
265
|
+
|
|
266
|
+
**Previous:** [Understanding Templates](./01-understanding-templates.md) ←
|