html-docs

Stars8

Forks0

UpdatedJuly 8, 2026 at 07:41

HTML 文档规范与交付 Skill。作为正式 HTML 文档生成的统一入口，用于把方案、技术设计、PRD、工作流说明、评审稿、接口说明、运行记录、任务清单和 handoff 等内容整理为结构清晰、可分享、可归档且支持系统暗黑模式的 HTML 文档；不要用于 .docx/.pptx 办公文件处理、普通聊天答复或与文档交付无关的写作。

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

ChoshimWy

ChoshimWy/iOSAgentSkills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

8 files

SKILL.md

readonly

More from this repository

same repository

codex-subagent-orchestration

ChoshimWy/iOSAgentSkills

默认优先使用的 iOS 主 Skill 入口；先按任务复杂度选择 lite / standard / full 档位，再协调 coder / reviewer / tester / reporter / main agent 分工；所有 iOS 生产代码与测试代码实施统一路由到 ios-feature-implementation 的内部模式，验证统一路由到 ios-verification，正式 HTML 文档生成统一路由到 html-docs，调试、性能、审查与构建配置仍路由到专项模块；除实现后的 code-review 必须由独立 reviewer subAgent 执行外，其它 subAgent 使用不做仓库级限制。

2026-07-148

design-context-compiler

ChoshimWy/iOSAgentSkills

iOS Design Context Compiler Skill。用于把明确的 Figma / Sketch / 人工设计证据归一化为 Canonical UI IR，校验设计真源、布局意图、token、状态、交互和 unknowns，解析 UIKit / SwiftUI 组件绑定，并按 screen / region / component 生成低 Token Agent Packet；也用于执行 screenshot-only、UI IR、UI IR+Binding 的收益基准。不要用于视觉方向探索、直接编写产品 UI、截图执行或最终视觉验收。

2026-07-148

ios-feature-implementation

ChoshimWy/iOSAgentSkills

统一 iOS 实施 Skill。作为所有 iOS 代码实施、测试代码编写、页面落地、SDK/Framework 架构契约和结构重构的单一实现入口；根据本地项目事实自动选择 business、swiftui、uikit、mixed-ui、advanced-swift、refactor、sdk-contract、liquid-glass 或 test-implementation 模式，覆盖 service/repository/use case/view model/coordinator/router、SwiftUI/UIKit 页面与组件、XCTest/XCUITest/Mock/Stub/Spy/Fake/fixture/Page Object、iOS 26+ SwiftUI Liquid Glass、复杂 Swift 并发/Sendable/泛型/类型擦除、行为保持型重构、跨模块 Public API、SDK 模块边界、Configuration、分发与版本演进；不要再把普通 SwiftUI/UIKit/Swift 进阶/SDK 架构/Liquid Glass 或测试代码编写拆到独立实现 Skill，构建配置、运行时调试、性能取证、Apple 官方事实检索和验证执行/证据裁决仍路由到对应专项 Skill。

2026-07-148

ui-ux-design-system

ChoshimWy/iOSAgentSkills

UI/UX 设计系统与开放式设计探索 Skill。用于视觉方向、设计系统、交互规则、色板、字体、无障碍、设计评审、原型方向、HTML review 优先的设计交付建议；也用于读取 Sketch 源文件 / SketchMCP / 蓝湖标注并整理可追溯 Design-to-Code source packet，iOS 高保真链路随后交给 design-context-compiler 生成 Canonical UI IR / Agent Packet；若需要正式 HTML 文档交给 html-docs。不要用于 SwiftUI/UIKit API 级实现、设计上下文编译、构建配置或性能取证。

2026-07-148

ios-verification

ChoshimWy/iOSAgentSkills

iOS / Apple Xcode 项目统一验证 Skill。用于验证前路由、优先通过官方 Xcode MCP 执行最窄交互式 build/test、按风险升级到 codex_verify wrapper + shared build-queue 的项目环境证据、读取 MCP 结果或结构化 artifact 做低 token 失败归因，以及在定向验证和独立 code-review 后裁决最终证据是否足够；替代原先分散的验证路由、受影响测试选择、定向验证执行、构建日志摘要、最终证据裁决与项目环境构建验证入口。

2026-07-108

app-store-opportunity-research

ChoshimWy/iOSAgentSkills

App Store 机会研究技能。用于在指定赛道中识别可商业化机会，完成竞品缺口分析、Top-3 机会排序与 MVP PRD 源素材整理；若需要正式 HTML 研究报告或 PRD，最终文档生成交给 html-docs；可按需补充 Rork 原型提示词。

2026-07-088

name

html-docs

description

HTML 文档规范

Purpose

Create, organize, and maintain structured HTML documentation for iOS engineering plans, workflow specifications, technical designs, PRDs, review reports, and handoff documents.

中文说明

该 Skill 是文档规范与 HTML 交付专项 Skill。

负责：

技术方案 HTML 文档。
PRD / 产品设计包 HTML 文档。
工作流、Agent 规范、构建验证规范文档。
接口说明、流程说明、评审稿、变更说明。
任务清单、运行报告、handoff 文档。
可归档、可分享、可浏览的正式文档页面。
HTML 文档样式基线与暗黑模式适配。

不负责：

.docx / Word 文件处理。
.pptx / PowerPoint 文件处理。
Excel / PDF 文件处理。
普通聊天中的短文案回复。

When to Use

Use this Skill when:

The user asks to generate an HTML document.
The user asks for a document that should be shareable, archived, or reviewed.
The output needs headings, table of contents, tables, code blocks, JSON examples, callouts, and responsive layout.
The topic is iOS engineering workflow, technical design, PRD, review report, implementation plan, or process specification.
Another Skill has produced a source packet, conclusion, evidence path, or checklist that must become a formal HTML document.

When Not to Use

Do not use this Skill when:

The user asks for .docx, Word, .pptx, PowerPoint, spreadsheet, or PDF editing.
The user only needs a short plain text answer.
The user needs source code implementation rather than documentation.
The user needs App Store release copy only; use app-store-changelog.

Agent Rules

Document Structure Rules

Use semantic HTML.
Include a clear title.
Include a table of contents for long documents.
Use consistent heading hierarchy.
Use tables for comparison, matrices, and structured decisions.
Use code blocks for commands, JSON, Swift, shell, and config snippets.
Use callout blocks for risks, decisions, assumptions, and next actions.
Prefer responsive layout suitable for browser review.

Content Rules

Keep the document actionable.
Separate background, goals, non-goals, architecture, workflow, implementation plan, validation, risks, and next steps.
Do not mix unverified facts with decisions; label assumptions clearly.
For engineering docs, include verification and rollback where relevant.
For workflow docs, include trigger conditions, inputs, outputs, and exit conditions.

Style Rules

Default style should be clean, lightweight, and Notion-like.
Avoid heavy visual effects.
Use readable spacing, line height, and code block formatting.
Do not inline huge logs or raw outputs.
Prefer concise summaries and linked/attached artifacts where available.
Generate a light-first visual baseline, but every HTML document must support system dark mode.
Use CSS custom properties for color tokens, then override them in @media (prefers-color-scheme: dark).
Include <meta name="color-scheme" content="light dark"> in <head>.
Do not hard-code light-only text, table, code, or callout colors; reference semantic variables such as --bg, --panel, --text, --muted, --border, --code-bg, and --callout-*.
Keep dark-mode contrast readable for body text, table borders, code blocks, links, chips, and checklist status marks.
Read references/dark-mode-style.md before writing final CSS unless the caller provides an equivalent dark-mode stylesheet.

Token Budget

Do not paste large raw logs into the HTML.
Summarize long data into tables or appendices.
Keep examples representative, not exhaustive.
Use collapsible sections only when helpful.

Inputs

Expected input contract:

{
  "goal": "Create HTML documentation",
  "document_type": "technical-design | prd | workflow | review | report | api-doc | handoff",
  "audience": "developer | product | reviewer | stakeholder | mixed",
  "source_material": [],
  "sections": [],
  "constraints": [],
  "theme_mode": "auto",
  "output_path": "optional"
}

Outputs

Return compact structured output:

{
  "status": "completed | partial | blocked",
  "document_type": "technical-design | prd | workflow | review | report | api-doc | handoff",
  "output_files": [],
  "summary": [],
  "sections": [],
  "dark_mode_support": "included | user-provided | blocked",
  "known_risks": [],
  "next_action": "review | publish | revise | blocked"
}

Exit Conditions

Return completed when:

HTML document is generated or fully specified.
Required sections are included.
Dark-mode behavior is included or an explicit reason for not including it is recorded.
Output path or delivery format is clear.

Return partial when:

Draft is useful but some source material, images, data, or decisions are missing.

Return blocked when:

Required source material or output constraints are missing.
The task actually requires a different artifact type such as .docx, .pptx, spreadsheet, or PDF editing.

Escalation Rules

Escalate to implementation or workflow Skills when:

The document reveals missing technical decisions that require code/workflow design.

Escalate to app-store-changelog when:

The task is App Store release notes or user-facing update copy.

Escalate to ui-ux-design-system when:

The task is primarily visual design system, typography, color, or accessibility guidance.

Escalate back to the source Skill when:

The input lacks enough domain evidence, decisions, screenshots, validation artifacts, or review findings to produce a reliable formal document.

Reporting Format

HTML docs status: completed | partial | blocked
Document type: ...
Output files:
- ...
Sections:
- ...
Known risks:
- ...
Next action: review | publish | revise | blocked

Reference Resources

references/template-overview.md: shared HTML skeleton and style baseline.
references/dark-mode-style.md: required color-token and prefers-color-scheme baseline for dark-mode support.
references/plan-template.md: proposal / technical-design template.
references/tasklist-template.md: task checklist / PR checklist template.
references/review-template.md: review / analysis report template.
references/interface-template.md: API / interface documentation template.

Relationship to Other Skills

iOS workflow docs can summarize outputs from codex-subagent-orchestration, ios-verification, code-review, ios-feature-implementation, and related Skills.
App Store release notes route to app-store-changelog.
Visual design guidance routes to ui-ux-design-system.
Code implementation routes to iOS implementation Skills.
Other Skills should route formal HTML doc generation here after producing source packets, conclusions, evidence paths, and risks.