Skills Registry

• Made reusable workflows easier to find, explain, and share.
• Turned a personal tool collection into a public product artifact that demonstrates workflow design judgment.

• Shifted the IA from a pure skill-name catalog toward task- and scene-first navigation.
• Kept the public site as the registry layer and handed full specs plus updates to GitHub.

• The live site explicitly says "find what you need to do first, then open the right skill" and groups content by scene.
• An earlier local "skills-hub" version still exists, showing that the project evolved from a personal directory into a public registry.

• Owner / Product Engineer: turned scattered reusable skills into a public-facing capability entry point with clear content boundaries.

• When a skill library grows, people often know the task they need help with but not the specific skill name to invoke.

• A public site cannot expose private workflow details or raw internal context.
• Putting every long-form instruction on the site would make the catalog heavy and harder to maintain.

Once reusable skills pile up, the bottleneck shifts from capability creation to capability discovery. This project makes hidden workflow knowledge visible and usable before a person even knows the exact skill name.

• Start from a task like research, writing, frontend work, or shipping when you do not yet know which skill to open first.
• Share reusable workflows publicly without forcing people to parse raw SKILL.md files or repo structure immediately.
• Separate public, sanitized-public, and still-private capabilities at the presentation layer.

• A task-first homepage that asks what you want to get done before exposing the skill list.
• Scene pages plus skill overview blocks for quicker triage and comparison.
• Direct GitHub handoff for full instructions, source, and recent updates.

• The information architecture evolved from a more directory-like "skills hub" into a task-first registry because most people know the job before they know the invoke phrase.
• The warm-paper surface, serif typography, and rule-based layout intentionally make it feel like a guide or registry rather than a noisy SaaS dashboard.
• Deep documentation stays in GitHub so the public site remains a selection layer instead of becoming an overloaded docs mirror.

• Published as a lightweight static website focused on content structure, navigation, and link governance.
• The public site and GitHub repo play different roles: discovery and curation on one side, full specs and change history on the other.
• The surface also communicates publishing state through counts such as public skills, sanitized-public skills, and live scenarios.

• Live site: https://skills.zondev.top.
• The page itself links out to the GitHub repository, full skill directory, and recent updates.