[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EKT3TWV5BVZF4WH2Q2G2EP":3,"skill-same:01M7EKT3TWV5BVZF4WH2Q2G2EP":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M7EKT3TWV5BVZF4WH2Q2G2EP","plan-ui-change",null,"> Plan complex Blazor UI features by decomposing them into focused components. USE FOR: building a complex Blazor page with multiple sections, planning component decomposition, designing a multi-section dashboard or layout, breaking down a large UI feature int","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcloud\u002Fplan-ui-change\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plan-ui-change\ndescription: \"> Plan complex Blazor UI features by decomposing them into focused components. USE FOR: building a complex Blazor page with multiple sections, planning component decomposition, designing a multi-section dashboard or layout, breaking down a large UI feature int\"\ncategory: cloud\nversion: 1.0.0\ndisable-model-invocation: false\nrisk: low\nsource:\n  repository: \"microsoft\u002Fskills\"\n  commit: \"8f3b1a2c\"\n  path: \"plugins\u002Fdotnet-blazor\u002Fskills\u002Fplan-ui-change\u002FSKILL.md\"\n  license: \"MIT\"\n  imported_at: \"2026-09-20\"\n---\n# Plan a Blazor UI Change\n\nWhen asked to build a complex UI feature, **plan the component decomposition first, then immediately implement it**. A single monolithic page component is almost never the right answer — break the UI into focused, composable components.\n\n## Planning Workflow\n\n### Step 1 — Map the Visual Regions\n\nRead the request and identify every distinct visual region. Each region that has its own data, behavior, or layout responsibility is a candidate component.\n\nDraw the component tree:\n\n```\nInventoryDashboard          (page — owns data, orchestrates layout)\n├── StockSummaryBar         (read-only stats: total items, low-stock count, value)\n├── InventoryFilters        (search box, category dropdown, stock-level toggle)\n├── InventoryTable          (sortable table of products)\n│   └── InventoryRow        (single product row with inline edit\u002Fdelete)\n└── AddProductForm          (slide-out form for new products)\n```\n\nRules for identifying components:\n- **Distinct responsibility** — a region owns its own state or behavior → separate component\n- **Repeated structure** — items in a list, cards in a grid → extract the item template\n- **Independent interactivity** — a section that handles user input separately from its siblings → separate component\n- **Size** — any section that would exceed ~150 lines of markup on its own → split it\n\n### Step 2 — Classify Each Component\n\nFor every component in the tree, determine:\n\n| Component | Action | Render Mode | State Owned | Lines (est.) |\n|-----------|--------|-------------|-------------|-------------|\n| InventoryDashboard | Create | InteractiveServer | product list, filter state | ~80 |\n| StockSummaryBar | Create | (inherits) | none — receives data | ~30 |\n| InventoryFilters | Create | (inherits) | search text, selected category | ~60 |\n| InventoryTable | Create | (inherits) | sort column, sort direction | ~50 |\n| InventoryRow | Create | (inherits) | inline-edit mode flag | ~60 |\n| AddProductForm | Create | (inherits) | form model | ~80 |\n\n**A page component that exceeds ~200 lines of combined markup + code is too large.** If your estimate puts a single component above that, split further.\n\n### Step 3 — Design Data Flow\n\nIdentify the **state owner** for each piece of data, then map how it flows:\n\n```\nInventoryDashboard (owns: products[], filters)\n  │\n  ├─ [Parameter] products ──→ StockSummaryBar (reads aggregate stats)\n  │\n  ├─ [Parameter] filters ──→ InventoryFilters\n  │   └─ EventCallback\u003CFilters> OnFiltersChanged ──→ InventoryDashboard\n  │\n  ├─ [Parameter] filteredProducts ──→ InventoryTable\n  │   └─ [Parameter] product ──→ InventoryRow\n  │       ├─ EventCallback\u003CProduct> OnSave ──→ InventoryTable ──→ InventoryDashboard\n  │       └─ EventCallback\u003CProduct> OnDelete ──→ InventoryTable ──→ InventoryDashboard\n  │\n  └─ EventCallback\u003CProduct> OnProductAdded ←── AddProductForm\n```\n\nRules:\n- Data always flows **down** through `[Parameter]`\n- Events always flow **up** through `EventCallback\u003CT>`\n- The page\u002Fparent **owns the data** and passes filtered\u002Ftransformed views to children\n- Children **never mutate parameters** — they notify the parent via callbacks\n- If data must cross more than 2 levels without intermediate components needing it, use a cascading value or a scoped service\n\n### Step 4 — Identify Reuse Opportunities\n\nBefore creating a new component, check if an existing component in the project can serve the purpose. Look for:\n- Existing list-item components that match the structure\n- Shared filter\u002Fsearch components already in the project\n- Generic components (e.g., `DataTable\u003CT>`, `Pagination`) that accept templates\n\nIf a component will be used in more than one page, place it in a `Shared\u002F` or `Components\u002F` folder.\n\n### Step 5 — Order the Implementation\n\nBuild bottom-up — leaf components first, then parents that compose them:\n\n1. **Models\u002FDTOs** — define the data shapes\n2. **Services** — data access, business logic (interface + implementation)\n3. **Leaf components** — components with no children (InventoryRow, StockSummaryBar)\n4. **Container components** — components that compose leaves (InventoryTable, InventoryFilters)\n5. **Page component** — wires everything together, registers routes\n6. **Configuration** — DI registration, render mode setup\n\nEach component should be independently compilable. Never reference a component that doesn't exist yet.\n\n## Output Format\n\nPresent the plan briefly, then **immediately proceed to implement** — never stop at just the plan or ask for confirmation before writing code. The plan is a thinking tool, not a deliverable.\n\n```markdown\n## Component Plan: [Feature Name]\n\n### Component Tree\n[ASCII tree showing parent-child relationships]\n\n### Component Table\n| Component | Action | Render Mode | Purpose | Est. Lines |\n|-----------|--------|-------------|---------|------------|\n| ... | ... | ... | ... | ... |\n\n### Data Flow\n[State owner] → [Parameters down] → [EventCallbacks up]\n\n### Implementation Order\n1. [First file to create — why]\n2. [Second file — why]\n...\n```\n\nAfter outputting the plan, **immediately begin implementing** the components in the order listed. Do not wait for approval or ask \"shall I proceed?\" — the plan is a guide for you to follow, not a proposal for the user to approve.\n\n## Anti-Patterns to Avoid\n\n| Anti-Pattern | Why It's Wrong | Correct Approach |\n|-------------|----------------|-----------------|\n| One page component with 500+ lines | Impossible to test, reuse, or maintain | Decompose into focused components |\n| Passing 10+ parameters through intermediate components | Parameter drilling obscures intent | Use cascading values or a scoped state service |\n| Child component fetching its own data from an API | Multiple components making redundant calls | Parent owns data, passes via parameters |\n| Inline rendering of list items with complex markup | Duplicated logic, no reuse, hard to test | Extract item template into its own component |\n| Building everything in one file then \"refactoring later\" | Refactoring rarely happens; the monolith ships | Plan the decomposition upfront |\n| Generic components for one-off usage | Over-engineering adds complexity | Only extract generics when reuse is proven |\n\n## Guidelines\n\n- **Plan briefly, then implement.** Write a concise component table and data flow map, then immediately create the `.razor` files — never stop at just the plan.\n- **Prefer many small components over one large one.** A component with a single clear purpose is easier to understand, test, and reuse.\n- **State ownership is the first decision.** Before writing fetch logic, decide which component owns the data.\n- **Build bottom-up.** Create leaf components first so parent components can reference them immediately.\n- **Name components after what they render**, not what they do internally: `ProductCard` not `ProductRenderer`, `OrderFilters` not `FilterHandler`.\n","# Plan a Blazor UI Change\n\nWhen asked to build a complex UI feature, **plan the component decomposition first, then immediately implement it**. A single monolithic page component is almost never the right answer — break the UI into focused, composable components.\n\n## Planning Workflow\n\n### Step 1 — Map the Visual Regions\n\nRead the request and identify every distinct visual region. Each region that has its own data, behavior, or layout responsibility is a candidate component.\n\nDraw the component tree:\n\n```\nInventoryDashboard          (page — owns data, orchestrates layout)\n├── StockSummaryBar         (read-only stats: total items, low-stock count, value)\n├── InventoryFilters        (search box, category dropdown, stock-level toggle)\n├── InventoryTable          (sortable table of products)\n│   └── InventoryRow        (single product row with inline edit\u002Fdelete)\n└── AddProductForm          (slide-out form for new products)\n```\n\nRules for identifying components:\n- **Distinct responsibility** — a region owns its own state or behavior → separate component\n- **Repeated structure** — items in a list, cards in a grid → extract the item template\n- **Independent interactivity** — a section that handles user input separately from its siblings → separate component\n- **Size** — any section that would exceed ~150 lines of markup on its own → split it\n\n### Step 2 — Classify Each Component\n\nFor every component in the tree, determine:\n\n| Component | Action | Render Mode | State Owned | Lines (est.) |\n|-----------|--------|-------------|-------------|-------------|\n| InventoryDashboard | Create | InteractiveServer | product list, filter state | ~80 |\n| StockSummaryBar | Create | (inherits) | none — receives data | ~30 |\n| InventoryFilters | Create | (inherits) | search text, selected category | ~60 |\n| InventoryTable | Create | (inherits) | sort column, sort direction | ~50 |\n| InventoryRow | Create | (inherits) | inline-edit mode flag | ~60 |\n| AddProductForm | Create | (inherits) | form model | ~80 |\n\n**A page component that exceeds ~200 lines of combined markup + code is too large.** If your estimate puts a single component above that, split further.\n\n### Step 3 — Design Data Flow\n\nIdentify the **state owner** for each piece of data, then map how it flows:\n\n```\nInventoryDashboard (owns: products[], filters)\n  │\n  ├─ [Parameter] products ──→ StockSummaryBar (reads aggregate stats)\n  │\n  ├─ [Parameter] filters ──→ InventoryFilters\n  │   └─ EventCallback\u003CFilters> OnFiltersChanged ──→ InventoryDashboard\n  │\n  ├─ [Parameter] filteredProducts ──→ InventoryTable\n  │   └─ [Parameter] product ──→ InventoryRow\n  │       ├─ EventCallback\u003CProduct> OnSave ──→ InventoryTable ──→ InventoryDashboard\n  │       └─ EventCallback\u003CProduct> OnDelete ──→ InventoryTable ──→ InventoryDashboard\n  │\n  └─ EventCallback\u003CProduct> OnProductAdded ←── AddProductForm\n```\n\nRules:\n- Data always flows **down** through `[Parameter]`\n- Events always flow **up** through `EventCallback\u003CT>`\n- The page\u002Fparent **owns the data** and passes filtered\u002Ftransformed views to children\n- Children **never mutate parameters** — they notify the parent via callbacks\n- If data must cross more than 2 levels without intermediate components needing it, use a cascading value or a scoped service\n\n### Step 4 — Identify Reuse Opportunities\n\nBefore creating a new component, check if an existing component in the project can serve the purpose. Look for:\n- Existing list-item components that match the structure\n- Shared filter\u002Fsearch components already in the project\n- Generic components (e.g., `DataTable\u003CT>`, `Pagination`) that accept templates\n\nIf a component will be used in more than one page, place it in a `Shared\u002F` or `Components\u002F` folder.\n\n### Step 5 — Order the Implementation\n\nBuild bottom-up — leaf components first, then parents that compose them:\n\n1. **Models\u002FDTOs** — define the data shapes\n2. **Services** — data access, business logic (interface + implementation)\n3. **Leaf components** — components with no children (InventoryRow, StockSummaryBar)\n4. **Container components** — components that compose leaves (InventoryTable, InventoryFilters)\n5. **Page component** — wires everything together, registers routes\n6. **Configuration** — DI registration, render mode setup\n\nEach component should be independently compilable. Never reference a component that doesn't exist yet.\n\n## Output Format\n\nPresent the plan briefly, then **immediately proceed to implement** — never stop at just the plan or ask for confirmation before writing code. The plan is a thinking tool, not a deliverable.\n\n```markdown\n## Component Plan: [Feature Name]\n\n### Component Tree\n[ASCII tree showing parent-child relationships]\n\n### Component Table\n| Component | Action | Render Mode | Purpose | Est. Lines |\n|-----------|--------|-------------|---------|------------|\n| ... | ... | ... | ... | ... |\n\n### Data Flow\n[State owner] → [Parameters down] → [EventCallbacks up]\n\n### Implementation Order\n1. [First file to create — why]\n2. [Second file — why]\n...\n```\n\nAfter outputting the plan, **immediately begin implementing** the components in the order listed. Do not wait for approval or ask \"shall I proceed?\" — the plan is a guide for you to follow, not a proposal for the user to approve.\n\n## Anti-Patterns to Avoid\n\n| Anti-Pattern | Why It's Wrong | Correct Approach |\n|-------------|----------------|-----------------|\n| One page component with 500+ lines | Impossible to test, reuse, or maintain | Decompose into focused components |\n| Passing 10+ parameters through intermediate components | Parameter drilling obscures intent | Use cascading values or a scoped state service |\n| Child component fetching its own data from an API | Multiple components making redundant calls | Parent owns data, passes via parameters |\n| Inline rendering of list items with complex markup | Duplicated logic, no reuse, hard to test | Extract item template into its own component |\n| Building everything in one file then \"refactoring later\" | Refactoring rarely happens; the monolith ships | Plan the decomposition upfront |\n| Generic components for one-off usage | Over-engineering adds complexity | Only extract generics when reuse is proven |\n\n## Guidelines\n\n- **Plan briefly, then implement.** Write a concise component table and data flow map, then immediately create the `.razor` files — never stop at just the plan.\n- **Prefer many small components over one large one.** A component with a single clear purpose is easier to understand, test, and reuse.\n- **State ownership is the first decision.** Before writing fetch logic, decide which component owns the data.\n- **Build bottom-up.** Create leaf components first so parent components can reference them immediately.\n- **Name components after what they render**, not what they do internally: `ProductCard` not `ProductRenderer`, `OrderFilters` not `FilterHandler`.\n",{"name":5,"risk":24,"source":25,"version":30,"category":31,"description":7,"disable-model-invocation":20},"low",{"path":26,"commit":27,"license":15,"repository":28,"imported_at":29},"plugins\u002Fdotnet-blazor\u002Fskills\u002Fplan-ui-change\u002FSKILL.md","8f3b1a2c","microsoft\u002Fskills","2026-09-20","1.0.0","cloud","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcloud\u002Fplan-ui-change","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill plan-ui-change",{"tool":44,"command":45},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill plan-ui-change",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill plan-ui-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcloud\u002Fplan-ui-change\u002FSKILL.md",true,[],[53,61,68,75,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":60},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":60},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":60},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":60},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":60},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]