@oriro/orirocli 0.1.8 → 0.1.11

package/skills/technical/email-marketing/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/email-marketing/SKILL.md

@@ -1,128 +1,128 @@
----
-watermark: ORIRO
-name: email-marketing
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-
-
-  Email marketing and transactional email — deliverability, templates, automation, list management, and tools.
-
-
-
-
-
-
-
-
-
-  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
----
-
-# Email Marketing and Transactional Email
-
-## Deliverability foundations
-
-### DNS records (critical)
-
-```
-# SPF: Authorize mail servers
-TXT @ "v=spf1 include:sendgrid.net include:resend.com -all"
-
-# DKIM: Cryptographic signing
-TXT mail._domainkey "v=DKIM1; k=rsa; p=MIGfMA0GCSq..."
-
-# DMARC: Policy for handling failures
-TXT _dmarc "v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com"
-```
-
-Without SPF, DKIM, and DMARC: Emails land in spam. Gmail and Yahoo now require these.
-DMARC `p=reject` is the strictest (and most trustworthy). Start with `p=none` to monitor.
-
-### Sender reputation
-
-Warm up new IP/domain slowly. Start with 100 emails/day, double each week.
-Use dedicated domain for marketing (marketing.yourdomain.com) separate from transactional.
-Remove bounced and unsubscribed addresses immediately.
-Maintain list hygiene: Remove inactive subscribers every 6 months.
-
-## Transactional email (Resend, SendGrid, Postmark)
-
-### Resend implementation
-
-```ts
-import { Resend } from "resend";
-
-const resend = new Resend(process.env.RESEND_API_KEY);
-
-await resend.emails.send({
-  from: "ORIRO <noreply@oriro.ai>",
-  to: user.email,
-  subject: "Verify your email",
-  html: WelcomeEmailTemplate({ name: user.name, verifyUrl }),
-  // Plain text fallback
-  text: `Welcome ${user.name}! Verify your email: ${verifyUrl}`,
-});
-```
-
-### React Email (templates)
-
-```tsx
-import { Html, Head, Body, Container, Text, Button, Link } from "@react-email/components";
-
-export function WelcomeEmail({ name, verifyUrl }: { name: string; verifyUrl: string }) {
-  return (
-    <Html>
-      <Head />
-      <Body style={{ fontFamily: "Arial, sans-serif", backgroundColor: "#f9f9f9" }}>
-        <Container style={{ maxWidth: "600px", margin: "0 auto", padding: "20px" }}>
-          <Text style={{ fontSize: "24px", fontWeight: "bold" }}>Welcome, {name}!</Text>
-          <Text>Click below to verify your email address.</Text>
-          <Button
-            href={verifyUrl}
-            style={{
-              backgroundColor: "#3b82f6",
-              color: "white",
-              padding: "12px 24px",
-              borderRadius: "6px",
-            }}
-          >
-            Verify Email
-          </Button>
-        </Container>
-      </Body>
-    </Html>
-  );
-}
-```
-
-## Marketing email best practices
-
-### Subject lines
-
-**Opens are 70% decided by subject line.**
-Working formulas:
-
-- Question: "Are you making this mistake in your [area]?"
-- Curiosity gap: "This one change increased signups by 47%"
-- Personalization: "Hey [name], here's your weekly report"
-- Urgency (use sparingly): "Last 24 hours: [offer]"
-- Plain: "Quick update from [company]" (outperforms "clever" for many audiences)
-
-**A/B test subject lines.** Send to 20% of list, winner gets 80%.
-
-### Email structure
-
-**Mobile first:** 50-60% of email opens are mobile. Single column. Large text (16px+ body). Large CTAs (min 44px tap target).
-**One goal:** Each email has one CTA. Don't confuse with multiple asks.
-**Above the fold:** Preview text (shows in inbox after subject) should support the subject. First 40 characters matter most.
-**Preheader text:** Shows in inbox preview. Often ignored. Use it.
-
-### List management
-
-**Double opt-in:** Confirmation email before adding to list. Lower quantity, higher quality.
-**Unsubscribe:** One-click unsubscribe required (CAN-SPAM, GDPR, Google/Yahoo 2024 requirements).
-**Segmentation:** Send relevant content to relevant segments. Better open rates + lower unsubscribes.
-**Re-engagement:** After 6 months inactivity, send re-engagement campaign. Remove non-openers after another 30 days.
-
-Sources: Resend documentation (resend.com/docs — free), React Email documentation (react.email — free), Litmus email marketing research (free summaries), Really Good Emails (free inspiration)
+---
+watermark: ORIRO
+name: email-marketing
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+
+
+  Email marketing and transactional email — deliverability, templates, automation, list management, and tools.
+
+
+
+
+
+
+
+
+
+  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
+---
+
+# Email Marketing and Transactional Email
+
+## Deliverability foundations
+
+### DNS records (critical)
+
+```
+# SPF: Authorize mail servers
+TXT @ "v=spf1 include:sendgrid.net include:resend.com -all"
+
+# DKIM: Cryptographic signing
+TXT mail._domainkey "v=DKIM1; k=rsa; p=MIGfMA0GCSq..."
+
+# DMARC: Policy for handling failures
+TXT _dmarc "v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com"
+```
+
+Without SPF, DKIM, and DMARC: Emails land in spam. Gmail and Yahoo now require these.
+DMARC `p=reject` is the strictest (and most trustworthy). Start with `p=none` to monitor.
+
+### Sender reputation
+
+Warm up new IP/domain slowly. Start with 100 emails/day, double each week.
+Use dedicated domain for marketing (marketing.yourdomain.com) separate from transactional.
+Remove bounced and unsubscribed addresses immediately.
+Maintain list hygiene: Remove inactive subscribers every 6 months.
+
+## Transactional email (Resend, SendGrid, Postmark)
+
+### Resend implementation
+
+```ts
+import { Resend } from "resend";
+
+const resend = new Resend(process.env.RESEND_API_KEY);
+
+await resend.emails.send({
+  from: "ORIRO <noreply@oriro.ai>",
+  to: user.email,
+  subject: "Verify your email",
+  html: WelcomeEmailTemplate({ name: user.name, verifyUrl }),
+  // Plain text fallback
+  text: `Welcome ${user.name}! Verify your email: ${verifyUrl}`,
+});
+```
+
+### React Email (templates)
+
+```tsx
+import { Html, Head, Body, Container, Text, Button, Link } from "@react-email/components";
+
+export function WelcomeEmail({ name, verifyUrl }: { name: string; verifyUrl: string }) {
+  return (
+    <Html>
+      <Head />
+      <Body style={{ fontFamily: "Arial, sans-serif", backgroundColor: "#f9f9f9" }}>
+        <Container style={{ maxWidth: "600px", margin: "0 auto", padding: "20px" }}>
+          <Text style={{ fontSize: "24px", fontWeight: "bold" }}>Welcome, {name}!</Text>
+          <Text>Click below to verify your email address.</Text>
+          <Button
+            href={verifyUrl}
+            style={{
+              backgroundColor: "#3b82f6",
+              color: "white",
+              padding: "12px 24px",
+              borderRadius: "6px",
+            }}
+          >
+            Verify Email
+          </Button>
+        </Container>
+      </Body>
+    </Html>
+  );
+}
+```
+
+## Marketing email best practices
+
+### Subject lines
+
+**Opens are 70% decided by subject line.**
+Working formulas:
+
+- Question: "Are you making this mistake in your [area]?"
+- Curiosity gap: "This one change increased signups by 47%"
+- Personalization: "Hey [name], here's your weekly report"
+- Urgency (use sparingly): "Last 24 hours: [offer]"
+- Plain: "Quick update from [company]" (outperforms "clever" for many audiences)
+
+**A/B test subject lines.** Send to 20% of list, winner gets 80%.
+
+### Email structure
+
+**Mobile first:** 50-60% of email opens are mobile. Single column. Large text (16px+ body). Large CTAs (min 44px tap target).
+**One goal:** Each email has one CTA. Don't confuse with multiple asks.
+**Above the fold:** Preview text (shows in inbox after subject) should support the subject. First 40 characters matter most.
+**Preheader text:** Shows in inbox preview. Often ignored. Use it.
+
+### List management
+
+**Double opt-in:** Confirmation email before adding to list. Lower quantity, higher quality.
+**Unsubscribe:** One-click unsubscribe required (CAN-SPAM, GDPR, Google/Yahoo 2024 requirements).
+**Segmentation:** Send relevant content to relevant segments. Better open rates + lower unsubscribes.
+**Re-engagement:** After 6 months inactivity, send re-engagement campaign. Remove non-openers after another 30 days.
+
+Sources: Resend documentation (resend.com/docs — free), React Email documentation (react.email — free), Litmus email marketing research (free summaries), Really Good Emails (free inspiration)

package/skills/technical/fintech-builder/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/fintech-builder/SKILL.md

@@ -1,141 +1,141 @@
----
-watermark: ORIRO
-disable-model-invocation: true
-name: fintech-builder
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-
-
-
-
-
-  Fintech development — payment processing, KYC/AML, PCI DSS, banking APIs, financial data, and compliance for financial applications.
-  Sources: Stripe docs, Anthropic docs, Sanity/Contentful docs, industry-specific technical resources.
----
-
-# Fintech Development
-
-## Compliance fundamentals (US)
-
-### KYC (Know Your Customer)
-
-**Legal requirement for:** Banks, brokerages, money transmitters, crypto exchanges.
-**Requirements:** Verify identity (name, DOB, address, SSN/TIN or government ID).
-**CDD (Customer Due Diligence):** Understand nature of customer relationship, expected activity.
-**EDD (Enhanced Due Diligence):** Higher-risk customers (PEPs, high-risk countries, large transactions).
-
-### AML (Anti-Money Laundering)
-
-**SAR (Suspicious Activity Report):** File with FinCEN for suspicious transactions.
-**CTR (Currency Transaction Report):** File for cash transactions > $10,000.
-**OFAC screening:** Check customers against sanctions lists before onboarding. Stripe Identity, Persona, or Jumio handle this.
-
-### Money transmission licensing
-
-If moving money between parties, likely a Money Services Business (MSB).
-**FinCEN registration:** Required for MSBs.
-**State MTLs (Money Transmitter Licenses):** Required in most states. Each state is separate. 50-state rollout = 1-3 years.
-**Banking-as-a-service (BaaS) partner:** Use Unit.co, Increase, Column, Synapse to operate under a bank's charter while building.
-
-## Payment rails
-
-### Card payments (Stripe)
-
-```ts
-// Payment Intent for card payments
-const paymentIntent = await stripe.paymentIntents.create({
-  amount: 5000, // $50.00 in cents
-  currency: "usd",
-  automatic_payment_methods: { enabled: true },
-  capture_method: "automatic", // or 'manual' for auth + capture split
-  metadata: { orderId: order.id },
-});
-
-// Return client_secret to frontend for Stripe.js
-```
-
-### ACH transfers (US bank accounts)
-
-```ts
-// Stripe ACH (takes 2-5 business days)
-const paymentIntent = await stripe.paymentIntents.create({
-  amount: 100000, // $1,000.00
-  currency: "usd",
-  payment_method_types: ["us_bank_account"],
-  payment_method_options: {
-    us_bank_account: { financial_connections: { permissions: ["payment_method"] } },
-  },
-});
-// Returns link to Plaid verification flow
-```
-
-### Real-time payments
-
-**RTP (Real-Time Payments):** The Clearing House. Instant, 24/7.
-**FedNow:** Federal Reserve's instant payment network (launched 2023).
-Both require bank integration (directly or via BaaS partner).
-
-## PCI DSS compliance
-
-**Never handle raw card numbers** unless you have PCI DSS SAQ A-EP certification or higher.
-Use Stripe.js / Stripe Elements → card data goes directly to Stripe, never touches your servers.
-SAQ A: Redirect-only (Stripe Checkout). Simplest.
-SAQ A-EP: JavaScript on your page. Stripe.js.
-SAQ D: Full card data handled on your servers. Requires extensive audit.
-
-## Financial data patterns
-
-### Money storage
-
-```ts
-// ALWAYS store money as integers (cents/smallest unit)
-// NEVER use floating point for money (0.1 + 0.2 = 0.30000000000000004)
-
-const amount = 2999; // $29.99 in cents
-const formatted = (amount / 100).toLocaleString("en-US", {
-  style: "currency",
-  currency: "USD",
-}); // "$29.99"
-
-// For complex calculations: use `dinero.js` or keep in cents
-```
-
-### Double-entry bookkeeping
-
-```sql
--- Every financial transaction has equal debits and credits
--- Credits table tracks money flow
-CREATE TABLE journal_entries (
-  id         UUID NOT NULL,
-  account_id UUID NOT NULL REFERENCES accounts(id),
-  amount     BIGINT NOT NULL,     -- Positive = credit, negative = debit
-  currency   CHAR(3) NOT NULL,
-  created_at TIMESTAMPTZ DEFAULT now(),
-  entry_id   UUID NOT NULL        -- Groups related debits and credits
-);
--- Sum of amount for any entry_id must always = 0
-```
-
-## Open Banking / Plaid integration
-
-```ts
-import { PlaidApi, Configuration } from "plaid";
-
-const plaid = new PlaidApi(new Configuration({ basePath: PlaidEnvironments.sandbox }));
-
-// Create link token for user to connect bank
-const linkToken = await plaid.linkTokenCreate({
-  user: { client_user_id: userId },
-  client_name: "My App",
-  products: ["transactions", "auth"],
-  country_codes: ["US"],
-  language: "en",
-});
-
-// Exchange public_token (from Plaid Link) for access_token
-const { access_token } = await plaid.itemPublicTokenExchange({ public_token });
-// Store access_token securely; use to fetch transactions
-```
-
-Sources: Stripe documentation (stripe.com/docs — free), Plaid documentation (plaid.com/docs — free), FinCEN guidance (fincen.gov — free), FFIEC AML examination manual (free), Unit.co documentation (free)
+---
+watermark: ORIRO
+disable-model-invocation: true
+name: fintech-builder
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+
+
+
+
+
+  Fintech development — payment processing, KYC/AML, PCI DSS, banking APIs, financial data, and compliance for financial applications.
+  Sources: Stripe docs, Anthropic docs, Sanity/Contentful docs, industry-specific technical resources.
+---
+
+# Fintech Development
+
+## Compliance fundamentals (US)
+
+### KYC (Know Your Customer)
+
+**Legal requirement for:** Banks, brokerages, money transmitters, crypto exchanges.
+**Requirements:** Verify identity (name, DOB, address, SSN/TIN or government ID).
+**CDD (Customer Due Diligence):** Understand nature of customer relationship, expected activity.
+**EDD (Enhanced Due Diligence):** Higher-risk customers (PEPs, high-risk countries, large transactions).
+
+### AML (Anti-Money Laundering)
+
+**SAR (Suspicious Activity Report):** File with FinCEN for suspicious transactions.
+**CTR (Currency Transaction Report):** File for cash transactions > $10,000.
+**OFAC screening:** Check customers against sanctions lists before onboarding. Stripe Identity, Persona, or Jumio handle this.
+
+### Money transmission licensing
+
+If moving money between parties, likely a Money Services Business (MSB).
+**FinCEN registration:** Required for MSBs.
+**State MTLs (Money Transmitter Licenses):** Required in most states. Each state is separate. 50-state rollout = 1-3 years.
+**Banking-as-a-service (BaaS) partner:** Use Unit.co, Increase, Column, Synapse to operate under a bank's charter while building.
+
+## Payment rails
+
+### Card payments (Stripe)
+
+```ts
+// Payment Intent for card payments
+const paymentIntent = await stripe.paymentIntents.create({
+  amount: 5000, // $50.00 in cents
+  currency: "usd",
+  automatic_payment_methods: { enabled: true },
+  capture_method: "automatic", // or 'manual' for auth + capture split
+  metadata: { orderId: order.id },
+});
+
+// Return client_secret to frontend for Stripe.js
+```
+
+### ACH transfers (US bank accounts)
+
+```ts
+// Stripe ACH (takes 2-5 business days)
+const paymentIntent = await stripe.paymentIntents.create({
+  amount: 100000, // $1,000.00
+  currency: "usd",
+  payment_method_types: ["us_bank_account"],
+  payment_method_options: {
+    us_bank_account: { financial_connections: { permissions: ["payment_method"] } },
+  },
+});
+// Returns link to Plaid verification flow
+```
+
+### Real-time payments
+
+**RTP (Real-Time Payments):** The Clearing House. Instant, 24/7.
+**FedNow:** Federal Reserve's instant payment network (launched 2023).
+Both require bank integration (directly or via BaaS partner).
+
+## PCI DSS compliance
+
+**Never handle raw card numbers** unless you have PCI DSS SAQ A-EP certification or higher.
+Use Stripe.js / Stripe Elements → card data goes directly to Stripe, never touches your servers.
+SAQ A: Redirect-only (Stripe Checkout). Simplest.
+SAQ A-EP: JavaScript on your page. Stripe.js.
+SAQ D: Full card data handled on your servers. Requires extensive audit.
+
+## Financial data patterns
+
+### Money storage
+
+```ts
+// ALWAYS store money as integers (cents/smallest unit)
+// NEVER use floating point for money (0.1 + 0.2 = 0.30000000000000004)
+
+const amount = 2999; // $29.99 in cents
+const formatted = (amount / 100).toLocaleString("en-US", {
+  style: "currency",
+  currency: "USD",
+}); // "$29.99"
+
+// For complex calculations: use `dinero.js` or keep in cents
+```
+
+### Double-entry bookkeeping
+
+```sql
+-- Every financial transaction has equal debits and credits
+-- Credits table tracks money flow
+CREATE TABLE journal_entries (
+  id         UUID NOT NULL,
+  account_id UUID NOT NULL REFERENCES accounts(id),
+  amount     BIGINT NOT NULL,     -- Positive = credit, negative = debit
+  currency   CHAR(3) NOT NULL,
+  created_at TIMESTAMPTZ DEFAULT now(),
+  entry_id   UUID NOT NULL        -- Groups related debits and credits
+);
+-- Sum of amount for any entry_id must always = 0
+```
+
+## Open Banking / Plaid integration
+
+```ts
+import { PlaidApi, Configuration } from "plaid";
+
+const plaid = new PlaidApi(new Configuration({ basePath: PlaidEnvironments.sandbox }));
+
+// Create link token for user to connect bank
+const linkToken = await plaid.linkTokenCreate({
+  user: { client_user_id: userId },
+  client_name: "My App",
+  products: ["transactions", "auth"],
+  country_codes: ["US"],
+  language: "en",
+});
+
+// Exchange public_token (from Plaid Link) for access_token
+const { access_token } = await plaid.itemPublicTokenExchange({ public_token });
+// Store access_token securely; use to fetch transactions
+```
+
+Sources: Stripe documentation (stripe.com/docs — free), Plaid documentation (plaid.com/docs — free), FinCEN guidance (fincen.gov — free), FFIEC AML examination manual (free), Unit.co documentation (free)