Can I use this for cloud infrastructure limits?

Yes, it is designed to document platform constraints such as database connection pools, regional runtime versions, and memory limits.

What is the difference between a constraint and a design decision?

Constraints (C-*) are external realities you must work within, like a Stripe API timeout. Design decisions (ADRs) are choices you make between alternatives, like choosing a specific database.

How does this skill help with regulatory compliance?

It provides specific categories for GDPR, PCI-DSS, and HIPAA, ensuring that non-negotiable legal requirements are documented and validated before coding begins.

What format does the skill use for documentation?

The skill outputs structured YAML blocks that include the constraint ID, source, ecosystem context, and specific implementation requirements.

Technical Constraint Extractor

Name: Technical Constraint Extractor
Author: foolishimp

byfoolishimp

Security & Testing

Extracts and documents external ecosystem constraints to ensure software compliance and architectural alignment.

About

The extract-constraints skill is a specialized requirements engineering tool designed for the AI-driven SDLC. It helps developers and architects identify 'given' external realities—such as API rate limits, regulatory compliance (GDPR/PCI-DSS), and platform dependencies—distinguishing them from flexible design choices. By formalizing these ecosystem constraints (C-*) early in the process, the skill provides a rigid framework for Claude to generate code that is compliant, performant, and perfectly adapted to its operating environment.

Key Features

Analyzes ecosystem E(t) to identify hidden performance and resource limits
Provides clear validation and implementation paths for documented constraints
Differentiates between external constraints and internal design decisions
0 GitHub stars
Categorizes constraints by API limits, Compliance, Platform, and Security
Standardizes documentation using structured YAML templates

Use Cases

Mapping out third-party API limitations and timeouts before backend implementation
Documenting regulatory compliance requirements for security-sensitive applications
Defining infrastructure and runtime dependencies for cloud-native deployments

About

Key Features

Analyzes ecosystem E(t) to identify hidden performance and resource limits
Provides clear validation and implementation paths for documented constraints
Differentiates between external constraints and internal design decisions
0 GitHub stars
Categorizes constraints by API limits, Compliance, Platform, and Security
Standardizes documentation using structured YAML templates

Use Cases

Mapping out third-party API limitations and timeouts before backend implementation
Documenting regulatory compliance requirements for security-sensitive applications
Defining infrastructure and runtime dependencies for cloud-native deployments