Branded output generation: HTML/CSS/JS, DOCX, XLSX, PDF, vector art, folios, templates (MetodologIA DS tokens in references/brand). Topics: brand-art, brand-docx, brand-html, brand-pdf, brand-xlsx, branded-html-output, folio-generator, html-brand, presentation-design, xlsx-template-creator.
Router skill for branded deliverable generation with MetodologIA DS tokens. Resolve
topic, then Read EXACTLY ONE playbook from routes: — never load the cluster. [EXPLICIT]
Any request to produce a branded artifact: HTML pages/folios, DOCX, XLSX, slides, or reusable templates. Not for raw content authoring (no brand) or non-MetodologIA output — route those elsewhere. [INFERENCE]
topic (one of the 8 enums), depth, the source content/data, target format.references/brand tokens; provenance-tagged where
claims aren't reproducible from the prompt. [CONFIG]topic from the request; ask only if genuinely ambiguous (≥2 enums fit equally). [EXPLICIT]deep → apply exhaustively, verify each step; quick → essentials. [EXPLICIT]brand-html (general) · html-brand (token-heavy/deep) · branded-html-output (lightweight) · folio-generator (paginated folios). [INFERENCE]presentation-design. DOCX → brand-docx. XLSX → brand-xlsx (one-off) vs xlsx-template-creator (reusable template). [INFERENCE]Spine: Discover → Analyze → Execute → Validate.
Router aids in assets/ — assets/routing-checklist.md and assets/quality-rubric.json (see assets/README.md). [CONFIG]
references/brand; no hardcoded brand values. [CONFIG][EXPLICIT]/[INFERENCE]/[ASSUMPTION]/[CONFIG]/[DOC]). [DOC]fdad39c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.