me2resh/apexyard / .claude/skills/journey
journey
VerifiedSelf-contained HTML user-journey map (boxes/arrows with per-page modals) — preview between PRD and tech-design.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 23.1 KB |
| fixtures/sample-checkout.yaml | config | 1.7 KB |
| tests/README.md | markdown | 2.1 KB |
| tests/render_smoke.py | script | 24.5 KB |
fixtures/sample-checkout.yaml
View on GitHubversion: 1
feature: sample-checkout
project: example-app
title: Sample Checkout Flow
description: Three-page checkout flow used as the smoke-test fixture for /journey.
generated_at: 2026-05-03T00:00:00Z
generated_by: /journey
personas: []
pages:
- id: cart
title: Cart
description: User reviews items they intend to purchase.
contents:
- List of cart items (image, name, price, quantity)
- Subtotal + estimated tax
- "Proceed to checkout" button
- "Continue shopping" link
success_state: User clicks "Proceed to checkout" with at least one item in cart.
error_state: Empty cart shows a placeholder and disables the proceed button.
- id: payment
title: Payment
description: User enters payment details and confirms the order.
contents:
- Address summary (read-only, with edit link)
- Payment-method selector (card / wallet)
- Card-details form (number, expiry, CVV)
- "Place order" button
success_state: Payment processor returns success → navigate to confirmation.
error_state: Validation errors inline; processor failure shows a retry banner.
- id: confirmation
title: Confirmation
description: Order placed. User sees their order number and next steps.
contents:
- Order number + estimated delivery date
- Receipt summary
- "View order status" link
- "Continue shopping" link
transitions:
- from: cart
to: payment
trigger: clicks "Proceed to checkout"
- from: payment
to: confirmation
trigger: payment processor returns success
entry: cart
notes: |
Smoke-test fixture. Three pages, two transitions — the minimal shape the
layout algorithm needs to exercise (entry, intermediate, terminal).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |