Skip to content

Agent skills for useful HTML artifacts, wireframes, interactive prototypes, plans, and diagrams.

Simplify skill prompts

Michael Ramosd83b36a722bf
diff --git a/skills/html-diagram/SKILL.md b/skills/html-diagram/SKILL.md
index 4f2d178..26b8cb9 100644
--- a/skills/html-diagram/SKILL.md
+++ b/skills/html-diagram/SKILL.md
@@ -1,58 +1,14 @@
---
name: html-diagram
-description: Create self-contained HTML files for architecture, system, stack, and codebase understanding with SVG-first diagrams and minimal prose. Use when the user wants a visual explainer, architecture view, stack overview, flow diagram, full-screen diagram, system map, or wants an HTML artifact focused on understanding relationships rather than reading dense text.
+description: Create a self-contained HTML file for visualizing architecture and understanding the stack with a high-quality SVG diagram. Use when the user wants a full-screen diagram or a visual explainer that is not prose-heavy.
---
# HTML Diagram
-Build a single self-contained HTML artifact that is visually led, not prose led.
+Review the SVG diagrams used throughout `references/html-effectiveness/`.
-## Workflow
+There are several of them, and some are focused on architecture and similar subjects. After reviewing them, create an HTML file that is strictly for visualizing the architecture and understanding the stack.
-1. Read `references/html-effectiveness/README.md` and `references/html-effectiveness/index.html` first.
-2. Review the relevant examples before designing:
- - `13-flowchart-diagram.html` for architecture and flow layout
- - `04-code-understanding.html` for codebase/system understanding
- - `10-svg-illustrations.html` for SVG craft and palette discipline
- - Any other nearby example that matches the requested output shape
-3. Infer the diagram's information architecture before writing HTML:
- - main entities
- - edges / relationships
- - grouping / layers
- - interaction, if any
-4. Build one standalone `.html` file with inline CSS and inline SVG. Do not require a build step.
-5. Keep prose light. The page should read primarily as a diagram, labels, legends, and compact annotations.
-6. Iterate on spacing, alignment, stroke hierarchy, and label clarity until the diagram carries the explanation.
+It should not be prose-heavy. It should simplify more into a full-screen diagram.
-## Output standard
-
-- Prefer a full-screen or near-full-screen composition.
-- Make SVG the primary medium for the architecture view.
-- Use restrained typography and a tight palette.
-- Keep text short, scannable, and subordinate to the visual structure.
-- Use legends, chips, and callouts only when they reduce ambiguity.
-- Avoid turning the page into a long memo with a diagram attached.
-
-## Diagram guidance
-
-- Show structure first, detail second.
-- Use layout to communicate hierarchy: layers, lanes, clusters, ownership boundaries, and flow direction.
-- Prefer direct labels on nodes and edges over long explanatory paragraphs.
-- Make the "what talks to what" and "where responsibility lives" obvious at a glance.
-- If the request is about architecture or stack understanding, include the actual stack/components, not abstract placeholders.
-- If interaction helps, keep it lightweight and supportive, such as hover details or a small side panel.
-
-## Implementation constraints
-
-- Deliver a single HTML file unless the user asks for another shape.
-- Keep assets inline when possible.
-- Use semantic HTML around the diagram, but let the SVG carry most of the information.
-- Avoid decorative filler that does not improve comprehension.
-
-## Reference corpus
-
-This skill bundles the `html-effectiveness` example set under `references/html-effectiveness/`.
-
-- Start with `README.md` and `index.html` to understand the gallery.
-- Then inspect the specific example files that match the requested diagram style.
-- The files are local references. Reuse their composition patterns, not their fictional subject matter.
+Build a high-quality diagram in SVG. Take your time iterating on the diagram more than anything.
diff --git a/skills/html-plan/SKILL.md b/skills/html-plan/SKILL.md
index f646d78..eb184b0 100644
--- a/skills/html-plan/SKILL.md
+++ b/skills/html-plan/SKILL.md
@@ -1,58 +1,14 @@
---
name: html-plan
-description: Create self-contained HTML implementation plans that are pragmatic, structured, and visually organized with milestones, phases, dependencies, risks, and lightweight diagrams. Use when the user wants a plan, rollout plan, execution plan, implementation roadmap, scoped proposal, or an HTML artifact that explains what to build and in what order without becoming prose heavy.
+description: Create a self-contained HTML implementation plan that is pragmatic, simple, and visually organized. Use when the user wants a plan page in the effective HTML style and wants the prose kept close to what they provided, with grammar corrected but not expanded into a heavier framework.
---
# HTML Plan
-Build a single self-contained HTML plan artifact that is practical, visually organized, and easy to scan.
+Review the files throughout `references/html-effectiveness/`.
-## Workflow
+After reviewing them, create an HTML file for the plan in a similar style.
-1. Read `references/html-effectiveness/README.md` and `references/html-effectiveness/index.html` first.
-2. Review the examples most relevant to planning:
- - `16-implementation-plan.html` for structure and pacing
- - `11-status-report.html` and `12-incident-report.html` for operational information density
- - `13-flowchart-diagram.html` when the plan needs a dependency or flow view
- - Any other example that matches the requested artifact shape
-3. Extract the actual execution structure before writing HTML:
- - goals
- - scope / non-goals
- - phases or milestones
- - dependencies
- - risks / open questions
- - success criteria, if useful
-4. Build one standalone `.html` file with inline CSS and no build step.
-5. Keep the writing concise. Use structure, layout, timelines, chips, tables, and compact diagrams to carry the plan.
-6. Prefer decisions and sequencing over generic explanation.
+Keep it pragmatic and simple.
-## Output standard
-
-- Make the plan scannable in one pass.
-- Surface sequence, ownership, dependencies, and risk clearly.
-- Use diagrams when they simplify the plan.
-- Keep long prose blocks out of the critical path.
-- Make the artifact useful for implementation, not just presentation.
-
-## Planning guidance
-
-- Start with the practical summary: what gets built, in what order, and what can block it.
-- Break work into phases that feel executable.
-- Use compact status strips, timelines, dependency maps, and callout panels when they help.
-- If the user asks for a plan from a prompt or repo context, translate that into concrete milestones and deliverables rather than restating the prompt.
-- Keep scope honest; call out what is intentionally deferred when that matters.
-
-## Implementation constraints
-
-- Deliver a single HTML file unless the user asks for another shape.
-- Keep everything self-contained.
-- Use lightweight diagrams rather than prose where possible.
-- Avoid decorative layouts that obscure sequence or priority.
-
-## Reference corpus
-
-This skill bundles the `html-effectiveness` example set under `references/html-effectiveness/`.
-
-- Start with `README.md` and `index.html`.
-- Use the planning, report, and diagram examples as compositional references.
-- Reuse the patterns that make those examples effective: clear sections, compact labels, restrained palette, and visual sequencing.
+If the user provides prose for the plan, keep it close to what they wrote. Correct the grammar and keep it at that.