@tinkcarlos/skillora 0.2.0

package/.claude/skills/fullstack-developer/references/phase-gate-template.md

@@ -0,0 +1,249 @@
+# Phase Gate Templates
+
+> Verify completion of each phase before proceeding.
+
+## General Phase Gate
+
+```markdown
+# Phase Gate: [Phase Name]
+
+## Date: [YYYY-MM-DD]
+## Phase: [1-7] of [Total]
+
+---
+
+## 1. Task Completion
+
+| Task ID | Description | Status | Notes |
+|---------|-------------|--------|-------|
+| T-001 | [Description] | ✅ Done | |
+| T-002 | [Description] | ✅ Done | |
+| T-003 | [Description] | ⚠️ Partial | [What's missing] |
+
+**Completion Rate**: X/Y tasks (Z%)
+
+---
+
+## 2. Test Results
+
+### Automated Tests
+| Type | Passed | Failed | Skipped | Coverage |
+|------|--------|--------|---------|----------|
+| Unit | 45 | 0 | 2 | 85% |
+| Integration | 12 | 0 | 0 | N/A |
+| E2E | 5 | 0 | 0 | N/A |
+
+### Manual Tests
+| Test | Result | Notes |
+|------|--------|-------|
+| Happy path | ✅ Pass | |
+| Error handling | ✅ Pass | |
+| Edge cases | ⚠️ Partial | [What wasn't tested] |
+
+---
+
+## 3. Quality Checks
+
+| Check | Status | Details |
+|-------|--------|---------|
+| No console errors | ✅ | |
+| No TypeScript errors | ✅ | |
+| Linting passes | ✅ | |
+| No security warnings | ✅ | |
+| No deprecated APIs | ✅ | |
+
+---
+
+## 4. Issues Found
+
+| ID | Severity | Description | Status | Resolution |
+|----|----------|-------------|--------|------------|
+| BUG-001 | Critical | [Description] | ✅ Fixed | [How fixed] |
+| BUG-002 | Minor | [Description] | ⏸️ Deferred | [Why deferred] |
+
+---
+
+## 5. Phase-Specific Verification
+
+### For Backend Phase:
+- [ ] All endpoints implemented
+- [ ] Swagger documentation complete
+- [ ] Unit tests pass (>80% coverage)
+- [ ] Integration tests pass
+- [ ] No N+1 queries
+- [ ] Error responses implemented
+
+### For Frontend Phase:
+- [ ] All components render
+- [ ] All interactions work
+- [ ] Mock API integration works
+- [ ] Loading states implemented
+- [ ] Error states implemented
+- [ ] Responsive design verified
+
+### For Integration Phase:
+- [ ] Real API calls work
+- [ ] Data contracts match
+- [ ] Auth flows work
+- [ ] Error handling works end-to-end
+
+---
+
+## 6. Decision
+
+### Gate Status
+
+- [ ] ✅ **PASS** - All criteria met, proceed to next phase
+- [ ] ⚠️ **CONDITIONAL PASS** - Proceed with noted items
+- [ ] ❌ **FAIL** - Must resolve issues before proceeding
+
+### Conditions (if applicable)
+1. [Condition to address in next phase]
+2. [Known limitation accepted]
+
+### Blockers (if failing)
+1. [What must be fixed]
+2. [Who is responsible]
+3. [Target resolution date]
+
+---
+
+## 7. Sign-off
+
+- [ ] Developer verified
+- [ ] Tests verified
+- [ ] Ready for next phase
+```
+
+---
+
+## Quick Gate Checklists
+
+### Backend Phase Gate
+
+```markdown
+## Backend Phase Gate ✓
+
+### Endpoints
+- [ ] All CRUD operations work
+- [ ] Request validation works
+- [ ] Response format correct
+- [ ] Error responses implemented
+
+### Documentation
+- [ ] Swagger UI accessible
+- [ ] All endpoints documented
+- [ ] Schemas complete
+- [ ] Examples provided
+
+### Testing
+- [ ] Unit tests pass (>80%)
+- [ ] Integration tests pass
+- [ ] No console errors
+- [ ] No security issues
+
+### Performance
+- [ ] Response times <500ms
+- [ ] No N+1 queries
+- [ ] Indexes created
+
+**GATE**: [ ] PASS  [ ] FAIL
+```
+
+### Frontend Phase Gate
+
+```markdown
+## Frontend Phase Gate ✓
+
+### Components
+- [ ] All components render
+- [ ] No console errors
+- [ ] No TypeScript errors
+- [ ] Props documented
+
+### States
+- [ ] Default state works
+- [ ] Loading state shows
+- [ ] Error state shows
+- [ ] Empty state shows
+
+### Interactions
+- [ ] All buttons work
+- [ ] All inputs work
+- [ ] All forms submit
+- [ ] All modals open/close
+
+### Responsive
+- [ ] Mobile (320px)
+- [ ] Tablet (768px)
+- [ ] Desktop (1024px)
+
+### Mock API
+- [ ] All endpoints mocked
+- [ ] Data displays correctly
+- [ ] Errors simulated
+
+**GATE**: [ ] PASS  [ ] FAIL
+```
+
+### Integration Phase Gate
+
+```markdown
+## Integration Phase Gate ✓
+
+### API Connection
+- [ ] Base URL configured
+- [ ] Auth tokens sent
+- [ ] Real data received
+- [ ] Real data displayed
+
+### Data Contract
+- [ ] Field names match
+- [ ] Types match
+- [ ] Nested objects work
+- [ ] Arrays work
+
+### Error Handling
+- [ ] 400 errors handled
+- [ ] 401 errors handled
+- [ ] 404 errors handled
+- [ ] 500 errors handled
+- [ ] Network errors handled
+
+### Edge Cases
+- [ ] Empty responses
+- [ ] Large datasets
+- [ ] Slow responses
+- [ ] Timeout handling
+
+**GATE**: [ ] PASS  [ ] FAIL
+```
+
+---
+
+## Bug Tracking During Gate
+
+```markdown
+## Bugs Found at [Phase] Gate
+
+### Critical (Must fix now)
+| Bug | Description | Resolution |
+|-----|-------------|------------|
+| | | |
+
+### Major (Fix before final)
+| Bug | Description | Target Phase |
+|-----|-------------|--------------|
+| | | |
+
+### Minor (Nice to fix)
+| Bug | Description | Priority |
+|-----|-------------|----------|
+| | | |
+
+### Action Required
+- [ ] All critical bugs fixed
+- [ ] Bug tracking updated
+- [ ] Regression tests added
+```
+

package/.claude/skills/fullstack-developer/references/post-edit-quality-gate.md

@@ -0,0 +1,30 @@
+# Post-Edit Quality Gate
+
+Every code modification must pass format + lint check before proceeding.
+
+## Workflow
+
+```
+Code Change → Format → Lint Check → Fix P0/P1 → Proceed
+```
+
+## Scripts
+
+| Script | Command |
+|--------|---------|
+| Format | `python scripts/format_code.py <file>` |
+| Format (dir) | `python scripts/format_code.py --dir src/` |
+| Lint | `python scripts/lint_check.py <file>` |
+| Lint + Fix | `python scripts/lint_check.py <file> --fix` |
+| IDE Lints | `read_lints(paths: ["<file>"])` |
+
+## Priority
+
+| Level | Examples | Action |
+|-------|----------|--------|
+| 🔴 P0 | Syntax errors | Must fix immediately |
+| 🟠 P1 | Type/import errors | Must fix before commit |
+| 🟡 P2 | Unused vars, warnings | Should fix |
+| ⚪ P3 | Style nits | Optional |
+
+**Rule**: Zero P0/P1 before proceeding.

package/.claude/skills/fullstack-developer/references/python-engineering.md

@@ -0,0 +1,79 @@
+# Python Engineering Reference
+
+## Scope
+This reference collects authoritative Python standards and practices used by the
+fullstack-developer skill when working on Python codebases.
+
+## Style and Readability (PEP 8, PEP 20)
+- Use 4-space indentation; spaces preferred.
+- Keep lines at or below 79 chars (docstrings/comments at or below 72) unless
+  project standards say otherwise.
+- Group imports: standard library, third-party, local; one per line.
+- Prefer readability and explicitness.
+
+## Docstrings (PEP 257)
+- Use triple double quotes for docstrings.
+- One-line docstrings are imperative, end with a period, and do not repeat the
+  signature.
+- Multi-line docstrings use a summary line, a blank line, then details; document
+  args, returns, side effects, and exceptions.
+
+## Type Hints (PEP 484, typing docs)
+- Type hints are optional and not enforced at runtime.
+- Annotate public functions; __init__ should return None.
+- Use typing for generics; use typing_extensions for backports.
+- Keep annotations simple and static for tool compatibility.
+
+## Exceptions (Python tutorial, built-in exceptions)
+- Catch specific exceptions; allow unexpected ones to propagate.
+- Use `raise ... from ...` when wrapping errors to preserve context.
+- Derive custom exceptions from Exception, not BaseException.
+
+## Logging (logging module, logging cookbook)
+- Use module-level loggers: `logger = logging.getLogger(__name__)`.
+- Configure logging in the application entry point.
+- Avoid attaching handlers in libraries; rely on hierarchy/propagation.
+- Avoid print for production diagnostics.
+
+## Environments and Packaging (venv, PyPA packaging guide)
+- Use `python -m venv .venv`; do not commit venv directories.
+- Recreate environments from requirements or pyproject.
+- Use `pyproject.toml` for build metadata and backend configuration.
+
+## Performance and Profiling (timeit, cProfile)
+- Use timeit for microbenchmarks; prefer repeat and the minimum result.
+- Use cProfile and pstats for profiling long-running code.
+- Profile before optimizing; do not use profilers for benchmarking.
+
+## Security Considerations (security warnings, pickle)
+- Never unpickle data from untrusted sources.
+- Logging configuration uses eval; treat untrusted configs as unsafe.
+- Use secrets for security-sensitive randomness.
+
+## Common Pitfalls and Fixes
+- Broad except blocks: catch specific exceptions and re-raise if needed.
+- Premature optimization: profile with timeit/cProfile before changing code.
+- Duplicate logs: configure handlers only at the application entry point.
+- Missing packaging metadata: add a minimal pyproject.toml early.
+
+## Verification
+- Style: run formatter/linter configured by the project.
+- Types: run the configured type checker if present.
+- Performance: use timeit or cProfile as appropriate.
+
+## Sources (accessed 2025-12-25)
+- PEP 8 - Style Guide for Python Code: https://peps.python.org/pep-0008/
+- PEP 20 - The Zen of Python: https://peps.python.org/pep-0020/
+- PEP 257 - Docstring Conventions: https://peps.python.org/pep-0257/
+- PEP 484 - Type Hints: https://peps.python.org/pep-0484/
+- typing - Support for type hints: https://docs.python.org/3/library/typing.html
+- Errors and Exceptions tutorial: https://docs.python.org/3/tutorial/errors.html
+- Built-in Exceptions: https://docs.python.org/3/library/exceptions.html
+- logging - Logging facility: https://docs.python.org/3/library/logging.html
+- Logging Cookbook: https://docs.python.org/3/howto/logging-cookbook.html
+- venv - Creation of virtual environments: https://docs.python.org/3/library/venv.html
+- Packaging Python Projects: https://packaging.python.org/en/latest/tutorials/packaging-projects/
+- timeit - Measure execution time: https://docs.python.org/3/library/timeit.html
+- The Python Profilers: https://docs.python.org/3/library/profile.html
+- Security Considerations: https://docs.python.org/3/library/security_warnings.html
+- pickle - Python object serialization: https://docs.python.org/3/library/pickle.html

package/.claude/skills/fullstack-developer/references/skill-orchestration.md

@@ -0,0 +1,214 @@
+# 多技能协作协议 (Multi-Skill Orchestration Protocol)
+
+本文档定义了全栈开发过程中何时、如何调用其他技能以实现完整、规范的开发。
+
+## 核心原则
+
+**单一技能无法完成完美的开发工作。** 全栈开发涉及多个领域：前端设计、后端架构、数据库设计、API 设计、测试、代码审查等。本协议确保在正确的时机调用正确的技能。
+
+## 技能路由表 (Skill Router)
+
+### 开发任务类型 → 推荐技能组合
+
+| 任务类型 | 主技能 | 协作技能 | 调用时机 |
+|----------|--------|----------|----------|
+| **新功能开发 (全栈)** | `fullstack-developer` | `frontend-design` + `api-design-principles` + `database-migration` + `code-review` | 各阶段 |
+| **前端 UI 开发** | `fullstack-developer` | `frontend-design` + `tailwind-design-system` + `react-state-management` | UI 设计阶段 |
+| **后端 API 开发** | `fullstack-developer` | `api-design-principles` + `async-python-patterns` / `nodejs-backend-patterns` | API 设计阶段 |
+| **数据库设计** | `fullstack-developer` | `database-migration` + `postgresql-table-design` + `sql-optimization-patterns` | Schema 设计阶段 |
+| **微服务开发** | `fullstack-developer` | `microservices-patterns` + `api-design-principles` + `distributed-tracing` | 架构设计阶段 |
+| **AI/LLM 功能** | `fullstack-developer` | `langchain-architecture` + `rag-implementation` + `prompt-engineering-patterns` | AI 功能开发时 |
+| **认证/授权** | `fullstack-developer` | `auth-implementation-patterns` | 安全模块开发时 |
+| **性能优化** | `fullstack-developer` | `python-performance-optimization` / `modern-javascript-patterns` + `sql-optimization-patterns` | 性能调优时 |
+
+### 强制技能调用 (Mandatory)
+
+| 触发条件 | 必须调用的技能 | 原因 |
+|----------|----------------|------|
+| **任何 UI/UX 工作** | `frontend-design` | 确保生产级界面质量 |
+| **开发完成后** | `code-review` | 确保代码质量，防止问题上线 |
+| **审查发现问题** | `bug-fixing` | 循环直到所有问题解决 |
+| **修改 ORM 模型** | `database-migration` | 确保 schema-model 同步 |
+| **新建/修改 API** | `api-design-principles` | 确保 API 设计符合最佳实践 |
+| **需求不明确** | `product-requirements` | 确保需求分析完整 |
+
+### 按技术栈推荐
+
+| 技术栈 | 推荐协作技能 |
+|--------|-------------|
+| **Python (FastAPI/Django)** | `async-python-patterns` + `python-testing-patterns` + `fastapi-templates` |
+| **JavaScript/TypeScript (Node.js)** | `nodejs-backend-patterns` + `modern-javascript-patterns` + `typescript-advanced-types` |
+| **React (Web)** | `react-state-management` + `tailwind-design-system` + `javascript-testing-patterns` |
+| **React (Next.js)** | `nextjs-app-router-patterns` + `react-state-management` + `tailwind-design-system` |
+| **PostgreSQL** | `postgresql-table-design` + `sql-optimization-patterns` + `database-migration` |
+
+## 开发阶段技能调用流程
+
+```
+需求输入
+       │
+       ▼
+┌──────────────────────────────────────────────────────┐
+│ Phase -1: 需求分析                                    │
+│ ─────────────────────────────────────────────────────│
+│ 需求不清晰? → 调用 `product-requirements`              │
+└──────────────────────────────────────────────────────┘
+       │
+       ▼
+┌──────────────────────────────────────────────────────┐
+│ Phase 0: 技术调研                                     │
+│ ─────────────────────────────────────────────────────│
+│ 识别技术栈 → 查询技能路由表 → 确定协作技能             │
+└──────────────────────────────────────────────────────┘
+       │
+       ▼
+┌──────────────────────────────────────────────────────┐
+│ Phase 1: 架构设计                                     │
+│ ─────────────────────────────────────────────────────│
+│ 复杂架构? → `architecture-patterns` / `microservices-patterns` │
+│ 数据库设计? → `database-migration` + `postgresql-table-design`  │
+│ API 设计? → `api-design-principles`                   │
+└──────────────────────────────────────────────────────┘
+       │
+       ▼
+┌──────────────────────────────────────────────────────┐
+│ Phase 2: UI/UX 开发 (如适用)                          │
+│ ─────────────────────────────────────────────────────│
+│ 🔴 强制调用 `frontend-design`                         │
+│ 状态管理? → `react-state-management`                  │
+│ 样式系统? → `tailwind-design-system`                  │
+└──────────────────────────────────────────────────────┘
+       │
+       ▼
+┌──────────────────────────────────────────────────────┐
+│ Phase 3: 后端开发                                     │
+│ ─────────────────────────────────────────────────────│
+│ Python 异步? → `async-python-patterns`                │
+│ Node.js? → `nodejs-backend-patterns`                  │
+│ AI/LLM? → `langchain-architecture` + `rag-implementation` │
+└──────────────────────────────────────────────────────┘
+       │
+       ▼
+┌──────────────────────────────────────────────────────┐
+│ Phase 4: 测试                                         │
+│ ─────────────────────────────────────────────────────│
+│ Python 测试? → `python-testing-patterns`              │
+│ JS/TS 测试? → `javascript-testing-patterns`           │
+│ E2E 测试? → `e2e-testing-patterns` / `webapp-testing` │
+└──────────────────────────────────────────────────────┘
+       │
+       ▼
+┌──────────────────────────────────────────────────────┐
+│ Phase 5: 代码审查 (MANDATORY)                         │
+│ ─────────────────────────────────────────────────────│
+│ 🔴 强制调用 `code-review`                             │
+│ 发现问题? → 调用 `bug-fixing` → 循环                   │
+└──────────────────────────────────────────────────────┘
+       │
+       ▼
+   开发完成 ✅
+```
+
+## 技能调用语法
+
+在开发过程中，使用以下格式记录技能调用：
+
+```markdown
+## 🔄 技能协作记录
+
+| 阶段 | 调用技能 | 原因 | 结果 |
+|------|----------|------|------|
+| Phase 0 | `product-requirements` | 需求澄清 | PRD 确认 |
+| Phase 1 | `database-migration` | 新表设计 | 创建迁移文件 |
+| Phase 2 | `frontend-design` | UI 组件开发 | 组件设计完成 |
+| Phase 3 | `async-python-patterns` | 异步 API | 性能优化 |
+| Phase 4 | `python-testing-patterns` | 单元测试 | 覆盖率 85% |
+| Phase 5 | `code-review` | 强制审查 | 通过 |
+```
+
+## 技能协作输出模板
+
+开发报告必须包含技能协作部分：
+
+```markdown
+## 📊 技能协作报告
+
+### 调用的技能
+| 技能 | 调用原因 | 贡献 |
+|------|----------|------|
+| `fullstack-developer` (主) | 开发主流程 | 功能实现 |
+| `frontend-design` | UI 开发 | 组件设计 |
+| `database-migration` | Schema 设计 | 迁移文件 |
+| `api-design-principles` | API 设计 | 契约规范 |
+| `code-review` | 强制审查 | 质量保证 |
+
+### 未调用但建议后续调用的技能
+| 技能 | 建议原因 |
+|------|----------|
+| `e2e-testing-patterns` | 可添加端到端测试 |
+| `prometheus-configuration` | 可添加监控指标 |
+```
+
+## 常见协作场景
+
+### 场景 1: 新功能开发 (前后端 + 数据库)
+
+```
+fullstack-developer (主)
+    │
+    ├─→ product-requirements (需求分析)
+    │
+    ├─→ database-migration + postgresql-table-design (数据库)
+    │
+    ├─→ api-design-principles (API 设计)
+    │
+    ├─→ frontend-design (UI 开发)
+    │
+    ├─→ python-testing-patterns (后端测试)
+    │
+    ├─→ javascript-testing-patterns (前端测试)
+    │
+    └─→ code-review (强制) → bug-fixing (如有问题)
+```
+
+### 场景 2: AI/LLM 功能开发
+
+```
+fullstack-developer (主)
+    │
+    ├─→ langchain-architecture (LLM 集成)
+    │
+    ├─→ rag-implementation (知识库/RAG)
+    │
+    ├─→ prompt-engineering-patterns (Prompt 优化)
+    │
+    ├─→ async-python-patterns (异步处理)
+    │
+    └─→ code-review (强制)
+```
+
+### 场景 3: 微服务开发
+
+```
+fullstack-developer (主)
+    │
+    ├─→ microservices-patterns (服务拆分)
+    │
+    ├─→ api-design-principles (服务间契约)
+    │
+    ├─→ distributed-tracing (追踪配置)
+    │
+    ├─→ k8s-manifest-generator (部署配置)
+    │
+    └─→ code-review (强制)
+```
+
+## Definition of Done
+
+开发完成前，确认：
+
+- [ ] 技能路由表已查询，协作技能已确定
+- [ ] 所有触发条件对应的技能已调用
+- [ ] `frontend-design` 已调用 (如涉及 UI)
+- [ ] `code-review` 已调用且通过
+- [ ] 技能协作报告已输出