@oriro/orirocli 0.1.8 → 0.1.11

package/skills/technical/gdpr-basics/SKILL.md

@@ -1,145 +1,145 @@
----
-watermark: ORIRO
-name: gdpr-basics
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-
-
-
-
-
-
-
-
-  GDPR implementation guide — technical requirements, data mapping, consent management, privacy by design, and compliance for developers.
-
-
-
-  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
----
-
-# GDPR Technical Implementation
-
-## Technical requirements for GDPR compliance
-
-### Consent management
-
-```ts
-// Store consent records — you must be able to prove consent
-interface ConsentRecord {
-  userId: string;
-  timestamp: Date;
-  ip: string;
-  userAgent: string;
-  consentVersion: string; // Version of your privacy policy
-  purposes: {
-    analytics: boolean;
-    marketing: boolean;
-    functional: boolean; // Usually pre-ticked if truly necessary
-  };
-}
-
-// Save to DB on consent
-await db.consentRecord.create({
-  data: {
-    userId: session.userId,
-    timestamp: new Date(),
-    ip: getClientIp(req),
-    userAgent: req.headers["user-agent"],
-    consentVersion: CURRENT_CONSENT_VERSION,
-    purposes: { analytics: true, marketing: false, functional: true },
-  },
-});
-```
-
-### Cookie consent banner requirements
-
-- Must present BEFORE setting non-essential cookies.
-- "Accept all" and "Reject all" buttons equally prominent.
-- Granular control must be available.
-- Pre-selected checkboxes for non-essential cookies = not valid consent.
-- Easy to withdraw consent (same ease as giving it).
-
-### Data subject rights implementation
-
-```ts
-// Data access request (must respond within 30 days)
-async function handleAccessRequest(userId: string) {
-  const userData = {
-    account: await db.user.findUnique({ where: { id: userId } }),
-    posts: await db.post.findMany({ where: { userId } }),
-    purchases: await db.order.findMany({ where: { userId } }),
-    consentHistory: await db.consentRecord.findMany({ where: { userId } }),
-    // Include all personal data you hold
-  };
-  return userData; // Send to user
-}
-
-// Deletion request (right to be forgotten)
-async function handleDeletionRequest(userId: string) {
-  // 1. Check if any legal obligation to retain (contracts, tax records — 7 years)
-  // 2. Anonymize or delete where no legal basis for retention
-  await db.user.update({
-    where: { id: userId },
-    data: {
-      email: `deleted-${userId}@deleted.invalid`,
-      name: "Deleted User",
-      phone: null,
-      deletedAt: new Date(),
-    },
-  });
-  // 3. Request deletion from third-party processors (analytics, email, CRM)
-  await analytics.deleteUser(userId);
-  await emailService.deleteContact(userId);
-}
-```
-
-## Data minimization
-
-Only collect what you actually use. Review forms — remove unnecessary fields.
-
-```ts
-// BAD: Collect everything
-const { name, email, phone, dob, address, employer, salary } = body;
-
-// GOOD: Collect only what you need for this service
-const { name, email } = body;
-```
-
-## Vendor management (Data Processing Agreements)
-
-Every vendor who processes personal data on your behalf needs a DPA.
-
-- Analytics (Mixpanel, Amplitude, PostHog)
-- Email (Mailchimp, SendGrid, Resend)
-- Cloud hosting (AWS, GCP, Vercel)
-- Support tools (Intercom, Zendesk)
-- Error tracking (Sentry)
-
-Most reputable vendors have standard DPAs (often in their terms or a self-serve portal).
-
-## Data breach response procedure
-
-```
-Hour 0-1: Identify and contain breach.
-Hour 1-4: Assess scope (what data, how many people, risk level).
-Hour 4-24: Internal notification chain. Legal counsel. DPO if you have one.
-Hour 24-72: Report to supervisory authority IF breach poses risk to individuals.
-           (In EU: your lead supervisory authority. UK ICO, CNIL France, BfDI Germany, etc.)
-Post-72h: If high risk to individuals: Notify affected individuals "without undue delay."
-```
-
-## Practical developer checklist
-
-- [ ] Privacy policy linked from all data collection points
-- [ ] Cookie consent before analytics/marketing cookies
-- [ ] Consent records stored with timestamp, version, IP
-- [ ] Access request process documented and tested
-- [ ] Deletion/anonymization process implemented
-- [ ] Data retention policy defined and enforced (auto-delete after X months)
-- [ ] All vendors have DPAs signed
-- [ ] Encryption at rest and in transit
-- [ ] Access controls and logging for personal data
-
-Sources: GDPR text (eur-lex.europa.eu — free), ICO guidance (ico.org.uk — free, best plain-language GDPR guides), EDPB guidelines (edpb.europa.eu — free)
+---
+watermark: ORIRO
+name: gdpr-basics
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+
+
+
+
+
+
+
+
+  GDPR implementation guide — technical requirements, data mapping, consent management, privacy by design, and compliance for developers.
+
+
+
+  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
+---
+
+# GDPR Technical Implementation
+
+## Technical requirements for GDPR compliance
+
+### Consent management
+
+```ts
+// Store consent records — you must be able to prove consent
+interface ConsentRecord {
+  userId: string;
+  timestamp: Date;
+  ip: string;
+  userAgent: string;
+  consentVersion: string; // Version of your privacy policy
+  purposes: {
+    analytics: boolean;
+    marketing: boolean;
+    functional: boolean; // Usually pre-ticked if truly necessary
+  };
+}
+
+// Save to DB on consent
+await db.consentRecord.create({
+  data: {
+    userId: session.userId,
+    timestamp: new Date(),
+    ip: getClientIp(req),
+    userAgent: req.headers["user-agent"],
+    consentVersion: CURRENT_CONSENT_VERSION,
+    purposes: { analytics: true, marketing: false, functional: true },
+  },
+});
+```
+
+### Cookie consent banner requirements
+
+- Must present BEFORE setting non-essential cookies.
+- "Accept all" and "Reject all" buttons equally prominent.
+- Granular control must be available.
+- Pre-selected checkboxes for non-essential cookies = not valid consent.
+- Easy to withdraw consent (same ease as giving it).
+
+### Data subject rights implementation
+
+```ts
+// Data access request (must respond within 30 days)
+async function handleAccessRequest(userId: string) {
+  const userData = {
+    account: await db.user.findUnique({ where: { id: userId } }),
+    posts: await db.post.findMany({ where: { userId } }),
+    purchases: await db.order.findMany({ where: { userId } }),
+    consentHistory: await db.consentRecord.findMany({ where: { userId } }),
+    // Include all personal data you hold
+  };
+  return userData; // Send to user
+}
+
+// Deletion request (right to be forgotten)
+async function handleDeletionRequest(userId: string) {
+  // 1. Check if any legal obligation to retain (contracts, tax records — 7 years)
+  // 2. Anonymize or delete where no legal basis for retention
+  await db.user.update({
+    where: { id: userId },
+    data: {
+      email: `deleted-${userId}@deleted.invalid`,
+      name: "Deleted User",
+      phone: null,
+      deletedAt: new Date(),
+    },
+  });
+  // 3. Request deletion from third-party processors (analytics, email, CRM)
+  await analytics.deleteUser(userId);
+  await emailService.deleteContact(userId);
+}
+```
+
+## Data minimization
+
+Only collect what you actually use. Review forms — remove unnecessary fields.
+
+```ts
+// BAD: Collect everything
+const { name, email, phone, dob, address, employer, salary } = body;
+
+// GOOD: Collect only what you need for this service
+const { name, email } = body;
+```
+
+## Vendor management (Data Processing Agreements)
+
+Every vendor who processes personal data on your behalf needs a DPA.
+
+- Analytics (Mixpanel, Amplitude, PostHog)
+- Email (Mailchimp, SendGrid, Resend)
+- Cloud hosting (AWS, GCP, Vercel)
+- Support tools (Intercom, Zendesk)
+- Error tracking (Sentry)
+
+Most reputable vendors have standard DPAs (often in their terms or a self-serve portal).
+
+## Data breach response procedure
+
+```
+Hour 0-1: Identify and contain breach.
+Hour 1-4: Assess scope (what data, how many people, risk level).
+Hour 4-24: Internal notification chain. Legal counsel. DPO if you have one.
+Hour 24-72: Report to supervisory authority IF breach poses risk to individuals.
+           (In EU: your lead supervisory authority. UK ICO, CNIL France, BfDI Germany, etc.)
+Post-72h: If high risk to individuals: Notify affected individuals "without undue delay."
+```
+
+## Practical developer checklist
+
+- [ ] Privacy policy linked from all data collection points
+- [ ] Cookie consent before analytics/marketing cookies
+- [ ] Consent records stored with timestamp, version, IP
+- [ ] Access request process documented and tested
+- [ ] Deletion/anonymization process implemented
+- [ ] Data retention policy defined and enforced (auto-delete after X months)
+- [ ] All vendors have DPAs signed
+- [ ] Encryption at rest and in transit
+- [ ] Access controls and logging for personal data
+
+Sources: GDPR text (eur-lex.europa.eu — free), ICO guidance (ico.org.uk — free, best plain-language GDPR guides), EDPB guidelines (edpb.europa.eu — free)

package/skills/technical/launch-playbook/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-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.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+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/skills/technical/launch-playbook/SKILL.md

@@ -1,95 +1,95 @@
----
-watermark: ORIRO
-name: launch-playbook
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-
-
-
-  Product launch — pre-launch checklist, launch strategy, distribution channels, press, community, and post-launch iteration.
-
-
-
-
-
-
-
-
-  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
----
-
-# Product Launch
-
-## Pre-launch checklist (weeks before)
-
-### Technical
-
-- [ ] Performance: Core Web Vitals all green. Load test with expected traffic.
-- [ ] Monitoring: Error tracking (Sentry), uptime monitoring (Better Uptime, Checkly), logging.
-- [ ] Analytics: Events fire correctly. Conversion tracking verified.
-- [ ] SEO: Title tags, meta descriptions, OG images, sitemap submitted.
-- [ ] Email: SPF/DKIM/DMARC configured. Test all transactional emails.
-- [ ] Payments: End-to-end checkout tested. Webhook handling verified.
-- [ ] Auth: Login, signup, password reset all tested.
-- [ ] Mobile: Test on iOS Safari and Chrome Android specifically.
-- [ ] Error pages: 404, 500 pages are branded and helpful.
-- [ ] Security: HTTPS, security headers, rate limiting in place.
-- [ ] Backups: Database backups verified. Restore tested.
-
-### Business
-
-- [ ] Legal: Terms of Service, Privacy Policy live and linked.
-- [ ] Support: Customer support channel set up and staffed.
-- [ ] Billing: Pricing page live, billing portal works, receipts send.
-- [ ] Onboarding: First user experience tested with 5 real people who don't know the product.
-- [ ] Docs: Basic documentation or FAQ available.
-
-## Launch channels
-
-### ProductHunt
-
-**Prepare 2-4 weeks before:**
-
-- Schedule for Tuesday-Thursday (higher traffic).
-- Prepare: tagline, description, gallery (screenshots/video demo).
-- Video demo (60-90 seconds) significantly boosts launch performance.
-- Ask your network to support, but don't beg — authentic supporters only.
-- Be available to respond to comments all launch day.
-- Goal: Top 5 of the day for meaningful traffic.
-
-### Hacker News (Show HN)
-
-- "Show HN: [Product name] – [what it does in plain English]"
-- Post Tuesday-Thursday morning, 9-11am Eastern.
-- Don't self-promote in comments. Answer questions genuinely.
-- Technical audience. Be honest about limitations.
-
-### Twitter/X and LinkedIn
-
-- Build in public before launch. Share progress updates. Announce launch day.
-- Maker community: Tag relevant builders and communities.
-- LinkedIn for B2B products: Often higher engagement than expected.
-
-### Direct outreach
-
-- Beta users: Personal email. Ask for reviews, tweets, testimonials.
-- Industry journalists: 1:1 embargoed pitch 1-2 weeks before.
-- Relevant newsletters: Find 5-10 newsletters whose audience matches.
-- Communities (Reddit, Discord, Slack): Find relevant communities. Engage authentically BEFORE launch.
-
-## Launch day operations
-
-- All hands monitoring: Be in Slack/Discord. Watch dashboards.
-- Respond to every comment, message, support ticket quickly.
-- Fix critical bugs immediately. Have rollback plan ready.
-- Screenshot and save all social mentions.
-- Keep a running "issues" document.
-
-## Post-launch
-
-**Week 1:** Fix what's broken. Respond to every user. Gather feedback.
-**Month 1:** Identify the users who love it. Why? Build more of that.
-**Iteration:** "Build → Measure → Learn" cycle. Ship improvements every week.
-
-Sources: Gabriel Weinberg "Traction" (principles), ProductHunt launch guide (free), Hacker News community guidelines (free), First Round Capital launch resources
+---
+watermark: ORIRO
+name: launch-playbook
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+
+
+
+  Product launch — pre-launch checklist, launch strategy, distribution channels, press, community, and post-launch iteration.
+
+
+
+
+
+
+
+
+  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
+---
+
+# Product Launch
+
+## Pre-launch checklist (weeks before)
+
+### Technical
+
+- [ ] Performance: Core Web Vitals all green. Load test with expected traffic.
+- [ ] Monitoring: Error tracking (Sentry), uptime monitoring (Better Uptime, Checkly), logging.
+- [ ] Analytics: Events fire correctly. Conversion tracking verified.
+- [ ] SEO: Title tags, meta descriptions, OG images, sitemap submitted.
+- [ ] Email: SPF/DKIM/DMARC configured. Test all transactional emails.
+- [ ] Payments: End-to-end checkout tested. Webhook handling verified.
+- [ ] Auth: Login, signup, password reset all tested.
+- [ ] Mobile: Test on iOS Safari and Chrome Android specifically.
+- [ ] Error pages: 404, 500 pages are branded and helpful.
+- [ ] Security: HTTPS, security headers, rate limiting in place.
+- [ ] Backups: Database backups verified. Restore tested.
+
+### Business
+
+- [ ] Legal: Terms of Service, Privacy Policy live and linked.
+- [ ] Support: Customer support channel set up and staffed.
+- [ ] Billing: Pricing page live, billing portal works, receipts send.
+- [ ] Onboarding: First user experience tested with 5 real people who don't know the product.
+- [ ] Docs: Basic documentation or FAQ available.
+
+## Launch channels
+
+### ProductHunt
+
+**Prepare 2-4 weeks before:**
+
+- Schedule for Tuesday-Thursday (higher traffic).
+- Prepare: tagline, description, gallery (screenshots/video demo).
+- Video demo (60-90 seconds) significantly boosts launch performance.
+- Ask your network to support, but don't beg — authentic supporters only.
+- Be available to respond to comments all launch day.
+- Goal: Top 5 of the day for meaningful traffic.
+
+### Hacker News (Show HN)
+
+- "Show HN: [Product name] – [what it does in plain English]"
+- Post Tuesday-Thursday morning, 9-11am Eastern.
+- Don't self-promote in comments. Answer questions genuinely.
+- Technical audience. Be honest about limitations.
+
+### Twitter/X and LinkedIn
+
+- Build in public before launch. Share progress updates. Announce launch day.
+- Maker community: Tag relevant builders and communities.
+- LinkedIn for B2B products: Often higher engagement than expected.
+
+### Direct outreach
+
+- Beta users: Personal email. Ask for reviews, tweets, testimonials.
+- Industry journalists: 1:1 embargoed pitch 1-2 weeks before.
+- Relevant newsletters: Find 5-10 newsletters whose audience matches.
+- Communities (Reddit, Discord, Slack): Find relevant communities. Engage authentically BEFORE launch.
+
+## Launch day operations
+
+- All hands monitoring: Be in Slack/Discord. Watch dashboards.
+- Respond to every comment, message, support ticket quickly.
+- Fix critical bugs immediately. Have rollback plan ready.
+- Screenshot and save all social mentions.
+- Keep a running "issues" document.
+
+## Post-launch
+
+**Week 1:** Fix what's broken. Respond to every user. Gather feedback.
+**Month 1:** Identify the users who love it. Why? Build more of that.
+**Iteration:** "Build → Measure → Learn" cycle. Ship improvements every week.
+
+Sources: Gabriel Weinberg "Traction" (principles), ProductHunt launch guide (free), Hacker News community guidelines (free), First Round Capital launch resources

package/skills/technical/marketing-copy/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-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.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+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.