Token导航 LogoToken导航TokenDH.com
中转站排行榜
研究检索敏感数据github未标认证来源可访问clear审计通过

blazor-blog-feature（Blazor 博客功能）

Agent Skill

blazor-blog-feature 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

629

周安装

27

GitHub Stars

15

下载量

220
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：blazor-blog-feature（Blazor 博客功能）
来源仓库：https://github.com/markpitt/claude-skills
仓库路径：skills/blazor-blog-feature
安装命令：
npx skills add https://github.com/markpitt/claude-skills --skill blazor-blog-feature
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异；本站展示可直接复制的安装命令，安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/markpitt/claude-skills --skill blazor-blog-feature

简介

blazor-blog-feature 提供完整的博客功能实现方案，适用于 Blazor WASM + Azure Functions。

  • 支持静态站点托管与无服务器后端处理，集成文件共享存储。
  • 包含 YAML 解析、DI 配置与组件分层结构指导。
  • 适用于内容管理系统与用户生成内容平台开发。
  • 使用前请确认 Azure Static Web Apps 部署环境与存储账户配置。

SKILL.md

Blog Feature Skill for Blazor WASM + Azure Functions

This skill provides a complete, production-ready blog feature for Blazor WASM applications hosted on Azure Static Web Apps with serverless backend processing.

Quick Reference: When to Load Which Resource

Your TaskLoad ResourceKey Concepts
Understand architecture, prerequisites, shared modelsresources/core-architecture.md3-layer architecture, project structure, data models
Implement backend services, Azure Functions, file share integrationresources/backend-services.mdBlogStorageService, YAML parsing, DI setup
Build Blazor components, UI pages, stylingresources/frontend-components.mdRazor components, markdown rendering, responsive design
Configure Azure environment, local settings, deploymentresources/azure-configuration.mdConnection strings, file share setup, environment variables
Create sample content, test workflow, troubleshoot issuesresources/sample-content-testing.mdSample markdown, testing checklist, common issues

Orchestration Protocol

Phase 1: Setup & Understanding

Before writing any code, establish context:

  1. Review your current Blazor WASM project structure
  2. Confirm you have Azure Functions API project ready
  3. Verify Azure Storage account and File Share access
  4. Load resources/core-architecture.md to understand 3-layer design

Quick assessment:

  • Do you have existing Blazor WASM + Functions project? → YES, proceed
  • Do you need to understand what to build? → Load core-architecture.md first
  • Are you setting up Azure resources? → Go to azure-configuration.md

Phase 2: Implementation Selection

Choose your implementation path:

Your SituationLoad This FirstThen Load
Starting from scratchcore-architecture.mdbackend-services.md
Backend complete, need UIfrontend-components.md(skip backend-services.md)
Just need configuration helpazure-configuration.md(reference other resources as needed)
Debugging or testingsample-content-testing.md(target troubleshooting section)

Phase 3: Execution & Validation

Implementation sequence:

  1. Create project structure (core-architecture.md Step 1-2)
  2. Add NuGet packages (backend-services.md)
  3. Implement BlogStorageService (backend-services.md)
  4. Create Azure Functions (backend-services.md)
  5. Build Blazor components (frontend-components.md)
  6. Configure Azure environment (azure-configuration.md)
  7. Test locally (sample-content-testing.md testing workflow)
  8. Deploy to Azure (azure-configuration.md deployment section)

Validation checkpoints:

  • Backend: Functions respond correctly to test calls
  • Frontend: Components load and display posts
  • Integration: End-to-end blog viewing works
  • Azure: Configuration deployed and accessible

Common Workflow Scenarios

Scenario 1: Fresh Implementation (First Time)

Timeline: 2-3 hours

  1. Read core-architecture.md → understand what you're building
  2. Follow backend-services.md → implement API layer
  3. Follow frontend-components.md → build UI layer
  4. Follow azure-configuration.md → configure Azure resources
  5. Use sample-content-testing.md → validate with sample posts

Scenario 2: Existing Backend, Need Frontend

Timeline: 1 hour

  1. Skip to frontend-components.md
  2. Reference core-architecture.md if component questions arise
  3. Use sample posts from sample-content-testing.md
  4. Deploy following azure-configuration.md

Scenario 3: Update Existing Blog

Timeline: 30 minutes

  1. Jump to relevant resource file
  2. Reference back to core-architecture.md for context
  3. Test changes with sample-content-testing.md checklist

Scenario 4: Troubleshooting Issues

Timeline: As needed

  1. Go directly to sample-content-testing.md
  2. Find problem in troubleshooting section
  3. Reference other resources for context if needed

Architecture Summary

Frontend → Backend → Storage:

  • Blazor WASM pages call HTTP endpoints
  • Azure Functions retrieve from File Share
  • Markdown files with YAML frontmatter contain all content
  • No database needed (files are the database)

Key Components:

  • BlogStorageService: Abstracts File Share interactions
  • BlogFunctions: HTTP endpoints for listing/retrieving posts
  • Index/Post Razor Components: Client UI for browsing
  • CSS Styling: Responsive design for all screen sizes

Implementation Complexity

ComponentComplexityTime
Backend ServicesMedium45 min
Azure FunctionsEasy30 min
Frontend ComponentsMedium60 min
StylingEasy30 min
ConfigurationEasy20 min
TotalEasy-Medium~3 hours

Prerequisites Checklist

  • ✅ Existing Blazor WASM SWA project
  • ✅ Azure Functions API project
  • ✅ Azure Storage account with File Share
  • ✅.NET 10 SDK (or later)
  • ✅ Azure CLI (for deployment)
  • ✅ Visual Studio Code or Visual Studio

Resource Files Summary

resources/core-architecture.md (285 lines)

Foundational knowledge about the blog system architecture, project structure, and shared data models needed across frontend and backend.

Load when: Getting started, understanding the design, creating shared models

resources/backend-services.md (425 lines)

Complete implementation of Azure File Share service integration, BlogStorageService class, and Azure Functions for blog operations.

Load when: Building the API layer, implementing backend services

resources/frontend-components.md (610 lines)

Blazor Razor components for blog listing and detail pages, CSS styling for responsive design, navigation integration.

Load when: Building the UI layer, styling components, creating Razor pages

resources/azure-configuration.md (445 lines)

Azure environment setup, local development configuration, File Share structure, deployment guidelines, and security considerations.

Load when: Setting up Azure resources, configuring environments, deploying to production

resources/sample-content-testing.md (395 lines)

Sample markdown formats, complete testing workflow checklist, troubleshooting guide for common issues, and enhancement ideas.

Load when: Creating test data, validating implementation, debugging problems

Best Practices

  1. Start with core-architecture.md - Don't skip understanding the design
  2. Implement sequentially - Backend first, then frontend, then configuration
  3. Test locally - Use Azure Storage Emulator before deploying
  4. Use sample content - Test with provided markdown examples
  5. Follow naming conventions - Consistent file naming prevents errors

Quick Navigation by Goal

I want to...ResourceSection
Understand the systemcore-architecture.mdArchitecture Overview
Create the backendbackend-services.mdBlogStorageService
Build the UIfrontend-components.mdBlog Listing Page
Set up Azureazure-configuration.mdAzure File Share Setup
Test everythingsample-content-testing.mdTesting Workflow
Fix a problemsample-content-testing.mdTroubleshooting Guide
Deploy to productionazure-configuration.mdDeployment Checklist

Support & Next Steps

After implementation:

  • Add pagination for better performance (recommended)
  • Implement search functionality
  • Consider caching for frequently-accessed posts
  • Monitor Azure Function cold starts
  • Optimize featured image sizes for performance

Enhancement opportunities:

  • RSS feed generation
  • Comment system integration
  • Post categories and tagging
  • Admin content management interface
  • Email newsletter subscription

Built with: Blazor WASM, Azure Functions, Azure File Share, Markdown, YAML frontmatter

Skill Type: Feature Implementation (Blazor WASM + Azure)

Difficulty: Easy-Medium (3-4 hours total)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.37%
按下载量换算60

OpenCode

24.14%
按下载量换算53

trae

16.98%
按下载量换算37

Codex

11.43%
按下载量换算25

Antigravity

7.6%
按下载量换算17

windsurf

3.85%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置，应进入高风险复核队列，默认不自动发布。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

GitHub 仓库

github.com

/markpitt/claude-skills

SKILL.md 来源

github.com

/markpitt/claude-skills/tree/main/skills/blazor-blog-feature

skills-sh

skills.sh

/markpitt/claude-skills/blazor-blog-feature

agentskills-to

agentskills.to

/markpitt/claude-skills/blazor-blog-feature

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

blazor-auth-security（Blazor 身份验证安全）

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论，涉及密钥、令牌、用户数据或生产系统时，应先确认最小权限、脱敏方式和操作边界。

下一个 Skill

blazor-expert（开拓者专家）

blazor-expert 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。