app-architecture

分类: 开发与编程 | 上传者: hrconsultnj | 下载: 0 | 版本: v1.0（最新）

用于构建从数据库到 UI 功能的完整架构指南。根据检测到的堆栈路由到前端/、全栈/、移动/、后端/或 sdks/。涵盖分解、多租户隔离、身份验证模型、查询模式和组件模式。

更新日志: Source: GitHub https://github.com/hrconsultnj/claude-plugins

目录结构

当前层级: tree/main/plugins/composure/skills/app-architecture/

📁 backend/
- 📁 c-cpp/
  - 📄 SKILL.md 2.4 KB
- 📁 go/
  - 📄 SKILL.md 1.7 KB
- 📁 python/
  - 📄 SKILL.md 2.0 KB
- 📁 rust/
  - 📄 SKILL.md 1.7 KB
- 📄 core.md 2.1 KB
- 📄 INDEX.md 1.5 KB
📁 frontend/
- 📁 angular/
  - 📄 angular.md 2.6 KB
- 📁 typescript/
  - 📁 data-patterns/
    
    📄 01-query-key-conventions.md 6.8 KB
    
    📄 02-component-patterns.md 8.8 KB
  - 📁 hooks/
    
    📄 cache-invalidation-guide.md 8.8 KB
    
    📄 common-patterns.md 17.9 KB
    
    📄 multi-tenant-patterns.md 13.9 KB
  - 📁 tanstack-query/
    
    📄 pattern-examples.md 7.3 KB
    
    📄 pattern-guide.md 6.5 KB
    
    📄 quick-reference.md 8.9 KB
  - 📄 01-component-decomposition.md 8.8 KB
  - 📄 02-tabs-and-views.md 11.0 KB
- 📁 vite/
  - 📄 vite.md 4.8 KB
- 📄 core.md 3.3 KB
- 📄 INDEX.md 2.3 KB
- 📄 react-best-practices.md 2.6 KB
- 📄 shadcn-conventions.md 3.4 KB
📁 fullstack/
- 📁 nextjs/
  - 📄 01-ssr-hydration-layout.md 15.6 KB
  - 📄 02-route-groups.md 8.9 KB
  - 📄 nextjs.md 2.8 KB
  - 📄 validation-rules.md 4.2 KB
- 📄 INDEX.md 902 B
📁 mobile/
- 📁 expo/
  - 📄 01-icon-patterns.md 4.5 KB
  - 📄 02-bottom-sheet-dynamic-sizing.md 5.0 KB
  - 📄 03-custom-ui-components.md 22.0 KB
  - 📄 expo.md 4.6 KB
- 📁 kotlin/
  - 📄 SKILL.md 2.6 KB
- 📁 swift/
  - 📄 SKILL.md 2.1 KB
- 📄 INDEX.md 1.2 KB
📁 sdks/
- 📄 ai-sdk-validation-rules.md 3.2 KB
- 📄 INDEX.md 914 B
📄 GENERATED-DOC-TEMPLATE.md 4.9 KB
📄 SKILL.md 9.2 KB

SKILL.md

---
name: app-architecture
description: Complete architecture guide for building features from database to UI. Routes to frontend/, fullstack/, mobile/, backend/, or sdks/ based on detected stack. Covers decomposition, multi-tenant isolation, auth model, query patterns, and component patterns.
---

# App Architecture — Index

**You MUST load framework-specific references before writing any code.** This is not optional. Your training data is 10+ months behind — the reference docs contain current API patterns from Context7.

> **This is the master barrel.** Detect the stack, then load ONLY the matching architecture files. Do NOT load everything.

## Step 1: Detect Stack

Read `.claude/no-bandaids.json` and extract:
- `frameworks` — which languages are in use
- `frontend` — which frontend framework (`"vite"`, `"nextjs"`, `"angular"`, `"expo"`, or `null`)
- `backend` — which backend framework (or `null`)

If the file is missing:
1. **Run `/composure:initialize`** to detect the stack and generate the config
2. If that's not possible, default to `typescript` with `frontend: null` — but warn the user: *"No `.claude/no-bandaids.json` found. Run `/composure:initialize` to detect your stack and generate framework-specific reference docs. Without it, only universal patterns are loaded."*

## Step 2: Route to Architecture Files

Based on the detected `frontend` value, load the matching INDEX.md which tells you exactly what files to read:

| `frontend` value | Load this INDEX | Then follow its MUST READ instructions |
|---|---|---|
| `"vite"` | [frontend/INDEX.md](frontend/INDEX.md) | `frontend/core.md` + `frontend/vite/vite.md` |
| `"angular"` | [frontend/INDEX.md](frontend/INDEX.md) | `frontend/core.md` + `frontend/angular/angular.md` |
| `"nextjs"` | [fullstack/INDEX.md](fullstack/INDEX.md) | `frontend/core.md` + `fullstack/nextjs/nextjs.md` + curated docs |
| `"expo"` | [mobile/INDEX.md](mobile/INDEX.md) | `frontend/core.md` + `mobile/expo/expo.md` + curated docs |
| `null` or other | [frontend/INDEX.md](frontend/INDEX.md) | `frontend/core.md` only |

**Always also load:**
- [frontend/core.md](frontend/core.md) — Points to curated reference docs (query patterns, hooks, decomposition)
- [backend/INDEX.md](backend/INDEX.md) → [backend/core.md](backend/core.md) — Database, RLS, auth model (if building data layer)
- [sdks/INDEX.md](sdks/INDEX.md) — Cross-cutting libraries if detected (AI SDK, Zod, Stripe, etc.)

## Step 3: Load Language-Specific Patterns

| Language | MUST Read |
|---|---|
| Python | `backend/python/SKILL.md` |
| Go | `backend/go/SKILL.md` |
| Rust | `backend/rust/SKILL.md` |
| C/C++ | `backend/c-cpp/SKILL.md` |
| Swift | `mobile/swift/SKILL.md` (only for native modules) |
| Kotlin | `mobile/kotlin/SKILL.md` (only for native modules) |

TypeScript patterns live in `frontend/typescript/` — loaded automatically via `frontend/INDEX.md`.

**Also load if `.claude/composure-pro.json` exists:**
- Composure Pro Patterns — read `pluginRoot` from the JSON, then load `data-patterns/` and `rls-policies/` from the plugin cache. Licensed templates for multi-tenant Supabase architecture. If not available, `backend/core.md` provides conceptual guidance.

## Step 4: Load Project-Level Docs

Check if `.claude/frameworks/` exists in the project. If it does, load docs from there too:

```
.claude/frameworks/{category}/{framework}/generated/  ← Context7 docs for this project
.claude/frameworks/{category}/{framework}/project/     ← team-written conventions
```

**Plugin and project docs are complementary — read BOTH, never discard.**

| # | Source | What | Why |
|---|--------|------|-----|
| 1 | Plugin | Category `INDEX.md` + curated docs | Battle-tested patterns (hooks, decomposition, query patterns) |
| 2 | Plugin | Framework-specific files + co-located curated docs | e.g., `fullstack/nextjs/nextjs.md` + `01-ssr-hydration-layout.md` |
| 3 | Plugin | Language `SKILL.md` | Anti-patterns for the detected language |
| 4 | Plugin | Composure Pro Patterns (if `.claude/composure-pro.json` exists) | Licensed Pro patterns — read from `pluginRoot` in JSON |
| 5 | Project | `.claude/frameworks/{category}/{framework}/generated/` | Context7 docs — may have newer API versions |
| 6 | Project | `.claude/frameworks/{category}/{framework}/project/` | Team conventions, decisions, overrides |

**When plugin and project docs cover the same topic:**
- **Read both.** Project docs may have newer API patterns. Plugin docs have architectural rules Context7 doesn't provide.
- **If they conflict on a specific API**, prefer the project doc — it was generated against the project's actual version.
- **Never skip plugin docs** just because project docs exist.

**To generate project docs:** Run `/composure:initialize --force`

---

## Directory Structure

```
skills/app-architecture/                  ← PLUGIN (curated, battle-tested)
├── SKILL.md                              ← You are here (thin router)
├── GENERATED-DOC-TEMPLATE.md             ← Template for Context7 agent output
│
├── frontend/                             ← Web frontend + shared TypeScript patterns
│   ├── INDEX.md
│   ├── core.md                           ← Routing file (points to typescript/)
│   ├── typescript/                       ← Curated: TanStack Query, hooks, data patterns
│   ├── vite/vite.md                      ← Phase 5+7 for Vite SPA
│   └── angular/angular.md               ← Phase 5+7 for Angular
│
├── fullstack/                            ← Full-stack web frameworks
│   ├── INDEX.md
│   └── nextjs/
│       ├── nextjs.md                     ← Phase 5+7 for Next.js
│       ├── 01-ssr-hydration-layout.md    ← Curated
│       └── 02-route-groups.md            ← Curated
│
├── mobile/                               ← Mobile frameworks
│   ├── INDEX.md
│   ├── swift/SKILL.md                    ← Native module language
│   ├── kotlin/SKILL.md                   ← Native module language
│   └── expo/
│       ├── expo.md                       ← Phase 5+7 + anti-patterns
│       ├── 01-icon-patterns.md           ← Curated
│       ├── 02-bottom-sheet-dynamic-sizing.md
│       └── 03-custom-ui-components.md
│
├── backend/                              ← Backend concerns + languages
│   ├── INDEX.md
│   ├── core.md                           ← Phases 1-2 (database, RLS, auth)
│   ├── python/SKILL.md
│   ├── go/SKILL.md
│   ├── rust/SKILL.md
│   └── c-cpp/SKILL.md
│
├── sdks/                                 ← Cross-cutting libraries
│   └── INDEX.md
│
└── references/
    └── private/                          ← Licensed patterns (git submodule)
```

```
.claude/frameworks/                       ← PROJECT (Context7 generated + team-written)
├── frontend/
│   ├── generated/                        ← typescript, shadcn, tailwind, tanstack-query
│   └── project/                          ← team conventions
├── fullstack/nextjs/
│   ├── generated/                        ← nextjs
│   └── project/
├── mobile/expo/
│   ├── generated/                        ← expo-sdk
│   └── project/
├── backend/supabase/
│   ├── generated/                        ← supabase-js
│   └── project/
└── sdks/
    ├── generated/                        ← ai-sdk, zod
    └── project/
```

---

## Quick Reference: The 7-Phase Workflow

```
Phase 1: Database     → backend/core.md
Phase 2: Auth Model   → backend/core.md
Phase 3: Query Keys   → frontend/core.md → frontend/typescript/
Phase 4: Query Hooks  → frontend/core.md → frontend/typescript/
Phase 5: App Shell    → fullstack/nextjs/ | frontend/vite/ | mobile/expo/
Phase 6: Page         → frontend/core.md → frontend/typescript/
Phase 7: Navigation   → fullstack/nextjs/ | frontend/vite/ | mobile/expo/
```

---

## Code Quality Toolchain

| Tool | How to use | When | Output |
|------|-----------|------|--------|
| **Automatic hook** | Fires on Read/Edit/Write | Logs tasks to `tasks-plans/tasks.md` silently | `tasks-plans/tasks.md` |
| `/decomposition-audit` | Invoke manually | Full codebase audit for size violations | `tasks-plans/decomposition-audit-{date}.md` |
| `/review-tasks` | Invoke manually | Process tasks from both sources | TaskCreate entries |
| `/review-tasks sync` | Invoke at session start | Load pending tasks into current session | TaskCreate entries |
| `/review-tasks delegate` | Invoke to execute | Dispatch parallel sub-agents to fix | Completed tasks |
| `find_large_functions_tool` | MCP tool (code-review-graph) | Query AST graph for oversized functions | Direct query results |

### /simplify Integration

After editing 5+ source files in a session, the PostToolUse hook will inject a systemMessage asking you to offer `/simplify` to the user. When you receive this message:

1. **Use AskUserQuestion** — ask: "Want me to run /simplify to refine what I just wrote before continuing?"
2. **Do NOT auto-run** — the user decides
3. `/simplify` preserves all functionality — it only refines *how* code is written, never *what* it does.

登录后下载/点赞/收藏 ❤ 61 | ★ 0

app-architecture

目录结构

SKILL.md

举报内容

提示