pkuppens/architecture-runtime
skills/architecture/architecture-runtime/SKILL.md
Documents runtime behaviour: technical execution paths, component interactions, sequences (arc42 §6). Use when documenting flows or tracing execution.
testing
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add pkuppens/pkuppens architecture-runtimeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 7:57 AM15.8s1 file scanned
SKILL.md
- name:
- architecture-runtime
- description:
- Documents runtime behaviour: technical execution paths, component interactions, sequences (arc42 §6). Use when documenting flows or tracing execution.
Architecture Runtime
Documents technical execution paths through components and services. Aligns with arc42 §6 (runtime view). Contrast with user flows (UX journey) — see design-consult for user flow documentation.
When to use
- Documenting critical execution paths
- When new features add significant flows
- Debugging complex interactions
Outputs
docs/architecture/03-runtime-flows.md— append/update scenariodocs/architecture/diagrams/sequences.mmd— sequence diagram
Flow scenario format
For each scenario in 03-runtime-flows.md:
- Trigger — what initiates; entry point; preconditions
- Step-by-step — technical sequence (HTTP → Controller → Service → DB)
- Components involved — links to component docs
- Data touched — tables, cache, external APIs
- Error handling — what can fail; retries; fallbacks
- Observability — logs, metrics, traces
Selection criteria
Prioritise: MVP smoke test path; most frequently executed; business-critical; complex (multi-component); error-prone.
Sequence diagram
Use Mermaid sequenceDiagram with participants, messages, returns, error paths.
Update rules
- Document actual code paths; cite evidence
- Link to component docs
- Show success and error paths
Integration
- Parent: architecture.
- Complements architecture-building-blocks for component details.
Related Skills
pkuppens/azure-devops-work-items
tools
VerifiedTrustedCommunity
Creates, queries, updates, and links Azure Boards work items via az boards CLI. Use when filing ADO work items, running WIQL queries, or setting area path, iteration, tags, and assignee.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-repos
tools
VerifiedTrustedCommunity
Creates, reviews, and completes Azure Repos pull requests and branch policies via az repos CLI. Use when opening ADO PRs, setting required reviewers, or configuring build validation policies.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-pipelines
development
VerifiedTrustedCommunity
Guides Azure Pipelines YAML structure, build validation on PRs, and staged deployment with environments and approvals. Use when authoring azure-pipelines.yml or configuring CI/CD on Azure DevOps.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops
tools
VerifiedTrustedCommunity
Orchestrates Azure DevOps work item, repo, and pipeline workflows using az CLI. Use when working with Azure DevOps, Azure Repos, Azure Boards, Azure Pipelines, or az devops commands.
SKILL.mdUpdated May 29, 2026