athola/architecture-aware-init
plugins/attune/skills/architecture-aware-init/SKILL.md
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market architecture-aware-initInstall 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: Jun 8, 2026, 3:25 AM223.4s5 files scanned
SKILL.md
- name:
- architecture-aware-init
- description:
- Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
- alwaysApply:
- false
- category:
- project-initialization
- - archetypes:
- architecture-paradigms
- tools:
- []
- complexity:
- advanced
- model_hint:
- deep
- estimated_tokens:
- 1800
- progressive_loading:
- true
Architecture-Aware Project Initialization
Overview
Project initialization that combines online research, archetype selection, template customization, and decision documentation into one workflow. Use this skill when the architecture is undecided and the choice deserves justification.
When to Use This Skill
- Starting a new project and unsure which architecture fits best
- Wanting modern, industry-standard architecture choices
- Needing justification for architectural decisions
- Wanting templates customized to the chosen paradigm
Use instead of project-init when architecture is undecided.
Use before project-specification to establish the
architectural foundation.
Required TodoWrite Items
arch-init:research-completed: Online research completedarch-init:paradigm-selected: Architecture paradigm chosenarch-init:templates-customized: Templates adapted to paradigmarch-init:decision-recorded: ADR created
5-Step Workflow
Steps 1-2: Gather context, research best practices
Load modules/research-flow.md for the full project-context
questionnaire and the three-tier search strategy. Output: a
synthesis brief that feeds Step 3.
Step 3: Select the architecture paradigm
Load modules/paradigm-selection.md for the decision matrix
(team size by domain complexity) and the special-case overrides
(streaming, serverless, microkernel, etc.). Two routes:
- Use the
archetypes:architecture-paradigmsskill for guided exploration. - Use the matrix directly for a fast recommendation.
Step 4-5: Customize templates and record the decision
Load modules/scaffold-generation.md for the paradigm-specific
directory layouts (Functional Core / Hexagonal / Microservices
shown; others delegated to the corresponding
archetypes:architecture-paradigm-{name} skill) and the ADR
template.
Output: Initialization Package
After completing the workflow, the project has:
- A directory structure matched to the chosen architecture
- Configuration that reflects the paradigm (test layout, tooling, dependency hints)
- An ADR explaining why this paradigm was chosen
- Links to the relevant paradigm skill for ongoing implementation guidance
- References to similar real-world projects from Step 2
Script Integration
The interactive workflow above is the default. For automation,
load modules/script-integration.md for the three Python
helpers under plugins/attune/scripts/ (architecture researcher,
template customizer, full interactive flow) and library-style
import examples.
Integration with Existing Commands
This skill enhances /attune:project-init by adding an
architecture-selection phase before scaffolding:
# Standard initialization (no architecture decision)
/attune:project-init --lang python --name my-project
# Architecture-aware initialization
/attune:brainstorm # Explore project needs
Skill(architecture-aware-init) # Select architecture
/attune:project-init --arch <paradigm> --name my-project
Example Session
User: "I'm creating a Python web API for a fintech application. Team of 8 developers, complex business rules, need high security and audit trails."
- Step 1 context: Web API, highly complex domain, 5-15 engineers, security and auditability requirements.
- Step 2 research: queries for fintech API patterns, audit-trail architecture, CQRS+ES Python examples.
- Step 3 selection: research plus decision matrix yields CQRS + Event Sourcing.
- Step 4 templates: command-handler module, query-handler module, event store, aggregate patterns, projection handlers.
- Step 5 ADR: documents why CQRS/ES fits (auditability, complex rules, regulatory compliance).
Result: project initialized with paradigm-appropriate structure and clear decision rationale.
Related Skills
Skill(archetypes:architecture-paradigms): paradigm catalogSkill(archetypes:architecture-paradigm-*): per-paradigm implementation guidanceSkill(attune:project-brainstorming): ideation before architectureSkill(attune:project-specification): requirements after the paradigm is chosen
See Also
/attune:project-init: basic project initialization/attune:blueprint: architecture planning after paradigm selectionplugins/archetypes/README.md: full paradigm reference
Related Skills
athola/ideate
research
VerifiedTrustedCommunity
Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.
304SKILL.mdUpdated Jun 8, 2026
athola/plugins/sanctum/skills/validate-pr
tools
VerifiedTrustedCommunity
--- name: validate-pr description: Use when you need a diff-derived test plan for a PR: reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions. alwaysApply: false category: validation tags: - pr - validation - test-plan - diff - revert-test - evidence tools: [] usage_patterns: - diff-derived-test-plan - revert-test-quality-check - evidence-capture complexity: intermediate model_hint: standard estimated_tokens: 650
304SKILL.mdUpdated Jun 8, 2026
athola/decision-journal
development
VerifiedTrustedCommunity
Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.
304SKILL.mdUpdated Jun 8, 2026
athola/graduated-implementation
development
VerifiedTrustedCommunity
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.
304SKILL.mdUpdated Jun 8, 2026