@tinkcarlos/skillora 0.2.0

package/.claude/skills/product-requirements/references/external-standards.md

@@ -0,0 +1,62 @@
+# External Standards & Authoritative Sources (for Product Requirements)
+
+Retrieved: 2025-12-23
+
+Use this document as a source-of-truth index for requirement-writing standards and UX/product practices. Prefer these sources when you need neutral justification for structure, terminology, or "definition of done" in a PRD.
+
+## 1) User Stories (Quality & Structure)
+
+- Agile Alliance Glossary - INVEST: https://www.agilealliance.org/glossary/invest/
+  - A checklist for "good" user stories: Independent, Negotiable, Valuable, Estimable, Small, Testable.
+  - If a story fails INVEST, rewrite/re-split rather than force it into the backlog.
+- Atlassian - User stories with examples and a template: https://www.atlassian.com/agile/project-management/user-stories
+  - Common structure: "As a..., I want..., so that...".
+  - User stories are a planning tool: keep them understandable and user-centric.
+
+## 2) Acceptance Criteria (Executable Specifications)
+
+- Cucumber Docs - Gherkin Reference: https://cucumber.io/docs/gherkin/reference/
+  - Standard keywords and structure: Feature / Scenario / Given-When-Then.
+  - Recommendations (e.g., 3-5 steps per scenario) help keep specs readable and maintainable.
+- Atlassian - Acceptance criteria: https://www.atlassian.com/agile/project-management/acceptance-criteria
+  - Acceptance criteria clarify "done" and reduce ambiguity before implementation.
+  - Well-written AC supports shared understanding across product/design/engineering/QA.
+
+## 3) Personas (User-Centered Framing)
+
+- Nielsen Norman Group - Personas Make Users Memorable: https://www.nngroup.com/articles/persona/
+  - Personas are fictional-but-research-based representations that help teams empathize with users.
+  - Include only details that affect design decisions; avoid irrelevant trivia.
+- Interaction Design Foundation - Personas: A Simple Introduction: https://www.interaction-design.org/literature/article/personas-why-and-how-you-should-use-them
+  - Personas should be derived from research patterns, not pure invention.
+  - Personas help ask "how would X experience this?" and support scenario-based reasoning.
+
+## 4) Journey / Flow Mapping (End-to-End UX)
+
+- Nielsen Norman Group - Journey Mapping 101: https://www.nngroup.com/articles/journey-mapping-101/
+  - Journey maps visualize a user's process to accomplish a goal (actions, mindsets, emotions, opportunities).
+  - Use journey maps for discovery/understanding; use story maps for planning/implementation.
+- Interaction Design Foundation - Customer Journey Maps: https://www.interaction-design.org/literature/article/customer-journey-maps-walking-a-mile-in-your-customer-s-shoes
+  - Journey maps are research-based tools across touchpoints/channels over time.
+  - Preparation includes personas, timescale, touchpoints/channels, and "moments of truth".
+
+## 5) Prioritization (Scope, MVP, Roadmaps)
+
+- Intercom - RICE prioritization framework: https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/
+  - Score ideas via Reach, Impact, Confidence, Effort to compare consistently.
+  - Use scores as decision support, not as an absolute rule (dependencies/table-stakes still matter).
+- Atlassian - MoSCoW prioritization: https://www.atlassian.com/agile/project-management/moscow-prioritization
+  - Categorize scope into Must/Should/Could/Won't to make trade-offs explicit.
+  - Helps define MVP and protect critical outcomes under constraints.
+
+## 6) Non-Functional Requirements (Security, Accessibility, Performance)
+
+- W3C Recommendation - WCAG 2.2: https://www.w3.org/TR/WCAG22/
+  - Accessibility guidance is expressed as testable success criteria (A/AA/AAA) that are technology-agnostic.
+  - Use WCAG to define accessibility scope and acceptance criteria early.
+- OWASP - Application Security Verification Standard (ASVS): https://owasp.org/www-project-application-security-verification-standard/
+  - A structured checklist of security requirements to guide design and verification planning.
+  - Reference requirements by version and identifier for auditability.
+- GoogleChrome - web-vitals (Core Web Vitals metrics): https://github.com/GoogleChrome/web-vitals
+  - Core Web Vitals: CLS, INP, LCP; other diagnostics include FCP and TTFB.
+  - Instrumentation has pitfalls (e.g., avoid registering observers multiple times).

package/.claude/skills/product-requirements/references/feature-spec-template.md

@@ -0,0 +1,359 @@
+# Feature Specification Template
+
+Complete this template for every page/feature before development begins.
+
+---
+
+## Feature Overview
+
+### Basic Information
+| Field | Value |
+|-------|-------|
+| Feature Name | |
+| Feature ID | F-XXX |
+| Epic | |
+| Owner | |
+| Status | Draft / In Review / Approved |
+| Priority | Must / Should / Could / Won't |
+| Target Release | |
+
+### Description
+**One-liner**: [What this feature does in one sentence]
+
+**Detailed Description**:
+[2-3 paragraphs explaining the feature, its purpose, and value]
+
+### Business Value
+- **Problem Solved**: [What user problem does this address?]
+- **Success Metric**: [How do we measure success?]
+- **Target Value**: [What's the target number?]
+
+---
+
+## User Context
+
+### Target Users
+| Persona | Primary/Secondary | Key Need |
+|---------|-------------------|----------|
+| [Persona 1] | Primary | [Need] |
+| [Persona 2] | Secondary | [Need] |
+
+### User Journey Position
+```
+[Previous Step] → [THIS FEATURE] → [Next Step]
+```
+
+### Entry Points
+| Source | Trigger | User State |
+|--------|---------|------------|
+| Homepage | Click CTA | Logged out |
+| Dashboard | Menu click | Logged in |
+| Email link | Direct URL | Any |
+
+### Exit Points
+| Destination | Trigger | User State |
+|-------------|---------|------------|
+| Success page | Complete action | Data saved |
+| Previous page | Cancel | No changes |
+| Error state | Failure | Retry needed |
+
+---
+
+## Page Layout
+
+### Wireframe (ASCII)
+```
++--------------------------------------------------+
+|  [Logo]           [Nav]           [User Menu]    |
++--------------------------------------------------+
+|                                                  |
+|  +--------------------------------------------+  |
+|  |            Hero / Title Section            |  |
+|  +--------------------------------------------+  |
+|                                                  |
+|  +--------------------+  +--------------------+  |
+|  |   Main Content     |  |    Sidebar        |  |
+|  |                    |  |                    |  |
+|  |   [Component A]    |  |   [Component D]   |  |
+|  |   [Component B]    |  |   [Component E]   |  |
+|  |   [Component C]    |  |                    |  |
+|  +--------------------+  +--------------------+  |
+|                                                  |
++--------------------------------------------------+
+|              [Footer]                            |
++--------------------------------------------------+
+```
+
+### Responsive Breakpoints
+| Breakpoint | Width | Layout Changes |
+|------------|-------|----------------|
+| Mobile S | <375px | Single column, stacked |
+| Mobile L | 375-767px | Single column |
+| Tablet | 768-1023px | Two columns |
+| Desktop | 1024-1439px | Full layout |
+| Desktop L | ≥1440px | Max-width container |
+
+---
+
+## Component Specifications
+
+### Component: [Component Name]
+
+#### Purpose
+[Why does this component exist?]
+
+#### Visual Specification
+| Property | Value |
+|----------|-------|
+| Position | [top-left, center, etc.] |
+| Dimensions | [width x height or responsive] |
+| Padding | [values] |
+| Margin | [values] |
+| Background | [color/gradient] |
+| Border | [width, style, color, radius] |
+| Shadow | [values] |
+
+#### Content
+| Element | Content | Dynamic? |
+|---------|---------|----------|
+| Title | "[Text]" | No |
+| Description | [Data field] | Yes |
+| Image | [Source] | Yes |
+
+#### States
+
+| State | Visual | Behavior | Duration |
+|-------|--------|----------|----------|
+| Default | Normal colors | Interactive | - |
+| Hover | Elevated shadow | Cursor pointer | - |
+| Focus | Blue outline | Keyboard accessible | - |
+| Active | Pressed effect | - | 100ms |
+| Loading | Skeleton/Spinner | Non-interactive | Until loaded |
+| Disabled | 50% opacity | Non-interactive | - |
+| Error | Red border | Show error message | Until fixed |
+| Success | Green accent | Show confirmation | 3s then fade |
+
+#### Interactions
+
+| Trigger | Action | Result | Animation |
+|---------|--------|--------|-----------|
+| Click | Submit form | API call | Button loading |
+| Hover | Show tooltip | Display info | Fade in 200ms |
+| Focus | Highlight | Visual focus ring | Immediate |
+| Blur | Validate | Show error if invalid | Immediate |
+
+#### Validation (if applicable)
+
+| Field | Rule | Error Message |
+|-------|------|---------------|
+| Email | Valid email format | "Please enter a valid email" |
+| Password | Min 8 chars | "Password must be at least 8 characters" |
+| Required | Not empty | "[Field] is required" |
+
+#### Accessibility
+
+| Aspect | Implementation |
+|--------|----------------|
+| Role | button / textbox / etc. |
+| ARIA Label | "[Accessible name]" |
+| Keyboard | Enter to activate, Tab to navigate |
+| Screen Reader | "[What SR announces]" |
+
+---
+
+## User Flows
+
+### Happy Path Flow
+
+```mermaid
+graph TD
+    A[User lands on page] --> B[Views content]
+    B --> C[Fills form / Takes action]
+    C --> D{Validation}
+    D -->|Valid| E[Submit to server]
+    E --> F{Server response}
+    F -->|Success| G[Show success message]
+    G --> H[Redirect to next page]
+    D -->|Invalid| I[Show field errors]
+    I --> C
+```
+
+### Error Flow
+
+```mermaid
+graph TD
+    A[User submits] --> B{Validation}
+    B -->|Client error| C[Show inline errors]
+    C --> D[User fixes errors]
+    D --> A
+    B -->|Valid| E[API call]
+    E --> F{Response}
+    F -->|400 Bad Request| G[Show form errors from API]
+    F -->|401 Unauthorized| H[Redirect to login]
+    F -->|403 Forbidden| I[Show permission error]
+    F -->|404 Not Found| J[Show not found state]
+    F -->|500 Server Error| K[Show generic error + retry]
+    F -->|Timeout| L[Show timeout + retry]
+```
+
+---
+
+## Error Handling Matrix
+
+| Code | Scenario | UI Message | Recovery | Log Level |
+|------|----------|------------|----------|-----------|
+| E001 | Network offline | "You're offline. Check your connection." | Auto-retry when online | warn |
+| E002 | Request timeout | "Request timed out. Please try again." | Retry button | warn |
+| E003 | Server error 500 | "Something went wrong. Please try again." | Retry button | error |
+| E004 | Validation error | "[Field specific message]" | Fix and resubmit | info |
+| E005 | Not found | "This item no longer exists." | Go back | warn |
+| E006 | Unauthorized | "Please log in to continue." | Login redirect | info |
+| E007 | Forbidden | "You don't have permission." | Contact admin | warn |
+| E008 | Rate limited | "Too many requests. Please wait." | Auto-retry with backoff | warn |
+| E009 | Conflict | "This was modified by someone else." | Refresh and retry | warn |
+| E010 | Payload too large | "File is too large. Max size: [X]MB" | Choose smaller file | info |
+| E011 | Invalid format | "Invalid file format. Allowed: [types]" | Choose valid file | info |
+| E012 | Session expired | "Your session expired. Please log in." | Login redirect | info |
+
+---
+
+## Acceptance Criteria
+
+### Feature: [Feature Name]
+
+```gherkin
+@happy-path
+Scenario: User successfully completes [action]
+  Given I am logged in as a [user type]
+  And I am on the [page name]
+  When I enter "[valid input]" in the [field]
+  And I click the "[button]" button
+  Then I should see "[success message]"
+  And I should be redirected to [destination]
+  And the [data] should be saved in the system
+
+@validation
+Scenario: User sees error for invalid [field]
+  Given I am on the [page name]
+  When I enter "[invalid input]" in the [field]
+  And I click outside the field
+  Then I should see error message "[error message]"
+  And the [field] should have a red border
+  And the form should not be submittable
+
+@error-handling
+Scenario: User sees error when server fails
+  Given I am on the [page name]
+  And the server will return a 500 error
+  When I submit the form with valid data
+  Then I should see "[error message]"
+  And I should see a "Retry" button
+  And my input should be preserved
+
+@accessibility
+Scenario: User can complete [action] using only keyboard
+  Given I am on the [page name]
+  When I press Tab to navigate to each field
+  And I enter data using the keyboard
+  And I press Enter to submit
+  Then the form should be submitted successfully
+
+@performance
+Scenario: Page loads within acceptable time
+  Given I have a [connection type] connection
+  When I navigate to the [page name]
+  Then the page should be interactive within [X] seconds
+  And no layout shifts should occur after initial render
+```
+
+---
+
+## Data Requirements
+
+### Data Model
+
+```typescript
+interface FeatureData {
+  id: string;
+  createdAt: Date;
+  updatedAt: Date;
+  // Add all fields with types
+}
+```
+
+### API Contract
+
+```yaml
+# OpenAPI 3.1
+paths:
+  /api/feature:
+    get:
+      summary: Get feature data
+      parameters:
+        - name: id
+          in: query
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          description: Success
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/FeatureData'
+        '404':
+          description: Not found
+    post:
+      summary: Create feature data
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/FeatureInput'
+      responses:
+        '201':
+          description: Created
+        '400':
+          description: Validation error
+```
+
+---
+
+## Analytics Events
+
+| Event | Trigger | Properties | Purpose |
+|-------|---------|------------|---------|
+| `feature_viewed` | Page load | `page_name`, `referrer`, `user_type` | Track page visits |
+| `feature_started` | User begins action | `action_type`, `entry_point` | Track engagement |
+| `feature_completed` | Success | `duration`, `steps_taken` | Track conversion |
+| `feature_abandoned` | User leaves without completing | `last_step`, `time_spent` | Track drop-off |
+| `feature_error` | Error shown | `error_code`, `error_message` | Track issues |
+
+---
+
+## Dependencies
+
+### Technical Dependencies
+| Dependency | Type | Required By |
+|------------|------|-------------|
+| Auth service | Backend | User authentication |
+| File storage | Backend | Upload feature |
+| Analytics SDK | Frontend | Event tracking |
+
+### Feature Dependencies
+| Feature | Relationship | Notes |
+|---------|--------------|-------|
+| User profile | Requires | Need user data |
+| Notification | Triggers | Send on completion |
+
+---
+
+## Out of Scope
+
+Explicitly list what this feature does NOT include:
+- [ ] [Feature X] - Will be in v2
+- [ ] [Edge case Y] - Intentionally not supported
+- [ ] [Integration Z] - Separate feature
+

package/.claude/skills/product-requirements/references/knowledge-acquisition-protocol.md

@@ -0,0 +1,251 @@
+# 领域知识获取协议 (Knowledge Acquisition Protocol)
+
+> **核心原则**: 最新性 > 准确性 > 完整性。知识冲突时，最新来源优先。
+
+---
+
+## 🔴 为什么必须先获取领域知识？
+
+```
+❌ 没有领域知识的需求分析:
+- 提问不专业，用户不信任
+- 推荐方案缺乏依据
+- 需求文档缺乏行业视角
+- 开发计划不切实际
+
+✅ 有领域知识的需求分析:
+- 提问专业，用户信任
+- 推荐方案有行业依据
+- 需求文档符合行业标准
+- 开发计划切实可行
+```
+
+---
+
+## 知识获取流程
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  Step 1: 识别领域                                               │
+│  ├─ 用户需求属于什么领域？(电商/金融/医疗/教育/...)            │
+│  └─ 涉及哪些技术栈？(Web/Mobile/Desktop/...)                   │
+│                                                                  │
+│  Step 2: MCP 工具获取 (优先)                                    │
+│  ├─ context7: 查询相关框架/库的官方文档                         │
+│  ├─ exa: 深度搜索行业最佳实践                                   │
+│  └─ WebSearch: 搜索最新趋势和案例                               │
+│                                                                  │
+│  Step 3: 多源验证                                               │
+│  ├─ 至少 2 个独立来源确认关键信息                               │
+│  ├─ 检查来源日期 < 1 年                                         │
+│  └─ 标记冲突信息，以最新来源为准                                │
+│                                                                  │
+│  Step 4: 知识融合                                               │
+│  ├─ 提取核心概念                                                │
+│  ├─ 识别行业最佳实践                                            │
+│  ├─ 记录常见陷阱/反模式                                         │
+│  └─ 生成知识摘要                                                │
+│                                                                  │
+│  Step 5: 完整性验证                                             │
+│  ├─ 核心概念覆盖率 ≥ 90%                                        │
+│  ├─ 边界情况覆盖率 ≥ 80%                                        │
+│  └─ 反模式覆盖率 ≥ 70%                                          │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## MCP 工具使用指南
+
+### context7 (官方文档查询)
+
+```
+使用场景: 查询框架/库的官方文档
+查询示例:
+- "React best practices for form handling"
+- "Next.js authentication patterns"
+- "FastAPI dependency injection"
+
+验证要点:
+- 确认文档版本与项目技术栈匹配
+- 检查是否有 Breaking Changes
+```
+
+### exa (深度搜索)
+
+```
+使用场景: 搜索行业最佳实践、案例研究
+查询示例:
+- "e-commerce checkout flow best practices 2024"
+- "SaaS pricing page conversion optimization"
+- "mobile app onboarding UX patterns"
+
+验证要点:
+- 来源权威性 (知名公司/专家)
+- 发布日期 < 1 年
+```
+
+### WebSearch (最新趋势)
+
+```
+使用场景: 搜索最新趋势、新闻、更新
+查询示例:
+- "[领域] trends 2024"
+- "[技术] latest updates"
+- "[产品类型] market analysis"
+
+验证要点:
+- 多个来源交叉验证
+- 区分事实 vs 观点
+```
+
+---
+
+## MCP 不可用时的备选方案
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  Fallback Strategy (MCP 不可用时)                               │
+├─────────────────────────────────────────────────────────────────┤
+│                                                                  │
+│  1. 使用 Claude 内置知识                                        │
+│     ├─ 明确标注: "基于 Claude 训练数据，截止日期: [日期]"       │
+│     └─ 建议用户验证关键信息                                     │
+│                                                                  │
+│  2. 请求用户提供资料                                            │
+│     ├─ "请提供相关行业文档/竞品链接"                            │
+│     └─ "请分享您了解的行业最佳实践"                             │
+│                                                                  │
+│  3. 分析项目现有代码/文档                                       │
+│     ├─ 从现有代码推断技术栈和模式                               │
+│     └─ 从现有文档提取领域知识                                   │
+│                                                                  │
+│  ⚠️ 必须在需求文档中标注知识来源限制                            │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## 知识验证清单
+
+### 最新性验证
+
+| 检查项 | 通过标准 |
+|--------|----------|
+| 来源发布日期 | < 1 年 |
+| 技术版本匹配 | 与项目技术栈一致 |
+| 无已知废弃 | 未被官方标记为 deprecated |
+
+### 准确性验证
+
+| 检查项 | 通过标准 |
+|--------|----------|
+| 多源确认 | 2+ 独立来源一致 |
+| 来源权威 | 官方文档/知名专家/权威机构 |
+| 无明显错误 | 与已知事实不冲突 |
+
+### 完整性验证
+
+| 检查项 | 通过标准 |
+|--------|----------|
+| 核心概念 | 覆盖率 ≥ 90% |
+| 边界情况 | 覆盖率 ≥ 80% |
+| 反模式/陷阱 | 覆盖率 ≥ 70% |
+
+---
+
+## 知识摘要模板
+
+```markdown
+## 领域知识摘要
+
+### 基本信息
+- **领域**: [领域名称]
+- **获取日期**: YYYY-MM-DD
+- **知识来源**: [来源列表]
+- **来源时效**: [最新来源日期]
+
+### 核心概念
+1. [概念1]: [简要说明]
+2. [概念2]: [简要说明]
+3. [概念3]: [简要说明]
+
+### 行业最佳实践
+1. [实践1]: [说明 + 来源]
+2. [实践2]: [说明 + 来源]
+3. [实践3]: [说明 + 来源]
+
+### 常见陷阱/反模式
+1. [陷阱1]: [说明 + 如何避免]
+2. [陷阱2]: [说明 + 如何避免]
+
+### 竞品分析摘要
+| 竞品 | 关键特性 | 可借鉴点 |
+|------|----------|----------|
+| [竞品1] | [...] | [...] |
+| [竞品2] | [...] | [...] |
+
+### 知识限制声明
+- [如有] MCP 工具不可用，部分知识基于 Claude 训练数据
+- [如有] 某些信息需要用户进一步验证
+```
+
+---
+
+## 常见领域知识获取示例
+
+### 电商领域
+
+```
+MCP 查询:
+- context7: "Stripe payment integration best practices"
+- exa: "e-commerce checkout optimization 2024"
+- WebSearch: "shopping cart abandonment solutions"
+
+关键知识点:
+- 支付流程安全标准 (PCI DSS)
+- 购物车转化率优化
+- 库存管理模式
+- 订单状态机设计
+```
+
+### SaaS 领域
+
+```
+MCP 查询:
+- context7: "subscription billing patterns"
+- exa: "SaaS pricing strategy best practices"
+- WebSearch: "SaaS metrics benchmarks 2024"
+
+关键知识点:
+- 订阅计费模式
+- 用户生命周期管理
+- 关键指标 (MRR, Churn, LTV)
+- 多租户架构
+```
+
+### 移动应用领域
+
+```
+MCP 查询:
+- context7: "React Native performance optimization"
+- exa: "mobile app onboarding best practices"
+- WebSearch: "app store optimization 2024"
+
+关键知识点:
+- 平台设计规范 (iOS HIG, Material Design)
+- 离线优先架构
+- 推送通知策略
+- 应用商店优化
+```
+
+---
+
+## 违规处理
+
+| 违规 | 后果 | 处理 |
+|------|------|------|
+| 跳过知识获取 | 需求分析无效 | 必须重新执行 Phase 0 |
+| 使用过期知识 | 推荐可能错误 | 标注风险，建议验证 |
+| 单一来源 | 准确性无法保证 | 寻找第二来源确认 |
+| 未标注来源 | 可追溯性缺失 | 补充来源标注 |