@techwavedev/agi-agent-kit 1.1.3 → 1.1.5

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/CHANGELOG.md CHANGED
@@ -5,6 +5,19 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [1.1.5] - 2026-01-27
9
+
10
+ ### Added
11
+
12
+ - **Stitch Skills Suite**: Added three new skills from Google Stitch:
13
+ - `design-md`: Analyzes Stitch projects to synthesize semantic `DESIGN.md` systems.
14
+ - `react-components`: Converts Stitch screens into modular, validating React components.
15
+ - `stitch-loop`: Orchestrates autonomous iterative website building loops.
16
+ - **Memory Integration**: Integrated `qdrant-memory` into the Stitch skills suite for:
17
+ - Storing design systems for future retrieval (`design-md`).
18
+ - Retrieving code patterns and interfaces (`react-components`).
19
+ - Leveraging past decisions and project context (`stitch-loop`).
20
+
8
21
  ## [1.1.2] - 2026-01-23
9
22
 
10
23
  ### Added
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to the Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2024-2026 Elton Machado (TechWaveDev)
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@techwavedev/agi-agent-kit",
3
- "version": "1.1.3",
3
+ "version": "1.1.5",
4
4
  "description": "Enterprise-Grade Agentic Framework - Modular skill-based AI assistant toolkit with deterministic execution and semantic memory.",
5
5
  "bin": {
6
6
  "agi-agent-kit": "./bin/init.js"
@@ -0,0 +1,34 @@
1
+ # Stitch Design System Documentation Skill
2
+
3
+ ## Install
4
+
5
+ ```bash
6
+ npx add-skill google-labs-code/stitch-skills --skill design-md --global
7
+ ```
8
+
9
+ ## Example Prompt
10
+
11
+ ```text
12
+ Analyze my Furniture Collection project's Home screen and generate a comprehensive DESIGN.md file documenting the design system.
13
+ ```
14
+
15
+ ## Skill Structure
16
+
17
+ This repository follows the **Agent Skills** open standard. Each skill is self-contained with its own logic, workflow, and reference materials.
18
+
19
+ ```text
20
+ design-md/
21
+ ├── SKILL.md — Core instructions & workflow
22
+ ├── examples/ — Sample DESIGN.md outputs
23
+ └── README.md — This file
24
+ ```
25
+
26
+ ## How it Works
27
+
28
+ When activated, the agent follows a structured design analysis pipeline:
29
+
30
+ 1. **Retrieval**: Uses the Stitch MCP Server to fetch project screens, HTML code, and design metadata.
31
+ 2. **Extraction**: Identifies design tokens including colors, typography, spacing, and component patterns.
32
+ 3. **Translation**: Converts technical CSS/Tailwind values into descriptive, natural design language.
33
+ 4. **Synthesis**: Generates a comprehensive DESIGN.md following the semantic design system format.
34
+ 5. **Alignment**: Ensures output follows Stitch Effective Prompting Guide principles for optimal screen generation.
@@ -0,0 +1,193 @@
1
+ ---
2
+ name: design-md
3
+ description: Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
4
+ allowed-tools:
5
+ - "stitch*:*"
6
+ - "Read"
7
+ - "Write"
8
+ - "web_fetch"
9
+ - "qdrant-memory"
10
+ ---
11
+
12
+ # Stitch DESIGN.md Skill
13
+
14
+ You are an expert Design Systems Lead. Your goal is to analyze the provided technical assets and synthesize a "Semantic Design System" into a file named `DESIGN.md`.
15
+
16
+ ## Overview
17
+
18
+ This skill helps you create `DESIGN.md` files that serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
19
+
20
+ ## Prerequisites
21
+
22
+ - Access to the Stitch MCP Server
23
+ - A Stitch project with at least one designed screen
24
+ - Access to the Stitch Effective Prompting Guide: https://stitch.withgoogle.com/docs/learn/prompting/
25
+ - (Optional) Qdrant Memory Skill for storing the design system
26
+
27
+ ## The Goal
28
+
29
+ The `DESIGN.md` file will serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with the existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
30
+
31
+ ## Retrieval and Networking
32
+
33
+ To analyze a Stitch project, you must retrieve screen metadata and design assets using the Stitch MCP Server tools:
34
+
35
+ 1. **Namespace discovery**: Run `list_tools` to find the Stitch MCP prefix. Use this prefix (e.g., `mcp_stitch:`) for all subsequent calls.
36
+
37
+ 2. **Project lookup** (if Project ID is not provided):
38
+ - Call `[prefix]:list_projects` with `filter: "view=owned"` to retrieve all user projects
39
+ - Identify the target project by title or URL pattern
40
+ - Extract the Project ID from the `name` field (e.g., `projects/13534454087919359824`)
41
+
42
+ 3. **Screen lookup** (if Screen ID is not provided):
43
+ - Call `[prefix]:list_screens` with the `projectId` (just the numeric ID, not the full path)
44
+ - Review screen titles to identify the target screen (e.g., "Home", "Landing Page")
45
+ - Extract the Screen ID from the screen's `name` field
46
+
47
+ 4. **Metadata fetch**:
48
+ - Call `[prefix]:get_screen` with both `projectId` and `screenId` (both as numeric IDs only)
49
+ - This returns the complete screen object including:
50
+ - `screenshot.downloadUrl` - Visual reference of the design
51
+ - `htmlCode.downloadUrl` - Full HTML/CSS source code
52
+ - `width`, `height`, `deviceType` - Screen dimensions and target platform
53
+ - Project metadata including `designTheme` with color and style information
54
+
55
+ 5. **Asset download**:
56
+ - Use `web_fetch` or `read_url_content` to download the HTML code from `htmlCode.downloadUrl`
57
+ - Optionally download the screenshot from `screenshot.downloadUrl` for visual reference
58
+ - Parse the HTML to extract Tailwind classes, custom CSS, and component patterns
59
+
60
+ 6. **Project metadata extraction**:
61
+ - Call `[prefix]:get_project` with the project `name` (full path: `projects/{id}`) to get:
62
+ - `designTheme` object with color mode, fonts, roundness, custom colors
63
+ - Project-level design guidelines and descriptions
64
+ - Device type preferences and layout principles
65
+
66
+ ## Analysis & Synthesis Instructions
67
+
68
+ ### 1. Extract Project Identity (JSON)
69
+
70
+ - Locate the Project Title
71
+ - Locate the specific Project ID (e.g., from the `name` field in the JSON)
72
+
73
+ ### 2. Define the Atmosphere (Image/HTML)
74
+
75
+ Evaluate the screenshot and HTML structure to capture the overall "vibe." Use evocative adjectives to describe the mood (e.g., "Airy," "Dense," "Minimalist," "Utilitarian").
76
+
77
+ ### 3. Map the Color Palette (Tailwind Config/JSON)
78
+
79
+ Identify the key colors in the system. For each color, provide:
80
+
81
+ - A descriptive, natural language name that conveys its character (e.g., "Deep Muted Teal-Navy")
82
+ - The specific hex code in parentheses for precision (e.g., "#294056")
83
+ - Its specific functional role (e.g., "Used for primary actions")
84
+
85
+ ### 4. Translate Geometry & Shape (CSS/Tailwind)
86
+
87
+ Convert technical `border-radius` and layout values into physical descriptions:
88
+
89
+ - Describe `rounded-full` as "Pill-shaped"
90
+ - Describe `rounded-lg` as "Subtly rounded corners"
91
+ - Describe `rounded-none` as "Sharp, squared-off edges"
92
+
93
+ ### 5. Describe Depth & Elevation
94
+
95
+ Explain how the UI handles layers. Describe the presence and quality of shadows (e.g., "Flat," "Whisper-soft diffused shadows," or "Heavy, high-contrast drop shadows").
96
+
97
+ ## Output Guidelines
98
+
99
+ - **Language:** Use descriptive design terminology and natural language exclusively
100
+ - **Format:** Generate a clean Markdown file following the structure below
101
+ - **Precision:** Include exact hex codes for colors while using descriptive names
102
+ - **Context:** Explain the "why" behind design decisions, not just the "what"
103
+
104
+ ## Output Format (DESIGN.md Structure)
105
+
106
+ ```markdown
107
+ # Design System: [Project Title]
108
+
109
+ **Project ID:** [Insert Project ID Here]
110
+
111
+ ## 1. Visual Theme & Atmosphere
112
+
113
+ (Description of the mood, density, and aesthetic philosophy.)
114
+
115
+ ## 2. Color Palette & Roles
116
+
117
+ (List colors by Descriptive Name + Hex Code + Functional Role.)
118
+
119
+ ## 3. Typography Rules
120
+
121
+ (Description of font family, weight usage for headers vs. body, and letter-spacing character.)
122
+
123
+ ## 4. Component Stylings
124
+
125
+ - **Buttons:** (Shape description, color assignment, behavior).
126
+ - **Cards/Containers:** (Corner roundness description, background color, shadow depth).
127
+ - **Inputs/Forms:** (Stroke style, background).
128
+
129
+ ## 5. Layout Principles
130
+
131
+ (Description of whitespace strategy, margins, and grid alignment.)
132
+ ```
133
+
134
+ ## Usage Example
135
+
136
+ To use this skill for the Furniture Collection project:
137
+
138
+ 1. **Retrieve project information:**
139
+
140
+ ```
141
+ Use the Stitch MCP Server to get the Furniture Collection project
142
+ ```
143
+
144
+ 2. **Get the Home page screen details:**
145
+
146
+ ```
147
+ Retrieve the Home page screen's code, image, and screen object information
148
+ ```
149
+
150
+ 3. **Reference best practices:**
151
+
152
+ ```
153
+ Review the Stitch Effective Prompting Guide at:
154
+ https://stitch.withgoogle.com/docs/learn/prompting/
155
+ ```
156
+
157
+ 4. **Analyze and synthesize:**
158
+ - Extract all relevant design tokens from the screen
159
+ - Translate technical values into descriptive language
160
+ - Organize information according to the DESIGN.md structure
161
+
162
+ 5. **Generate the file:**
163
+ - Create `DESIGN.md` in the project directory
164
+ - Follow the prescribed format exactly
165
+ - Ensure all color codes are accurate
166
+ - Use evocative, designer-friendly language
167
+
168
+ 6. **Store in Memory (Optional):**
169
+ - If **Qdrant Memory Skill** is active, store the design system summary for future retrieval.
170
+
171
+ ## Best Practices
172
+
173
+ - **Be Descriptive:** Avoid generic terms like "blue" or "rounded." Use "Ocean-deep Cerulean (#0077B6)" or "Gently curved edges"
174
+ - **Be Functional:** Always explain what each design element is used for
175
+ - **Be Consistent:** Use the same terminology throughout the document
176
+ - **Be Visual:** Help readers visualize the design through your descriptions
177
+ - **Be Precise:** Include exact values (hex codes, pixel values) in parentheses after natural language descriptions
178
+
179
+ ## Tips for Success
180
+
181
+ 1. **Start with the big picture:** Understand the overall aesthetic before diving into details
182
+ 2. **Look for patterns:** Identify consistent spacing, sizing, and styling patterns
183
+ 3. **Think semantically:** Name colors by their purpose, not just their appearance
184
+ 4. **Consider hierarchy:** Document how visual weight and importance are communicated
185
+ 5. **Reference the guide:** Use language and patterns from the Stitch Effective Prompting Guide
186
+
187
+ ## Common Pitfalls to Avoid
188
+
189
+ - ❌ Using technical jargon without translation (e.g., "rounded-xl" instead of "generously rounded corners")
190
+ - ❌ Omitting color codes or using only descriptive names
191
+ - ❌ Forgetting to explain functional roles of design elements
192
+ - ❌ Being too vague in atmosphere descriptions
193
+ - ❌ Ignoring subtle design details like shadows or spacing patterns
@@ -0,0 +1,154 @@
1
+ # Design System: Furniture Collections List
2
+ **Project ID:** 13534454087919359824
3
+
4
+ ## 1. Visual Theme & Atmosphere
5
+
6
+ The Furniture Collections List embodies a **sophisticated, minimalist sanctuary** that marries the pristine simplicity of Scandinavian design with the refined visual language of luxury editorial presentation. The interface feels **spacious and tranquil**, prioritizing breathing room and visual clarity above all else. The design philosophy is gallery-like and photography-first, allowing each furniture piece to command attention as an individual art object.
7
+
8
+ The overall mood is **airy yet grounded**, creating an aspirational aesthetic that remains approachable and welcoming. The interface feels **utilitarian in its restraint** but elegant in its execution, with every element serving a clear purpose while maintaining visual sophistication. The atmosphere evokes the serene ambiance of a high-end furniture showroom where customers can browse thoughtfully without visual overwhelm.
9
+
10
+ **Key Characteristics:**
11
+ - Expansive whitespace creating generous breathing room between elements
12
+ - Clean, architectural grid system with structured content blocks
13
+ - Photography-first presentation with minimal UI interference
14
+ - Whisper-soft visual hierarchy that guides without shouting
15
+ - Refined, understated interactive elements
16
+ - Professional yet inviting editorial tone
17
+
18
+ ## 2. Color Palette & Roles
19
+
20
+ ### Primary Foundation
21
+ - **Warm Barely-There Cream** (#FCFAFA) – Primary background color. Creates an almost imperceptible warmth that feels more inviting than pure white, serving as the serene canvas for the entire experience.
22
+ - **Crisp Very Light Gray** (#F5F5F5) – Secondary surface color used for card backgrounds and content areas. Provides subtle visual separation while maintaining the airy, ethereal quality.
23
+
24
+ ### Accent & Interactive
25
+ - **Deep Muted Teal-Navy** (#294056) – The sole vibrant accent in the palette. Used exclusively for primary call-to-action buttons (e.g., "Shop Now", "View all products"), active navigation links, selected filter states, and subtle interaction highlights. This sophisticated anchor color creates visual focus points without disrupting the serene neutral foundation.
26
+
27
+ ### Typography & Text Hierarchy
28
+ - **Charcoal Near-Black** (#2C2C2C) – Primary text color for headlines and product names. Provides strong readable contrast while being softer and more refined than pure black.
29
+ - **Soft Warm Gray** (#6B6B6B) – Secondary text used for body copy, product descriptions, and supporting metadata. Creates clear typographic hierarchy without harsh contrast.
30
+ - **Ultra-Soft Silver Gray** (#E0E0E0) – Tertiary color for borders, dividers, and subtle structural elements. Creates separation so gentle it's almost imperceptible.
31
+
32
+ ### Functional States (Reserved for system feedback)
33
+ - **Success Moss** (#10B981) – Stock availability, confirmation states, positive indicators
34
+ - **Alert Terracotta** (#EF4444) – Low stock warnings, error states, critical alerts
35
+ - **Informational Slate** (#64748B) – Neutral system messages, informational callouts
36
+
37
+ ## 3. Typography Rules
38
+
39
+ **Primary Font Family:** Manrope
40
+ **Character:** Modern, geometric sans-serif with gentle humanist warmth. Slightly rounded letterforms that feel contemporary yet approachable.
41
+
42
+ ### Hierarchy & Weights
43
+ - **Display Headlines (H1):** Semi-bold weight (600), generous letter-spacing (0.02em for elegance), 2.75-3.5rem size. Used sparingly for hero sections and major page titles.
44
+ - **Section Headers (H2):** Semi-bold weight (600), subtle letter-spacing (0.01em), 2-2.5rem size. Establishes clear content zones and featured collections.
45
+ - **Subsection Headers (H3):** Medium weight (500), normal letter-spacing, 1.5-1.75rem size. Product names and category labels.
46
+ - **Body Text:** Regular weight (400), relaxed line-height (1.7), 1rem size. Descriptions and supporting content prioritize comfortable readability.
47
+ - **Small Text/Meta:** Regular weight (400), slightly tighter line-height (1.5), 0.875rem size. Prices, availability, and metadata remain legible but visually recessive.
48
+ - **CTA Buttons:** Medium weight (500), subtle letter-spacing (0.01em), 1rem size. Balanced presence without visual aggression.
49
+
50
+ ### Spacing Principles
51
+ - Headers use slightly expanded letter-spacing for refined elegance
52
+ - Body text maintains generous line-height (1.7) for effortless reading
53
+ - Consistent vertical rhythm with 2-3rem between related text blocks
54
+ - Large margins (4-6rem) between major sections to reinforce spaciousness
55
+
56
+ ## 4. Component Stylings
57
+
58
+ ### Buttons
59
+ - **Shape:** Subtly rounded corners (8px/0.5rem radius) – approachable and modern without appearing playful or childish
60
+ - **Primary CTA:** Deep Muted Teal-Navy (#294056) background with pure white text, comfortable padding (0.875rem vertical, 2rem horizontal)
61
+ - **Hover State:** Subtle darkening to deeper navy, smooth 250ms ease-in-out transition
62
+ - **Focus State:** Soft outer glow in the primary color for keyboard navigation accessibility
63
+ - **Secondary CTA (if needed):** Outlined style with Deep Muted Teal-Navy border, transparent background, hover fills with whisper-soft teal tint
64
+
65
+ ### Cards & Product Containers
66
+ - **Corner Style:** Gently rounded corners (12px/0.75rem radius) creating soft, refined edges
67
+ - **Background:** Alternates between Warm Barely-There Cream and Crisp Very Light Gray based on layering needs
68
+ - **Shadow Strategy:** Flat by default. On hover, whisper-soft diffused shadow appears (`0 2px 8px rgba(0,0,0,0.06)`) creating subtle depth
69
+ - **Border:** Optional hairline border (1px) in Ultra-Soft Silver Gray for delicate definition when shadows aren't present
70
+ - **Internal Padding:** Generous 2-2.5rem creating comfortable breathing room for content
71
+ - **Image Treatment:** Full-bleed at the top of cards, square or 4:3 ratio, seamless edge-to-edge presentation
72
+
73
+ ### Navigation
74
+ - **Style:** Clean horizontal layout with generous spacing (2-3rem) between menu items
75
+ - **Typography:** Medium weight (500), subtle uppercase, expanded letter-spacing (0.06em) for refined sophistication
76
+ - **Default State:** Charcoal Near-Black text
77
+ - **Active/Hover State:** Smooth 200ms color transition to Deep Muted Teal-Navy
78
+ - **Active Indicator:** Thin underline (2px) in Deep Muted Teal-Navy appearing below current section
79
+ - **Mobile:** Converts to elegant hamburger menu with sliding drawer
80
+
81
+ ### Inputs & Forms
82
+ - **Stroke Style:** Refined 1px border in Soft Warm Gray
83
+ - **Background:** Warm Barely-There Cream with transition to Crisp Very Light Gray on focus
84
+ - **Corner Style:** Matching button roundness (8px/0.5rem) for visual consistency
85
+ - **Focus State:** Border color shifts to Deep Muted Teal-Navy with subtle outer glow
86
+ - **Padding:** Comfortable 0.875rem vertical, 1.25rem horizontal for touch-friendly targets
87
+ - **Placeholder Text:** Ultra-Soft Silver Gray, elegant and unobtrusive
88
+
89
+ ### Product Cards (Specific Pattern)
90
+ - **Image Area:** Square (1:1) or landscape (4:3) ratio filling card width completely
91
+ - **Content Stack:** Product name (H3), brief descriptor, material/finish, price
92
+ - **Price Display:** Emphasized with semi-bold weight (600) in Charcoal Near-Black
93
+ - **Hover Behavior:** Gentle lift effect (translateY -4px) combined with enhanced shadow
94
+ - **Spacing:** Consistent 1.5rem internal padding below image
95
+
96
+ ## 5. Layout Principles
97
+
98
+ ### Grid & Structure
99
+ - **Max Content Width:** 1440px for optimal readability and visual balance on large displays
100
+ - **Grid System:** Responsive 12-column grid with fluid gutters (24px mobile, 32px desktop)
101
+ - **Product Grid:** 4 columns on large desktop, 3 on desktop, 2 on tablet, 1 on mobile
102
+ - **Breakpoints:**
103
+ - Mobile: <768px
104
+ - Tablet: 768-1024px
105
+ - Desktop: 1024-1440px
106
+ - Large Desktop: >1440px
107
+
108
+ ### Whitespace Strategy (Critical to the Design)
109
+ - **Base Unit:** 8px for micro-spacing, 16px for component spacing
110
+ - **Vertical Rhythm:** Consistent 2rem (32px) base unit between related elements
111
+ - **Section Margins:** Generous 5-8rem (80-128px) between major sections creating dramatic breathing room
112
+ - **Edge Padding:** 1.5rem (24px) mobile, 3rem (48px) tablet/desktop for comfortable framing
113
+ - **Hero Sections:** Extra-generous top/bottom padding (8-12rem) for impactful presentation
114
+
115
+ ### Alignment & Visual Balance
116
+ - **Text Alignment:** Left-aligned for body and navigation (optimal readability), centered for hero headlines and featured content
117
+ - **Image to Text Ratio:** Heavily weighted toward imagery (70-30 split) reinforcing photography-first philosophy
118
+ - **Asymmetric Balance:** Large hero images offset by compact, refined text blocks
119
+ - **Visual Weight Distribution:** Strategic use of whitespace to draw eyes to hero products and primary CTAs
120
+ - **Reading Flow:** Clear top-to-bottom, left-to-right pattern with intentional focal points
121
+
122
+ ### Responsive Behavior & Touch
123
+ - **Mobile-First Foundation:** Core experience designed and perfected for smallest screens first
124
+ - **Progressive Enhancement:** Additional columns, imagery, and details added gracefully at larger breakpoints
125
+ - **Touch Targets:** Minimum 44x44px for all interactive elements (WCAG AAA compliant)
126
+ - **Image Optimization:** Responsive images with appropriate resolutions for each breakpoint, lazy-loading for performance
127
+ - **Collapsing Strategy:** Navigation collapses to hamburger, grid reduces columns, padding scales proportionally
128
+
129
+ ## 6. Design System Notes for Stitch Generation
130
+
131
+ When creating new screens for this project using Stitch, reference these specific instructions:
132
+
133
+ ### Language to Use
134
+ - **Atmosphere:** "Sophisticated minimalist sanctuary with gallery-like spaciousness"
135
+ - **Button Shapes:** "Subtly rounded corners" (not "rounded-md" or "8px")
136
+ - **Shadows:** "Whisper-soft diffused shadows on hover" (not "shadow-sm")
137
+ - **Spacing:** "Generous breathing room" and "expansive whitespace"
138
+
139
+ ### Color References
140
+ Always use the descriptive names with hex codes:
141
+ - Primary CTA: "Deep Muted Teal-Navy (#294056)"
142
+ - Backgrounds: "Warm Barely-There Cream (#FCFAFA)" or "Crisp Very Light Gray (#F5F5F5)"
143
+ - Text: "Charcoal Near-Black (#2C2C2C)" or "Soft Warm Gray (#6B6B6B)"
144
+
145
+ ### Component Prompts
146
+ - "Create a product card with gently rounded corners, full-bleed square product image, and whisper-soft shadow on hover"
147
+ - "Design a primary call-to-action button in Deep Muted Teal-Navy (#294056) with subtle rounded corners and comfortable padding"
148
+ - "Add a navigation bar with generous spacing between items, using medium-weight Manrope with subtle uppercase and expanded letter-spacing"
149
+
150
+ ### Incremental Iteration
151
+ When refining existing screens:
152
+ 1. Focus on ONE component at a time (e.g., "Update the product grid cards")
153
+ 2. Be specific about what to change (e.g., "Increase the internal padding of product cards from 1.5rem to 2rem")
154
+ 3. Reference this design system language consistently
@@ -0,0 +1,36 @@
1
+ # Stitch to React Components Skill
2
+
3
+ ## Install
4
+
5
+ ```bash
6
+ npx add-skill google-labs-code/stitch-skills --skill react:components --global
7
+ ```
8
+
9
+ ## Example Prompt
10
+
11
+ ```text
12
+ Convert my Landing Page screen in my Podcast Stitch Project to a React component system.
13
+ ```
14
+
15
+ ## Skill Structure
16
+
17
+ This repository follows the **Agent Skills** open standard. Each skill is self-contained with its own logic, validation scripts, and design tokens.
18
+
19
+ ```text
20
+ skills/react-components/
21
+ ├── SKILL.md — Core instructions & workflow
22
+ ├── package.json — Validator dependencies
23
+ ├── scripts/ — Networking & AST validation
24
+ ├── resources/ — Style guides & API references
25
+ └── examples/ — Gold-standard code samples
26
+ ```
27
+
28
+ ## How it Works
29
+
30
+ When activated, the agent follows a high-fidelity engineering pipeline:
31
+
32
+ 1. **Retrieval**: Uses a system-level `curl` script to bypass TLS/SNI issues on Google Cloud Storage.
33
+ 2. **Mapping**: Cross-references Stitch metadata with the local `style-guide.json` to ensure token consistency.
34
+ 3. **Generation**: Scaffolds components using a strict Atomic Design pattern.
35
+ 4. **Validation**: Runs an automated AST check using `@swc/core` to prevent hardcoded hex values or missing interfaces.
36
+ 5. **Audit**: Performs a final self-correction check against a 20-point architecture checklist.