wizz-method 1.4.1 → 1.5.1

package/src/skills-lib/form-cro/references/trust-and-form-types.md

@@ -0,0 +1,54 @@
+# Trust/Friction Reduction and Form-Type Guidance
+
+Load this file when writing trust copy near the form, or when the form is a specific known type (lead capture, contact, demo request, quote, survey) that has its own conventions.
+
+## Trust and Friction Reduction
+
+### Near the Form
+- Privacy statement: "We'll never share your info"
+- Security badges if collecting sensitive data
+- Testimonial or social proof
+- Expected response time
+
+### Reducing Perceived Effort
+- "Takes 30 seconds"
+- Field count indicator
+- Remove visual clutter
+- Generous white space
+
+### Addressing Objections
+- "No spam, unsubscribe anytime"
+- "We won't share your number"
+- "No credit card required"
+
+## Form Types: Specific Guidance
+
+### Lead Capture (Gated Content)
+- Minimum viable fields (often just email)
+- Clear value proposition for what they get
+- Consider asking enrichment questions post-download
+- Test email-only vs. email + name
+
+### Contact Form
+- Essential: Email/Name + Message
+- Phone optional
+- Set response time expectations
+- Offer alternatives (chat, phone)
+
+### Demo Request
+- Name, Email, Company required
+- Phone: Optional with "preferred contact" choice
+- Use case/goal question helps personalize
+- Calendar embed can increase show rate
+
+### Quote/Estimate Request
+- Multi-step often works well
+- Start with easy questions
+- Technical details later
+- Save progress for complex forms
+
+### Survey Forms
+- Progress bar essential
+- One question per screen for engagement
+- Skip logic for relevance
+- Consider incentive for completion

package/src/skills-lib/graphify/SKILL.md

@@ -987,16 +987,7 @@ Replace `QUESTION` with the question, `ANSWER` with your full answer text, `SOUR
 
 Find the shortest path between two named concepts in the graph.
 
-First check the graph exists:
-```bash
-$(cat graphify-out/.graphify_python) -c "
-from pathlib import Path
-if not Path('graphify-out/graph.json').exists():
-    print('ERROR: No graph found. Run /graphify <path> first to build the graph.')
-    raise SystemExit(1)
-"
-```
-If it fails, stop and tell the user to run `/graphify <path>` first.
+First check the graph exists - run the same pre-check as `/graphify query` above (identical `graphify-out/graph.json` existence check). If it fails, stop and tell the user to run `/graphify <path>` first.
 
 ```bash
 $(cat graphify-out/.graphify_python) -c "
@@ -1060,16 +1051,7 @@ $(cat graphify-out/.graphify_python) -m graphify save-result --question "Path fr
 
 Give a plain-language explanation of a single node - everything connected to it.
 
-First check the graph exists:
-```bash
-$(cat graphify-out/.graphify_python) -c "
-from pathlib import Path
-if not Path('graphify-out/graph.json').exists():
-    print('ERROR: No graph found. Run /graphify <path> first to build the graph.')
-    raise SystemExit(1)
-"
-```
-If it fails, stop and tell the user to run `/graphify <path>` first.
+First check the graph exists - run the same pre-check as `/graphify query` above (identical `graphify-out/graph.json` existence check). If it fails, stop and tell the user to run `/graphify <path>` first.
 
 ```bash
 $(cat graphify-out/.graphify_python) -c "