semantic-pattern-guardrails

@fritzandfriends · 收录于昨天 · 上游提交 1 个月前

Guardrails for implementing Web Forms semantic page-pattern rewrites in the migration CLI

场景表单迁移页面重构

适合你，如果正在用 CLI 工具迁移 Web 表单并需要语义化重写

/ 下载安装

https://github.com/fritzandfriends/blazorwebformscomponents/tree/dev/.squad/skills/semantic-pattern-guardrails ↗

/ 通过 npx 安装 校验哈希

npx oh-my-skill add fritzandfriends/blazorwebformscomponents/semantic-pattern-guardrails

/ 通过 bash 安装

curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fritzandfriends/blazorwebformscomponents/semantic-pattern-guardrails

/ 已经装过?验证本机副本,不用重装

npx oh-my-skill verify fritzandfriends/blazorwebformscomponents/semantic-pattern-guardrails

安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。

449GitHub stars

~551上下文体积 · 单文件

索引托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 3154758

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

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。

…