How do I install the Semantic Pattern Guardrails skill?

Run npx skillmds@latest add fritzandfriends/semantic-pattern-guardrails in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Semantic Pattern Guardrails safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Semantic Pattern Guardrails?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Semantic Pattern Guardrails free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Semantic Pattern Guardrails?

fritzandfriends (@fritzandfriends) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Semantic Pattern Guardrails by fritzandfriends

Name: Semantic Pattern Guardrails
Author: fritzandfriends

File contents

Context

Use this when adding semantic catalog entries to the Web Forms migration CLI. These rules apply to cross-file page-shape rewrites where the mechanical transforms have already converted raw syntax and the remaining work is contract normalization.

Patterns

Master/content normalization belongs in the semantic pass

Let the markup transforms do the local tag conversion first.
Then normalize generated master/page pairs to the BWFC-tested contract:
- master shell markup → ChildContent
- migrated <Content ContentPlaceHolderID="..."> blocks → ChildComponents
- preserve exact placeholder IDs, including head slots

Query/detail pages must stay read-only

Safe matches:

SelectMethod/code-behind only filters by [QueryString] / [RouteData]
no writes, redirects, form access, auth calls, or postback branches
one clear data-display page shape

Stop and emit TODO/manual review if:

the page mutates state
the page mixes route/query entry points in a way you cannot preserve exactly
the code-behind depends on postback/event sequencing

Action pages must still act

Safe matches:

empty or scaffold-only page
action happens on load from deterministic query inputs
one redirect target
no auth cookies, no POST body dependency, no external provider workflow

Anti-pattern:

converting an action page into a visible informational page that does nothing

Account pages are high-risk and mostly manual

Treat these as manual/TODO boundaries unless you have explicit HTTP endpoint/handler output:

login/logout
register
password reset token issuance/consumption
external auth challenge/callback
2FA provider selection and verification
add/remove external logins
phone / security settings that resignal identity state

Why:

Web Forms account pages depend on live HTTP response semantics and OWIN/Identity middleware
a Blazor component event handler cannot safely fake that contract

Minimum valid output contract

Master shell

<MasterPage>
    <Head>...</Head>
    <ChildContent>
        ...chrome...
        <ContentPlaceHolder ID="MainContent" />
    </ChildContent>
    <ChildComponents>
        @ChildComponents
    </ChildComponents>
</MasterPage>

Child page

<Site>
    <ChildComponents>
        <Content ContentPlaceHolderID="MainContent">
            ...
        </Content>
    </ChildComponents>
</Site>

Anti-Patterns

Rewriting multi-placeholder masters to @Body
Dropping ContentPlaceHolderID names
Pretending auth pages are fully migrated when only the shell was understood
Converting redirect-only action pages into dead-end content pages
Collapsing query/route precedence to a single hard-coded id path

---name: semantic-pattern-guardrailsdescription: Guardrails for implementing Web Forms semantic page-pattern rewrites in the migration CLI---## ContextUse this when adding semantic catalog entries to the Web Forms migration CLI. These rules apply to cross-file page-shape rewrites where the mechanical transforms have already converted raw syntax and the remaining work is contract normalization.## Patterns### Master/content normalization belongs in the semantic pass- Let the markup transforms do the local tag conversion first.- Then normalize generated master/page pairs to the BWFC-tested contract: - master shell markup → `ChildContent` - migrated `<Content ContentPlaceHolderID="...">` blocks → `ChildComponents` - preserve exact placeholder IDs, including head slots### Query/detail pages must stay read-onlySafe matches:- `SelectMethod`/code-behind only filters by `[QueryString]` / `[RouteData]`- no writes, redirects, form access, auth calls, or postback branches- one clear data-display page shapeStop and emit TODO/manual review if:- the page mutates state- the page mixes route/query entry points in a way you cannot preserve exactly- the code-behind depends on postback/event sequencing### Action pages must still actSafe matches:- empty or scaffold-only page- action happens on load from deterministic query inputs- one redirect target- no auth cookies, no POST body dependency, no external provider workflowAnti-pattern:- converting an action page into a visible informational page that does nothing### Account pages are high-risk and mostly manualTreat these as manual/TODO boundaries unless you have explicit HTTP endpoint/handler output:- login/logout- register- password reset token issuance/consumption- external auth challenge/callback- 2FA provider selection and verification- add/remove external logins- phone / security settings that resignal identity stateWhy:- Web Forms account pages depend on live HTTP response semantics and OWIN/Identity middleware- a Blazor component event handler cannot safely fake that contract## Minimum valid output contract**Master shell**```razor<MasterPage> <Head>...</Head> <ChildContent> ...chrome... <ContentPlaceHolder ID="MainContent" /> </ChildContent> <ChildComponents> @ChildComponents </ChildComponents></MasterPage>```**Child page**```razor<Site> <ChildComponents> <Content ContentPlaceHolderID="MainContent"> ... </Content> </ChildComponents></Site>```## Anti-Patterns- Rewriting multi-placeholder masters to `@Body`- Dropping `ContentPlaceHolderID` names- Pretending auth pages are fully migrated when only the shell was understood- Converting redirect-only action pages into dead-end content pages- Collapsing query/route precedence to a single hard-coded `id` path

Frequently asked questions

Semantic Pattern Guardrails