Initial skills documentation — 25 categories, all SKILL.md + references + scripts
This commit is contained in:
@@ -0,0 +1,47 @@
|
||||
# Live WPForms Verification Technique
|
||||
|
||||
Demonstrated Jul 13, 2026 when verifying the Apex Track Experience Roebling Road registration form.
|
||||
|
||||
## Problem
|
||||
Memory/plans said a vehicle selector field existed on the Apex registration form. Live verification proved it didn't. Need a reliable way to inspect WPForms on live WordPress sites.
|
||||
|
||||
## Technique
|
||||
|
||||
### 1. Enumerate all form fields via CSS classes
|
||||
```bash
|
||||
curl -sk --connect-timeout 10 'https://example.com/page/' \
|
||||
| grep -oP 'wpforms-field-[a-zA-Z0-9_-]+' | sort -u
|
||||
```
|
||||
This extracts every field type (name, email, phone, address, payment-single, payment-total, layout, etc.) without needing to parse the DOM.
|
||||
|
||||
### 2. Check for specific field/data presence
|
||||
```bash
|
||||
curl -sk --connect-timeout 10 'https://example.com/page/' \
|
||||
| grep -i -c 'vehicle\|apex-vehicle\|car-select'
|
||||
```
|
||||
Returns count of matches — 0 means field/payload absent.
|
||||
|
||||
### 3. Get form content (readable)
|
||||
```python
|
||||
web_extract(urls=["https://example.com/page/"], char_limit=10000)
|
||||
```
|
||||
Clean markdown output with form labels, field types, option lists, and payment amounts. Best for understanding what the user sees.
|
||||
|
||||
### 4. Get raw form HTML for structure analysis
|
||||
```bash
|
||||
curl -sk --connect-timeout 10 'https://example.com/page/' \
|
||||
| grep -i 'vehicle'
|
||||
```
|
||||
Shows surrounding HTML structure including field IDs, quantity selectors, order summary rows.
|
||||
|
||||
## Application to Apex
|
||||
- Form #272 on /roebling-road/
|
||||
- Fields: name, email, phone, address, payment-single (×5 items), payment-total, paypal-commerce
|
||||
- No vehicle selector, no `apex-vehicle-field`, no make/model/year dropdown
|
||||
- "Additional Vehicle" is a quantity picker (0-5), not an identification field
|
||||
- Memory had claimed `apex-vehicle-field` CSS class existed — it doesn't
|
||||
|
||||
## Pitfalls
|
||||
- Browser tools may fail (Chromium/DBus issues on headless servers) — always have curl fallback
|
||||
- `curl | python3` pipes are blocked by security scanning — use web_extract or curl+grep instead
|
||||
- WPForms loads field CSS even when the form isn't fully rendered — `wpforms-field-*` classes are reliable indicators of configured fields
|
||||
Reference in New Issue
Block a user