architecture
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
npx skills add iOfficeAI/AionUi --skill architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Architecture Skill Determine correct file placement and structure for an Electron multi-process project. ## Detailed References - **Renderer layer** (components, hooks, utils, pages, CSS): [references/renderer.md](references/renderer.md) - **Main process & shared layer** (bridges, services, worker, preload): [references/process.md](references/process.md) - **Project root & monorepo layout** (directory structure, migration status): [references/project-layout.md](references/project-layout.md) --- ## Decision Tree — Where Does New Code Go? ``` Is it UI (React components, hooks, pages)? └── YES → packages/desktop/src/renderer/ → see references/renderer.md Is it an IPC handler responding to renderer calls? └── YES → packages/desktop/src/process/bridge/ → see references/process.md Is it business logic running in the main process? └── YES → packages/desktop/src/process/services/ → see references/process.md Is it an AI platform connection (API client, message protocol)? └── YES → packages/desktop/src/process/agent/<platform>/ Is it a background task that runs in a worker thread? └── YES → packages/desktop/src/process/worker/ Is it used by BOTH main and renderer processes? └── YES → packa
- Detailed References
- Decision Tree — Where Does New Code Go?
- Process Boundary Rules
- Naming Conventions
- Directories
- Files
- Structural Rules
- Test File Mapping
- Quick Checklist
What does the architecture skill do?
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
How do I install it?
Run `npx skills add iOfficeAI/AionUi --skill architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From iOfficeAI/AionUi, a repository with 31,403 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.