nexu-io/open-design / plugins/community/hallmark
hallmark
FlaggedAnti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
references/macrostructures/06-conversational-faq.md
View on GitHub## 06 · Conversational FAQ
Bold questions, brief answers. The page reads like an honest interview with the product. Often each Q/A is a collapsible accordion.
- **Heading:** each section *is* a question — a short, direct phrase ending in `?`.
- **Body:** answer in 2–4 short paragraphs immediately below the question.
- **Divider:** thin rule between Q/A pairs, or zero rule and a paper-colour swap.
- **Button:** typographic link inside answers ("Read the full policy →"); one outlined CTA at the foot.
- **Image:** sparse — maybe one diagram per long answer; mostly text.
- **Reveal:** none on load; accordion expand uses 200 ms `--ease-out` on `grid-template-rows: 0fr → 1fr`.
Reach for it near pricing, for products that meet skepticism, for educational/regulated industries.
Avoid as the *primary* page. FAQ usually pairs with another macrostructure that opens the page.
Reference: many SaaS pricing pages, Casper, Substack help pages.
**Sample opening lines** (imitate the *specificity* — questions are real questions, answers are short and concrete):
> *"What is this for? — A single-binary CLI for parsing log streams from stdin."* — names the form factor, names the input
> *"How is this different from X? — It's about time."* — cron.com — answers obliquely, with a phrase that has weight
> *"Who built this? — Three of us, in Lisbon, since 2014."* — date + place + count, no marketing
```html
<section class="faq">
<details>
<summary><h2>How long does setup take?</h2></summary>
<div class="answer">…</div>
</details>
<details>…</details>
</section>
```
---
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 |