architecture-design

Define and optimize chip architectures from requirements to modular decomposition.

2|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/tangyangchao578-art/icer_skill_package --skill architecture-design-tangyangchao578-art
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-design
Source: https://github.com/tangyangchao578-art/icer_skill_package/tree/main/skills/architecture-design
Command: npx skills add https://github.com/tangyangchao578-art/icer_skill_package --skill architecture-design-tangyangchao578-art

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chip architecture design is the process of turning high-level requirements into a modular, scalable SoC blueprint. This skill provides a repeatable framework, templates, and decision criteria to guide architecture from concept to implementation, reducing risk and rework.

Core Features & Use Cases

  • System-level requirement-to-module decomposition and interface planning.
  • Trade-off analysis across PPA (power, performance, area) and risk assessment.
  • Architecture documentation, top-down module budget, and clock/reset strategy.

Quick Start

Define a top-level SoC goal and generate a module partitioning plan using the skill's guidelines.

Frequently Asked Questions about architecture-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a chip architecture from high-level requirements to module partitioning?

Chip architecture planning translates high-level requirements into a modular SoC blueprint by applying top-down decomposition, module scoping, and standardized interface definitions. This framework reduces risk and rework by providing repeatable templates and decision criteria.

What is the best way to perform PPA trade-off analysis during SoC design?

PPA trade-off analysis evaluates power, performance, and area constraints against design risk during SoC development. It uses standardized decision criteria to optimize the chip architecture and balance module budgets before implementation begins.

How do I define clock, reset, and power domain strategies for a new SoC architecture?

Defining clock, reset, and power domain strategies involves planning timing, resets, and power domains during the architecture phase. This ensures the SoC blueprint addresses power and area budgeting constraints systematically.

Can I use this architecture design framework for top-down module decomposition and interface planning?

Yes, this framework supports top-down module decomposition and interface planning by generating a structured module partitioning plan. It defines standardized interfaces and scopes modules from a top-level SoC goal.

What limitations exist when defining chip architecture blueprints for complex SoC designs?

The framework focuses on architecture-level planning, trade-off analysis, and documentation, meaning it does not handle lower-level RTL coding or physical layout implementation. It guides conceptualization to modular decomposition rather than detailed circuit design.

Why does SoC module partitioning require standardized interface definitions and risk assessment?

SoC module partitioning requires standardized interface definitions to ensure seamless module integration and communication. Risk assessment during this phase identifies potential architectural bottlenecks early, reducing rework.