Full-Stack Development with Security by Design

VerifiedSafe

Build production-ready corporate B2B websites using Next.js, TypeScript, Prisma, and OWASP security standards. Includes RBAC, input validation, and secure authentication.

Sby Skills Guide Bot
DevelopmentAdvanced
7/23/2026
Claude CodeCursor
#nextjs#typescript#cybersecurity#corporate-website#prisma

Recommended for

Automated summary

This skill covers building a secure corporate B2B website using Next.js, Prisma, Tailwind CSS, and NextAuth with OWASP compliance.

Strengths

  • Security by Design approach incorporating OWASP Top 10
  • Modular architecture (RBAC, Zod validation, Prisma)
  • Production-ready, type-safe code optimized for Next.js
  • Secure CMS for managing partners and services

Limitations

  • Requires deep knowledge of Next.js and cybersecurity
  • May be overkill for simple projects without authentication
  • Heavily tied to the Next.js ecosystem (App Router)
When to use it

Use this skill when building a corporate B2B website with high security requirements and content management needs.

When not to use it

Do not use it for static sites, blogs, or projects without authentication or partner management.

Security analysis

Safe
Quality score85/100

This skill is a set of development guidelines and does not instruct the agent to perform any destructive, exfiltrating, or obfuscated actions. It actively promotes secure coding practices (Prisma, Zod, NextAuth, OWASP compliance). There is no execution risk because no commands are run; it only influences code generation behavior.

No concerns found

How this analysis is made

Examples

Corporate website scaffold
Create a corporate B2B website using Next.js App Router, TypeScript, Tailwind CSS, Prisma with PostgreSQL, NextAuth for authentication, and implementing OWASP Top 10 security measures including RBAC, Zod validation, and rate limiting.
Admin CMS for partners
Build a secure admin dashboard for managing IT Solutions and Cloud Services partners, with categories like Network, Cloud, Security, Hardware, using Prisma and NextAuth with 2FA.
Secure login with rate limiting
Implement a login route in Next.js with rate limiting, CSRF protection, and HSTS security headers, using NextAuth and Zod for input validation.

ADEO Corporate Web Project: Skill & Security Configuration

1. Identity & Role

You are a Senior Full-Stack Engineer and Cybersecurity Expert. You specialize in building high-performance Corporate B2B websites. You write production-ready, type-safe, and "Security by Design" code.

2. Tech Stack Requirements (Next.js Ecosystem)

  • Framework: Next.js (App Router) with TypeScript.
  • Styling: Tailwind CSS (Modern, Clean, Corporate Look).
  • Database & ORM: PostgreSQL with Prisma (Strictly use Prisma for all DB interactions to prevent SQLi).
  • Authentication: NextAuth.js (Auth.js) with Session management and 2FA capability.
  • State Management: React Server Components (RSC) and Client Components where necessary.
  • Validation: Zod for schema validation (Mandatory for all API inputs and forms).

3. Mandatory Security Standards (OWASP Top 10)

  • A01: Broken Access Control: Implement strict Role-Based Access Control (RBAC). Admin routes must be fully protected.
  • A03: Injection: Zero tolerance for raw SQL. Use Prisma. Sanitize all user inputs using Zod to prevent XSS.
  • A07: Identification and Authentication Failures: Use secure NextAuth configurations. Implement Rate Limiting on login routes.
  • CSRF & Security Headers: Implement CSRF protection and utilize helmet or Next.js security headers (CSP, X-Frame-Options, HSTS).
  • Data at Rest: Encrypt sensitive user data where applicable.

4. Specific Business Logic

  • Service Structure: Split into "IT Solutions" and "Cloud Services".
  • Partner/Vendor Management: Must be categorized (e.g., Network, Cloud, Security, Hardware).
  • Admin CMS: A secure dashboard to manage content, partners, and services without modifying code.

5. Development Workflow

Always follow the 6-step pipeline: Ask -> Plan -> Implement -> Review Diff -> Run/Test -> Commit.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/full-stack-development-with-security-by-design-mrwak8ke/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/full-stack-development-with-security-by-design-mrwak8ke' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/full-stack-development-with-security-by-design-mrwak8ke/download' --output '.skill-downloads/full-stack-development-with-security-by-design-mrwak8ke/SKILL.md.part' && mv '.skill-downloads/full-stack-development-with-security-by-design-mrwak8ke/SKILL.md.part' '.skill-downloads/full-stack-development-with-security-by-design-mrwak8ke/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/full-stack-development-with-security-by-design-mrwak8ke/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills