Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

html

Sterne3

Forks0

Aktualisiert22. Juni 2026 um 13:40

Writes and reviews semantic, accessible HTML and template markup that stays readable and low-noise. Use when creating or refactoring HTML or Svelte templates, cleaning up div soup, choosing better elements, improving form markup, fixing heading or landmark structure, or replacing custom controls with native HTML.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

maplepy

maplepy/dotfiles

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

WebentwicklerInformatik- und Mathematikberufe·SOC 15-1254

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

(no description)

Review AI-generated or human-written code changes with fallow's graph-grounded review brief. Subtracts deterministic concerns (unused code, complexity, duplication, styling) from the loop, ranks what to look at by blast radius and risk, and surfaces the few consequential structural decisions (new public-API contracts, coupling/boundary crossings, new dependencies) as framed judgment questions anchored to verifiable signals. Drives a closed agent-contract loop: fetch the walkthrough guide, return a judgment, and have fallow post-validate it against the live graph (hallucinated or stale judgments are rejected). Use when asked to review a PR, review a branch, review a diff, do a code review, or check changed code before merge.

2026-07-053

fallow

maplepy/dotfiles

Codebase intelligence for TypeScript and JavaScript. Static analysis of code and styles reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security candidates. Runtime coverage can merge production execution data for hot-path review, cold-path deletion confidence, and stale-flag evidence. 123 framework plugins, zero configuration, sub-second static analysis. Use when asked to audit PR risk, find unused code or dependencies, detect duplicates, check styling consistency, inspect architecture boundaries, merge runtime coverage, auto-fix supported issues, or run fallow.

2026-07-053

readme-gen

maplepy/dotfiles

Generates project READMEs with two variants: a generic open-source template and a specialized 42 School project template. Use when the user asks to generate, update, or create a README file.

2026-05-313

deep-research

maplepy/dotfiles

Deep web research using parallel sub-agents. Classifies question into depth tier (quick/standard/deep), spawns proportional researcher sub-agents, synthesizes into short answer + detailed report with citations. Use when user asks "best X for Y", "compare A vs B", "what is best approach for Z", "research X", "how does X compare to Y", or needs deep investigation.

2026-05-293

deep-work

maplepy/dotfiles

Execute a planned workflow autonomously without stopping to explain steps. Halts only for manual testing, missing information, or major ambiguity. Use when user wants to start deep work, run autonomously, or execute a plan without interruptions.

2026-05-143

name	html
description	Writes and reviews semantic, accessible HTML and template markup that stays readable and low-noise. Use when creating or refactoring HTML or Svelte templates, cleaning up div soup, choosing better elements, improving form markup, fixing heading or landmark structure, or replacing custom controls with native HTML.
metadata	{"category":"Frontend & Accessibility","tags":["html","semantics","accessibility","forms","markup"]}

HTML

Write HTML that is semantic, accessible, maintainable, and easy to scan. Prefer simple structure, meaningful elements, and minimal wrapper noise.

Core Principle

Use the most appropriate HTML element for the content and interaction. Do not apply best practices mechanically.

When to Use This Skill

Use this skill when:

writing raw HTML or template markup
refactoring noisy or wrapper-heavy markup
improving semantics, landmarks, or heading structure
fixing form labeling and control choice
deciding between div, section, article, ul, and other structural elements
replacing custom interactions with better native HTML
cleaning up Svelte component markup without changing its behavior

Do not use this skill for:

pure CSS architecture decisions
JavaScript behavior design unless the HTML choice is the root issue
marketing copy or content strategy
deep framework-specific state or reactivity changes unrelated to markup structure

Decision Order

When writing or reviewing markup:

choose the element that best matches the content or interaction
prefer native HTML behavior before custom behavior
remove wrappers that add no structural value
ensure labels, headings, landmarks, and image handling are correct
add ARIA only when native HTML cannot express the needed behavior

Template Safety

When the markup lives inside Svelte or another HTML-like template language:

treat the file as template markup, not as a plain standalone HTML document
preserve framework syntax such as {#if}, {#each}, {:else}, {@html}, bind:, class, style:, event attributes, and special elements like <svelte:head>
do not replace components or capitalized tags with native elements unless the task explicitly asks for that change
improve the HTML around directives and blocks without breaking bindings, keys, control flow, or component boundaries
apply full-document rules like <!doctype html>, html, head, and body only when the file is actually a document shell
in Svelte, treat compiler accessibility warnings as useful guardrails and do not add svelte-ignore comments casually

Rules

1. Prefer Semantic Elements

Use semantic tags whenever they accurately match the content:
- header
- main
- section
- article
- nav
- aside
- footer
- button
- form
- label
Do not use div when a semantic element is clearly better
Do not force a semantic element where a plain container is more accurate

2. Structure Content by Meaning

HTML should describe content structure, not visual appearance
Choose elements based on what the content is
Do not choose elements based on default browser styles
Do not invent extra structure just to satisfy a rule

3. Keep Nesting Shallow

Avoid unnecessary wrappers
Prefer flatter, easier-to-read markup
Every extra layer should have a real structural, behavioral, or styling purpose

4. Heading Hierarchy Must Make Sense

Use one clear h1 for the page or main view
Follow a logical heading order:
- h1
- h2
- h3
Do not skip heading levels without reason
Do not use headings just to create large text

5. Accessibility Is Required

Always use proper labels for form controls
Use button for actions and a for navigation
Add meaningful alt text to informative images
Use ARIA only when native HTML cannot solve the problem
Do not add unnecessary ARIA

6. Prefer Native HTML Behavior

Use built-in HTML features before custom solutions
Prefer:
- button
- details
- summary
- dialog
- input
- select
- fieldset
- table
Avoid rebuilding native controls with generic elements

7. Write Readable Markup

Keep formatting consistent
Use clear indentation
Keep attributes readable
Break lines when markup becomes hard to scan
Optimize for humans reading the source

8. Keep Class Names Purposeful

Add classes only when needed for styling or scripting
Do not add classes to every element by default
Prefer simple, meaningful class names
Avoid naming based only on presentation when possible

9. Avoid Div Soup

Do not create long chains of anonymous div elements
If many wrappers appear, reconsider the structure
Simplify before adding more containers
A plain div is fine when no stronger semantic exists

10. Forms Must Be Explicit

Every input needs an associated label
Use type values correctly
Use name for submitted fields
Use fieldset and legend for grouped inputs
Mark required fields with HTML attributes, not only text
Do not rely on placeholder text as the label

11. Use Lists Only When Content Is Truly a List

Use ul / ol / li when the content is actually a list:
- steps
- menu items
- bullet points
- grouped items where membership in a list is the important meaning
Do not use list markup just because content repeats
Repetition alone is not list semantics

Use `article` when:

each repeated item can stand on its own
each item has its own heading, metadata, or actions
the repeated content is more like cards, posts, results, stories, or entries

Use `section` when:

content is grouped by theme or purpose
the group benefits from its own heading
the point is thematic grouping, not list membership

Use plain containers when:

the markup is mainly for layout
there is no stronger semantic meaning
list or landmark semantics would be artificial

Avoid:

wrapping card grids in ul / li by default
using li for any repeated component pattern
forcing semantics onto layout-only structures

12. Keep Content and Behavior Separate

HTML defines structure
CSS defines presentation
JavaScript defines behavior
Avoid inline styles and plain HTML event handler strings like onclick="..."
In template languages, do not mistake framework event attributes for plain inline JS

13. Links and Buttons Are Not Interchangeable

Use a when going somewhere
Use button when doing something
Never use a clickable div or span instead of a button
Never use a button for plain navigation unless there is a real app-style reason

14. Images Need Intentional Handling

Use alt="" for decorative images
Use descriptive alt for informative images
Provide width and height when possible to reduce layout shift
Use figure and figcaption when the caption is part of the content

15. Metadata Matters

For full HTML documents, include:
- <!doctype html>
- lang on html
- meta charset="utf-8"
- meta name="viewport" content="width=device-width, initial-scale=1"
- meaningful title
For component files or template fragments, add document metadata only through the framework's proper mechanism, such as <svelte:head> in Svelte
Add other metadata only when it serves a clear purpose

16. Avoid Semantic Overfitting

Do not apply rules mechanically
"Semantic HTML" does not mean using the most specialized element possible everywhere
The best element is the one that most accurately reflects the content and interaction
A simple structure with a few plain containers is better than incorrect semantics

17. Landmarks Should Be Meaningful

Use landmarks like main, nav, header, footer, and aside where they help define page structure
Do not wrap every small subsection in landmark elements
Landmarks should help orientation, not create noise

18. Prefer Minimal Honest Markup

Start with the smallest correct structure
Add elements only when they improve meaning, accessibility, or maintainability
Do not add wrappers, labels, or semantics just in case

Anti-Patterns

using div for buttons or links
adding ARIA when native HTML already works
skipping labels on inputs
using headings for styling only
deeply nested wrapper elements
using tables for layout
plain HTML inline event handler strings like onclick="..."
rewriting valid Svelte directives or blocks as if they were broken HTML
adding html, head, or body tags inside component files
meaningless class names like box1, red_text, left_side
wrapping card layouts in ul / li by default
using semantic elements only because content repeats
adding extra landmarks with no navigational value
placeholder text used instead of labels

Heuristics

can each element justify why it exists?
is there a semantic element that should replace this div?
would this still make sense without CSS?
can a screen reader understand the structure?
are actions buttons and destinations links?
is the heading order logical?
are forms fully labeled and grouped correctly?
is any ARIA actually necessary?
is this truly a list, or just repeated content?
does each repeated item stand alone enough to be an article?
am I editing a full document, or a component/template fragment?
would this cleanup break a Svelte directive, binding, block, key, or component boundary?
am I choosing an element because it is accurate, or because it is a rule I memorized?

Output Guidelines

When writing HTML:

start with semantic structure first
keep the markup minimal
prefer native elements and native behavior
optimize for readability and maintainability
remove unnecessary wrappers
do not add ARIA, classes, or attributes unless they have a clear job
do not force ul / li, section, or article when the semantics are weak
in Svelte or other template files, preserve directives, block syntax, bindings, and special elements
prefer accurate structure over mechanical best-practice compliance

Example Preferences

Good

semantic landmarks where they help
shallow nesting
explicit labels
logical headings
minimal wrappers
native controls
article for standalone repeated entries
ul / ol only for actual lists
plain containers when semantics are minimal

Bad

div soup
clickable non-interactive elements
vague structure
helper text replacing proper semantics
extra wrappers for no reason
custom controls when native HTML works
using list markup for every repeated card
over-structuring simple layouts
semantic overfitting

html

Mehr aus diesem Repository

Mehr aus diesem Repository

HTML

Core Principle

When to Use This Skill

Decision Order

Template Safety

Rules

1. Prefer Semantic Elements

2. Structure Content by Meaning

3. Keep Nesting Shallow

4. Heading Hierarchy Must Make Sense

5. Accessibility Is Required

6. Prefer Native HTML Behavior

7. Write Readable Markup

8. Keep Class Names Purposeful

9. Avoid Div Soup

10. Forms Must Be Explicit

11. Use Lists Only When Content Is Truly a List

Use article when:

Use section when:

Use plain containers when:

Avoid:

12. Keep Content and Behavior Separate

13. Links and Buttons Are Not Interchangeable

14. Images Need Intentional Handling

15. Metadata Matters

16. Avoid Semantic Overfitting

17. Landmarks Should Be Meaningful

18. Prefer Minimal Honest Markup

Anti-Patterns

Heuristics

Output Guidelines

Example Preferences

Good

Bad

HTML

Core Principle

When to Use This Skill

Decision Order

Template Safety

Rules

1. Prefer Semantic Elements

2. Structure Content by Meaning

3. Keep Nesting Shallow

4. Heading Hierarchy Must Make Sense

5. Accessibility Is Required

6. Prefer Native HTML Behavior

7. Write Readable Markup

8. Keep Class Names Purposeful

9. Avoid Div Soup

10. Forms Must Be Explicit

11. Use Lists Only When Content Is Truly a List

Use article when:

Use section when:

Use plain containers when:

Avoid:

12. Keep Content and Behavior Separate

13. Links and Buttons Are Not Interchangeable

14. Images Need Intentional Handling

15. Metadata Matters

16. Avoid Semantic Overfitting

17. Landmarks Should Be Meaningful

18. Prefer Minimal Honest Markup

Anti-Patterns

Heuristics

Output Guidelines

Example Preferences

Good

Bad

Use `article` when:

Use `section` when:

Use `article` when:

Use `section` when: