result-web-feedback
Apply Result<T>-based feedback patterns in Razor Pages and HTMX flows.
Best use case
result-web-feedback is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply Result<T>-based feedback patterns in Razor Pages and HTMX flows.
Teams using result-web-feedback should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/result-web-feedback/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How result-web-feedback Compares
| Feature / Agent | result-web-feedback | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply Result<T>-based feedback patterns in Razor Pages and HTMX flows.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Context Use this when a Web-layer flow moves from sentinel values to `Result`/`Result<T>`. It covers Razor Page handlers, redirect feedback, and HTMX partial re-renders. ## Patterns - For admin redirect flows, send failure text through `TempData["ErrorMessage"]` so `_ToastMessages` renders it after the redirect. - For same-page create/edit posts, add `ModelState` errors and return `Page()` so validation summaries show the failure. - For HTMX partials, keep the server-populated response model (`Model.NewExpertiseResponse`) when re-rendering instead of creating a new one. - For lookup/filter HTMX handlers, return small server-rendered HTML error fragments when a `Result` fails. ## Examples - `Areas\Admin\Pages\Catalog\Expertises\Categories\Index.cshtml.cs` - `Areas\Identity\Pages\Account\Register.cshtml.cs` - `Pages\Profile\Edit.cshtml.cs` - `Pages\Speakers\Index.cshtml.cs`
Related Skills
result-foundation
Add or extend MoreSpeakers Domain Result types with explicit factory methods and structured errors.
{skill-name}
{what this skill teaches agents}
xunit-v3-discovery
Fix xUnit v3 test projects that compile but show zero discovered tests under dotnet test.
reflection-contract-tests
Use reflection-based tests to lock an API contract before the implementation lands.
windows-compatibility
Cross-platform path handling and command patterns
test-discipline
Update tests when changing APIs — no exceptions
squad-conventions
Core conventions and patterns used in the Squad codebase
session-recovery
Find and resume interrupted Copilot CLI sessions using session_store queries
secret-handling
Never read .env files or write secrets to .squad/ committed files
release-process
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters
project-conventions
Core conventions and patterns for this codebase
Personal Squad — Skill Document
## What is a Personal Squad?