Skip to content

lean-interactive-html: add plugin for generating interactive HTML artifacts#6

Open
mkucharski17 wants to merge 1 commit into
mainfrom
lean-interactive-html
Open

lean-interactive-html: add plugin for generating interactive HTML artifacts#6
mkucharski17 wants to merge 1 commit into
mainfrom
lean-interactive-html

Conversation

@mkucharski17

Copy link
Copy Markdown

Adds a new lean-interactive-html plugin: a /interactive-html skill that generates polished single-file interactive HTML artifacts (reports, stats dashboards, architecture diagrams, migration/feature plans, decision questionnaires, process proposals). It ships a copy-first skeleton.html (design tokens, dark mode, tabs, stat cards, badges, filterable tables, localStorage persistence, clipboard helpers) and per-archetype recipes (references/archetypes.md) with the nontrivial JS patterns — runtime SVG connectors, step-through simulator, sticky answer bar — distilled from real artifacts that survived multiple review rounds. Artifacts are always self-contained: no CDN, no frameworks, no build step, so they open offline and can be forwarded safely.

Heads-up: this is the first non-Flutter plugin in the marketplace. CONTRIBUTING.md says the repo "currently ships LeanCode's Flutter plugins", but the lean-<scope> naming convention from /lean-contribute exists exactly for repo-wide capabilities with no Flutter domain, so it follows that path (like lean-core). Only this plugin is touched (plus its registration in marketplace.json and the root README, under a new "Docs and reporting" group). No breaking changes. go run ./cmd/validate-plugins passes (15 plugins checked).

…ifacts

Codifies the recurring ask for single-file interactive HTML deliverables
(reports, architecture diagrams, plans, questionnaires, proposals) into a
reusable skill with a copy-first skeleton and per-archetype recipes, so
artifacts share one house style instead of being reinvented per session.
@wzslr321

Copy link
Copy Markdown
Member

@mkucharski17 could you please move this PR to the internal repository?

For now we want to keep public one strictly flutter-related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants