Zensical Site Assistant

Use this skill to create, revise, and organize content for zensical.org.

This skill is intentionally lightweight: use compact reference pages for output-critical rules, and link out to upstream docs for deep detail.

When to use this skill

Use this skill if the user asks to:

• Draft new pages/posts for zensical.org.
• Rewrite existing copy for clarity, tone, or SEO.
• Build content outlines, page briefs, or navigation structure.
• Summarize or compare pages from zensical.org.
• Convert rough notes into Zensical-style markdown.

Core workflow

1. Clarify the content objective (page type, audience, and intent).
2. Collect source material from zensical.org and any user-provided notes.
3. Open Authoring Reference Index and load only the subject references needed for this task.
4. Draft using the output template in this skill.
5. Run a quality pass for tone, structure, links, front matter, and factual consistency.
6. Return final markdown plus a short rationale and suggested next edits.

Output format

Always provide:

1. Draft (markdown ready to paste into the site)
2. Rationale (2-5 bullets explaining important choices)
3. Open Questions (only when missing info blocks quality)

Use the page template in Page Draft Template unless the user requests another format.

Writing guidance

• Prefer plain language and concrete examples.
• Keep paragraphs short and scannable.
• Use descriptive headings.
• Avoid hype and vague claims.
• Include links with meaningful anchor text.

Reference routing

Start with:

• Authoring Reference Index

Then load only what is needed:

• Markdown and Links for links, heading structure, and title behavior.
• Front Matter for page metadata.
• Callouts and Interactive Elements for admonitions, buttons, tabs, and tooltips.
• Code and Technical Content for code blocks, diagrams, and math.
• Layout and Media for grids, images, and icons/emojis.
• Data and Visualization for tables and structured visual content patterns.
• Inline Formatting and Microcontent for lists, inline formatting, and footnotes.

If output depends on setup/runtime behavior, feature flags, or config snippets, load:

• Configuration Reference
• Extension Prerequisites
• Navigation and Runtime Caveats
• Customization Boundaries

Use Shared Patterns for common rules and shared conventions.

Sources and verification

• If browsing is available, reference exact pages used.
• Flag uncertainty instead of guessing.
• Do not invent product features, policies, or URLs.
• If deeper implementation detail is needed, cite the relevant upstream Zensical doc rather than expanding these references inline.