product-engineer
Takes an existing HTML concept/prototype and adds product-level functionality — state management, interactions, behaviors, and polish that make it feel like a real shipping product.
- License 许可
- MIT
- 最近更新
- 2026-06-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- product-engineer
- description
- Takes an existing HTML concept/prototype and adds product-level functionality — state management, interactions, behaviors, and polish that make it feel like a real shipping product.
03 SKILL.md 正文
Product Engineer — Enhance Prototype to Product
You take an existing HTML concept and make it feel like a real product. You ADD functionality to what's already there — you don't redesign or restructure.
Your Role
Read the existing HTML. Understand its structure, its data model, its visual language. Then ADD:
State & Data
- Interactive status — click a task to cycle its status (pending → running → pass → failed)
- Running timers — tasks in "running" state show a live elapsed counter
- Progress tracking — parent tasks show aggregate progress of children
- Persistence — save state to localStorage so refresh doesn't lose changes
Interactions
- Expand/collapse — sections and nested levels can be toggled open/closed
- Task body reveal — click to show the full markdown body of any task
- Smooth transitions — all state changes animate smoothly (height, opacity, color)
- Hover states — subtle feedback on interactive elements
- Keyboard navigation — arrow keys to move between tasks, Enter to expand
Product Polish
- Status filter — toggle buttons or pills to filter by status (all / running / failed / pass)
- Search — find tasks by title
- Breadcrumb — when deep in nesting, show where you are
- Empty states — when filtering leaves no results, show a helpful message
- Counts — show task counts per status in a summary bar
How to Work
- Read the existing HTML completely
- Identify the data structure (how tasks are stored in JS)
- Add new functions that manipulate existing DOM/data
- Add new CSS for new states and transitions
- Don't change the existing visual design — add behavior to it
- Test that all new interactions work together
Rules
- Visual quality must match or exceed the reference. Study the concept's palette, spacing, typography, surfaces. Don't degrade it — elevate it.
- Fresh build, not a patch. Create a new file that incorporates the design AND the behaviors together from the start. This produces better results than editing an existing file.
- Keep it self-contained. No new external dependencies.
- Smooth everything. Every state change should have a transition.
- Mobile-friendly. Touch targets, responsive behavior.
04 同仓库更多 Skills
hello-checker
Use this skill when asked to "verify", "check", or "validate" a file's existence and content. It provides a reliable workflow for confirming files meet their spec.
ask-skill
暂无简介
html-review-artifact
Framework-wide guidance for crafting polished human-review artifacts as markdown or HTML
converge-planning
Design a Converge playbook end-to-end. Use when the user says "plan a project", "design a playbook", "decompose into tasks", "scaffold a Converge workflow", "onboard to Converge", or asks how to write TASK.md / playbook.yml. Two entry points: plan a new playbook or update an existing one. Hand off to `/converge-control` after producing the playbook structure.
converge-control
Operate a Converge playbook end-to-end — start runs, monitor progress, narrow failures with `--select`, inspect runtime state, validate definitions, surgically reset subtrees, and stop stuck or orphaned runs. Use this skill whenever the user says "run my playbook", "execute this", "monitor the run", "converge failed", "the run is stuck", "retry failures", "babysit this playbook", "what's the status?", "show me the gantt", or asks how to use `converge run` / `--select` / `inspect` / `doctor` / `clean` / `stop`. Also use it for `HTTP 401` / `Invalid API key` failures on the first task — those are environment-not-playbook problems — and for any post-run cleanup work. Hand off to `converge-planning` if the user wants to design or restructure the playbook itself.
repair-taskts
Fix task.ts definition issues — Seed syntax, missing .build(), empty checks, import errors, TypeScript errors