Claude Cursor opencode Skill

architecture

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

LLM Mart · 0 points · 3 views 0 listing impressions 0 install-command copies
Download vodailocz-kilo-kit-mcp-skills_engineering_architecture-0448e6c.zip · 6 KB

Install

skills CLI npx skills add https://github.com/VoDaiLocz/kilo-kit-mcp/tree/main/skills/engineering/architecture
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vodailocz-kilo-kit-mcp@llmmart
Git git clone https://github.com/VoDaiLocz/kilo-kit-mcp.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vodailocz/kilo-kit-mcp collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Architecture Decision Framework

"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."

🎯 Selective Reading Rule

Read ONLY files relevant to the request! Check the content map, find what you need.

File Description When to Read
context-discovery.md Questions to ask, project classification Starting architecture design
trade-off-analysis.md ADR templates, trade-off framework Documenting decisions
pattern-selection.md Decision trees, anti-patterns Choosing patterns
examples.md MVP, SaaS, Enterprise examples Reference implementations
patterns-reference.md Quick lookup for patterns Pattern comparison

🔗 Related Skills

Skill Use For
@[skills/database-design] Database schema design
@[skills/api-patterns] API design patterns
@[skills/deployment-procedures] Deployment architecture

Core Principle

"Simplicity is the ultimate sophistication."

  • Start simple
  • Add complexity ONLY when proven necessary
  • You can always add patterns later
  • Removing complexity is MUCH harder than adding it

Validation Checklist

Before finalizing architecture:

  • Requirements clearly understood
  • Constraints identified
  • Each decision has trade-off analysis
  • Simpler alternatives considered
  • ADRs written for significant decisions
  • Team expertise matches chosen patterns
Files (kilo-kit-mcp)
  • context-discovery.md 1.6 KB
    Loading…
  • examples.md 2.4 KB
    Loading…
  • pattern-selection.md 2.6 KB
    Loading…
  • patterns-reference.md 2.3 KB
    Loading…
  • SKILL.md 1.7 KB
    ---
    name: architecture
    description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
    allowed-tools: Read, Glob, Grep
    ---
    
    # Architecture Decision Framework
    
    > "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
    
    ## 🎯 Selective Reading Rule
    
    **Read ONLY files relevant to the request!** Check the content map, find what you need.
    
    | File | Description | When to Read |
    |------|-------------|--------------|
    | `context-discovery.md` | Questions to ask, project classification | Starting architecture design |
    | `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions |
    | `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns |
    | `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations |
    | `patterns-reference.md` | Quick lookup for patterns | Pattern comparison |
    
    ---
    
    ## 🔗 Related Skills
    
    | Skill | Use For |
    |-------|---------|
    | `@[skills/database-design]` | Database schema design |
    | `@[skills/api-patterns]` | API design patterns |
    | `@[skills/deployment-procedures]` | Deployment architecture |
    
    ---
    
    ## Core Principle
    
    **"Simplicity is the ultimate sophistication."**
    
    - Start simple
    - Add complexity ONLY when proven necessary
    - You can always add patterns later
    - Removing complexity is MUCH harder than adding it
    
    ---
    
    ## Validation Checklist
    
    Before finalizing architecture:
    
    - [ ] Requirements clearly understood
    - [ ] Constraints identified
    - [ ] Each decision has trade-off analysis
    - [ ] Simpler alternatives considered
    - [ ] ADRs written for significant decisions
    - [ ] Team expertise matches chosen patterns
    
  • trade-off-analysis.md 1.5 KB
    Loading…

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.