@friedbotstudio/create-baseline 0.2.0 → 0.3.0

package/obj/template/.claude/skills/google-analytics/references/user-tracking.md

@@ -0,0 +1,417 @@
+# GA4 User ID and Cross-Device Tracking
+
+Complete guide to User ID implementation, user properties, and cross-device tracking in GA4.
+
+## Overview
+
+User ID enables cross-device tracking for authenticated users. User properties allow tracking custom user attributes across all events. Together, they provide a unified view of user behaviour across devices and sessions.
+
+## User ID Implementation
+
+### What is User ID
+
+- Persistent identifier for authenticated users
+- Enables cross-device tracking
+- Requires explicit user authentication
+- Must not contain PII (hash if needed)
+- Set when user logs in, cleared on logout
+
+### Implementation Methods
+
+#### Method 1: gtag.js
+
+**On Login:**
+```javascript
+// Set User ID when user logs in
+gtag('config', 'G-XXXXXXXXXX', {
+  'user_id': 'USER_12345'
+});
+
+// Or use gtag('set')
+gtag('set', 'user_id', 'USER_12345');
+```
+
+**On Logout:**
+```javascript
+// Clear User ID - MUST use null, never empty string
+gtag('set', 'user_id', null);
+```
+
+#### Method 2: GTM Data Layer
+
+**Push to Data Layer:**
+```javascript
+// On login
+dataLayer.push({
+  'user_id': 'USER_12345'
+});
+
+// On logout
+dataLayer.push({
+  'user_id': null
+});
+```
+
+**GTM Configuration:**
+1. Create Data Layer Variable: `user_id`
+2. In GA4 Configuration tag, add parameter:
+   - Parameter: `user_id`
+   - Value: `{{DL - User ID}}`
+
+#### Method 3: Measurement Protocol
+
+```json
+{
+  "client_id": "client_123",
+  "user_id": "USER_12345",
+  "events": [
+    {
+      "name": "login",
+      "params": {
+        "method": "email"
+      }
+    }
+  ]
+}
+```
+
+### User ID Best Practices
+
+| Do | Don't |
+|----|-------|
+| Use internal user IDs | Use email addresses |
+| Hash sensitive IDs | Use phone numbers |
+| Set on login | Use PII directly |
+| Clear on logout | Use empty string to clear |
+| Document ID format | Expose ID format publicly |
+
+### User ID Format Examples
+
+**Good:**
+- `USER_12345` (internal ID)
+- `abc123def456` (hashed value)
+- `u_a1b2c3d4` (prefixed ID)
+
+**Bad:**
+- `john@example.com` (email - PII)
+- `+1-555-123-4567` (phone - PII)
+- `John Smith` (name - PII)
+
+## Reporting Identity
+
+Configure how GA4 identifies users across sessions.
+
+### Path
+
+Admin -> Data Settings -> Reporting Identity
+
+### Options
+
+| Option | Description | Best For |
+|--------|-------------|----------|
+| Blended | User ID + Device ID + Google Signals | Most comprehensive |
+| Observed | User ID + Device ID only | More privacy-focused |
+| Device-based | Device ID only | Most restrictive |
+
+### Blended (Recommended)
+
+- Uses User ID when available
+- Falls back to Device ID + Google Signals
+- Most complete user view
+- Enables cross-device insights
+
+### Observed
+
+- Uses User ID and Device ID only
+- No Google Signals data
+- More privacy-focused
+- Fewer users identified
+
+### Device-based
+
+- Uses only client_id (device)
+- No cross-device tracking
+- Maximum privacy
+- Limited user insights
+
+## User Properties
+
+### What are User Properties
+
+- Custom attributes set at user level
+- Persist across all events from that user
+- Different from event parameters
+- Must be registered as custom dimensions to report
+
+### Limits
+
+| Limit | Value |
+|-------|-------|
+| User properties per property | 25 |
+| Property name length | 24 characters |
+| Property value length | 36 characters |
+
+### Setting User Properties
+
+**gtag.js:**
+```javascript
+gtag('set', 'user_properties', {
+  'user_tier': 'premium',
+  'account_age_days': 365,
+  'preferred_category': 'electronics'
+});
+```
+
+**GTM Data Layer:**
+```javascript
+dataLayer.push({
+  'user_properties': {
+    'user_tier': 'premium',
+    'account_age_days': 365
+  }
+});
+```
+
+**Measurement Protocol:**
+```json
+{
+  "client_id": "client_123",
+  "user_properties": {
+    "user_tier": {
+      "value": "premium"
+    },
+    "account_age_days": {
+      "value": 365
+    }
+  },
+  "events": [...]
+}
+```
+
+### Common User Properties
+
+| Property | Values | Use Case |
+|----------|--------|----------|
+| user_tier | free, premium, enterprise | Segment by subscription |
+| signup_date | YYYY-MM-DD | Cohort analysis |
+| subscription_status | active, trial, cancelled | Revenue analysis |
+| customer_ltv | Numeric bucket | Value segmentation |
+| industry | Technology, Finance, etc. | B2B analysis |
+| company_size | 1-10, 11-50, 51-200, etc. | Enterprise targeting |
+| interests | Category string | Personalisation |
+
+### PII Considerations
+
+**Avoid:**
+- email
+- name
+- phone_number
+- address
+- credit_card
+
+**Use Instead:**
+- email_domain
+- first_name_initial
+- user_segment
+- location_region
+
+## Cross-Device Tracking
+
+### How It Works
+
+1. User visits on mobile (logged in) -> user_id set
+2. User visits on desktop (logged in) -> same user_id
+3. GA4 stitches sessions together
+4. Reports show unified user journey
+
+### Requirements
+
+- User ID implemented and set on login
+- Google Signals enabled (for Blended identity)
+- Users signed into Google accounts
+- User opt-in to personalisation
+
+### Enabling Google Signals
+
+1. Admin -> Data Settings -> Data Collection
+2. Enable Google Signals
+3. Accept terms
+4. Wait 24 hours for data
+
+### Cross-Domain Tracking
+
+For User ID across domains:
+
+**gtag.js Configuration:**
+```javascript
+gtag('config', 'G-XXXXXXXXXX', {
+  'linker': {
+    'domains': ['example.com', 'shop.example.com', 'blog.example.com']
+  }
+});
+```
+
+**What This Does:**
+- Passes client_id between domains via URL parameter
+- Preserves user_id if set
+- Maintains session continuity
+- Uses `_gl` URL parameter
+
+**GTM Setup:**
+1. In GA4 Configuration tag
+2. Expand Configuration Settings
+3. Add Fields to Set:
+   - Field Name: linker
+   - Value: `{"domains": ["example.com", "shop.example.com"]}`
+
+### Testing Cross-Domain
+
+1. Visit domain1.com
+2. Click link to domain2.com
+3. Verify `_gl` parameter in URL
+4. Check DebugView shows same user
+5. Confirm session continues
+
+## User-Scoped Custom Dimensions
+
+Register user properties for reporting:
+
+### Registration
+
+1. Admin -> Data Display -> Custom Definitions
+2. Click "Create custom dimension"
+3. Configure:
+   - Dimension name: "User Tier"
+   - Scope: User
+   - User property: `user_tier`
+4. Save
+
+### Using in Reports
+
+- Add as dimension in Explorations
+- Filter/segment by dimension
+- Analyse user cohorts
+- Compare user segments
+
+## User Data Deletion
+
+### GDPR/CCPA Compliance
+
+**Path:** Admin -> Data Settings -> Data Deletion Requests
+
+### Process
+
+1. Click "Create deletion request"
+2. Select parameter: User ID
+3. Enter User ID value to delete
+4. Choose scope: All data or date range
+5. Submit request
+
+### Processing
+
+- Takes up to 72 hours
+- Deletes ALL events for that User ID
+- Cannot be undone
+- Confirmation email sent
+
+### Use Cases
+
+- GDPR right to erasure requests
+- CCPA deletion requests
+- User account deletion
+- Data cleanup
+
+## Testing User ID
+
+### Verification Workflow
+
+1. **Implement User ID**
+2. **Enable DebugView**
+3. **Test Login:**
+   - Before login: Events have only client_id
+   - After login: Verify user_id in event details
+4. **Test Logout:**
+   - After logout: Verify user_id cleared/null
+5. **Test Cross-Device:**
+   - Login on Device 1
+   - Login on Device 2 with same account
+   - Verify same user_id
+
+### DebugView Verification
+
+1. Open Admin -> DebugView
+2. Click any event
+3. Expand event details
+4. Check "User ID" field populated
+
+### Reports Verification
+
+- Wait 24-48 hours
+- Check user count vs sessions
+- Lower user count = User ID working (same user, multiple sessions)
+
+## Common Issues
+
+### User ID Not Appearing
+
+**Causes:**
+- Set after gtag config
+- Cleared immediately
+- Wrong parameter name
+
+**Solutions:**
+1. Set user_id in config call
+2. Verify login flow
+3. Check parameter is 'user_id' exactly
+
+### Cross-Device Not Working
+
+**Causes:**
+- Different User IDs
+- User ID not set on all devices
+- Reporting Identity not configured
+
+**Solutions:**
+1. Verify same User ID across devices
+2. Ensure login sets User ID
+3. Check Reporting Identity = Blended
+
+### User Properties Not in Reports
+
+**Cause:** Not registered as custom dimensions
+
+**Solution:**
+1. Register as user-scoped custom dimension
+2. Wait 24-48 hours
+3. Use in Explorations
+
+## Quick Reference
+
+### Set User ID
+
+```javascript
+gtag('config', 'G-XXXXXXXXXX', {
+  'user_id': 'USER_123'
+});
+```
+
+### Set User Properties
+
+```javascript
+gtag('set', 'user_properties', {
+  'user_tier': 'premium'
+});
+```
+
+### Clear User ID
+
+```javascript
+gtag('set', 'user_id', null);
+```
+
+### Limits
+
+- 25 user properties per property
+- User property name: 24 characters max
+- User property value: 36 characters max
+- User ID: Must not contain PII

package/obj/template/.claude/skills/harness/SKILL.md

@@ -105,12 +105,14 @@ The phases the harness loops through, in order:
 
 ```
 intake → scout → research → spec → /approve-spec → tdd → simplify →
-security → integrate → document → archive → /grant-commit → commit
+security → integrate → document → archive → memory-flush →
+/grant-commit → commit
 ```
 
 - Phases listed in `workflow.json → exceptions` are skipped.
 - Non-git projects auto-except `grant-commit` and `commit`; the workflow ends after `/archive`.
 - The four-pillar framing (Intake analysis · Track alignment · Implementation · Tying open ends) is documentary; the actual execution model is one phase per loop iteration, with the loop continuing through every non-gated boundary until it exits cleanly.
+- Inside `/tdd`'s seeded worker chain, the harness inlines a **drift-check-tick** task between the last `design-ui-tick` (or `verify-tick` when no design rows) and `tdd-finalize`. It invokes `python3 .claude/skills/tdd/drift_check.py --slug <slug>` against the approved spec and the branch diff. Exit 0 (zero unresolved) → continue to `tdd-finalize`; exit 1 (≥ 1 unresolved) → EXIT LOOP with YIELD (`reason: "drift analysis: <N> unresolved items"`). Drift failures stop-and-surface (NO auto-loop) — the user fixes the impl gap or amends the spec + re-`/approve-spec`s. The drift report lands at `.claude/state/drift/<slug>.md`. `chore`-track workflows (no spec on disk) exit 0 with "no spec; skipped" and proceed to `tdd-finalize`.
 
 ### Swarm vs solo at Phase 6
 

package/obj/template/.claude/skills/humanizer/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) blader (https://github.com/blader/humanizer)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/obj/template/.claude/skills/humanizer/NOTICE

@@ -0,0 +1,21 @@
+humanizer
+=========
+
+This skill is vendored from the `humanizer` skill published by @blader and is
+redistributed here under the terms of the MIT License (see LICENSE in this
+directory).
+
+Upstream:
+  Repository: https://github.com/blader/humanizer
+  Author:     @blader
+
+Vendored into:  .claude/skills/humanizer/
+Vendored on:    2026-05-15 (this commit) — prior install date unknown; LICENSE
+                + NOTICE added retroactively as part of the licensing-attribution
+                drift fix in the branch-aware-git-policy workflow.
+
+Local changes:
+  - Frontmatter `owner: baseline` added so the audit-baseline drift check
+    tracks this file as a shipped baseline artifact. The MIT license permits
+    this redistribution; attribution is preserved in the SKILL.md frontmatter
+    `description` block, which retains the upstream credit line.

package/obj/template/.claude/skills/impeccable/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.