Catalog · topic

Security

Close the holes before someone finds them. Login and access patterns, secrets management, threat mapping and the hardening checklists we run before every release.

The order here is deliberate: doors before alarms. Login and access control come first, then threat mapping and the hardening lists you run on every release. These are checklists written to be executed, not read once and shelved.

22 skills

Who this shelf is for
  • Developer shipping a login system and unsure where the holes are
  • Founder who needs a real threat assessment, not a compliance PDF
  • Engineer hardening servers and infrastructure before an audit
Where to start

There is no kit; start at the door. If your login is already live, begin with Auth Implementation Patterns, then map your exposure with Attack Tree Construction.

Skills 22

Security Skill

Create Auth Skill

Skill for creating auth layers in TypeScript/JavaScript apps using Better Auth.

$15
Inspect →
Security Skill

GDPR Data Handling

Implement GDPR-compliant data handling with consent management, data subject rights, and…

$15
Inspect →
Security Skill

Guard

Security hardening and authentication patterns for authorization, OWASP compliance…

$15
Inspect →
Security Skill

Memory Forensics

Master memory forensics techniques including memory acquisition, process analysis, and…

$15
Inspect →
Security Skill

PCI Compliance

Implement PCI DSS compliance requirements for secure handling of payment card data and payment…

$15
Inspect →
Security Skill

SAST Configuration

Configure Static Application Security Testing (SAST) tools for automated vulnerability…

$15
Inspect →
Security Skill

Secrets Management

Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or…

$15
Inspect →
Questions · still in the air

Catch what's on your mind.

the air is clear. nothing between you and the forge.
catch a spark: the forge will answer

  1. Where does hardening start for a small team?

    With the doors, not the alarms: Auth Implementation Patterns and Better Auth Best Practices close the most common entry mistakes, then the hardening checklists sweep what ships with every release.

  2. Is threat modeling here, or just checklists?

    Both layers. Attack Tree Construction builds the actual threat model: who attacks, through what, at what cost, and the checklists turn its output into repeatable release discipline.

  3. Can Claude audit the auth I already built?

    Yes: the auth skills review sessions, token lifetimes, reset flows and role boundaries against known failure patterns, and return findings as fixes ranked by exposure.