sparc-architecture-example-3-security-architecture
Sub-skill of sparc-architecture: Example 3: Security Architecture (+1).
Best use case
sparc-architecture-example-3-security-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of sparc-architecture: Example 3: Security Architecture (+1).
Teams using sparc-architecture-example-3-security-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/example-3-security-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sparc-architecture-example-3-security-architecture Compares
| Feature / Agent | sparc-architecture-example-3-security-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of sparc-architecture: Example 3: Security Architecture (+1).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Example 3: Security Architecture (+1)
## Example 3: Security Architecture
```yaml
security_architecture:
authentication:
methods:
- jwt_tokens:
algorithm: RS256
expiry: 15m
refresh_expiry: 7d
- oauth2:
providers: [google, github]
scopes: [email, profile]
- mfa:
methods: [totp, sms]
required_for: [admin_roles]
authorization:
model: RBAC
implementation:
- role_hierarchy: true
- resource_permissions: true
- attribute_based: false
example_roles:
admin:
permissions: ["*"]
user:
permissions:
- "users:read:self"
- "users:update:self"
- "posts:create"
- "posts:read"
encryption:
at_rest:
- database: "AES-256"
- file_storage: "AES-256"
in_transit:
- api: "TLS 1.3"
- internal: "mTLS"
compliance:
- GDPR:
data_retention: "2 years"
right_to_forget: true
data_portability: true
- SOC2:
audit_logging: true
access_controls: true
encryption: true
```
## Example 4: Scalability Design
```yaml
scalability_patterns:
horizontal_scaling:
services:
- auth_service: "2-10 instances"
- user_service: "2-20 instances"
- notification_service: "1-5 instances"
triggers:
- cpu_utilization: "> 70%"
- memory_utilization: "> 80%"
- request_rate: "> 1000 req/sec"
- response_time: "> 200ms p95"
caching_strategy:
layers:
- cdn: "CloudFlare"
- api_gateway: "30s TTL"
- application: "Redis"
- database: "Query cache"
cache_keys:
- "user:{id}": "5 min TTL"
- "permissions:{userId}": "15 min TTL"
- "session:{token}": "Until expiry"
database_scaling:
read_replicas: 3
connection_pooling:
min: 10
max: 100
sharding:
strategy: "hash(user_id)"
shards: 4
```Related Skills
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
label-driven-prompt-generation-architecture
Pattern for building automation scripts that classify GitHub issues into prompt templates using label-based routing and extract contextual data for batch processing
skill-dedup-collision-reconciliation-with-content-security-scan
Reconcile duplicate/colliding workspace-hub skills without losing useful content, while avoiding pre-commit skill-content security scan regressions.
repo-architecture-analysis
Scan a Python repo's package structure, count classes/functions, classify module maturity (PRODUCTION/DEVELOPMENT/SKELETON/GAP), and generate architecture reports with Mermaid diagrams. Use when asked to analyze codebase structure, find untested packages, or assess module maturity.
doc-extraction-naval-architecture
Layer 3 domain sub-skill for extracting naval architecture data from SNAME PNA, IMO stability codes, IACS structural rules, and classification society guidelines. Provides detection heuristics for stability constants, resistance equations, hull form coefficients, hydrostatic curves, IMO stability criteria, and structural scantling tables. type: reference
sparc-specification
SPARC Specification phase specialist for requirements analysis, constraint identification, use case definition, and acceptance criteria creation
sparc-refinement
SPARC Refinement phase specialist for iterative improvement through TDD, code optimization, refactoring, performance tuning, and quality improvement
sparc-pseudocode
SPARC Pseudocode phase specialist for algorithm design, data structure selection, complexity analysis, and design pattern identification
sparc-architecture
SPARC Architecture phase specialist for system design, component architecture, interface design, scalability planning, and technology selection
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
multi-tool-architecture-assessment
Systematic comparison of competing tools/approaches before committing to a multi-account, multi-tool architecture. Uses parallel subagents for research, system-state audit, and data quality analysis. Produces a decision matrix with explicit trade-offs.
modular-architecture-documentation
Systematically document multi-module system architectures including module boundaries, CLI commands, and architecture decisions.