product-data-import

Name: product-data-import
Author: AlpacaLabsLLC

260stars54forks

How to install product-data-import?

alpacalabsllc/skills-for-architects/product-data-import

$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill product-data-import

Installs into the current project.

Summary

Generate a formatted FF&E specification schedule from raw product data — notes, CSV, or pasted lists — compatible with the 33-column master schema. Use when the user pastes or uploads raw product data and asks to "import products", build a schedule, or get items into the master s

Files · 1

View on GitHub

SKILL.md

1	# /product-data-import — Product Data Importer
2
3	Takes raw, unstructured product data and formats it into a proper FF&E specification schedule. Input can be notes, a CSV, a pasted spreadsheet, or a conversation. Output is a formatted schedule as markdown, CSV, or written to a Google Sheet — using the same 33-column schema as `/product-research`, `/product-spec-bulk-fetch`, and other product skills.
4
5	## When to Use
6
7	- Designer has a list of products in notes or conversation and needs it formatted for a deliverable
8	- A rough product list needs to become a spec-ready schedule with item numbers, quantities, and extended pricing
9	- Products from multiple sources need to be consolidated into one formatted schedule
10	- An existing schedule needs to be reformatted to match the standard schema
11
12	## Step 1: Accept Input
13
14	The designer provides product data in any format:
15
16	Raw notes:
17	```
18	3x Eames Lounge Chair, Herman Miller, walnut/black leather, $5,695 each
19	2x Nelson Platform Bench 48", Herman Miller, natural maple, $2,195
20	1x Noguchi Coffee Table, Herman Miller, walnut/glass, $2,095
21	Pendant light for above the table - something by Flos, budget $800-1200
22	```
23
24	Pasted spreadsheet or CSV:
25	```
26	Product, Brand, Qty, Price
27	Eames Lounge Chair, Herman Miller, 3, $5695
28	Nelson Bench 48, Herman Miller, 2, $2195
29	```
30
31	A file path:
32	```
33	/product-data-import ./product-list.csv
34	```
35
36	Conversational:
37	```
38	"We need 8 task chairs — Steelcase Leap V2, black, about $1,200 each.
39	Also 4 monitor arms, any brand, under $300."
40	```
41
42	Accept whatever the designer gives. Don't ask for more structure — work with what you have.
43
44	## Step 2: Parse and Enrich
45
46	For each product in the input:
47
48	1. Extract known fields: product name, brand, quantity, price, dimensions, materials, finish, category
49	2. Fill in from knowledge: If the product is well-known (Eames Lounge Chair, Steelcase Leap, etc.), fill in standard dimensions, materials, and weight from your training data. Mark these as "from reference" in notes.
50	3. Assign categories: Map to the canonical vocabulary defined in `../../schema/product-schema.md`
51	4. Calculate extended prices: Unit price × quantity
52	5. Assign item numbers: Sequential within each category group (S-01, S-02 for Seating; T-01 for Tables; L-01 for Lighting, etc.)
53	6. Flag unknowns: If a product is vague ("pendant light, Flos, $800-1200"), note it as "TBD — needs specification" and include budget range
54
55	### Category prefixes for item numbers
56
57	Item number prefixes are defined in `../../schema/product-schema.md` under Item Number Prefixes. Read that file for the full mapping of canonical categories to prefixes (e.g. Chair → S, Table → T, Light → L).
58
59	## Step 3: Present the Schedule
60
61	Show the formatted schedule as a markdown table:
62
63	```
64	## FF&E Schedule — [Project Name if known]
65
66	[n] items · [total qty] units · $[total extended] estimated
67
68	\| Item # \| Product \| Brand \| Qty \| W \| D \| H \| Unit \| Materials \| Finish \| Unit $ \| Ext $ \| Lead \| Notes \|
69	\|--------\|---------\|-------\|-----\|---\|---\|---\|------\|-----------\|--------\|--------\|-------\|------\|-------\|
70	\| S-01 \| Eames Lounge Chair \| Herman Miller \| 3 \| 32.75 \| 32.5 \| 33.5 \| in \| Molded plywood, leather \| Walnut/Black \| $5,695 \| $17,085 \| 8-12w \| \|
71	\| T-01 \| Nelson Platform Bench 48" \| Herman Miller \| 2 \| 48 \| 18.5 \| 14 \| in \| Solid maple \| Natural \| $2,195 \| $4,390 \| 6-8w \| \|
72	\| T-02 \| Noguchi Coffee Table \| Herman Miller \| 1 \| 50 \| 36 \| 15.75 \| in \| Walnut, glass \| — \| $2,095 \| $2,095 \| 6-8w \| \|
73	\| L-01 \| TBD Pendant \| Flos \| 1 \| — \| — \| — \| — \| — \| — \| $800-$1,200 \| $800-$1,200 \| — \| Needs specification \|
74
75	Subtotals by category:
76	- Seating: $17,085 (3 units)
77	- Tables: $6,485 (3 units)
78	- Lighting: $800-$1,200 (1 unit, TBD)
79	- Total: $24,370-$24,770
80	```
81
82	### Presentation rules
83
84	- Group by category, sorted by item number within each group
85	- Show subtotals per category and a grand total
86	- Flag TBD items clearly — include budget range if given
87	- Show dimensions from reference data when you know the product; leave blank and note "dims TBD" when you don't
88	- Don't fabricate prices — if you're unsure, note "price TBD" or "estimated" and use the designer's stated budget
89	- Currency — default USD unless the designer specifies otherwise
90
91	## Step 4: Ask for Output Format
92
93	Ask the designer how they want the schedule:
94
95	1. Markdown — stay in conversation (already shown)
96	2. CSV file — save as `.csv` to the current di

People who liked this also viewed

6 picks

Type

product-data-import

260stars54forks

View on GitHub

How to install product-data-import?

alpacalabsllc/skills-for-architects/product-data-import

$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill product-data-import

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /product-data-import — Product Data Importer
2
3	Takes raw, unstructured product data and formats it into a proper FF&E specification schedule. Input can be notes, a CSV, a pasted spreadsheet, or a conversation. Output is a formatted schedule as markdown, CSV, or written to a Google Sheet — using the same 33-column schema as `/product-research`, `/product-spec-bulk-fetch`, and other product skills.
4
5	## When to Use
6
7	- Designer has a list of products in notes or conversation and needs it formatted for a deliverable
8	- A rough product list needs to become a spec-ready schedule with item numbers, quantities, and extended pricing
9	- Products from multiple sources need to be consolidated into one formatted schedule
10	- An existing schedule needs to be reformatted to match the standard schema
11
12	## Step 1: Accept Input
13
14	The designer provides product data in any format:
15
16	Raw notes:
17	```
18	3x Eames Lounge Chair, Herman Miller, walnut/black leather, $5,695 each
19	2x Nelson Platform Bench 48", Herman Miller, natural maple, $2,195
20	1x Noguchi Coffee Table, Herman Miller, walnut/glass, $2,095
21	Pendant light for above the table - something by Flos, budget $800-1200
22	```
23
24	Pasted spreadsheet or CSV:
25	```
26	Product, Brand, Qty, Price
27	Eames Lounge Chair, Herman Miller, 3, $5695
28	Nelson Bench 48, Herman Miller, 2, $2195
29	```
30
31	A file path:
32	```
33	/product-data-import ./product-list.csv
34	```
35
36	Conversational:
37	```
38	"We need 8 task chairs — Steelcase Leap V2, black, about $1,200 each.
39	Also 4 monitor arms, any brand, under $300."
40	```
41
42	Accept whatever the designer gives. Don't ask for more structure — work with what you have.
43
44	## Step 2: Parse and Enrich
45
46	For each product in the input:
47
48	1. Extract known fields: product name, brand, quantity, price, dimensions, materials, finish, category
49	2. Fill in from knowledge: If the product is well-known (Eames Lounge Chair, Steelcase Leap, etc.), fill in standard dimensions, materials, and weight from your training data. Mark these as "from reference" in notes.
50	3. Assign categories: Map to the canonical vocabulary defined in `../../schema/product-schema.md`
51	4. Calculate extended prices: Unit price × quantity
52	5. Assign item numbers: Sequential within each category group (S-01, S-02 for Seating; T-01 for Tables; L-01 for Lighting, etc.)
53	6. Flag unknowns: If a product is vague ("pendant light, Flos, $800-1200"), note it as "TBD — needs specification" and include budget range
54
55	### Category prefixes for item numbers
56
57	Item number prefixes are defined in `../../schema/product-schema.md` under Item Number Prefixes. Read that file for the full mapping of canonical categories to prefixes (e.g. Chair → S, Table → T, Light → L).
58
59	## Step 3: Present the Schedule
60
61	Show the formatted schedule as a markdown table:
62
63	```
64	## FF&E Schedule — [Project Name if known]
65
66	[n] items · [total qty] units · $[total extended] estimated
67
68	\| Item # \| Product \| Brand \| Qty \| W \| D \| H \| Unit \| Materials \| Finish \| Unit $ \| Ext $ \| Lead \| Notes \|
69	\|--------\|---------\|-------\|-----\|---\|---\|---\|------\|-----------\|--------\|--------\|-------\|------\|-------\|
70	\| S-01 \| Eames Lounge Chair \| Herman Miller \| 3 \| 32.75 \| 32.5 \| 33.5 \| in \| Molded plywood, leather \| Walnut/Black \| $5,695 \| $17,085 \| 8-12w \| \|
71	\| T-01 \| Nelson Platform Bench 48" \| Herman Miller \| 2 \| 48 \| 18.5 \| 14 \| in \| Solid maple \| Natural \| $2,195 \| $4,390 \| 6-8w \| \|
72	\| T-02 \| Noguchi Coffee Table \| Herman Miller \| 1 \| 50 \| 36 \| 15.75 \| in \| Walnut, glass \| — \| $2,095 \| $2,095 \| 6-8w \| \|
73	\| L-01 \| TBD Pendant \| Flos \| 1 \| — \| — \| — \| — \| — \| — \| $800-$1,200 \| $800-$1,200 \| — \| Needs specification \|
74
75	Subtotals by category:
76	- Seating: $17,085 (3 units)
77	- Tables: $6,485 (3 units)
78	- Lighting: $800-$1,200 (1 unit, TBD)
79	- Total: $24,370-$24,770
80	```
81
82	### Presentation rules
83
84	- Group by category, sorted by item number within each group
85	- Show subtotals per category and a grand total
86	- Flag TBD items clearly — include budget range if given
87	- Show dimensions from reference data when you know the product; leave blank and note "dims TBD" when you don't
88	- Don't fabricate prices — if you're unsure, note "price TBD" or "estimated" and use the designer's stated budget
89	- Currency — default USD unless the designer specifies otherwise
90
91	## Step 4: Ask for Output Format
92
93	Ask the designer how they want the schedule:
94
95	1. Markdown — stay in conversation (already shown)
96	2. CSV file — save as `.csv` to the current di

People who liked this also viewed

6 picks

Type