security-first-scrum

Enforces security-first TDD coding rules for .NET 8, React, Blazor, and Azure development.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill security-first-scrum-theviziusgroup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-first-scrum
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/security-first-dev/skills/security-first-scrum
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill security-first-scrum-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Greenfield development on Azure often ships code with inconsistent security controls, missing tests, and unclear architecture boundaries. This Skill provides a single master ruleset that governs every coding decision — from authentication flows to commit hygiene — so AI-generated code meets the same security and quality bar as a senior engineer's work. ## Core Features & Use Cases - Security-First Framework: Enforces three laws (Security First, People First, Agile/Scrum), eight Saltzer-Schroeder security principles, and Zero Trust tenets across all code. - Mandatory TDD Workflow: Requires RED→GREEN→REFACTOR→SCAN→COMMIT with two tests per security control (positive and adversarial) and coverage gates up to 100% for security-critical paths. - Stack-Specific Guidance: Provides concrete patterns for .NET 8 Web APIs (Microsoft.Identity.Web, FluentValidation, rate limiting), React/Blazor (MSAL, DOMPurify, CSP), Cosmos DB and PostgreSQL (Managed Identity, parameterized queries), Databricks (Unity Catalog, PII masking), and Bicep infrastructure with DevSecOps pipeline gates. - Use Case: When starting a new .NET 8 API endpoint, the Skill ensures you write a failing security test first, apply [Authorize] by default, validate input with FluentValidation, prevent BOLA in the service layer, and pass Semgrep scanning before committing. ## Quick Start Ask the AI to scaffold a new authenticated .NET 8 Web API endpoint with Cosmos DB persistence following the security-first-scrum ruleset.

Frequently Asked Questions about security-first-scrum

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TDD and security testing in .NET 8 API development?▼

Follow the RED→GREEN→REFACTOR→SCAN→COMMIT cycle: write a failing test expressing the security behavior first, then the minimum secure implementation. Every security control needs two tests — one proving legitimate requests pass and one proving the attack vector is blocked.

What authentication flow should I use for React SPA with Azure AD?▼

Use Authorization Code flow with PKCE via MSAL.js — never the deprecated Implicit Grant. Store tokens in sessionStorage rather than localStorage to reduce XSS exposure, and instantiate PublicClientApplication outside the React component tree.

How do I prevent BOLA vulnerabilities in ASP.NET Core APIs?▼

Place resource-level ownership checks in the service layer, not the controller, using an IAuthorizationHandler implementation. Every endpoint returning user-owned data must verify the requesting user owns the resource, since UI-level hiding is not a security boundary.

Does Cosmos DB support Managed Identity instead of connection strings?▼

Yes, use DefaultAzureCredential or ManagedIdentityCredential with the CosmosClient instead of connection strings with embedded keys. Note that Azure control-plane roles do not grant data-plane access — you must assign Cosmos DB native data-plane RBAC roles separately.

Why does my Blazor WASM authorization not protect my API?▼

Blazor WASM assemblies are downloadable and decompilable, so [Authorize] attributes and AuthorizeView components are UX features only. The API must re-validate every JWT and re-check authorization on every request regardless of client-side guards.

What security gates should a DevSecOps pipeline include for .NET projects?▼

Include Semgrep and CodeQL for SAST, Snyk for dependency scanning, Gitleaks for secrets detection with full history, Trivy for container scanning, Checkov for Bicep IaC scanning, and a coverage-gated test stage. Never soft-fail or bypass these gates to meet deadlines.