Oliver Hine avatar

Oliver Hine

Community

@oliyh · London

158Followers
|
122Public Repos
|
2Published Skills

Dad, developer, photographer, optimist. Clojuring @juxt

Skills Distribution
DomainDeveloper To...Specification Docu.. (45%)Static HTML Genera.. (25%)Wireframing & Diag.. (20%)Onboarding & Narra.. (10%)

Agent Skills by Oliver Hine

Showing 2 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Oliver Hine

FAQPage Schema
What tasks can I accomplish with oliyh's narrate and alluminate skills?

Narrate produces a plain-language HTML story of an Allium spec's behaviour, rationale, and open questions. Alluminate generates a rich static HTML document with usage journeys, a reference appendix, transition diagrams, wireframe mockups, and inline validation findings.

Who are these Allium documentation skills designed for?

They target people who own, build, or use the system a .allium spec describes — developers, product owners, and stakeholders needing onboarding documents, product walkthroughs, or human-readable overviews rather than raw specification source.

What input do the narrate and alluminate skills require?

Both skills require an Allium specification file (.allium). All diagrams, mockups, and narration are built strictly from what the spec declares, including its entrypoints, config, entities, rules, and surfaces — nothing external is invented.

What is the difference between narrate and alluminate?

Narrate creates a plain-language story with rationale, mockups, and unsettled questions for onboarding. Alluminate creates a structural reference: chronological usage journeys, a config/entities/rules/surfaces appendix, diagrams, wireframes, and validation findings.

What output format do these skills produce?

Both skills output static HTML documents suitable for publishing as a page, report, living document, or static site. Alluminate additionally embeds transition and relationship diagrams plus low-fidelity wireframes for each declared surface.