@codihaus/claude-skills 1.6.21 → 1.6.23

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,106 +0,0 @@
1
- # Research Query Templates
2
-
3
- Use these to gather **references for engineers**, not to prescribe solutions.
4
-
5
- ## Goal
6
-
7
- Populate `references.md` with:
8
- - Official documentation links
9
- - Industry examples
10
- - Implementation case studies
11
- - Compliance/standards resources
12
-
13
- ## Query Templates
14
-
15
- ### Documentation
16
- ```
17
- "{feature} official documentation"
18
- "{service} API documentation"
19
- "{feature} developer guide"
20
- "{service} SDK documentation"
21
- ```
22
-
23
- ### Industry Examples
24
- ```
25
- "how {company} implements {feature}"
26
- "{feature} case study"
27
- "{industry} {feature} examples"
28
- "best {feature} implementations"
29
- ```
30
-
31
- ### User Flows
32
- ```
33
- "{feature} user flow examples"
34
- "{feature} UX patterns"
35
- "{feature} wireframe examples"
36
- ```
37
-
38
- ### Compliance & Standards
39
- ```
40
- "{feature} {regulation} compliance"
41
- "{feature} security requirements"
42
- "{industry} {feature} standards"
43
- "GDPR {feature} requirements"
44
- "PCI DSS {feature}"
45
- ```
46
-
47
- ### Open Source / Tutorials
48
- ```
49
- "{feature} open source implementation"
50
- "{feature} tutorial github"
51
- "building {feature} from scratch"
52
- ```
53
-
54
- ## By Domain
55
-
56
- ### SaaS / B2B
57
- ```
58
- "enterprise {feature} requirements"
59
- "B2B SaaS {feature} examples"
60
- "{feature} multi-tenant considerations"
61
- ```
62
-
63
- ### E-commerce
64
- ```
65
- "{feature} e-commerce best practices"
66
- "shopify {feature} documentation"
67
- "stripe {feature} guide"
68
- ```
69
-
70
- ### Marketplace
71
- ```
72
- "two-sided marketplace {feature}"
73
- "platform {feature} patterns"
74
- ```
75
-
76
- ## Search Strategy
77
-
78
- 1. **Start broad**: "{feature} documentation"
79
- 2. **Get specific**: "{service} {feature} API"
80
- 3. **Find examples**: "how {leader} does {feature}"
81
- 4. **Check compliance**: "{feature} {regulation}"
82
- 5. **Gather tutorials**: "{feature} implementation guide"
83
-
84
- ## What to Capture
85
-
86
- For each useful result, note:
87
- - **Title**: Page/article title
88
- - **URL**: Direct link
89
- - **Why relevant**: 1-line note for engineers
90
- - **Applies to**: Which use cases benefit
91
-
92
- ## Example Output
93
-
94
- ```markdown
95
- ## Documentation
96
- | Topic | Link | Notes |
97
- |-------|------|-------|
98
- | Stripe Billing | [Stripe Subscriptions](https://stripe.com/docs/billing) | Core billing API |
99
- | Usage metering | [Stripe Usage Records](https://stripe.com/docs/billing/subscriptions/usage-based) | For usage-based billing |
100
-
101
- ## Industry Examples
102
- | Company | Link | What to Learn |
103
- |---------|------|---------------|
104
- | Notion | [How Notion Prices](https://www.notion.so/pricing) | Freemium + team pricing |
105
- | Slack | [Slack Billing](https://slack.com/pricing) | Per-seat model |
106
- ```
@@ -1,141 +0,0 @@
1
- # Use Case Template
2
-
3
- Standard template for use case files.
4
-
5
- ## File Naming
6
-
7
- Format: `UC-{GROUP}-{NNN}-{slug}.md`
8
-
9
- Examples:
10
- - `UC-PAY-001-checkout.md`
11
- - `UC-AUTH-002-password-reset.md`
12
-
13
- ## Template
14
-
15
- ```markdown
16
- # UC-{GROUP}-{NNN}: {Title}
17
-
18
- > **Feature**: [[feature-{name}]]
19
- > **Related**: [[uc-xxx-nnn]], [[uc-xxx-nnn]]
20
- > **Priority**: Must | Should | Could
21
- > **Status**: Draft | Confirmed | Updated
22
-
23
- ## User Story
24
-
25
- As a {role},
26
- I want {goal},
27
- so that {benefit}.
28
-
29
- ## Acceptance Criteria
30
-
31
- - [ ] Given {precondition}, when {action}, then {expected result}
32
- - [ ] Given {precondition}, when {action}, then {expected result}
33
- - [ ] Given {precondition}, when {action}, then {expected result}
34
-
35
- ## Business Rules
36
-
37
- - {Rule 1: condition → outcome}
38
- - {Rule 2: condition → outcome}
39
-
40
- ## Edge Cases
41
-
42
- | Scenario | Expected Behavior |
43
- |----------|-------------------|
44
- | {Edge case 1} | {How to handle} |
45
- | {Edge case 2} | {How to handle} |
46
-
47
- ## Open Questions
48
-
49
- - [ ] {Question requiring stakeholder input}
50
- - [ ] {Question for engineering to answer}
51
-
52
- ## References
53
-
54
- - [{Relevant doc}]({url})
55
- - [{Related example}]({url})
56
- ```
57
-
58
- ## Priority Levels
59
-
60
- | Priority | Meaning | Scope Tier |
61
- |----------|---------|------------|
62
- | **Must** | Core functionality, cannot launch without | Core |
63
- | **Should** | Expected by users, standard feature | Standard |
64
- | **Could** | Nice to have, differentiator | Full |
65
-
66
- ## Status Values
67
-
68
- | Status | Meaning |
69
- |--------|---------|
70
- | **Draft** | Initial version, needs review |
71
- | **Confirmed** | Stakeholder approved |
72
- | **Updated** | Changed after initial confirmation |
73
-
74
- ## Writing Tips
75
-
76
- ### User Stories
77
- - Keep role specific: "As a **paying customer**" not "As a user"
78
- - Goal should be concrete: "change my subscription plan"
79
- - Benefit explains the "why"
80
-
81
- ### Acceptance Criteria
82
- - Use Given/When/Then format
83
- - Each criterion is independently testable
84
- - Cover happy path + key error paths
85
-
86
- ### Business Rules
87
- - Rules that constrain behavior
88
- - Not implementation details
89
- - "Users cannot downgrade during trial period"
90
-
91
- ### Open Questions
92
- - Mark with `[ ]` so they can be checked off
93
- - Tag who needs to answer: "(Stakeholder)" or "(Engineering)"
94
-
95
- ## Example
96
-
97
- ```markdown
98
- # UC-PAY-001: Checkout
99
-
100
- > **Feature**: [[feature-billing]]
101
- > **Related**: [[uc-pay-002]], [[uc-cart-001]]
102
- > **Priority**: Must
103
- > **Status**: Draft
104
-
105
- ## User Story
106
-
107
- As a customer with items in cart,
108
- I want to complete my purchase,
109
- so that I receive my order.
110
-
111
- ## Acceptance Criteria
112
-
113
- - [ ] Given valid cart, when I click checkout, then I see payment form
114
- - [ ] Given payment details, when I submit, then payment is processed
115
- - [ ] Given successful payment, when complete, then I see confirmation
116
- - [ ] Given failed payment, when error occurs, then I see clear error message
117
-
118
- ## Business Rules
119
-
120
- - Minimum order value: $10
121
- - Maximum items per order: 50
122
- - Payment must complete within 30 minutes of cart creation
123
-
124
- ## Edge Cases
125
-
126
- | Scenario | Expected Behavior |
127
- |----------|-------------------|
128
- | Cart expires during checkout | Show message, redirect to cart |
129
- | Item goes out of stock | Remove item, notify user |
130
- | Network error during payment | Retry option, no duplicate charge |
131
-
132
- ## Open Questions
133
-
134
- - [ ] (Stakeholder) Do we support guest checkout?
135
- - [ ] (Engineering) Which payment processor to use?
136
-
137
- ## References
138
-
139
- - [Stripe Checkout](https://stripe.com/docs/checkout)
140
- - [Baymard Checkout UX](https://baymard.com/checkout-usability)
141
- ```