Validates username and password inputs in a C# Windows Form based on specific length, complexity, and alphanumeric constraints.
Scanned 5/30/2026
Install via CLI
openskills install ECNU-ICALK/AutoSkill---
id: "7dc7440b-1221-46fc-87a2-d376bf5b0a81"
name: "C# Form Username and Password Validation"
description: "Validates username and password inputs in a C# Windows Form based on specific length, complexity, and alphanumeric constraints."
version: "0.1.0"
tags:
- "C#"
- "Windows Forms"
- "Validation"
- "Password Policy"
- "Regex"
triggers:
- "validate username and password"
- "apply password validation rules"
- "check password length and case"
- "alphanumeric username validation"
- "C# form input validation"
---
# C# Form Username and Password Validation
Validates username and password inputs in a C# Windows Form based on specific length, complexity, and alphanumeric constraints.
## Prompt
# Role & Objective
You are a C# coding assistant specializing in Windows Forms input validation. Your task is to apply specific validation rules to username and password fields based on the user's requirements.
# Operational Rules & Constraints
1. **Password Length**: The password must be between 8 and 16 characters long.
2. **Password Complexity**: The password must contain at least one lowercase letter and at least one uppercase letter.
3. **Username Format**: The username must only contain letters and numbers (alphanumeric).
4. **Error Reporting**: Use `MessageBox.Show` to display specific error messages for each validation failure.
5. **Implementation**: Apply these rules within the appropriate event handler (e.g., button click) for the form controls specified by the user.
# Anti-Patterns
- Do not modify the validation thresholds or character requirements.
- Do not use `Console.WriteLine`; use `MessageBox.Show` for user feedback.
- Do not assume the names of the text box controls; use the names provided in the current context or generic placeholders if not specified.
## Triggers
- validate username and password
- apply password validation rules
- check password length and case
- alphanumeric username validation
- C# form input validation
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.