Saved Markdown

saved-markdown

Publish immutable, anonymous pages to https://saved.md. Pages can be Markdown (with 图表 wid获取s), HTML (sanitized static pages with CSS), or JSX (sandboxed interactive React).

Core principle

Frontmatter decides when to use this 技能. Everything below defines how to 执行 once triggered.

工作流 modes

After triggering, pick the mode that best matches user intent. If unclear, default to one-shot and mention that other modes exist.

Mode When What h应用ens One-shot Quick 报告s, 记录s, 导出s 生成 → publish → return URL Interactive 恢复s, landing pages, anything user-facing 生成 → show draft → user edits → publish Local-only User explicitly wants no publishing Save .md / .html / .jsx, no API call Enhance Existing markdown needs 图表s or polish Read → enhance → publish new URL

Pages are immutable — edits always produce a new URL.

Execution flow (high level) Decide mode Decide 启动ing point (template scaffold or freehand) Decide 格式化 (Markdown / HTML / JSX) 生成 or 转换 content 验证 Publish (unless local-only) 启动ing point decision 1) User explicitly asks for a scaffold Read templates/索引.md Show relevant templates (过滤器 by 格式化 if known) Let user choose Load selected template 2) User wants a scaffold from a screenshot / description Follow templates/创建-template.md 创建 a new template file under: templates/markdowns/ for markdown templates/htmls/ for html templates/jsx/ for jsx 更新 templates/索引.md Then continue like a normal template flow 3) User wants to enhance existing markdown Analyze content Identify 可视化 opportunities: trends → line categories → bar proportions → pie relationships → scatter 添加 multiple 图表s where justified Keep original structure intact Publish as a new page 4) User describes content (no scaffold mentioned) Match content type using routing table Load cor响应ing scaffold template 生成 content from it 5) Nothing matches 生成 freehand: title structured body optional footer 格式化 decision 格式化 Use when contentType Markdown 报告s, docs, 仪表盘s, 恢复s, 图表s "markdown" (or omit) HTML Layout-heavy pages, visual polish, static UI "html" JSX Interactivity, 过滤器s, 状态, dynamic 图表s "jsx" Critical rule

If using HTML or JSX, always explicitly 设置 contentType. Otherwise the page renders incorrectly.

Content-type routing

Use this when generating structured Markdown or HTML content.

Content type Triggers Template 恢复 / CV 恢复, CV, 性能分析 恢复-cv.md 报告 报告, analysis, findings 报告.md Company 性能分析 company, about, 服务s company-性能分析.md 仪表盘 KPIs, 指标, scorecard 仪表盘-指标.md Documentation docs, 图形界面de, manual documentation-图形界面de.md Proposal proposal, pitch, quote proposal-pitch.md Newsletter newsletter, digest, change记录 newsletter-更新.md Portfolio portfolio, projects portfolio-showcase.md Event event, invitation, RSVP event-invitation.md Generic everything else freehand Golden rule

Never invent content to fill sections. Omit anything without real data.

Template scaffold 工作流

When a template is selected:

Read template file from templates/ Show the scaffold skeleton to the user in a code block Ask what to change: content sections colors Replace placeholders with user data and 移除 irrelevant sections 验证 Publish

If the user already provided full content, skip template browsing and go strAIght to generation.

Markdown enhancement (图表s)

When enhancing markdown:

添加 图表s using markdown-ui-wid获取 Use multiple 图表s when data supports it Ensure: numeric values are plAIn numbers (no $, %, K, etc.) units go in labels, not values

Template 图形界面de: templates/图表s.md

验证 检查列出

Before publishing:

Content under 100 KB Correct contentType 图表s valid (if markdown) HTML sanitized (no scripts) JSX: only allowed 导入s (react, react-dom) no external packages No placeholder text left

Template 图形界面de: templates/验证.md

Publishing Preferred (script) python scripts/publish.py --file --content-type --title "