@pugi/cli 1.0.0-alpha.216 → 1.0.0-alpha.217
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/models.json +1 -1
- package/package.json +7 -7
- package/skills/landing-templates/SKILL.md +1 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pugi/cli",
|
|
3
|
-
"version": "1.0.0-alpha.
|
|
3
|
+
"version": "1.0.0-alpha.217",
|
|
4
4
|
"description": "Pugi CLI - terminal-native software execution system",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"homepage": "https://pugi.io",
|
|
@@ -40,11 +40,11 @@
|
|
|
40
40
|
"LICENSE"
|
|
41
41
|
],
|
|
42
42
|
"optionalDependencies": {
|
|
43
|
-
"@pugi/cli-darwin-arm64": "1.0.0-alpha.
|
|
44
|
-
"@pugi/cli-darwin-x64": "1.0.0-alpha.
|
|
45
|
-
"@pugi/cli-linux-arm64": "1.0.0-alpha.
|
|
46
|
-
"@pugi/cli-linux-x64": "1.0.0-alpha.
|
|
47
|
-
"@pugi/cli-windows-arm64": "1.0.0-alpha.
|
|
48
|
-
"@pugi/cli-windows-x64": "1.0.0-alpha.
|
|
43
|
+
"@pugi/cli-darwin-arm64": "1.0.0-alpha.217",
|
|
44
|
+
"@pugi/cli-darwin-x64": "1.0.0-alpha.217",
|
|
45
|
+
"@pugi/cli-linux-arm64": "1.0.0-alpha.217",
|
|
46
|
+
"@pugi/cli-linux-x64": "1.0.0-alpha.217",
|
|
47
|
+
"@pugi/cli-windows-arm64": "1.0.0-alpha.217",
|
|
48
|
+
"@pugi/cli-windows-x64": "1.0.0-alpha.217"
|
|
49
49
|
}
|
|
50
50
|
}
|
|
@@ -16,6 +16,7 @@ Landing / dashboard / marketing section templates — hero, pricing, features, C
|
|
|
16
16
|
- Starting from a template is the minimal path, not an extra layer. Writing a section from a blank page while a matching template is available is the slow and generic path.
|
|
17
17
|
- Take only the sections the brief asks for. A template that has a testimonials block is not a reason to ship one.
|
|
18
18
|
- Each section has one primary action. Two equally loud buttons side by side mean the page has not decided what it wants.
|
|
19
|
+
- Decide how bold to be from the brief before the first section: a vague brief ("modern", "clean", no references) gets a confident, distinctive treatment, not the safest default; a brief with brand rules follows them with restraint; a business tool stays conservative; a personal project may experiment; "like <site>" follows that site closely.
|
|
19
20
|
|
|
20
21
|
|
|
21
22
|
## Grounding
|