Aetheria-Labs1/storefront-skills / skills/audit
audit
VerifiedRead-only conversion audit of a whole storefront page. Scores above-the-fold, offer strength, proof, copy, design, mobile and funnel data against the build rules and returns ranked fixes. Never edits; hand approved fixes to /optimize.
references/workflow-intent.md
View on GitHub# Storefront Workflow Intent
Infer the outcome the user wants from their words, the current conversation,
the requested deliverable, and the reversibility of the next action. Do not
require a magic phrase.
## Modes
| Mode | Typical intent | Outcome |
|---|---|---|
| `fast-draft` | create, try, show, preview, explore, iterate, make a first version, move quickly | ask fewer optional questions; the plan is still complete and approved before design |
| `production-ready` | final polish, campaign handoff, exhaustive QA, launch preparation, ready for review | collect every optional choice explicitly; `DESIGN_APPROVED` only after hosted QA |
| `publish` | release, launch live, publish this version | use the separate publish workflow and require explicit approval for the named page/version |
Signals such as "assume specifics", "use your judgment", "do whatever is
needed", or impatience with questions strengthen `fast-draft`; they are not
required. A previous request for a preview or first pass also counts.
## Routing Rules
1. Prefer the outcome implied by the whole request, not one keyword.
2. If the next action is reversible and intent is reasonably clear, proceed
and state the inferred mode briefly.
3. If question depth is ambiguous, ask fewer questions; never skip plan
approval.
4. Ask only when the missing choice would materially change the campaign,
spend credits, publish, delete, overwrite shared work, or perform another
consequential action.
5. Inferred intent never authorizes publishing, paid generation, deletion, or
destructive replacement.
6. A user correction overrides the inference immediately.
## Manifest Evidence
Record compact evidence under `workflow`:
```json
{
"intentMode": "fast-draft",
"intentConfidence": "high",
"intentSignals": ["asked to create a preview", "delegated specifics"],
"userOverride": false
}
```
Use `high`, `medium`, or `low` confidence. Keep signals short and derived from
the request; do not store private chain-of-thought or long conversation text.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |