Skip to content

smorky850612/Aurakit / skills/aura

All-in-one fullstack dev engine. /aura: 46 modes (build/fix/clean/deploy/review/spec/lore/ax/experiment/payment/debug/qa/orchestrate/escalate+), 6-layer security with 32 hooks, tiered models (ZERO/ECO/PRO/MAX), 8 languages, 16 specialized agents, SPEC/EARS/TRUST5/XLOOP/RALF/Autopus absorbed. ~55% token savings.

FileKindSize
SKILL.mdskill md29.2 KB
resources/agent-security.mdmarkdown4.2 KB
resources/agent-spawning.mdmarkdown5.9 KB
resources/agent-team.mdmarkdown5.7 KB
resources/archive-pipeline.mdmarkdown3.5 KB
resources/autopus-agent-teams.mdmarkdown6.8 KB
resources/autopus-ax-annotation.mdmarkdown6.1 KB
resources/autopus-executor-profiles.mdmarkdown9.9 KB
resources/autopus-experiment-loop.mdmarkdown5.9 KB
resources/autopus-lore-commit.mdmarkdown6.0 KB
resources/autopus-pipeline-v2.mdmarkdown8.5 KB
resources/autopus-spec-system.mdmarkdown4.8 KB
resources/autopus-validator-gates.mdmarkdown7.0 KB
resources/autopus-worktree-isolation.mdmarkdown4.6 KB
resources/baas-pipeline.mdmarkdown3.8 KB
resources/batch-pipeline.mdmarkdown4.9 KB
resources/brainstorming.mdmarkdown4.7 KB
resources/branch-finishing.mdmarkdown4.7 KB
resources/build-pipeline.mdmarkdown12.0 KB
resources/build-resolvers-cpp.mdmarkdown10.0 KB
resources/build-resolvers-go.mdmarkdown1.2 KB
resources/build-resolvers-java.mdmarkdown9.1 KB
resources/build-resolvers-kotlin.mdmarkdown8.7 KB
resources/build-resolvers-python.mdmarkdown9.0 KB
resources/build-resolvers-rust.mdmarkdown1.2 KB
resources/build-resolvers-swift.mdmarkdown11.9 KB
resources/build-resolvers.mdmarkdown1.6 KB
resources/business-skills.mdmarkdown7.0 KB
resources/cache-engineering.mdmarkdown6.6 KB
resources/clean-pipeline.mdmarkdown6.5 KB
resources/common-protocol.mdmarkdown7.4 KB
resources/config-schema.mdmarkdown3.0 KB
resources/cross-harness.mdmarkdown16.6 KB
resources/deploy-enterprise.mdmarkdown9.0 KB
resources/deploy-pipeline.mdmarkdown6.9 KB
resources/design-pipeline.mdmarkdown3.2 KB
resources/desktop-pipeline.mdmarkdown3.5 KB
resources/discovery-protocol.mdmarkdown3.3 KB
resources/e2e-pipeline.mdmarkdown7.7 KB
resources/explain-pipeline.mdmarkdown972 B
resources/fix-pipeline.mdmarkdown5.6 KB
resources/framework-patterns.mdmarkdown8.3 KB
resources/gap-check.mdmarkdown3.4 KB
resources/install-guide.mdmarkdown3.4 KB
resources/instinct-system.mdmarkdown6.8 KB
resources/iterate-pipeline.mdmarkdown2.5 KB
resources/language-reviewers.mdmarkdown18.5 KB
resources/loop-pipeline.mdmarkdown3.5 KB
resources/mcp-configs.mdmarkdown4.7 KB
resources/migrate-pipeline.mdmarkdown1.5 KB
resources/mobile-pipeline.mdmarkdown3.5 KB
resources/mode-reference.mdmarkdown6.1 KB
resources/model-routing.mdmarkdown9.1 KB
resources/orchestration-patterns.mdmarkdown5.9 KB
resources/payment-lemonsqueezy.mdmarkdown5.6 KB
resources/payment-pipeline.mdmarkdown10.6 KB
resources/payment-polar.mdmarkdown3.6 KB
resources/payment-steppay.mdmarkdown4.8 KB
resources/payment-stripe.mdmarkdown6.7 KB
resources/payment-toss.mdmarkdown7.2 KB
resources/pipeline-guide.mdmarkdown6.1 KB
resources/plan-pipeline.mdmarkdown2.4 KB
resources/pm-pipeline.mdmarkdown4.5 KB
resources/qa-pipeline.mdmarkdown8.8 KB
resources/report-pipeline.mdmarkdown3.0 KB
resources/review-pipeline.mdmarkdown8.0 KB
resources/rollback-pipeline.mdmarkdown1.3 KB
resources/security-rules.mdmarkdown17.5 KB
resources/snippets-guide.mdmarkdown4.6 KB
resources/status-dashboard.mdmarkdown5.3 KB
resources/style-guide.mdmarkdown2.7 KB
resources/systematic-debugging.mdmarkdown5.7 KB
resources/tdd-pipeline.mdmarkdown4.4 KB

resources/design-pipeline.md

View on GitHub
# AuraKit — DESIGN Pipeline (설계 문서 모드)

> `/aura design:` 또는 `/aura design:[기능명]` 호출 시 로딩.
> DB 스키마, API 명세, 컴포넌트 구조 설계 문서화.
> PLAN 완료 후, BUILD 전에 실행하는 설계 단계.

---

## 역할

- 기술 설계 명세서 생성 (구현 없음)
- 산출물: `.aura/docs/design-[기능명].md`
- 이후 `/aura build:` 시 이 설계를 기준으로 구현

---

## 실행 순서

### Step 1 — 프로젝트 프로필 + Plan 문서 로딩

```
.aura/project-profile.md → 스택, DB 종류 확인
.aura/docs/plan-[기능명].md → Plan 내용 참조 (있으면)
```

### Step 2 — 3 Worker 병렬 설계 [필수]

```
Worker-DB   Agent(model="sonnet") — ECO/PRO 기준   → DB 스키마 설계
Worker-API  Agent(model="sonnet") — ECO/PRO 기준   → API 명세 설계
Worker-UI   Agent(model="haiku")  ← ECO 필수       → 컴포넌트 트리 설계

→ 3개 동시 실행 → 결과 취합 → 설계 문서 합성
```

### Step 3 — 설계 문서 작성

```markdown
# Design: [기능명]

## DB 스키마

### [테이블명]
| 컬럼 | 타입 | 제약 | 설명 |
|------|------|------|------|
| id | UUID | PK, NOT NULL | |
| created_at | TIMESTAMP | NOT NULL | |

### 인덱스
- [테이블].[컬럼] — [이유]

### 관계
- [테이블A] 1:N [테이블B] via [foreign key]

---

## API 명세

### POST /api/[resource]
- 인증: Bearer JWT
- Request Body:
  ```json
  {
    "field": "type"
  }
  ```
- Response 200:
  ```json
  {
    "success": true,
    "data": {}
  }
  ```
- Error Cases:
  - 400: 입력 검증 실패
  - 401: 인증 없음
  - 500: 서버 오류

### GET /api/[resource]/[id]
...

---

## 컴포넌트 트리

```
[PageComponent]
  ├── [HeaderComponent]
  ├── [MainComponent]
  │   ├── [ListComponent]
  │   │   └── [ItemComponent]
  │   └── [FormComponent]
  └── [FooterComponent]
```

### 상태 관리
- 전역: [Zustand/Redux store 구조]
- 로컬: [컴포넌트별 useState]

### Props 인터페이스
```typescript
interface [ComponentName]Props {
  [prop]: [type]
}
```

---

## 보안 설계
- 인증: [방식]
- 인가: [권한 체계]
- 입력 검증: [zod 스키마]

---

## 다음 단계
- [ ] `/aura build:[기능명]` — 이 설계 기반으로 구현
```

### Step 4 — 파일 저장

```bash
mkdir -p .aura/docs
# 파일명: design-[kebab-case-기능명].md
```

### Step 5 — 완료 출력

```
✅ DESIGN 완료 — [기능명]
저장: .aura/docs/design-[기능명].md

📐 설계 요약:
  DB: [N]개 테이블
  API: [N]개 엔드포인트
  컴포넌트: [N]개

다음: /aura build:[기능명]
```

---

## 에이전트 배정

| 에이전트 | 모델 | 역할 |
|---------|------|------|
| Worker-DB | sonnet/opus(MAX) | DB 스키마 설계 |
| Worker-API | sonnet/opus(MAX) | API 명세 설계 |
| Worker-UI | haiku/sonnet(PRO)/opus(MAX) | 컴포넌트 트리 설계 |

ECO: Worker-UI → haiku (절약). PRO/MAX: 전체 sonnet/opus.

---

## 빠른 시작

```bash
/aura design:소셜 로그인
/아우라 design:결제 시스템
/aura pro design:마이크로서비스 API
```

---

*AuraKit DESIGN — 3-Worker 병렬 기술 설계, 구현 없음*
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall