gitea/skills/html-style/SKILL.md

name, description

name

description

html-style

Set which HTML layout and style a kind of Gitea wiki page or issue gets when jsc-gitea:html-export renders it. Offer all six layouts from tools/html-style.sh layouts and all five styles from tools/html-style.sh styles as decision-tree options per jsc-ask, then write the pair with tools/html-style.sh set - either to the project file .jsc/html-styles or to the global $JSC_HOME/html-styles.conf. Use when a kind of page or issue should come out looking different, or when the export reported source builtin or default; not for rendering a page, which is jsc-gitea:html-export.

html-style — which template a kind of page gets

One kind of page, one layout, one style. jsc-gitea:html-export reads what this skill writes.

Steps

1. Settle the kind key. Show the current configuration with tools/html-style.sh list first, then ask per jsc-ask:ask rules which kind this run sets. The three shapes are fixed: WIKI:{page-name prefix} (WIKI:PLAN, WIKI:ANALYZE, WIKI:LOG …), ISSUE:{label name} (ISSUE:bug), and DEFAULT for everything that matches nothing else. Every option states its impact scope — DEFAULT changes every kind that has no row of its own. Completion condition: exactly one key is agreed, and its current value from tools/html-style.sh get {key} has been read back with its source column.
2. Pick the layout — offer all six. Run tools/html-style.sh layouts; it prints each name with its Traditional Chinese description, taken from the template file itself. Present all six as options per jsc-ask:ask rules, each with what it does to the content (report builds a table of contents beside the text, slide turns every ## into a keyboard-flipped page, dashboard turns them into cards, spec freezes table headers, timeline strings them along a line, onepager narrows everything into one printable page). Completion condition: the user has picked one layout name that the script listed.
3. Pick the style — offer all five. Run tools/html-style.sh styles and present every one it prints (minimal, corporate, dark, print, vivid) with its description. Never trim the list to a shortlist: the point of this skill is that the user sees the whole set. Completion condition: the user has picked one style name that the script listed.
4. Pick the scope. Ask per jsc-ask:ask rules: --project writes ./.jsc/html-styles, which only applies inside this working directory and is committed with the repository; --global writes $JSC_HOME/html-styles.conf, which follows the user across every project on this machine. State that the project file wins whenever both hold the same key. Completion condition: the user has picked one scope.
5. Write it: tools/html-style.sh set {key} {layout} {style} [--project|--global]. Exit 4 means the name is not one of the listed templates — go back to step 2 or 3 rather than editing the file by hand. Completion condition: the script exits 0 and prints the file it wrote.
6. Read it back with tools/html-style.sh get {key} and report the resolved layout, style and source. Completion condition: the source column shows project or global, matching the scope chosen in step 4.

Rules

• Only names the script listed may be written. A key holding a template that does not exist fails at export time, long after the mistake was made.
• Removing a row is tools/html-style.sh unset {key} [--project|--global]; after that the kind falls back to DEFAULT, then to the built-in report/minimal.
• New layouts live in templates/html/layout/{name}.html and new styles in templates/html/style/{name}.css, each starting with a one-line Traditional Chinese comment — that comment is what the option list shows.