plannotator/effective-html

html-plan

Direct-invocation specialist for clear, self-contained HTML plans that preserve source material while improving hierarchy, sequence, ownership, dependencies, and reviewability.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/plannotator/effective-html --skill html-plan

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

HTML Plan

Turn source material into a plan people can inspect and act on. Preserve the user's scope, ordering, commitments, and terminology unless they ask for broader synthesis.

Shape the document around the work

Read the conversation, project instructions, and supplied plan before designing. Match an existing design language when one is present. Otherwise derive a quiet, workmanlike direction from the audience and subject.

When `design-artifact` is available, read its fundamentals to make that direction intentional. Keep this skill's traceability and source-preservation rules authoritative; creative direction must not inflate the plan into a dashboard or campaign page.

Decide what the plan actually needs:

  • phases or sequence;
  • status and decision points;
  • owners and collaborators;
  • dependencies and risks;
  • acceptance checks;
  • unresolved questions.

Do not add a timeline, progress percentage, status badge, or dashboard summary unless the source supports it. Improve grammar and structure without inflating an implementation plan into a strategy document.

Preserve traceability

  • Keep source commitments recognizable.
  • Separate accepted decisions from assumptions and open questions.
  • Show sequence and dependency only where they are real.
  • Use tables for exact mappings, comparisons, or repeated fields.
  • Use a flow or timeline only when it makes order materially easier to understand.
  • Keep long prose readable instead of forcing every paragraph into a card.

Build and verify

Deliver one responsive, accessible, self-contained HTML file. Use semantic headings, lists, tables, and landmarks. Keep essential CSS and JavaScript inline, avoid external services, and make any navigation or disclosure keyboard-operable.

Inspect the result at wide and narrow widths. Check that no commitment disappeared, that stages remain in the intended order, that ownership and dependencies are legible, and that long content does not overflow.

Return the absolute path and note any structural interpretation you introduced.

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
plannotator
Społeczność

design-artifact

Design principles and creative direction for building HTML artifacts — pages, reports, plans, landing pages, demos, decks, and small tools. Use when creating or restyling any visual HTML deliverable and deciding its palette, type pairing, layout, theming, or overall register, or when the output must not look generically AI-generated.

Instalacje / 1h
1
GitHub Stars
3,8 tys.
Aktualizacja
15 paź
plannotator
Społeczność

html-diagram

Direct-invocation specialist for self-contained HTML diagrams whose layout, notation, and interaction clarify relationships, sequence, topology, state, hierarchy, or quantitative structure. Use when the user explicitly invokes html-diagram or the broad html skill routes a diagram request here. Do not activate independently from a general request.

Instalacje / 1h
1
GitHub Stars
3,8 tys.
Aktualizacja
15 paź
plannotator
Społeczność

html-wireframe

Direct-invocation specialist for low-fidelity, self-contained HTML wireframes that test information hierarchy, content, navigation, task flow, and responsive structure before visual design. Use when the user explicitly invokes html-wireframe or the broad html skill routes a wireframe request here. Do not activate independently from a general request. Do not use for polished mockups or production-like interaction; use html-prototype for those.

Instalacje / 1h
3
GitHub Stars
3,7 tys.
Aktualizacja
15 paź
plannotator
Społeczność

big-pics-little-words

- Explain the current subject in HTML with large visuals and minimal text while preserving key details.

Instalacje / 1h
2
GitHub Stars
3,7 tys.
Aktualizacja
15 paź