microsoft/power-platform-skills / plugins/power-pages/skills/author-webpage-content
author-webpage-content
VerifiedGenerates and fills the localized HTML body of an existing webpage in a PAC CLI-downloaded non-SPA Power Pages site from a resolved page-content specification. Use whenever a caller has resolved the existing webpage metadata and asks to compose, replace, append, or modify the exact localized `.webpage.copy.html` file with Design Studio-compatible sections, columns, flex containers, text, images, buttons, videos, iframes, Generative AI Search components, basic forms, lists, multistep forms, or spacers. This skill owns only HTML generation and the supplied target file; the coordinator's webpage reference workflow owns discovery, records, metadata, languages, routes, templates, navigation, and companion-file creation. Do not use for React, Angular, Vue, or Astro SPA sites.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.9 KB |
| references/design-studio-basic-form-component.md | markdown | 4.5 KB |
| references/design-studio-button-component.md | markdown | 10.2 KB |
| references/design-studio-component-authoring.md | markdown | 4.3 KB |
| references/design-studio-flex-container-component.md | markdown | 4.2 KB |
| references/design-studio-generative-ai-search-component.md | markdown | 5.4 KB |
| references/design-studio-iframe-component.md | markdown | 8.0 KB |
| references/design-studio-image-component.md | markdown | 10.7 KB |
| references/design-studio-list-component.md | markdown | 5.6 KB |
| references/design-studio-multistep-form-component.md | markdown | 5.1 KB |
| references/design-studio-section-layouts.md | markdown | 11.9 KB |
| references/design-studio-spacer-component.md | markdown | 7.9 KB |
| references/design-studio-text-component.md | markdown | 8.8 KB |
| references/design-studio-video-component.md | markdown | 11.1 KB |
| references/webpage-content-composition.md | markdown | 13.6 KB |
references/design-studio-component-authoring.md
View on GitHub# Design Studio Component Authoring
Canonical decision rules for skills that add or edit Design Studio page elements in
PAC CLI-downloaded non-SPA Power Pages sites.
## Start with the user's prompt
Read the complete user request before asking questions or choosing markup. Extract and
retain every detail the user already supplied, including:
- page and locale;
- existing component text, source, URL, or nearby content that identifies the target;
- whether to add a component or edit an existing one;
- section layout, column, and relative position;
- requested content, behavior, appearance, and accessibility details;
- properties the user explicitly wants preserved.
Do not ask the user to repeat a detail that is clear from the prompt. Examples in a
component reference illustrate markup; they do not override the user's requested values.
## Inspect before deciding
Read the complete selected localized `.webpage.copy.html` and relevant YAML or web-file
metadata. For an edit, find candidate components using both the prompt and the local
markup. Use section number, column, nearby heading/text, current properties, and sibling
components to distinguish candidates.
Before introducing version-specific markup, use the caller's verified Bootstrap evidence or
inspect the site's actual assets. Follow **Bootstrap version** in `design-studio-section-layouts.md`:
the examples using `text-start` target Bootstrap 5, not every non-SPA site. Preserve existing
Bootstrap 3 and RTL conventions; a narrow content edit is not permission to migrate the framework.
If the prompt uniquely identifies one component or insertion point, use it. If several
candidates remain plausible, present concise distinguishing details and ask the user to
choose. Never apply a broad search-and-replace merely because multiple components share
the same label, URL, filename, or class.
## Use engineering judgment
Use sound judgment for low-risk implementation details that follow directly from the
request, the target page's conventions, and these references. Examples include:
- preserving existing indentation, attribute order, and line endings;
- retaining unspecified classes, styles, attributes, and sibling components;
- selecting the documented markup form that matches the requested source type;
- escaping text and attributes;
- adding required safe-link or accessibility attributes;
- using an existing page-local convention when it differs harmlessly from an example.
Do not interrupt the user for mechanical choices with one safe, conventional answer.
Do not invent content, destinations, sources, layout placement, visual design, destructive
cleanup, or behavior that changes the user's intent.
Ask a focused question only when the missing detail could materially change:
- which page, locale, component, section, or column is modified;
- user-visible content or navigation;
- security, privacy, accessibility, or external-resource behavior;
- whether existing content is moved, replaced, or deleted;
- a structural layout mapping where more than one result is reasonable.
## Add versus edit
For an add request, insert the smallest valid component markup at the resolved location.
Create a new section only when the prompt requires one or no suitable existing placement
exists and the calling workflow resolves that choice.
For an edit request:
1. Identify the narrowest component boundary that contains the requested property.
2. Change only requested properties plus mechanically required companion attributes.
3. Preserve every unspecified property and surrounding node.
4. Do not modernize, reformat, relocate, or clean up unrelated markup.
5. Verify exactly one intended target changed unless the prompt explicitly requests a
batch edit.
If the user's prompt already contains a clear, local, reversible edit, do not invent a
second confirmation requirement. Follow any approval gate explicitly defined by the
calling `SKILL.md`; references do not create or bypass workflow gates.
## Before writing
Resolve and retain:
- the exact localized target file;
- whether this is add, edit, move, replace, or delete;
- the exact target component or insertion boundary;
- the final property values derived from the prompt;
- any material assumption made through engineering judgment.
Surface assumptions only when they affect the result. Then apply the smallest change and
use the component reference's verification checklist.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |