personalized-storefront-render

Translates internal markdown artifacts into persona-tuned client-facing storefront documents with ELI5 and TLDR layers.

Updated May 16, 2026
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill personalized-storefront-render-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: personalized-storefront-render
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/personalized-storefront-render
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill personalized-storefront-render-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Internal artifacts like pitch decks, business plans, and research are written in internal jargon that clients cannot parse. This Skill renders those artifacts into per-persona client-facing surfaces written in each client's domain language, with ELI5/TLDR layers, while enforcing a scaffold-and-curate workflow so nothing auto-publishes without human ratification. ## Core Features & Use Cases - Persona-driven translation: Consumes persona lexicon files ({id}.lexicon.yaml) to substitute forbidden terms, map analogies, and shape ELI5/TLDR projections per audience. - Voice enforcement: Scores every generated draft against the persona's voice_constitution before it can be ratified and moved from _generated/ to _curated/. - Orphan refusal: Refuses to render any artifact lacking traceable bridge_to: lineage to a real internal source, preventing personalization theatre. - CLI workflow: Provides organvm storefront subcommands (sync, audit, ratify, status, feedback) for idempotent rendering, staleness audits, and client feedback capture. - Use Case: After updating a business plan in a client repo, run organvm storefront sync to regenerate a Rob-persona draft in plain domain language, review the voice score, ratify it, and ship it to a link-gated storefront route. ## Quick Start Ask the agent to run the storefront sync command for your client repository so it renders persona-tuned client-facing drafts from your tagged internal artifacts.

Frequently Asked Questions about personalized-storefront-render

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a client-facing version of an internal document?▼

Tag the internal artifact with `audiences:` frontmatter naming the target persona, then run `organvm storefront sync --repo <path>`. The skill renders a draft to `docs/storefront/_generated/` per audience entry, which you review and ratify into `_curated/`.

What is a persona lexicon and why is it required?▼

A persona lexicon is a `{id}.lexicon.yaml` file in `~/Documents/personas/` containing the machine-readable translation table for a client: forbidden terms, analogy mappings, and register rules. The skill refuses to render for any persona lacking this file.

Does the storefront publish content automatically?▼

No. The workflow is scaffold-and-curate: drafts land in `_generated/`, are scored against the persona's voice constitution, and only move to `_curated/` after a human runs `organvm storefront ratify`. Deployment happens through the repo's own build step.

Why does the skill refuse to render some artifacts?▼

Rendering is refused when the source file is missing, the `bridge_to:` reference is absent from the persona's lexicon, or the audience persona has no lexicon file. This prevents output that sounds personalized but contains nothing the client would care about.

When should I not use this storefront rendering skill?▼

Skip it for internal-only governance or SOP documents tagged `audiences: [internal]`, for bespoke creative deliverables better handled by a domain-specific skill, and for client surfaces already hand-curated outside this substrate.